BLANK TEMPLATE

PROJECT
Client or project:
Deliverable:
Updated:
Updated by:

START HERE
Next action:
Expected result of that action:
Stop and ask if:

CURRENT STATE
Current output and location:
Status: working / needs input / ready for review / blocked / accepted
What has actually been checked:
What remains unchecked:

DECISIONS
Approved decisions and who approved them:
Proposals that are still unapproved:
Exclusions that affect the next action:

MATERIAL TO READ
Current brief and location:
Supporting files needed for this task:
Conflicting or potentially stale sources:

OPEN QUESTIONS
Question:
Who can answer:
Task affected by the answer:

BOUNDARIES
Authorized work:
Actions requiring another decision:
Material outside this task:

BEFORE CHANGING ANYTHING
Confirm the current output, approved decisions and next action.
Identify missing files or conflicts. Do not silently resolve them.

WHEN FINISHED
State the output location, changes, checks and remaining questions.
Update this handoff to describe the new current state.

FILLED EXAMPLE — Northline is fictional. Paths and decisions are illustrative, not a live test.

PROJECT
Client or project: Northline website proposal
Deliverable: proposal for a five-page website
Updated: example date; replace with the real update date
Updated by: project owner in this fictional example

START HERE
Next action: check the Contact section for custom-booking promises.
Expected result: wording that follows the approved existing-booking-link scope.
Stop and ask if: the approved brief and decision record disagree.

CURRENT STATE
Current output: outputs/proposal-draft-v2.md
Status: ready for review
Checked: the outline names Home, About, Services, Service detail and Contact.
Unchecked: Contact booking wording; commercial terms; final owner approval.

DECISIONS
Approved: the project owner selected a link to the existing booking service.
Unapproved: no additional booking feature is approved.
Excluded: building an embedded booking flow.

MATERIAL TO READ
Current brief: inputs/approved-website-brief.md
Supporting files: decisions/booking-scope.md
Potentially stale source: earlier chat suggesting an embedded booking system.

OPEN QUESTIONS
Question: does the Contact section still promise a custom booking system?
Who can answer: the worker inspecting the draft can identify the wording;
the project owner accepts the revision.
Task affected: proposal review before client delivery.

BOUNDARIES
Authorized: inspect and prepare a wording revision for owner review.
Another decision required: commercial terms, new scope, client delivery.
Outside this task: Cedar's campaign materials and other client projects.

BEFORE CHANGING ANYTHING
Name the current draft, booking decision and intended revision.
Flag missing files or conflicting scope before continuing.

WHEN FINISHED
Report the revised output, the wording checked and remaining review items.
Keep the result unaccepted until the owner has reviewed it.

Instructions are workflow guidance, not technical access controls. Do not include secrets.