See the handoff.
Before you define the scope.
Explore six practical output structures. The examples are fictional demonstrations; the downloads are blank CSV templates you can adapt to your own workflow.
Administrative follow-up
A clear view of commitments, next actions and the decisions that need your attention.
| Task | Owner | Next action | Due / review | Status |
|---|---|---|---|---|
| Demo appointment | Client | Approve two suggested time slots | Agreed review date | Needs approval |
| Demo follow-up | Assistant | Prepare a reminder for review | Agreed review date | In progress |
Scroll horizontally to view all columns.
Responsibility to agree: Your team authorises scheduling rules, communication and access.
Choose another working example ↑Research handoff
Records carry their criteria, source reference and review status so your team can assess their usefulness.
| Record | Criteria | Source reference | Review status | Next action |
|---|---|---|---|---|
| Sample supplier A | Matches agreed region | Agreed public source | Needs verification | Check contact details |
| Sample supplier B | Service scope unclear | Agreed public source | Question raised | Confirm qualification |
Scroll horizontally to view all columns.
Responsibility to agree: Agree the sources, required fields and quality criteria before collecting information.
Choose another working example ↑Request and escalation log
Routine requests stay distinct from decisions that belong to your authorised team.
| Request | Category | Assigned owner | Next action | Escalation |
|---|---|---|---|---|
| Demo request 01 | Account query | Assistant | Gather approved account context | Client approval needed |
| Demo request 02 | Product question | Client specialist | Review technical question | Specialist review |
Scroll horizontally to view all columns.
Responsibility to agree: Product changes, account permissions and policy decisions remain with your business.
Choose another working example ↑Publishing coordination
A publishing plan makes the asset, approver and outstanding dependencies visible.
| Asset | Channel | Approver | Dependency | Status |
|---|---|---|---|---|
| Demo article | Company website | Client editor | Approve final copy | Awaiting approval |
| Demo update | Approved social channel | Client marketing lead | Confirm publishing slot | Ready for review |
Scroll horizontally to view all columns.
Responsibility to agree: Your specialists own creative direction, campaign decisions and final publishing approval.
Choose another working example ↑Order exception register
A consistent format helps internal teams see what happened and who needs to act.
| Reference | Exception | Responsible team | Next action | Approval status |
|---|---|---|---|---|
| Demo order 01 | Address clarification | Client operations | Request approved clarification | Pending |
| Demo order 02 | Refund request | Client finance | Review refund authority | Client decision |
Scroll horizontally to view all columns.
Responsibility to agree: Your team authorises refunds, pricing, payments and fulfilment decisions.
Choose another working example ↑Weekly progress update
Separate finished actions, open work and decisions so progress is easy to discuss.
| Work item | Owner | Progress | Dependency | Next review |
|---|---|---|---|---|
| Demo document pack | Assistant | Prepared for review | Client feedback | Agreed review date |
| Demo project milestone | Client lead | Waiting on decision | Confirm revised scope | Agreed review date |
Scroll horizontally to view all columns.
Responsibility to agree: Owners and review points are agreed together; this template is not a substitute for specialist project judgement.
Choose another working example ↑