Example workflow · Revenue and customer operations
Deal approvals
Complete deal approvals before the buyer deadline.
- Work covered
- Review a deal when the requested terms need extra approval.
- Owner
- Head of Deal Desk
- Human decision
- The Head of Deal Desk decides whether to approve, return, escalate, or decline the exception.
- Starting measure
- Approval wait
Follow one case from start to decision.
Use the map to correct the workflow, connect each step to a source record, and mark what is missing.
Example
Deal approvals
What this workflow covers: Review a deal when the requested terms need extra approval.
Your workflow map connects each step to its source records and marks missing information.
Starts with
A quote or contract request crosses a policy threshold.
Source systems
- CRM
- Quote system
- Contract repository
Review packet
Gather the requested terms, policy exception, account details, approval history, open dependencies, and buyer deadline under the deal ID.
Owner
Head of Deal Desk
Decision
The Head of Deal Desk decides whether to approve, return, escalate, or decline the exception.
Starting measure
Approval wait
Start with the current number. Compare after the change.
What the sources show—and what they do not.
The labels below separate what the source records show, what needs a person’s judgment, and what remains unknown until review.
- Seen in source records
- Directly visible in a record, interview, example, or system.
- Working assumption—confirm with the owner
- A reasonable explanation that still needs to be checked.
- Not yet known—confirm during review
- Missing information that we will not turn into a guess.
What we would check.
- How a request enters the approval process.
- Where terms, account details, and policy records are gathered.
- How other reviewers and dependencies add waiting time.
- Where the final decision and reason are recorded.
What stays with the accountable person.
- The review packet does not make the final decision.
- The named owner sees the source records before deciding.
- The decision stays logged to the case.
- The Head of Deal Desk makes the commercial decision.
Questions we need answered first.
Why this workflow may fit
The work repeats, the deadline is visible, and one person owns the commercial decision.
- Which deal ID stays consistent across the quote, contract, and approvals?
- Which thresholds reliably trigger a review?
- What is usually missing when a request reaches Deal Desk?
- Which decisions need finance, legal, or executive review?
The 3-Day Workflow Proof
Replace this example with work from your own team.
Bring 5–10 real examples and the rules a good employee follows. In three days, watch a working version handle the agreed test. If it fails, you owe nothing.