- Approve the commercial state—not merely a PDF—and connect every decision to a specific quote version.
- Reserve human review for thresholds, exceptions and judgment that exceed delegated authority.
- Recalculate and re-evaluate affected rules after a material revision; an old approval should not follow a changed quote automatically.
Define the decision before designing the approval
An approval is permission for a specific commercial state to move forward. The reviewer needs to know which customer, quote version, products or services, prices, costs, quantities, terms, delivery commitments and exceptions are being approved. A link to a document without those decision facts forces the approver to reconstruct the quote.
This approval stage belongs inside the complete sales quotation process. Intake must establish reliable requirements, and downstream delivery must release only the version that satisfied the decision path.
Write the decision as a question with an accountable owner: may this quote be released at these prices, scope and terms? If finance, technical delivery and commercial leadership answer different questions, model them as distinct decisions rather than one generic approval status.
Decision object
One identified quote version and the commercial values that can change its acceptability.
Authority
The role or group permitted to decide this type and size of exception.
Evidence
Calculations, source requirements, rule results, changes and rationale presented together.
Outcome
Approve, reject, request revision or escalate, with the reviewer and time recorded.
Choose approval triggers from real commercial policy
Interview the people who currently decide difficult quotes and review recent examples. Convert durable policy into explicit conditions, but keep judgment-based decisions visible as judgment. Do not pretend that every exception can be reduced to a threshold simply because software needs a field.
The examples below are categories, not recommended values. A business should set thresholds from its economics, risk appetite, contracts and delegated authority. Test combinations as well as individual fields because a standard discount and standard payment term may together create an unusual exposure.
Price and margin
Discount, floor-price deviation, cost coverage, contribution margin or missing cost evidence.
Scope and delivery
Custom work, unsupported configuration, accelerated schedule or a promise requiring operational confirmation.
Terms
Payment, warranty, cancellation, service, liability or other non-standard commercial conditions.
Value and risk
Deal size, credit, geography, data, contractual or customer-specific conditions outside normal authority.
Use the shortest approval path that preserves authority
A standard quote that satisfies approved rules should not wait for a ceremonial click. An exception should reach the smallest set of reviewers who can resolve it. Parallel review is appropriate when independent questions can be decided at the same time; sequential review is appropriate when a later decision depends on an earlier one.
Define absence and delegation. The workflow should know who may act when the normal reviewer is unavailable, how long to wait, when to escalate and which roles must never approve their own exception. A faster route is useful only when the substitute has the required authority and context.
Automatic proceed
All evaluated conditions are within delegated policy and no judgment-based exception exists.
Single approval
One authority can resolve the complete commercial question.
Parallel approval
Independent decisions can occur together, such as delivery feasibility and payment terms.
Sequential approval
One decision changes the evidence or authority required for the next.
Stop
A prohibited or unsupported condition prevents release unless the quote itself changes.
Give the reviewer a decision packet, not an inbox task
Show the quote summary, customer and opportunity context, requested exception, calculated impact, applicable policy, supporting evidence and the difference from the previous version. Separate internal notes from customer-facing content. Make the requested decision and consequences clear.
Human review works when evidence and authority arrive together. OpSmith's guide to human-in-the-loop automation explains why review depth should rise with uncertainty and consequence.
Record the rationale for non-standard decisions in structured language where practical. Free-text comments may still be necessary, but a durable category makes recurring exceptions measurable and can reveal where policy, pricing or intake needs improvement.
Reapprove the change—not necessarily the entire quote
A material revision creates a new commercial state. Recalculate affected prices, margin and other derived measures, then evaluate the approval rules again. Never carry approval forward solely because the customer name and document filename are unchanged.
Use a change comparison to determine which decisions are affected. A revised delivery date may require operations review without changing pricing approval. A quantity change may alter both price and authority threshold. Preserve the previous version, decisions and released status so the audit trail remains understandable.
Detect
Compare controlled fields and derived results between the approved and proposed versions.
Invalidate
Withdraw only the approvals whose underlying conditions materially changed.
Recalculate
Run affected formulas and policy checks using the new state.
Release
Make only the current fully approved version available for customer delivery or acceptance.
Plan for failed, late and uncertain approvals
An approval workflow can fail even when the pricing rules are correct. Notifications may not arrive, a reviewer may leave, the quote may change during review or a release action may time out without confirming whether the customer received it.
Use the workflow exception recovery runbook builder to define containment and a safe resume point. If release status is uncertain, reconcile the destination before retrying so the customer does not receive duplicate or conflicting quotes.
Set response targets as escalation signals, not automatic approvals. A timer can route or notify; it should not manufacture commercial authority.
Implement and measure one approval class
Start with one recurring exception such as a discount band, non-standard term or custom delivery commitment. Collect recent cases and compare the policy people describe with the decisions that were actually made. Resolve contradictions before encoding the rule.
Pilot by preparing approval packets and recommendations while reviewers retain control. Measure decision time, missing-context requests, revisions, overrides and incorrect routes. Review whether the workflow reduced waiting without increasing unauthorized or poorly understood commitments.
OpSmith's quote automation service connects intake, pricing preparation and governed approval into the existing sales operation. The Operational AI Blueprint can map the current decision path before implementation.
Frequently asked questions
Should every sales quote require approval?
Usually not. Quotes within explicit delegated policy can proceed without ceremonial review. Human approval should be reserved for exceptions, uncertainty or commitments that exceed the preparer's authority.
What should trigger quote approval?
Triggers can include price, margin, discount, deal value, scope, delivery, payment or service terms, risk and unsupported conditions. The correct thresholds come from the business's own policy and economics.
Can quote approvals run in parallel?
Yes when independent reviewers can decide without waiting for one another. Use sequential review when one decision changes the evidence or authority required for the next.
Does a revised quote need approval again?
Re-evaluate rules after every material revision. Only approvals whose underlying conditions remain unchanged should continue, and that relationship should be explicit rather than assumed.
Can an approval time out and become automatically approved?
That is generally a weak control for consequential commitments. A timeout should escalate, delegate under an approved authority rule or hold the quote—not create authority that no person or policy granted.