A default decision clause sets the outcome that takes effect when a client doesn't answer a decision request by an agreed deadline, so the engagement moves on to a known next step instead of waiting. The clause holds up best when it is agreed in the SOW at the start, used only for reversible choices, and backed by emails that repeat its wording. Below are the clause, three emails, and a decision log entry you can copy.
What is a default decision clause?
A default decision clause is a contract term that sets a predetermined outcome when one party fails to respond to a request for input or approval within an agreed time. In a consulting engagement, a default decision clause turns a silent client into a known next step instead of an open-ended wait.
Law Insider defines a default decision clause as one where, if a party doesn't provide input, approval, or objection in time, "a predetermined outcome or the other party's proposal is automatically accepted." Its decision by default entry gives the example of a change being deemed accepted or rejected if not approved within ten days. Most published samples come from banking and court procedure, so project teams need wording of their own. Sandra Julian suggests telling clients at onboarding that "silence on their end can mean you move forward with the initial recommendations."
When is a default decision fair to use?
A default decision is fair when the choice is reversible, inside the agreed scope and budget, and the client was told the default in writing before the deadline. A default is unfair, and risky, for anything that commits the client's money, legal position, or reputation, or that cannot be undone.
Use this test before you name a default:
- Reversible: Could the client change course later at a known, modest cost?
- In scope: Does the default stay inside the current SOW and budget?
- Recommended: Is the default the option your team would recommend anyway?
- Notified: Did the client receive the request, the default, and a final notice?
Keep these out of any default, and say so in the clause:
- Final acceptance of a deliverable or milestone that triggers payment
- Legal, regulatory, security, or compliance sign-off
- Any increase to scope, fees, or timeline beyond the clause itself
- Irreversible actions: go-live, launch, publication, data migration cutover, third-party purchases
For those, the default is to pause, not to proceed.
How do you pick and cost the default option?
Pick the default option as the one your team would recommend, written so the client can see what the default means for scope, cost, and timeline. If no option is safe to proceed on, the default is a pause with a day-for-day schedule shift, and the decision request should say what that pause costs.
For each decision request, write down:
- The options you put to the client, usually two or three.
- The default and why it is your recommendation.
- The impact of the default on deliverables, dates, and fees.
- The impact of a pause, if the client prefers to stop rather than accept the default.
- The reversal cost: what changing course after the default would take, in effort or change orders.
If the reversal cost is large, the decision probably belongs in the carve-out list. Clients accept a default more readily when the email shows you have thought about undoing it.
How long should the client have to respond?
A client should have a response window agreed at kickoff for each decision type. For routine approvals, the 48-hour approval rule gives a short window with a 24-hour reminder. For changes that need internal review, Law Insider's decision by default example uses ten days. Name the approver and write each window into the governance section.
The 24/48 rule is named in PM Resource Hub's decision escalation framework template. Panel of Tools describes the 48-hour approval rule for design studios: set the rule at kickoff, put the deadline in every approval email, send a 24-hour reminder, and document delays. Its stated consequence is that the next phase "will shift by the equivalent business days." Consulting SOW guidance from NMS Consulting also points to day-for-day extension language.
Read together as one pattern, the 24/48 routine runs like this:
- Send the decision request with the deadline and the default stated.
- Send the reminder at the 24-hour mark, repeating the default and the deadline.
- When the 48-hour window closes, apply the default or shift the affected dates day for day, and log it.
For decisions that need the client's internal review, use the ten-day deemed-acceptance example as a reference point and keep the same order: request, reminder, then default. Write your own figures into the clause as [agreed window] and [agreed period] rather than borrowing a number that doesn't fit the sponsor's approval path.
Ask the sponsor at kickoff: "Who signs off on [decision type], and how long does that usually take on your side?" Then write that answer into the governance section.
Unblockd sends asks to the sponsor with a first reminder after 3 days and another the day before the deadline.
What should the SOW clause say?
A default decision SOW clause should name the trigger, the approver, the response window, the final notice, the default outcome, the carve-outs, and the schedule and fee consequences. Each element should use the same words as your emails, so the client recognises the default mechanism when your team applies the clause.
Adapt this with your counsel:
Client Decisions and Default Outcomes. (a) Decision Requests. Where [Consultancy] needs a decision, review, or approval from Client to proceed, [Consultancy] will send a written Decision Request to Client's Named Approver, [role], at [email address]. Each Decision Request will state the options, [Consultancy]'s recommendation, the Default Outcome, and the Response Deadline. (b) Response Window. Client will respond by the Response Deadline, which will be no earlier than [agreed window] after the Decision Request is sent, unless the parties agree otherwise in writing. (c) Final Notice. If no response is received, [Consultancy] will send a Final Notice no later than [agreed period] before the Response Deadline. (d) Default Outcome. If Client does not respond by the Response Deadline, the Default Outcome stated in the Decision Request will take effect and [Consultancy] may proceed on that basis. Client may later request a different outcome through the Change Control process in Section [X]. (e) Excluded Decisions. Paragraph (d) does not apply to final acceptance of Deliverables, legal, regulatory, or security approvals, changes to Fees or Scope, or actions that cannot reasonably be reversed. For these, the Default Outcome is a pause of the affected work. (f) Schedule and Fees. Any period between the Response Deadline and Client's response will extend affected delivery dates on a day-for-day basis. Where a pause exceeds [agreed period], [Consultancy] may reassign staff and the parties will agree a revised schedule, and any [holding or remobilisation fee] set out in Section [Y] will apply.
Link paragraph (d) to your existing change control and acceptance clauses so a later change of mind is a change request, not a dispute.
What email do you send to the sponsor?
Send the sponsor three short emails for each default decision: the decision request, a final notice, and a confirmation once the default applies. Each email names the decision, the options, the default, and the deadline in the clause's own words, so the sponsor can answer quickly and nobody is surprised.
1. Decision request
Subject: Decision needed by [date]: [decision in a few words]
Hi [sponsor name],
We need your decision on [decision] to keep [deliverable] on track for [date].
Options: A. [option A], [impact on scope, cost, timeline] B. [option B], [impact on scope, cost, timeline]
We recommend [option], because [reason based on project evidence].
Under Section [X] of our SOW, if we have no decision by [time, date], we will proceed with [default option]. You can change course later through change control; that would mean [reversal cost].
A one-line reply with A or B is all we need.
[your name]
2. Final notice
Subject: Reminder: [decision] defaults to [option] on [date]
Hi [sponsor name],
A reminder that we need your decision on [decision] by [time, date]. Without a reply, we will proceed with [default option] as set out in Section [X]. If you need more time, tell us by then and we will pause [affected work] and shift [deliverable] day for day.
A one-line reply is all we need.
[your name]
3. Default applied
Subject: Proceeding with [option] on [decision]
Hi [sponsor name],
We didn't receive a decision on [decision] by [date], so we are proceeding with [default option] under Section [X]. [Deliverable] stays on track for [date]. If you would like a different direction, reply and we will raise a change request covering [reversal cost].
[your name]
Will a default decision clause hold up if the client disputes it?
A default decision clause is on firmer ground when both parties signed it before the decision arose and the client received written notice before the default applied. A default first raised in an email carries less weight, because the client never agreed to it upfront. Have counsel review the wording before it enters your standard SOW.
Law Insider's default by client samples show real service contracts that give the client written notice of default and a period to remedy it before a remedy such as suspension applies. The Final Notice in paragraph (c) follows the same order: notice first, consequence second. An email that introduces a default for the first time skips the agreed term and the notice step, so it gives you much less to point to.
Treat the clause, the notices, and your records as what carries the weight, rather than silence on its own. Have your counsel check the wording for your jurisdiction and contract type. Commercially, the bigger risk is the relationship: a default used on a sensitive choice can feel like a trap even if the clause stands. Keep defaults to the recommended, reversible option, and phone the sponsor before the deadline on anything that matters to them.
How do you record the outcome so it doesn't become a dispute?
Record every default as a decision in the project's decision log on the day the default takes effect, with links to the request, the final notice, and the confirmation. That record shows the client was asked, warned, and told, and the log entry ties any schedule shift or change request to a dated decision.
Copy this log entry:
Decision: [decision] Requested: [date] to [named approver], via [channel] Options offered: [A], [B] Recommendation and default: [option] Final notice sent: [date] Deadline: [date] Outcome: Default applied / Client decided [option] on [date] Impact: [deliverables, dates, fees affected] Evidence: [links to emails and SOW section]
Mention defaulted decisions in your next status report under a "Decisions this period" heading, so the sponsor sees them in context rather than discovering them at invoice time.
How do you roll out a default decision rule across every engagement?
To roll a default decision rule out across a portfolio, put one clause in the firm's standard SOW, one set of email templates in the delivery playbook, and one decision log format in every project. Then explain the rule to each client at kickoff so the default reads as shared governance.
Steps for a head of delivery:
- Agree the clause wording with counsel and add it to the SOW template.
- Add the three emails and the log entry to your delivery playbook.
- Add a kickoff agenda item: "How we make decisions together," covering named approvers, windows, and carve-outs.
- Ask leads to flag any default applied on a carve-out-adjacent decision for your review.
- Review defaulted decisions across engagements at your regular portfolio meeting, and talk to sponsors where defaults keep recurring.