Choose one deliverable and define its intended decision.
Agree what is included, excluded and dependent on client inputs.
Describe how the client will check and accept the result.
Keep a change request separate from the original scope.
WORKED EXAMPLE
What a useful result looks like
Fictional example: a consultant is asked to review a lead form. Scope: one form, its confirmation state and its notification handoff. Deliverables: an evidence table and prioritized recommendations. Excluded: redesigning the whole site, CRM migration and implementing changes. The client provides a staging link and a safe test recipient. Acceptance: each finding has reproduction steps and a source; the client confirms receipt of the agreed files. If the client adds a second site, record a new scope request and agree effort before doing it. The example includes no real client data or completed engagement.
Scope and compatibility
Delivery templates support scope and quality control. They are not legal contracts or a system for granting account access.
The files are editable Markdown and CSV. The optional original plugin contains one skill for Codex; its instructions can also be used in a regular AI chat. No accounts are connected automatically.
Want help applying it?
Adapt the delivery process to one of your services with Mark. Agree scope and price before implementation.