Sample report
Client Onboarding Document Kit — sample
Sample · Document Kit
The five documents, in full.
This is the whole kit, shown on the fictional agency Riverbend Creative. In a paid engagement these are rebuilt from your own SOW, your service list and two real examples of a project where scope went sideways — the engagement is the customization, not the download.
- $1,750 founding · $2,500 list
Or read what the engagement covers.
SAMPLE — Riverbend Creative is a fictional agency. All figures are illustrative and invented. This is not a client engagement, not a client result, and no client data appears in this document.
What is in the kit
Built from eight years of enterprise operations — the intake and change-control systems designed at Accenture and AARP.
01
Statement of Work
Deliverables with counts, revision rounds with a closing rule, and an explicit not-in-scope list.
- Deliverables table with a count and a definition of done on every row
- Revision rounds, and the sentence that closes one
- A not-in-scope list written as sentences, not categories
- Client-delay clause that moves every later date
- Acceptance: written, or deemed after five business days
02
Scope and exclusions sheet
One page, attached to every proposal. In scope, not in scope, and what the excluded items would cost.
- Two tables: in scope with limits, out of scope with prices
- The five questions that catch most scope creep
- The sentence to say out loud at kickoff
03
Kickoff agenda
Forty-five minutes, run the same way every time, sent before the call.
Read the scope out loud and ask “is that what you think you’re buying?”
- Name the one person whose written yes closes a round
- Walk the what-you-owe-me table line by line
- Written notes within two hours, and ask for a written yes
04
Handoff checklist
Run at every internal handover and at final delivery.
- Six internal checks — hours logged, out-of-scope flagged, round state, approved version
- Seven delivery checks — counts, formats, acceptance, credentials, ownership
- A 30-minute post-project review: quoted versus actual, and which exclusion failed
05
Change order
One page, signed before work starts. The document whose absence causes most write-offs.
- What is asked for, and which SOW line it falls outside
Hours table and cost
- What it does to the schedule, stated explicitly
- What happens if it is not approved
- The wording that makes it sound like service, not resistance
- The one that pays for the rest
Work added without a change order is the largest single cause of write-offs. The change-order page exists so that the answer to an out-of-scope request is never “that’s out of scope” — it is “happy to do that, let me put a quick change order together so you know exactly what it costs and what it does to the timeline.” Same outcome, and it reads as service rather than resistance.