Decide Which Quote Changes Need Fresh Internal Approval
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A quote is approved at one price, then the customer asks for a smaller deposit, free freight, and an earlier delivery date. Each request sounds manageable. Together, they may create an offer nobody approved.
Revised quotes need fresh internal approval when a change moves the offer outside its documented approval boundaries, changes an assumption behind the decision, or combines with earlier concessions to exceed a package-level limit. Corrections that leave commercial meaning unchanged can preserve approval. Negotiated changes can also preserve it, but only where the original approval explicitly allowed that flexibility.
The practical task is to define what approval covers, not simply to mark a document approved. The filled hypothetical matrix below shows how to make that distinction without sending every punctuation change back through management.
1. Anchor approval to an offer and a negotiation envelope
Approval should identify a specific quote revision and the conditions under which its commercial decision remains valid. An informal acknowledgement leaves room for interpretation: does it approve the displayed price, the margin, the payment timing, or any offer above a minimum value?
Record a compact approval baseline containing:
- The approved document: quote identifier, revision, date, and customer entity.
- The commercial package: scope, quantities, prices, discounts, included extras, and delivery commitments.
- The cash schedule: milestone amounts and the events that trigger them.
- The decision assumptions: cost estimate, capacity confirmation, availability, and customer dependencies.
- The permitted envelope: changes the negotiator may make without another commercial decision.
- The limits: cumulative concession allowance, minimum contribution or margin, and approval expiry or review conditions.
If the approval contains no permitted envelope, do not invent one during negotiation. Treat a substantive change as needing a decision until the commercial owner clarifies the boundary. That avoids turning silence into delegated discretion.
This is a recommended operating design, not a description of a software control. A controlled document and revision log can support it.
2. Use three revision outcomes, not a minor-change label
The size of an edit does not establish its effect. Replacing a delivery estimate with an unconditional commitment may change only a few words while materially changing the offer.
- Approval preserved—editorial: presentation or wording changes without changing meaning, amounts, commitments, timing, or scope.
- Approval preserved—within envelope: the commercial offer changes, but every applicable permission, assumption, and package-level limit still holds.
- Fresh approval required: a boundary is crossed, an important assumption is no longer supported, or the effect cannot be established confidently.
The second category matters. A discount within an approved range is not harmless; it is a concession already covered by an earlier decision. Keep evidence of the check even when no fresh approval is needed.
Classify the proposed revision before issuing it as approved. Requiring fresh approval means the existing internal decision does not cover the revised offer; it does not determine the legal status of anything already sent.
3. Filled hypothetical reapproval matrix
Fictional worked example: All identifiers, quantities, prices, costs, thresholds, roles, and revisions below are hypothetical. They illustrate a policy design, not universal limits or Alactic customer results.
Quote Q-214, revision 3, covers 100 equipment units at a list price of $1,000 each, with a 10% discount. Net revenue is $90,000. Estimated direct cost is $60,000, giving a contribution of $30,000 and a contribution margin of approximately 33.3%. Here, contribution means net revenue less the direct costs included in the approval calculation; contribution margin is contribution divided by net revenue.
Payment is 50% on order and 50% before dispatch. Delivery is estimated at six weeks after deposit receipt and specification confirmation. Freight is customer-paid.
The sales director has approved this negotiation envelope, with finance and operations confirming the relevant boundaries:
- Quantity may move between 90 and 110 identical units at approved unit pricing, provided operations reconfirms availability and the cost estimate remains applicable.
- The discount may increase to 12%, subject to all other limits.
- Company-funded freight may be added up to $1,500.
- Total discretionary concessions may not exceed $3,000 against the approved baseline for the same quantity.
- Contribution margin must remain at least 30% using current estimated direct costs.
- Payment milestones, delivery wording, and scope are not delegated for negotiation.
Each decision card records the proposed edit, outcome, reason, evidence, and escalation route. Reuse these fields when documenting a different quote or approval envelope.
Wording correction
- Proposed edit: correct a spelling error in the customer's street name; the customer entity and delivery destination remain unchanged.
- Outcome: approval preserved—editorial.
- Reason: no commercial meaning or delivery location changes.
- Evidence: record the corrected field and confirmation that the destination is unchanged.
- Escalation route: none for this correction. A different destination goes to the freight and delivery owners for review.
Quantity increase
- Proposed edit: increase from 100 to 105 identical units, keeping the 10% discount.
- Outcome: approval preserved—within envelope, after the required checks.
- Reason: 105 units is within the permitted range. Revenue becomes $94,500 and direct cost becomes $63,000 if the $600 unit cost remains applicable.
- Evidence: operations reconfirms availability; the cost owner confirms no additional batch or handling cost.
- Escalation route: a quantity outside the range, changed specification, or unsupported capacity goes to the commercial approver with operations' assessment.
Additional discount
- Proposed edit: increase the discount from 10% to 12% for the original 100 units, with no other concessions.
- Outcome: approval preserved—within envelope.
- Reason: revenue becomes $88,000, contribution $28,000, and margin approximately 31.8%. The additional concession is $2,000.
- Evidence: retain the calculation and confirm no earlier concessions are omitted.
- Escalation route: a discount above 12% goes to the commercial approver even if margin remains above its floor.
Payment milestone change
- Proposed edit: replace 50% on order and 50% before dispatch with 20% on order and 80% after delivery.
- Outcome: fresh approval required.
- Reason: the cash schedule is outside the envelope despite an unchanged headline price.
- Evidence: at the baseline $90,000 price, compare $45,000 on order and $45,000 before dispatch with $18,000 on order and $72,000 after delivery.
- Escalation route: finance reviews cash exposure; the commercial approver decides the package. This is internal commercial review, not legal evaluation.
Delivery commitment
- Proposed edit: replace the conditional six-week estimate with guaranteed delivery four weeks after order.
- Outcome: fresh approval required.
- Reason: timing, certainty, and the starting event all change.
- Evidence: include operations' feasibility assessment, dependencies, and additional cost.
- Escalation route: operations reviews feasibility; the commercial approver decides whether to accept the revised commitment.
Cumulative concessions
- Proposed edit: retain 100 units, increase the discount to 12%, and include $1,500 of company-funded freight.
- Outcome: fresh approval required.
- Reason: the $2,000 additional discount plus $1,500 freight totals $3,500, exceeding the $3,000 allowance. Each concession fits its individual limit; the combination does not.
- Evidence: revenue is $88,000 and direct cost including freight is $61,500. Contribution is $26,500, or approximately 30.1%.
- Escalation route: the commercial approver reviews the whole package. Passing the margin floor does not override the cumulative limit.
4. Compare every revision with the approved baseline
A common failure is comparing each draft only with the previous draft. The discount changes in one revision, freight in the next, and payment timing later. Every change looks small because the comparison keeps resetting.
Use two comparisons: the latest revision against its predecessor to explain what changed, and the latest revision against the last approved baseline to decide whether approval still applies.
For quantity changes, compare discretionary concessions at the revised quantity. Otherwise, a larger order can hide weaker unit economics behind a higher total value. In the hypothetical example, 105 units should use the approved 10% discount at 105 units as the price reference, not the original $90,000 total.
Maintain a concession ledger with the revision, changed term, estimated effect, and remaining allowance. Use consistent costing for monetary concessions. Keep separate checks for payment timing and delivery unless an evaluation method has explicitly been approved. Do not assign arbitrary dollar values merely to combine every risk into one total.
5. Separate hard boundaries from tradeable allowances
An envelope should distinguish concessions that can be traded from conditions that cannot. A negotiator might exchange some discount for company-funded freight within a combined allowance. Unused discount headroom does not automatically permit an earlier delivery commitment.
In the hypothetical matrix, the discount ceiling, cumulative allowance, and margin floor apply simultaneously. Payment timing and delivery wording need separate decisions. Passing one test does not cancel another.
This approach has a cost: an attractive package may still need escalation. The alternative—letting negotiators offset any change against any apparent benefit—requires broader judgement and produces less predictable decisions.
Keep the envelope narrow enough to understand but broad enough for recurring negotiations. Where the same exception repeatedly receives approval, review whether it deserves an explicit permission. Do not quietly turn repeated exceptions into policy.
6. Make the review packet smaller than the negotiation
A fresh approval request should explain the decision without making the reviewer reconstruct a message thread. Include:
- The approved baseline and proposed revision.
- All departures from that baseline, including concessions retained from earlier drafts.
- Updated revenue, relevant costs, contribution, cash milestones, and delivery dependencies.
- The boundary crossed or assumption needing confirmation.
- The requested decision and proposed negotiation fallback.
Record whether the decision approves only that revision or also establishes a new envelope. A one-off exception should not silently expand future discretion.
Distinguish functional input from the final commercial decision. Operations confirming feasibility does not approve a discount. Finance confirming a calculation does not necessarily approve a delivery promise.
7. Recover when an unapproved revision has been sent
If a revised quote went out beyond its approval boundary, first establish what was sent rather than overwriting the file.
- Preserve the issued revision and identify its recipients.
- Mark its internal approval status as unresolved and stop issuing further revisions as approved.
- Compare the sent offer with the last approved baseline.
- Escalate the complete package, including customer responses.
- Have the commercial owner decide the next communication and whether a corrected offer is needed.
Do not assume internal reapproval resolves every consequence of an external communication. Involve appropriate specialists where questions extend beyond the internal commercial decision.
Then fix the cause: an ambiguous envelope, omitted concession, outdated cost assumption, or changed commitment treated as proofreading. Adding a signature to every quote may create delay without addressing that cause.
8. Test the matrix before adopting it
For a hypothetical pilot, select ten recent revisions and ask two people to classify each independently. This is an illustrative sample, not a benchmark.
Record disagreements, missing assumptions, concessions that were difficult to reconstruct, and unclear decision ownership. Rewrite ambiguous rows before wider use.
In the next review cycle, track the share of sampled revisions with a traceable baseline and documented classification, plus the reasons for avoidable escalations. Look for fewer unexplained decisions, not simply fewer approvals. Start by giving one live quote an explicit envelope and testing its next revision against the whole approved package.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications