Choose the documents your project needs
- Discovery summary and requirements: objectives, users, current workflow, agreed needs, exclusions, dependencies, decisions, and unresolved questions, traced to supplied notes.
- Acceptance checklist: an agreed observable result for each requirement, a review method, evidence needed, and the person who accepts it. A checklist is not a claim that acceptance has occurred.
- Implementation handoff: deliverables, responsibilities, prerequisites, configuration decisions, dependencies, open issues, and the next owner for each action.
- Training and SOP documents: purpose, audience, numbered steps, expected results, exception paths, approval points, completion checks, and maintenance/version fields.
- Editable handover: the agreed documents, source and decision references, and a consolidated list of items that still need your team’s decision.
The fixed procedure packages include the SOP, a companion completion checklist, editable files, and the stated preference-revision allowance. The five walkthrough-built procedures package also includes an index. Broader requirements, handoffs, training packs, and documentation programs are quoted separately.
Existing procedure packages and custom project scope
The $79 USD source-ready package uses approved written source material totaling up to 2,500 words. It includes one SOP of up to four procedure pages, plus one completion checklist and one consolidated in-scope preference revision. It does not include a walkthrough or interview.
The $125 USD walkthrough-built package uses one supplied walkthrough of up to 20 minutes. It includes one SOP of up to six procedure pages, plus one completion checklist and one consolidated in-scope preference revision. The $399 USD five walkthrough-built procedures package uses supplied walkthroughs totaling up to 100 minutes and includes five SOPs of up to five procedure pages each, five completion checklists, an index, and one combined in-scope preference revision.
A consolidated preference revision is one collected request to adjust the delivered work within the accepted source material, process, audience, output structure, and package limits. New source material, a different process, added documents, or a changed purpose is new scope. Covered corrections under the 30-day corrections guarantee are separate and do not use the included preference revision.
Discovery synthesis, requirements, agreed approval checks, implementation handoffs, training packs, longer recordings, additional processes, and ongoing maintenance are custom work. We confirm the inputs, document list, depth, reviewer, delivery date, and price before starting.
Your process owner confirms policy, technical accuracy, and acceptance decisions. Documentation does not include implementation, system administration, formal acceptance sign-off, regulatory certification, legal advice, or safety validation. A live rollout, recorded training session, or migration needs a separate agreement.
You review and approve the finished work before paying. Final editable files follow confirmed payment. Payment takes place on a hosted Stripe invoice after approval; this website does not collect card details.
When this fits
A project has moved from discovery to delivery, but decisions and responsibilities are spread across notes. Or a recurring task still depends on someone explaining it each time.
- Give delivery teams an agreed set of needs and questions before implementation.
- Make the evidence required for acceptance explicit.
- Hand work from sales or discovery to delivery, and from delivery to operations, without hiding unresolved decisions.
- Turn an approved process into a procedure and quick checklist for the next person.
Useful inputs
- Authorized discovery notes, existing scope, decisions, walkthroughs or recordings, and relevant source documents.
- The intended readers, process owner, reviewer, system context, and agreed terminology.
- Known requirements, dependencies, exceptions, approved policies, and examples of a correct result.
- A person who can resolve conflicting accounts and confirm what counts as complete.
Describe the task and source volume first. Share redacted examples where possible and agree handling requirements before sharing project records.
How the documentation is developed
- Agree on the intended reader, source material, documents, and review responsibilities.
- Organize supplied evidence into requirements, steps, decisions, and open questions.
- Draft the documents with traceable references, consistent terms, and clear stop or approval points.
- Review with the named subject-matter owner; record decisions and incorporate the agreed feedback.
- Deliver the approved version, editable originals, and maintenance notes after confirmed payment.
Unknown requirements stay open until your reviewer confirms them. We do not invent a policy or silently turn an assumption into a commitment.
How the documents are checked
- Trace requirements and instructions to supplied material and approved decisions.
- Check roles, terminology, cross-references, sequence, and checks for completed work for consistency.
- Read through normal and exception paths with your reviewer; agree any safe practical trial separately.
- Keep unresolved questions, version status, and the responsible decision maker visible.
See the documentation approach
The shared-drive handover procedure turns published NARA guidance into eight steps, readiness checks, and source references. The editable document and review PDF are available. It is an independent public-source example; local owners must approve roles and policies before use.
Tell us what the next person needs to know
Tell us which task or handoff is unclear, who needs to use the result, and whether you have approved written material or a walkthrough. We’ll confirm whether a fixed procedure package or custom scope fits, then agree on the delivery date before starting.
Clear scope. Careful checks.