Delivery stage evidence
Every delivery stage says what evidence it owes and the document checklist answers. Two kinds of line can close a door, and only if you marked them.
The default: no gate at all
Delivery rules ship inert. A workspace that marked no line has no closed door, and its engagements move exactly as they did before. Everything in this guide means something only once you mark a line on an engagement's document checklist yourself.
Two marks, two behaviours
| Mark on the line | What it does |
|---|---|
| Required | The stage and the card say it has not arrived. The move is not refused. |
| Kind “contract” | Until every line of this kind has arrived, entering the contract stage is refused. |
| Kind “deliverable” | Until every line of this kind has arrived, entering the review stage is refused. |
What opens the door
The line arriving. When that line's document is received the move is free again; nothing else is needed. An outstanding line that is neither required nor of a kind never blocks. Moving back is never tied to the checklist.
The three compliance facts, signed contract, NDA and independence, are no longer typed; they are read off the documents that arrived.
An unknown kind is refused
Only kinds the server actually enforces can be put on a line. A misspelling is not stored, because a line the firm believes closes a door and does not is the worst case.
Read this next
- Contacts & engagementsCreate an engagementService, stage, lead and team — and where the title comes from on its own.
- Pipeline & opportunitiesMoving an opportunityOne step forward is free; a skip or a step back needs a note. An unfinished playbook and an unsent document never block a move.
- Pipeline & opportunitiesRecording what you sent the clientWhich document, to whom, on which day. The record has no edit and no delete; a correction is a new line.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.