Set bid escalation rules before the decision window closes

Purpose of escalation

Escalate the decision the owner cannot make

An escalation should identify what must change hands: permission to exceed a resource limit, a decision between incompatible technical positions, a resolution of competing priorities, or authority over a commitment. A general announcement that the bid is at risk gives the recipient no bounded decision. Keep ordinary corrections with the role already empowered to make them, unless their consequences or timing trigger another rule.

PM² Guide 3.1, section 9.8 and appendix B.4, distinguishes issue management from decision recording and calls for defined escalation procedures and thresholds. It considers category, urgency and impact. The method below adapts that project guidance into a bid rulebook rather than prescribing a particular management hierarchy.

The owner who discovers the problem remains responsible for progressing the referral until a defined receiver accepts it or the established alternative route takes over. Copying someone does not establish acceptance. The issue can have a coordinator and several required decision authorities; retain one coherent request so technical and commercial reviewers do not receive different versions of the same proposed change.

Define what stays local. A spelling correction with no change of meaning may fit the document owner’s mandate. A changed service promise does not become a spelling correction because only one digit changes. The test is the decision and its consequence, not the size of the edit or the seniority of the person who noticed it.

The rulebook should reference existing mandates and the responsibility matrix. It does not confer powers by itself. A newly approved rule can establish an internal operating procedure only to the extent that its approver has that authority; it cannot override a buyer instruction, a partner’s rights or a reserved corporate decision.

Materiality and urgency

Use consequence and time, not one colour or cost score

The Orange Book’s A4, A5 and C2 connect clear responsibilities with agreed triggers for rapid attention and timely escalation. Its D5 also asks that evidence limitations be considered. This is UK government risk guidance; the bid thresholds and timing rules here require approval within the bidder’s own context.

Write triggers in observable terms. Examples include a forecast that an approved cumulative resource limit will be exceeded, a required decision outside the current role’s delegation, a credible indication that mandatory evidence may not be available in time, or the remaining window becoming shorter than the decision route plus downstream work. Record the source, affected bid objects and uncertainty behind the trigger.

Materiality asks what the issue can change: eligibility, the offered obligation, evaluation, cost, delivery, confidentiality or submission validity. Urgency asks how long a useful intervention remains possible. A major contract position can need senior authority while allowing several days for review. A low-cost missing attachment can need immediate attention when it threatens the required submission. Do not average those dimensions into a reassuring middle score.

Some triggers should operate before the feared event occurs. A forecast breach is useful because the owner can still change course. A credible but incomplete indication can justify escalation with an explicit uncertainty label; waiting for a finished investigation can consume the decision window. That does not permit presenting a suspicion as an established fact.

For financial thresholds, state currency, gross or net basis, the relevant entity, aggregation period and whether the measure concerns committed, forecast or proposed exposure. Connected changes may cross a limit together even if each falls below it. Do not add mutually exclusive alternatives or count a superseded proposal twice. Unknown cost is not zero, and a qualitative authority trigger need not wait for a price estimate.

Receiving authority

The right recipient is the one who can decide this consequence

GovS 002, section 7.6, calls for escalation or reassignment when an owner cannot resolve a risk or issue. It also links risk beyond appetite or tolerance to authorization. The standard concerns government project delivery; it does not make a bidder’s nearest manager competent to approve every consequence.

Build the route from the requested action. A delivery authority may decide whether a service configuration is supportable. A commercial authority may decide its price treatment. A disclosure authority may permit use of a reference. The release role consumes those decisions but does not automatically replace them. Where several approvals are required, show the combination and the version they must all cover.

Name an alternate with a verified mandate, not merely someone likely to answer their phone. If only a governing body can decide, specify the permitted convening or referral route. A faster communication channel does not enlarge authority. Internal escalation to decide whether to ask the buyer a question also does not authorize that external contact or extend the buyer’s deadline.

Provide an exception route when the normal recipient is unavailable, lacks authority, has a conflict or is implicated in a suspected control failure. Use the established compliance or protected-reporting process where relevant; do not force a sensitive allegation through the person whose conduct is in question. The rule should restrict the audience to those needed for the decision and preserve evidence without broadcasting protected material.

Worked timing case

Dunmere’s ordinary response time is already too slow

Dunmere Controls is fictional. All times are on the same working day in the verified submission time zone, with the relevant roles available throughout the stated windows. The buyer deadline is 17:00. A separately checked plan requires 75 minutes of implementation and assembly after a usable decision, then 45 minutes of review, followed by 30 minutes reserved for submission and its contingency. Those intervals are sequential, non-overlapping and include the time allowances used in this example.

The remaining downstream path is 150 minutes. The latest useful decision time under this plan is therefore 14:30. This is a conditional planning result, not a guarantee of successful submission. If a decision adds rework or a review reveals a defect, the downstream estimate changes and the cutoff must be recalculated.

The ordinary decision route needs an allowed planning window of sixty minutes, so its latest activation is 13:30. The team discovers the issue at 13:40. Waiting until the ordinary response target of 14:40 would produce a planned finish of 17:10, ten minutes late. Immediate escalation after discovery is still late relative to this route’s useful window.

A separately authorized alternate can provide the same required decision through a thirty-minute route, assuming the necessary evidence and participants are available. Its latest activation is 14:00. The rule therefore directs the owner at 13:40 to request that route immediately, with acknowledgement due within five minutes. If no acknowledgement arrives by 13:45, the named contingency contact takes over under the agreed mandate; the decision cutoff remains 14:30.

At 13:45, a thirty-minute route would finish at 14:15, leaving fifteen minutes before the cutoff. Waiting until 14:05 to start that route would yield 14:35, five minutes too late. Neither calculation establishes that the alternate will decide favorably. The route may reject the proposal or require evidence that cannot arrive in time.

Clock semantics

An acknowledgement stops only the acknowledgement timer

Record detection time, rule activation, accepted receipt, target decision time and latest useful decision time separately. A reply saying received demonstrates contact, not the requested authority’s acceptance of the case or a substantive decision. An accepted referral should identify the receiving role, the decision sought and the promised response point. Keep the original issue identity when the case changes hands.

A generic one-business-day service target cannot overrule a cutoff this afternoon. Define the clock’s time zone, working calendar, start event and whether the stated duration covers triage, review or a decision. If the applicable route cannot fit, activate the permitted exception route early. Do not silently remove review time to make the arithmetic pass.

For several dependent approvals, import the actual decision path from scheduling. Some reviews can happen together; others must wait for a prior result. Adding every reviewer’s estimate can overstate the duration, while taking only the longest can understate it when decisions are sequential. The rule consumes a checked lead time and states its assumptions rather than rebuilding a full schedule inside an escalation cell.

A request for more information does not reset the buyer deadline. Record what is missing, who can obtain it and whether the recipient’s revised decision forecast remains useful. The owner may propose a new internal response target for authorized agreement, but must retain the original target and any breach. Changing the due field should not erase the fact that the escalation route failed its earlier commitment.

Fallback boundary

No answer must lead to a permitted action, never silent approval

The rule must say what the owner may do while awaiting a decision and at the cutoff. It might permit isolated internal analysis while prohibiting inclusion of an unsupported promise in the release candidate. It might reserve an affected branch for a release decision. These are specific controls with scope, owner and expiry, not a general permission to stop other teams or rewrite the offer.

If no usable decision arrives by Dunmere’s cutoff, the current plan cannot rely on that unresolved proposal. The authorized release process must decide the consequence for the affected candidate. Removing an optional claim, switching to an alternative or seeking buyer relief each requires its own eligibility and authority checks. An automation must not choose one merely because the timer expired.

A late decision can still be useful under a newly validated plan, but it cannot be backdated into the old one. Record the new downstream work and the separate authority for any changed path. A favorable answer with unmet conditions is not yet usable for the transition those conditions control. Do not stop monitoring simply because the decision field contains approve.

The GAO’s 2025 Green Book, principle 17, separates timely issue reporting, evaluation and documented corrective action. It allows different reporting routes for certain sensitive issues. This US federal control framework supports checking what happened after referral; it does not establish that an internal bid escalation has resolved the underlying problem.

Operational record

Preserve the route, its test and the evidence of handoff

Each rule needs an identifier, applicable scope, trigger evidence, severity criteria, current owner, decision request, receiving authority, alternate, clocks, permitted interim action and cutoff consequence. Add who approved the rule and when it must be revalidated. Test a normal case and the failure paths before relying on the arrangement during a submission window.

The individual escalation record then captures the observed trigger, source and artifact versions, requested options, actual contacts, acknowledgements, reassignment and decision reference. Keep protected evidence in its controlled location and share only what the recipient needs. A short decision packet can point to the complete evidence without duplicating sensitive material into an unrestricted message chain.

Close the referral according to its defined outcome, such as an accepted handoff or a usable authorized decision. Do not label the underlying issue resolved until the separate disposition and implementation checks support that state. Review missed triggers, unsuitable recipients and late acknowledgements to improve the rules. A low escalation count is not automatically success; it can mean issues remained hidden.

An assistant may assess authorized records against the rules, calculate candidate cutoffs and prepare a routing request. It must state uncertainty and preserve clock history. Sending messages, appointing alternates, accepting risk, changing approved scope, disclosing evidence, contacting the buyer or submitting the offer requires separate authorization. A detected trigger identifies a need for action; it does not grant the assistant permission to execute every possible response.