A research brief arrives on schedule. The consultant calls it complete. The client asks whether it answers the question they meant to ask.
Put the acceptance evidence beside the deliverable before writing it. Name the condition, the proof, and the person who evaluates it. Give disagreement a specific place to land.
Consulting deliverable acceptance criteria describe observable conditions for reviewing an agreed output. “Useful research” needs a narrower test. “Every recommendation identifies its supporting source and a stated limitation” gives the reviewer something to inspect.
Atlassian's acceptance criteria guide describes clear, testable conditions for completing work. The worksheet below adapts that idea to consulting documents. It proposes a review process, with fictional examples throughout.
Separate the work from the result being reviewed
Start with four different objects: activity, deliverable, business outcome, and acceptance condition. Write each on its own line before setting a deadline.
An activity is work performed. Reading source documents, interviewing permitted participants, and drafting diagrams are activities. A record of those activities can support delivery evidence.
A deliverable is the output being handed over. A research brief or process map has a version, a defined audience, and a purpose. Name that output precisely.
A business outcome is a change the organization wants. Better purchasing decisions or fewer workflow errors may motivate the engagement. Neither belongs in a document acceptance checklist as a guaranteed result.
An acceptance condition describes what the evaluator can check in the delivered output. For a research brief, that might mean tracing each recommendation to evidence or a labeled assumption.
Keep the wider engagement structure in the consulting statement of work. This worksheet adds item-level evidence. It does not supply contract clauses, payment terms, or implied acceptance rules.
Write conditions that another person can inspect
Use this sentence pattern: the named output contains or demonstrates a specified feature, checked through a named evidence location. Add the evaluator separately.
Replace “the brief is thorough” with “the brief addresses each approved research question in a labeled section.” The evaluator compares the question list with the section headings.
Replace “the map is clear” with “every decision node names the question and labels each outgoing branch.” The evaluator follows each branch against the diagram legend.
Do not turn a page count into a quality claim. A length limit can constrain a document, but it cannot establish sound reasoning or useful coverage.
For judgment-heavy conditions, state the decision the document must support. Ask the evaluator what evidence would make the analysis sufficient for that decision. Record remaining discretion openly.
Avoid a combined condition such as “accurate, complete, concise, and actionable.” Split it into separate rows. Otherwise a single rejected word can leave the entire review status unclear.
Work through a fictional research brief
Assume a fictional service team commissions a research brief about three possible documentation approaches. The approved purpose is to compare those approaches before choosing a small pilot.
The original request says: “Give us a useful recommendation with enough research.” Preserve that wording in the intake record. Then propose observable conditions for the client to confirm.
First, each of the three approaches receives the same comparison headings. Those headings cover intended use, prerequisites, evidence, limitations, and unanswered questions. The approved outline supplies the comparison test.
Second, every externally checkable assertion in the comparison points to a source and its checked date. Unknown information appears as unknown. An unsupported statement cannot become a fact through repetition.
Third, each recommendation identifies the research question it answers and the evidence behind it. When evidence is incomplete, the recommendation names the assumption and proposes a question for the pilot.
Fourth, the conclusion separates findings from the proposed next step. The document can recommend a pilot without claiming the pilot will deliver a business improvement.
Define the evidence locations before drafting. Use section identifiers for the comparison and recommendation table. If the final export changes pagination, update those locations before submitting it.
In this example, the client designates a research lead to evaluate coverage and a sponsor to record final acceptance. These roles are fictional assignments. Confirm equivalent authority in a real engagement.
Test the same method on a process map
A second fictional request says: “Map our request intake process so someone else can understand it.” The agreed boundary runs from receipt of a request to its assignment or rejection.
One proposed condition requires a visible start point and two named end states. Evidence is the diagram itself, including the legend. The evaluator traces the paths from start to finish.
Another requires each activity to name a responsible role. An unconfirmed responsibility appears in a separate open-question list. Do not invent an owner to make the diagram look finished.
A third condition requires decision branches for complete and incomplete requests. Both paths must identify the next step. A line ending without an explanation leaves that condition unresolved.
A fourth condition uses two fictional walkthroughs. One request has all required information; the other lacks it. The evaluator records the path each takes and any ambiguity found.
These walkthroughs test the diagram's internal explanation. They do not prove that staff follow the process or that the process works under actual operating conditions.
Agree on which questions may remain open at delivery. For example, an unknown backup owner may be an explicitly accepted exception. An unknown primary owner may block acceptance.
Put the conditions into an evidence worksheet
Create one worksheet per deliverable version. Add a stable condition identifier so revisions can refer to the same requirement without relying on page position.
| Field | Entry to record |
|---|---|
| Condition ID | Stable reference, such as BR-01 or MAP-02 |
| Condition | Observable requirement agreed before review |
| Evidence | File version, section, table row, or walkthrough result |
| Evaluator | Confirmed person responsible for checking this condition |
| Review date | Agreed date, including the time zone when relevant |
| Status | Not submitted, awaiting review, accepted, rejected, or blocked |
| Unresolved exception | Missing evidence, disputed interpretation, or accepted limitation |
These fictional rows come from the two separate worksheets. The dates are example review appointments, not delivery commitments.
| Condition | Evidence | Evaluator | Review date | Status | Unresolved exception |
|---|---|---|---|---|---|
| BR-01: Every approved question has a labeled answer section | Brief v1, coverage table | Research lead | 2026.11.04 | Awaiting review | None recorded |
| BR-02: Each recommendation identifies evidence and limitations | Brief v1, recommendation table | Research lead | 2026.11.04 | Rejected | Second recommendation lacks a limitation |
| MAP-01: Both intake outcomes have a labeled path | Map v1, branch walkthrough | Process evaluator | 2026.11.05 | Accepted | Acceptance applies to this condition only |
| MAP-02: Each activity identifies a confirmed primary role | Map v1, role list | Process evaluator | 2026.11.05 | Blocked | Client has not confirmed assignment authority |
Use “awaiting review” when nobody has evaluated the row. Use “blocked” when evaluation cannot proceed. Neither status communicates approval.
Keep completion and acceptance as separate records
Technical completion is the consultant's statement that the output is ready for review. Client acceptance is the authorized client's recorded judgment about that submitted version.
Keep both fields visible. A file can pass internal checks while client acceptance remains pending. A client can accept an exception without changing what the internal check found.
Agile Alliance describes acceptance tests as software behavior examples or usage scenarios, generally with pass-or-fail results. The walkthroughs above adapt that example-based approach. Client acceptance remains a separate decision in this proposed process.
Record the submitted version, the conditions evaluated, the evaluator, the decision, and the decision date. Preserve any limitation attached to the acceptance.
Silence never counts as approval in this proposed process. When the review date passes without a decision, leave acceptance pending and identify the unanswered request. Record any revised review date explicitly.
The consulting project management guide addresses the wider delivery workflow. Keep this worksheet focused on the evidence needed for one output's review.
Reject a condition with a specific revision request
A rejection needs a condition identifier, an observed gap, and the evidence supporting that finding. “This needs more work” gives the consultant no bounded revision target.
For BR-02, record: recommendation two cites a source but does not describe its limits. The requested revision adds the limitation and checks whether the recommendation still follows.
Assign the revision to a named owner and identify the version that will return for review. Keep the rejected result attached to v1. Evaluate the revision against v2.
If the request changes the approved condition, record the proposed change separately. Adding a fourth research approach changes the comparison boundary. It is not the same repair as filling a missing limitation.
Use the scope boundaries guide for the broader change discussion. The evidence worksheet records the difference between a failed condition and a newly requested condition.
Do not promise an organizational result to settle a document dispute. The consultant can revise the analysis and explain its limits. The client still owns decisions outside the agreed deliverable.
Preserve exceptions when the output is accepted
An exception needs its own description. Identify what remains unknown, why it remains open, who accepts that limitation, and which use of the deliverable it affects.
For the fictional process map, the client might accept the diagram with a missing backup role. Record that exception alongside the acceptance. Keep the primary role requirement intact.
If the client cannot accept the limitation, leave the relevant row unresolved. Name the missing decision or evidence. A delivery date does not supply missing knowledge.
Before closing review, compare the final file with the accepted worksheet version. Confirm that later edits did not change a condition already reviewed. Reopen affected conditions when the evidence changes.
Keep the file, worksheet, revision record, and acceptance together. A later reader should be able to identify exactly what was reviewed and which limitations survived.
Set the condition. Attach the evidence. Record the decision.
Sources
- Atlassian: acceptance criteria, for clear and testable conditions defined around an output.
- Agile Alliance: acceptance testing, for software behavior examples, usage scenarios, and pass-or-fail checks.