Required documents on deals
Define the paperwork a deal needs — per stage or for every deal — and choose whether a missing document merely nags or actually blocks the deal from advancing.
Some deals cannot responsibly move forward without paperwork: a signed contract before Closed Won, a compliance form before legal review. Document requirements let you write those rules down once and have every deal carry a checklist. Each requirement asks for a document with a specific tag — contract, proposal, and so on — and is met when a matching document is attached to the deal, or explicitly waived.
Two kinds of requirement
- Workspace policies, set in Settings → Requirements. A policy applies to every deal, or to deals in one pipeline stage. Only admins configure these.
- Per-deal requirements, added on a single deal for its particular paperwork. These are always reminders — they never block a stage move.
Setting up a policy
- 1Open Settings → Requirements and add a requirement.
- 2Give it a label and pick the document tag that satisfies it.
- 3Choose the scope: every deal, or deals in a specific pipeline stage.
- 4Choose the enforcement: Remind (the default) or Block.
The checklist on the deal
Every deal shows its requirements as a checklist in the deal panel. A requirement is met when a live document with the right tag is attached to it; deleting or archiving that document flips it back to unmet. From the checklist you can attach a document or waive a requirement that does not apply to this deal. Stage-scoped requirements appear once the deal reaches that stage.
Remind or Block: what actually happens
Enforcement is real, and it is your choice per requirement. A Block requirement genuinely stops the deal: moving it forward past the requirement’s stage — from the board or from the deal page — is rejected by the server with the list of missing documents. A Remind requirement never blocks anything; it shows as unmet on the checklist and turns up in the daily digest.
- Blocking applies only to forward moves within the same pipeline. Moving a deal backward, or to another pipeline, is never gated.
- Only workspace policies can block. Per-deal requirements are reminder-only.
- On the deal page, a blocked move opens a dialog listing what is missing, with a one-click Waive and move. On the board, the card snaps back with the error — open the deal to attach or waive.
A waive is a self-service override, recorded on the deal — there is no approval step. Blocking keeps the team honest; it is not a lock an admin has to come and open.
The digest nag
Your daily digest email includes a Missing documents section: each open deal with unmet requirements, and what it is missing, linked back to the deal. All unmet requirements appear there — Remind and Block, policy and per-deal — so nothing waits silently for someone to open the deal.
Spotted something out of date? Email hello@neokivo.com.