Process and QA

Delivery flow (high level)

1. Scope confirmation: pack selection, target framework(s), deadline, and constraints.
2. Intake: existing docs, tooling overview, owners, and the “what reviewers ask” context.
3. Build: tailor artefacts, assemble mappings and evidence prompts, write implementation notes.
4. QA: run the checklist, remove placeholders, verify mapping completeness.
5. Revision loop: minor revisions within the fixed artefact list.
6. Handover: editable docs + PDF export, plus a short handover call.

QA checklist (excerpt)

We run this on every delivery. The full checklist is longer, but the excerpt is enough to show the system.

• Every document has: owner, approver, version, effective date, and review cadence.
• Policy language matches the pack’s selected scope and your actual tools.
• Control mapping has no orphan controls and no orphan evidence items.
• Evidence prompts are specific enough to collect in the next 30 days.
• Implementation notes include common reviewer questions and pitfalls.
• Cross-references are consistent (IDs, titles, and links match).
• No placeholder text remains; all “TBD” removed.
• Exported formats: editable docs plus PDF set for reviewers.

Download the excerpt as PDF: QA checklist excerpt

Revision policy (clarity without defensiveness)

• Packs include the revision rounds stated on the pricing page.
• Minor revisions mean: wording, tailoring, and alignment inside the fixed artefact list.
• New frameworks, new artefacts, or expanded scope are handled as a scoped add-on.

Handling sensitive information

We do not require credentials. We only request what we need to tailor documentation. You can share documents using your preferred secure method. We can agree retention and deletion expectations during the call.

Download the delivery memo excerpt: Delivery memo excerpt