Pricing exception is a bounded administrative review for approval evidence. It exists to organize quote version, requested term, quantity, rationale, approval matrix, effective date, and revision history, not to make a commercial or policy decision. The work packet should identify the triggering event, the record identifier, the source order, the permitted update, and the person who owns an exception.
Pricing exception uses discount, quote, margin, and term as distinct control objects. Keep quantity separate from approval; record effective only when the source supports it, and route revision to the accountable pricing approver. A reviewer should be able to reconstruct the case from the governed record without relying on private chat context.
Define the approval evidence boundary
Start this pricing exception workflow when a new request, changed record, meeting event, or policy queue creates an item. The coordinator may collect quote version, requested term, quantity, rationale, approval matrix, effective date, and revision history and describe what the records show. The pricing approver decides questions of authority, ownership, customer meaning, and policy interpretation.
Use a passing case and a stopped case to teach the boundary. In a passing case, discount and quote have identifiable sources and the permitted action is administrative. In a stopped case, a request lacks a quote version, rationale, or required approver; preserve the governed value and write the unresolved question for the pricing approver.
Assemble a approval evidence packet
Open the packet with the received timestamp, record key, request wording, and source locations. For pricing exception, place quote version, requested term, quantity, rationale, approval matrix, effective date, and revision history in an order that lets the checker distinguish margin from term. Preserve original attachments or links instead of paraphrasing away the qualifying detail.
Arrange the quote revision, requested term, rationale, quantity, approval matrix, and effective date as separate checkpoints. A plausible discount is still unapproved without its route.
Run the pricing exception review
Compare quote revision and requested term with the approval matrix, then record the exact commercial field still needing authority.
The stop condition for this route is simple: a request lacks a quote version, rationale, or required approver. When it occurs, label the item blocked, preserve quantity, and send one focused question to the pricing approver. Do not close the queue item merely because a plausible answer is available from memory.
Control access and changes
Use the quote register for pricing intake; keep discount approval, terms, and customer-facing language with the pricing approver.
Capture the prior quote revision, requested term, approval source, reviewer, and pricing consequence before any exception change.
Sample and improve the queue
Sample one ordinary pricing exception case, one missing-source case, one conflict, and one handoff. A second checker should reproduce the result from discount, quote, and margin. Track whether disagreement came from a missing definition, an unavailable source, or an unauthorized request.
Review missing quote identity, rationale gaps, and approval conflicts separately; change the intake rule only after the pricing approver confirms the matrix.
Prepare the handoff
Pricing handoff: attach quote revision, requested term, rationale, approval route, and the unresolved commercial field.
For this pricing exception route, close accepted work by recording discount, quote, the rule version, and the reviewer. Close stopped work by retaining margin, naming the pricing approver, and dating the follow-up. This keeps approval evidence useful for audit and future procedure changes without turning term into an invented business conclusion.
Route-specific scenario: begin with discount and quote, then test whether margin is supported by the source before interpreting term. If quantity is missing, preserve approval and mark effective as unresolved. The pricing approver should receive the exact question, the relevant revision, and the proposed administrative next step. This sequence keeps pricing exception grounded in its own record rather than borrowing a conclusion from another queue.
Frequently asked questions
What does pricing exception verify?
It verifies quote version, requested term, quantity, rationale, approval matrix, effective date, and revision history. It does not authorize a policy conclusion beyond the written boundary for approval evidence.
What happens when approval evidence conflicts?
Preserve discount, quote, and margin as separate references, identify the missing decision, and route the conflict to the pricing approver.
Can a specialist approve the exception?
No. The specialist may organize quote version, requested term, quantity, rationale, approval matrix, effective date, and revision history and prepare a proposed administrative step; the pricing approver decides the exception.
How should this route be quality checked?
Sample a passing case and a stopped case, verify term, and inspect whether effective remained traceable to its source. Before handoff, reconcile quote revision with term, rationale, and approval route, flag missing commercial fields, and leave a dated authority question for pricing. The packet is ready only when intake has not implied approval. The pricing reviewer should preserve quote revision, requested term, and approval basis together so later negotiation does not imply a decision. For pricing intake, keep quote revision, discount term, quantity, rationale, approval matrix, and effective date discrete. See the CRM data hygiene guide for record controls and the remote sales support teams guide for delegated preparation. Microsoft’s opportunity management documentation is adjacent context, not evidence for this case. Contact SalesSupportStaff when the accountable owner needs help organizing the packet.
Related articles
Preserve Source Custody for Every Sales Lead
An evidence-led operating guide for lead source custody with clear ownership, exceptions, and review boundaries.
Sales OperationsControl Changes to Critical CRM Fields
An evidence-led operating guide for CRM field changes with clear ownership, exceptions, and review boundaries.
Sales OperationsBuild a Lead Routing Exception Queue
An evidence-led operating guide for lead routing with clear ownership, exceptions, and review boundaries.