Name each deliverable in ordinary language and explain what it contains, how it will be used and what review is included. Separate activities from handed-over artifacts. Specify format and important limits, then check that a client could recognize the completed item without needing your internal terminology.
Name what the client receives
Start with tangible items rather than a list of internal activities. “Stakeholder alignment” might mean a meeting, a decision record or a signed agreement, and those are different commitments. Describe the actual item you can hand over. If a meeting itself is part of the service, explain its purpose, participants and record. A client should be able to distinguish the time spent doing the work from the artifacts available after the engagement ends.
For each item, write one sentence explaining its use. An issue register may help an internal owner decide which documentation problems to address first. A sample page may demonstrate an agreed editorial structure. Avoid implying that a document makes the decision for the client or substitutes for specialist approval. Useful deliverables support a next task, and naming that task helps you omit attractive but unnecessary material from the scope.
Specify contents and working format
Describe the expected components of the artifact. A review report might contain the material examined, observed issues, supporting examples and unresolved questions. State whether recommendations are prioritized and what that priority means. If the client needs editable files, say which formats you can supply and check that their team can use them. A visually polished PDF can be unsuitable when the practical task is maintaining a shared working document after handover. Show a small labelled sample when the proposed format might otherwise remain unfamiliar.
Clarify whether underlying working material is included. Interview notes, source files and reusable templates may have different permissions or sensitivity from the final report. Do not assume that everything produced during an engagement can be shared automatically. Explain any dependency on a client-owned system or account. When the output contains examples or placeholder content, label them so they cannot be mistaken for verified operational information or approved instructions.
Agree what a review checks
Explain the review stage in terms of its purpose and scope. A factual review checks whether the report accurately describes supplied information. A design revision changes the presentation within an agreed direction. Neither necessarily includes a new round of research or a different strategy. Define how comments should be consolidated and who represents the client. Otherwise the same deliverable can attract incompatible requests from several people without a clear decision route.
Use completion criteria that can be checked against the brief: agreed sections included, required file formats provided, identified corrections addressed and remaining questions documented. Avoid subjective promises such as a deliverable being perfect or universally persuasive. Ask a potential reader to explain the handover back to you before publication. Any disagreement about whether they receive a recommendation, implementation or ongoing maintenance signals a description that needs another edit.
Fictional example: specifying a content-audit handover
A fictional content consultant, Pavel, initially lists “audit and strategic recommendations” as his deliverable. His revised description specifies a spreadsheet listing the agreed pages, an issue category for each, a short explanation of priority and a report describing recurring problems. The client receives editable files and a discussion of questions; raw access credentials and private interview notes are excluded from the handover.
Pavel includes one factual correction round based on consolidated comments from the client’s nominated owner. A request to write replacement copy would require separate agreement. A synthetic sample row shows what the spreadsheet looks like without borrowing client content. The final description makes the artifact inspectable while leaving implementation choices and their consequences with the appropriate client team.
A checklist for your next step
- List handed-over artifacts separately.
- Explain the use of each item.
- Name contents and editable formats.
- Clarify working-material access.
- State what the review checks.
Common questions
Is a workshop a deliverable?
It can be part of the agreed service. Specify the session and any record or materials supplied afterward.
Should I promise a page count for every report?
Use a page count only when it meaningfully defines scope. Required contents and agreed coverage may communicate more than length.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.