What Does a 30-Day Supplier Onboarding Compliance Plan Cover?

Onboarding is the gap between agreeing to work together and being able to work together, and it is where a surprising amount of value is lost. Most programmes treat it as an administrative phase to be got through, and most of the problems that surface in month six — a document that was never agreed, a contact who was never named, a specification nobody owns — are onboarding problems that were never finished rather than relationship problems that developed later.

Thirty days is the right length. Shorter and the specification work is rushed; longer and the momentum from the decision dissipates and the file goes cold. This piece sets out a four-week structure with a named output per week, the documents that change hands, who owns each step on the buyer side, and what "onboarded" means once the month is over.

What Is Onboarding For?

Three outcomes. Both sides can transact: entity, bank details, terms and document flow are settled. Both sides can build: the specification is signed, the inspection plan is agreed and a pilot has run. And both sides can govern: the scorecard, the communication protocol and the control addendum exist and have owners.

Those three map onto a simple test at the end of the month. Could the buyer place a second order without asking a single new question. If yes, onboarding worked. If no, something in the month was skipped, and the gap will show up as a delay on the second order rather than as a visible failure at the time.

What Happens in Week One?

Documents, contacts and identity. The entity record and bank details are exchanged and checked, the commercial terms are confirmed in writing, the document list for the programme is agreed, and an operating contact list is exchanged on both sides with role, channel and working hours. Four outputs, none of which requires a decision, all of which block everything else.

The contact list is the output most often skipped and the one with the highest daily return. Most first-year friction in a sourcing relationship is not disagreement; it is a message sent to somebody who does not own the question, and a day lost before it reaches somebody who does. A contact list agreed in week one removes that class of delay for the whole relationship.

What Happens in Week Two?

The specification and the inspection plan. The tech pack is finalised and signed off with a version and a date; the inspection standard, level and class list are agreed; the sampling and bulk windows are confirmed against the trigger events. Two outputs and they are the two that everything else depends on.

The defect class list deserves more attention than it usually gets, because it is the document that decides what a disagreement about quality is actually about. A generic list produces argument; a list written for the specific product, with examples of what counts as critical, major and minor on that construction, produces a verdict. Writing it in week two costs an afternoon and saves a week per lot.

What Happens in Week Three?

The pilot goes in. On this programme that means an order at MOQ 500 pcs per style and colourway, running on production tooling rather than through a sample room, with slot dates named for sampling and for goods-ready. The pilot is the first real transaction and it exercises everything agreed in the first two weeks.

The buyer side output for the week is not the goods; it is a record. Four artefacts should be collected when the pilot closes: a retained reference unit from the production run, the recorded parameter set, the inspection report with defect counts by class, and a written note of what would change at scale. Week three is not complete until all four exist.

What Happens in Week Four?

Governance. The scorecard is set up with its five dimensions, weights, bands and actions. The communication protocol is agreed and acknowledged. The control addendum is signed, covering the material lot rule, the recorded parameter set with a tolerance, the retained reference as the arbiter and written notice before substitution. And the retention rule for programme records is set.

The week should end with a short review meeting — thirty minutes is enough — at which both sides confirm the four governance documents and the specification is frozen. The freeze is the point of the month. A specification that keeps moving after onboarding is a specification nobody can build to consistently, and the end of week four is the last moment at which freezing it is easy.

Which Documents Change Hands in the First 30 Days?

Twelve, and listing them makes the month tractable: entity record, bank details, commercial terms, contact list, document list, signed tech pack, inspection plan, defect class list, the order for the pilot, the reference unit record, the parameter set, and the control addendum. Twelve documents in thirty days is a manageable pace and it is roughly one every two working days.

Each should be acknowledged rather than merely sent. An acknowledgement is a one-line reply and it converts a document from something transmitted into something agreed. Where a document sits unacknowledged, it is not part of the relationship yet, and the first disagreement will reveal that it never was.

A buyer-side output that is easy to forget and expensive to omit: the artwork and the marking. Logo files, label copy, carton marks and any regulated text have to be supplied early in week two, because they sit on the critical path for sampling and because a change to them later re-opens the sample approval. Where the buyer cannot supply them in week two, the month should be planned around that rather than discovering it in week three.

Who Owns Each Step on the Buyer Side?

Three people, in sequence. The commercial owner runs week one: entity, terms, contacts. The technical owner runs week two: specification and inspection plan. The programme owner runs weeks three and four: the pilot and the governance file. One owner per week, named at the start of the month rather than discovered as each week arrives.

Where a buyer is one person, all three roles are held by that person and the value of the split is lost — but the sequence still matters. Doing week one work in week three, or signing the specification before the contact list exists, produces rework regardless of how many people are involved. The sequence is the instrument; the headcount is not.

The twelve documents also have a natural order of difficulty. The first five are administrative and fast. Numbers six to eight — the tech pack, the inspection plan and the defect class list — are the ones that take real thought and the ones that decide whether the programme works. Numbers nine to eleven depend on the pilot running. The last one, the control addendum, is a single page and is the one most often left until later and then never written.

What Does "Onboarded" Mean, and How Is It Signed Off?

A single document, one page, listing the three outcomes and the twelve documents, with a date and two names. It is not a contract and it should not read like one; it is a shared statement that the relationship is operational. Producing it takes ten minutes and it is the artefact that makes the next conversation short.

It also creates a natural point for the first quarterly review. Onboarding closes on day thirty, the first quarter runs from there, and the first review has something to review. Without the closing document, the first review is a discussion about whether the relationship ever started.

What Should Be Frozen After Onboarding?

The specification, the inspection plan, the defect class list and the commercial terms. Those four are the foundation; everything else can move. Freezing them does not mean they can never change — it means a change requires a version increment and a written acknowledgement from both sides, rather than a message and a nod.

The freeze is also what makes a reorder a reorder. Where the specification has a version and the version is unchanged, the next order is a repeat and can be treated as one. Where the specification has drifted through informal changes, every order is a fresh negotiation and the programme never accumulates any of the efficiency it was supposed to.

One more output belongs in week four and is usually forgotten: the record retention rule. Which programme documents are kept, for how long, by whom and where. Set it while the folder is small and everything is still findable; setting it eighteen months later, when the folder holds several hundred files, is a job nobody volunteers for and the rule then never gets written at all.

What If the Month Slips?

Slip the freeze, not the sequence. A programme that reaches day forty with weeks one and two complete is fine and will recover; a programme that reaches day thirty with the specification signed but no contact list and no inspection plan will spend its first year fixing those gaps. The order matters more than the calendar, and the two things that must not be skipped are the defect class list and the control addendum.

Where a slip is caused by the buyer side — an artwork not supplied, an approval not given — record it. The weekly status note that the protocol establishes includes a line for what waits on the buyer, and that line is as useful in month one as it is in month twelve. Most onboarding slips are buyer-side and most buyer-side slips are invisible until somebody writes them down.

1. Entity record

Week one, commercial owner

2. Bank details

Week one, confirmed through a second channel

3. Commercial terms

Week one, matched to the quotation

4. Contact list

Week one, both sides, with role and channel

5. Document list

Week one, what arrives with each lot

6. Signed tech pack

Week two, with version and date

7. Inspection plan

Week two, standard, level, class list

8. Defect class list

Week two, written for the product

9. Pilot order

Week three, at MOQ 500 pcs per style and colourway

10. Reference unit record

Week three, retained by both sides

11. Parameter set

Week three, recorded as values with tolerances

12. Control addendum

Week four, lot rule, notice and arbiter

The commercial frame is what onboarding installs: MOQ 500 pcs per style and colourway, sampling 6-10 working days from a signed-off tech pack, bulk production 35-50 days from written sample approval, inspection at AQL 2.5 under ISO 2859-1 General Inspection Level II, T/T 30/70, quoted FOB Xiamen. By day thirty all six of those should be written down, agreed, and sitting in one folder.

There is one more buyer-side task in week two that pays for itself immediately: write the defect class list with the production side rather than for them. A list produced jointly, with examples both sides accept, produces a verdict at the inspection gate instead of an argument. A list produced alone and sent across is technically complete and practically useless, because the disagreement it was meant to prevent has simply moved to its contents.

The month also has a natural rhythm worth respecting. Weeks one and two are document-heavy and slow-moving, and it is tempting to compress them. Week three feels productive because an order is placed, and week four feels administrative and is the one most likely to be dropped. Week four is where the scorecard, the protocol and the control addendum are installed, and dropping it means the relationship starts without any instrument for managing it.

One closing observation. The programmes that onboard well are the ones where the buyer does their own work on schedule. Every day of buyer-side delay in week two is a day of production-side delay in week three, and the relationship then starts with a schedule slip that was not caused by production at all. Onboarding is the one phase where the buyer side controls almost all of the timeline.

Frequently Asked Questions

People Also Ask