From discovery to a usable handover

Procedures, requirements & handoffs

Important steps stuck in notes or someone’s head? Start with a $79 USD procedure based on approved written material, a $125 USD procedure based on a walkthrough you supply, or five walkthrough-built procedures for $399 USD. Receive clear steps, completion checklists, and editable files.

$79 USD
Source-ready procedureApproved written material up to 2,500 words · One SOP up to 4 pages + checklist · One consolidated preference revision
$125 USD
Walkthrough-built procedureOne supplied walkthrough up to 20 minutes · One SOP up to 6 pages + checklist · One consolidated preference revision
$399 USD
Five walkthrough-built proceduresSupplied walkthroughs up to 100 minutes total · Five SOPs up to 5 pages each + five checklists + index · One combined preference revision
Discuss process documentation

Confirm the scope and price first · Approve the finished work before paying

At a glance

Useful when
Your team is working from scattered notes, unclear requirements, or repeated verbal instructions.
What you receive
Fixed packages include a written procedure and completion checklist. Requirements, handover notes, and training material are separately quoted.
What we agree first
Choose a fixed procedure package or agree on the documents and price for a larger project.

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

  1. Agree on the intended reader, source material, documents, and review responsibilities.
  2. Organize supplied evidence into requirements, steps, decisions, and open questions.
  3. Draft the documents with traceable references, consistent terms, and clear stop or approval points.
  4. Review with the named subject-matter owner; record decisions and incorporate the agreed feedback.
  5. 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.

Read how to write a usable SOP.

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.

Ask about delivery documentation or procedures

Have a task in mind?

Start with the result you need.

Tell us what you need
Need help using this site?

New here? You do not need to know the service name. Tell us what you have now and what a useful finished result would look like.

  1. Start a short inquiry. A few sentences are enough, and no account or files are needed.
  2. Compare services, package prices, and quote options, or see complete public-source examples before you ask.
  3. Already working with Cleargrain? Use Client Login for private requests, files, messages, and project review.

Still unsure? Describe the result you need, including technical detail if useful. Larger spreadsheets and custom work are welcome; we’ll review the task before agreeing on the work and price.

What do the file types and technical terms mean?
PDF
A document you can read in a browser or PDF reader.
XLSX
An Excel workbook. Open it in a spreadsheet app to inspect the full example.
DOCX
An editable Word document. Open it in Word or another compatible document app.
CSV
A plain spreadsheet file. Open it in a spreadsheet app to see rows and columns.
TXT
A plain-text checklist or template. Open it in a text editor or copy its text.
SOP (standard operating procedure)
A step-by-step guide for a recurring task.
CRM (customer relationship management)
A system used to organize customer or contact records.
Workflow
The steps that move a task from start to finish.
Flat file
One table of rows and columns, with one header row.
Exception list
Records that need a decision or more information, with references to the original rows.
Source-ready procedure
A procedure written from approved material you already have, rather than from a supplied walkthrough.
Preference revision
One collected round of requested adjustments within the agreed work. Correcting work that fails the written scope is separate.
White-label support
Work prepared for your agency to review and present in its own branding.

To download a file, select its download link. It may open in your browser or appear in Downloads. If the browser asks, choose where to save it. Downloading an example does not place an order.