ILLUSTRATIVE ENGAGEMENT 02 / B2B WORKFLOW
Supplier Onboarding Portal
A near-final portal may work on screen and still fail across the supplier, buyer, compliance and administrator handovers that determine whether onboarding actually completes.
BUSINESS DECISION Release with conditions after correcting the exception route and clarifying who owns a rejected document.
The Workflow, Not the Interface, Is the Product
A hypothetical manufacturer is preparing to replace email-based supplier onboarding with a self-service portal. The release candidate includes supplier invitation, organisation setup, document upload, bank-detail review, compliance questions and buyer approval. Internal demonstrations look smooth because the demonstrator already knows the right sequence. Intended-use validation asks whether real users can complete the same chain without that hidden knowledge.
Illustrative Portal Scope
- Supplier invitation A named supplier contact has 72 hours to accept an invitation and establish organisation access.
- Evidence pack Six document categories may be requested, including insurance, quality certification, tax information and bank verification.
- Role controls Supplier contributor, supplier approver, buyer, compliance reviewer and portal administrator have different permissions.
- Exception logic Expired, missing or mismatched evidence must return to the right owner without deleting valid work.
- Completion state The portal should show whether the record is submitted, under review, returned for action or approved.
Note: The portal scope, figures and release decision are hypothetical and are included to demonstrate how the service could be applied.
Participant Field Built Around the Handover Chain
The sample is not a general group of software users. It is a linked field of people who create, receive, check, return and govern the supplier record. Participants are selected for real responsibility in supplier onboarding and for exposure to small-business constraints, multi-site structures, document expiry and approval exceptions.
12
supplier users
5
buyers
3
compliance reviewers
4
portal administrators
The Validation Is Delivered as a Relay
Instead of giving every participant the same isolated script, August Research runs a connected handover. One participant creates a record, another reviews it, a third returns an exception and the supplier resolves it. The evidence follows the record across roles.
Handover | Task challenge | Evidence captured |
|---|---|---|
Invite to supplier | Accept the invitation, assign the correct organisation and recover from an expired link. | Completion, time, incorrect account creation and support dependency |
Supplier to buyer | Upload six requested items and submit a record with one deliberately expired certificate. | Field errors, status understanding and ownership of the exception |
Buyer to compliance | Confirm commercial fields and route regulated evidence without overstepping permissions. | Permission failure, rework and handover clarity |
Compliance to supplier | Return one item with a clear reason while retaining approved information. | Message comprehension and recovery path |
Administrator to closure | Resolve duplicate organisation access and confirm the final audit trail. | Escalation quality and record integrity |
How the Data Is Triangulated
Screen and event logs establish what happened. A short online form captures clarity, effort and confidence immediately after each handover. Follow-up interviews identify why the user chose that route. Buyer, supplier, compliance and administrator accounts are then compared against the same record, so a role-specific preference is not mistaken for a workflow-wide acceptance failure.
Illustrative Handover Readout
The output is organised as a chain of completed and broken handovers, not a generic usability score.
Stage | Acceptance rule | Illustrative signal |
|---|---|---|
Invitation accepted | At least 11 of 12 suppliers enter the correct organisation without support. | 11 of 12 complete. One creates a duplicate account after the invitation expires. |
Evidence pack submitted | At least 10 of 12 suppliers submit all six categories and recognise the expired item. | 10 submit. Eight correctly identify who must replace the expired certificate. |
Returned item resolved | At least 9 of 12 suppliers correct the item without losing approved information. | 7 resolve independently. Five contact the buyer because ownership is unclear. |
Approval completed | All buyer and compliance users distinguish commercial approval from evidence approval. | 6 of 8 do so. Two attempt to approve outside their role. |
Audit trail located | All four administrators locate invitation, return and approval events. | 4 of 4 complete within the agreed time. |
Note: All counts and observations are illustrative. They show the proposed evidence format and are not findings from a real client project.
What the Client Would Receive
- Role-by-role acceptance protocol The permissions, tasks, data, assistance rules and consequences agreed before the first relay begins.
- Handover integrity map A visual record of where the supplier file passes cleanly, stalls, returns to the wrong role or loses context.
- Support-dependency register Every point where participants require email, phone or researcher intervention, linked to the root cause and owner.
- Exception-copy pack Prioritised revisions to status language, return reasons, ownership cues and recovery instructions.
- Release conditions A concise statement of what can go live, which supplier segments need assisted onboarding and what must be retested.
- Operational measurement plan Post-release measures for abandonment, returned documents, duplicate organisations, time to approval and support contacts.
Illustrative Project Delivery
A project of this scope might be delivered over approximately 5 to 7 weeks. The portal can be tested remotely with controlled accounts and scenario data, while a smaller number of sessions may be conducted in the supplier workplace where local records, connectivity or shared access materially affect use.
Delivery block | Method | Indicative duration |
|---|---|---|
Acceptance design | Working session with procurement, compliance, product and support owners | 1 week |
Participant recruitment | Screen linked user roles and prepare controlled portal records | 1 to 2 weeks |
Relay fieldwork | Run 6 linked record journeys across 24 participants | 2 weeks |
Triangulation | Compare logs, online forms, interviews and cross-role evidence | 1 week |
Decision close | Release-condition workshop and final output pack | 1 week |
Note: The timing is illustrative. Primary-research timelines are subjective and depend on participant response time, client access, portal stability, test-account preparation, supplier availability and the speed of internal review.
Let's Discuss Your Release Decision
If a B2B platform is nearly ready but success depends on several organisations completing one connected process, August Research can test the real handovers, expose hidden support and turn the evidence into practical release conditions.
Research Basis
Sources reviewed in framing: NIST, Common Industry Specification for Usability Requirements; NIST, Usability Testing; UK Government Service Manual, Writing User Stories and Quality Assurance: Testing Your Service Regularly. Accessed August 2026.
Note: This is a hypothetical illustrative engagement created to demonstrate Intended-Use Validation. It is not a client case study, and the numbers, findings, recommendation and timeline are not presented as actual outcomes.
