Keep the submitted version and the client's decision together.
Keep the deliverable version, client comments and acceptance decision together.
How to build your client deliverable acceptance
Describe the job
Keep the deliverable version, client comments and acceptance decision together.
Review the first version
Choose how the project coordinator records the Engagement reference and how the delivery lead reviews the next step.
Refine the views
Ask First to adjust the fields and views for the people who will use the app.
Test before sharing
Walk through the process with a sample record and check who owns the next action.
Follow Acceptance DA-045 through the handoffs.
This fictional client deliverable acceptance example shows the ordinary handoff and the decision that remains open.
Client deliverable acceptance example
- Record
- Acceptance DA-045
- Deliverable
- Operations handover pack
Current stage · Project lead
Submit the deliverable version
A fictional consultant submits an operations handover pack for client review.
Read the full walkthrough
Submit the deliverable version
A fictional consultant submits an operations handover pack for client review.
- Record:
- Acceptance DA-045
- Deliverable:
- Operations handover pack
Record the client's requested changes
The client requests a missing responsibility table on version 1.
- Record:
- Acceptance DA-045
- Initial version:
- 1
Submit a revised version
The project lead submits version 2 while preserving the version 1 review.
- Record:
- Acceptance DA-045
- Required change:
- Responsibility table
Record acceptance against the revision
The named client contact accepts version 2, leaving a later change outside that decision.
- Record:
- Acceptance DA-045
- Accepted version:
- 2
What to include in your client deliverable acceptance
Keep the Engagement reference in context
Keep Engagement reference, deliverable, version, review round, client approver, requested changes and acceptance state together so the next person can understand the request or record.
When the next step needs a decision
A sample consultant submits an operations handover pack for client review. The client requests a missing responsibility table on version 1.
Keep acceptance state visible
Record acceptance against the reviewed version and preserve outstanding changes.
Choose what each person needs
Give the project coordinator a working view and the delivery lead a review view. Keep Engagement reference and deliverable attached to the decision as the work moves between them.
Questions about client deliverable acceptance
Start with Engagement reference, deliverable, version, review round, client approver, requested changes and acceptance state. Describe who enters the information and who reviews the next step.
Try the workflow with your own process in mind.
Start with your workflow and make it yours.
Get started