A contract renewal should end in a clear decision.

But in many organizations, that decision is surprisingly vague.

A spreadsheet may contain:

Renew? Yes / No

An email may say:

We probably still need this.

A procurement manager may assume the business wants to continue.

Legal may prepare an amendment before the commercial strategy is fully settled.

That ambiguity creates risk.

A strong renewal process should convert all of the evidence collected during the renewal cycle into one explicit, traceable decision:

Renew, renegotiate, reduce, replace, extend, or terminate?

A dedicated Contract Renewal Tracker can structure that decision so the organization knows:

• what was decided;
• why;
• who owns the decision;
• what evidence supports it;
• what financial impact it creates;
• what workflow should happen next.

That is contract renewal decision management.

Why Renewal Decisions Need Structure

A renewal decision sits at the center of everything else.

Before it, the organization gathers:

• contract terms;
• usage;
• supplier performance;
• spend;
• risk;
• business need.

After it, the organization launches:

• negotiation;
• approval;
• replacement;
• termination;
• execution.

The decision is therefore the bridge between:

Analysis

and:

Action

If the decision itself is unclear, every downstream workflow becomes harder.

Still Using “Renew: Yes or No” as the Entire Decision Process?

Most contract renewals involve more options than simply keeping or cancelling a supplier.

Contract Renewal Tracker is designed to turn renewal decisions into structured, evidence-based choices that automatically trigger the correct commercial, legal, approval, and execution workflows.

Make every renewal decision explicit, explainable, and actionable →

The Six Core Renewal Decisions

A practical decision model can use six primary outcomes:

Renew

Continue substantially as-is.

Renegotiate

Continue with materially improved commercial or contractual terms.

Reduce

Continue but with lower quantity, scope, or service level.

Replace

Move to another supplier or internal solution.

Extend

Use a temporary bridge rather than a full renewal.

Terminate

End the relationship.

These options cover the majority of renewal scenarios.

Decision 1: Renew

Renew means the organization intends to continue the agreement substantially as it exists today.

This may still involve:

• minor pricing changes;
• administrative updates;
• normal approvals.

But there is no major change in business scope or supplier strategy.

When Renew Makes Sense

Typical conditions include:

• service still required;
• utilization healthy;
• supplier performance strong;
• pricing competitive;
• risk acceptable.

For example:

Annual value:

€120K.

Usage:

94%.

Supplier score:

91/100.

Price increase:

2%.

Recommendation:

Renew

This may be suitable for a streamlined workflow.

Renew Should Not Mean “Nobody Objected”

This distinction matters.

A passive outcome is:

We did nothing, so it renewed.

A managed outcome is:

We reviewed the business need and explicitly chose to renew.

Contract Renewal Tracker should distinguish the two.

Decision 2: Renegotiate

Renegotiate means the organization intends to keep the supplier or service but wants material changes before committing again.

Possible objectives include:

• lower pricing;
• improved payment terms;
• reduced escalation;
• better termination rights;
• stronger SLAs;
• shorter term.

This should trigger a procurement or commercial workflow.

Example Renegotiation Decision

Current:

€600K.

Supplier proposal:

€690K.

Supplier performance:

Strong.

Business need:

Critical.

Decision:

Renegotiate

Target:

≤€630K.

The organization wants the service but not at the proposed commercial position.

Renegotiate vs Renew

The distinction should be explicit.

Renew

means:

commercial position broadly acceptable.

Renegotiate

means:

continuation depends on improving terms.

This helps procurement prioritize work.

Decision 3: Reduce

Reduce means the organization intends to continue but buy less.

Possible reductions include:

• licenses;
• users;
• locations;
• service hours;
• support tiers;
• add-ons.

This is one of the most valuable renewal decisions.

Example Reduce Decision

Current licenses:

1,000.

Expected requirement:

Decision:

Reduce

Target renewal quantity:

This should feed directly into:

• negotiation;
• savings calculation;
• approval.

Reduction Should Be Quantified

Do not record only:

Reduce.

Record:

Current Quantity

1,000.

Target

Expected Annual Impact

−€150K.

This turns the decision into an executable instruction.

Decision 4: Replace

Replace means the organization intends to stop using the incumbent supplier and move to an alternative.

This is not the same as simple termination.

Replacement requires transition planning.

Replacement Decision Inputs

Before choosing Replace, evaluate:

• alternative identified;
• implementation time;
• migration cost;
• operational risk;
• notice deadline.

If replacement is unrealistic before renewal, a temporary extension may be necessary.

Example Replace Decision

Supplier score:

54/100.

Annual value:

€800K.

Alternative selected:

Yes.

Migration:

6 months.

Notice deadline:

8 months.

Decision:

Replace

This is actionable because sufficient runway exists.

Replacement Readiness

A useful status might be:

Not Started

Alternative Evaluation

Supplier Selected

Migration Planning

Ready

This helps determine whether termination timing is realistic.

Decision 5: Extend

Extend means the organization deliberately chooses a shorter bridge period rather than the supplier’s standard renewal term.

This is extremely useful when:

• replacement is underway;
• strategy is unresolved;
• migration needs more time;
• sourcing cannot finish before expiry.

Example Temporary Extension

Supplier proposes:

36 months.

Replacement project:

9 months from completion.

Decision:

Extend 12 Months Maximum

This preserves flexibility.

Extension Must Have a Purpose

A temporary extension should answer:

Why are we extending?

and:

What must happen before the new end date?

Otherwise bridge agreements can become permanent through repeated inertia.

Extension Exit Plan

For example:

Extension

6 months.

Reason

Complete migration.

Exit Milestone

Alternative platform live by March 1.

Owner

CIO.

This makes the extension a managed strategy.

Decision 6: Terminate

Terminate means the organization intends to end the contractual relationship without replacement inside the same renewal process.

Typical reasons include:

• service no longer required;
• duplicate capability;
• poor value;
• business closure.

This should immediately trigger a termination playbook.

Termination Decision Requires Evidence

For example:

Business Need:

No longer required.

Annual value:

€90K.

Dependencies:

None.

Notice deadline:

72 days.

Decision:

Terminate

Now legal and contract operations know what to do.

Termination Is Not Complete Until Notice Is Delivered

The decision:

Terminate

does not itself end the contract.

The system must still manage:

• notice verification;
• notice preparation;
• authorization;
• delivery;
• evidence.

This distinction should be explicit in the product.

Decision Status vs Execution Status

For example:

Renewal Decision

Terminate.

Execution Status

Notice Not Yet Sent.

This prevents false confidence.

Decision Evidence

Every renewal decision should be supported by appropriate evidence.

Possible evidence includes:

• business review;
• usage;
• supplier scorecard;
• pricing benchmark;
• risk assessment;
• budget.

The required evidence can vary by value and complexity.

Evidence-Based Decision Package

For a strategic contract:

Business Need

High.

Usage

92%.

Supplier Score

63/100.

Current Spend

€2.4M.

Supplier Proposal

€2.8M.

Price Benchmark

18% above median.

Replacement Feasibility

Medium.

Decision

Renegotiate.

This is much stronger than a standalone status field.

Decision Ownership

Someone must own the decision.

Possible roles:

Business Owner

Procurement

Executive Sponsor

The appropriate owner depends on the decision.

Business Owner Decision

The business owner is usually best placed to decide:

Do we still need the service?

But they may not have authority to approve:

€3M of spend.

Decision ownership and financial approval should remain separate.

Decision vs Approval

This distinction is critical.

Decision

We want to renew.

Approval

The organization authorizes the financial/legal commitment.

Both are needed for material contracts.

Decision Authority

Organizations can define who may select certain decisions.

For example:

Business owner can:

Renew / Reduce.

But:

Terminate strategic supplier

requires executive confirmation.

This adds proportional governance.

Decision Deadline

Every renewal should have an internal date by which strategy must be decided.

For example:

Notice deadline:

October 1.

Internal decision deadline:

August 15.

This leaves time for:

• negotiation;
• legal;
• approval.

Decision Readiness

The system can calculate:

Ready

if required evidence exists.

For example:

Business review complete.

Supplier score available.

Usage verified.

Then:

Decision Ready.

If information is missing:

Decision Incomplete.

Decision Readiness Checklist

For a strategic renewal:

• business need confirmed;
• usage reviewed;
• supplier performance reviewed;
• budget available;
• alternatives considered.

This prevents premature decisions.

Conditional Decisions

Sometimes the organization wants:

Renew only if certain terms are achieved.

This is different from a final unconditional decision.

Example Conditional Renewal

Decision:

Renew if annual value ≤€550K

Otherwise:

Escalate / Replace

This creates a commercial boundary.

Conditional Decision Rule

IF final_value <= 550000
THEN decision = RENEW
ELSE executive_review = REQUIRED

This connects decision logic with negotiation outcome.

Another Conditional Decision

Renew only if supplier closes critical security findings.

This ties renewal to remediation.

Conditional Decision Tracking

The system should show:

Decision

Conditional Renew.

Conditions

Satisfied

Outstanding

This prevents execution before conditions are met.

Decision Confidence

Some decisions are highly certain.

Others are tentative.

Possible statuses:

Confirmed

Provisional

Under Review

This is useful during long renewal cycles.

Provisional Decision

For example:

Likely:

Replace.

But final migration study pending.

The system can record:

Provisional Replace

without triggering termination immediately.

This preserves planning visibility.

Decision Confidence vs Forecast Probability

These are different concepts.

Decision confidence reflects:

How settled is the internal strategy?

Forecast probability might reflect:

What is likely to happen commercially?

Both can coexist.

Decision Reversals

Renewal strategy may change.

For example:

June:

Terminate.

July:

Replacement delayed.

August:

Extend.

The system should preserve this history.

Decision History

For example:

June 4:

Replace.

July 16:

Temporary Extension.

Reason:

Migration slipped 90 days.

This context matters during future reviews.

Require Reasons for Material Changes

A change from:

Terminate

to:

Renew

should not happen silently.

The system can require:

Reason

and possibly:

Reapproval

depending on value.

Decision Change Rule

IF decision_changed_after_approval = TRUE
THEN reapproval_required = TRUE

This protects governance.

Decision and Risk

Different decisions create different risk profiles.

For example:

Renew

Operational continuity high.

Replace

Transition risk increases.

Extend

Lock-in reduced but project pressure remains.

Terminate

Business continuity must be verified.

The risk engine should update accordingly.

Replacement Risk

If Replace selected but:

alternative not ready,

risk increases.

The system can show:

Replacement decision is confirmed, but migration completion date is after the notice deadline.

This is a serious issue.

Termination Risk

If Terminate selected but:

dependencies unknown,

the system should require:

Impact Review.

This prevents accidental operational disruption.

Reduce Risk

If quantity is cut too aggressively:

service shortage may result.

For example:

Forecast need:

Decision:

The system can flag:

Target quantity is below forecast demand.

This supports safer optimization.

Extend Risk

Repeated extensions can create strategic drift.

The system can flag:

This contract has received three consecutive temporary extensions.

That may require executive review.

Extension Limit Policy

For example:

Maximum:

2 temporary extensions

without executive approval.

This prevents indefinite postponement.

Decision and Financial Impact

Each outcome should show expected impact.

For example:

Renew

Expected spend:

€500K.

Reduce

€380K.

Replace

€350K + €100K migration.

Terminate

€0.

This helps business owners understand consequences.

Decision Scenario Comparison

For strategic contracts, compare options side-by-side.

This supports more informed decisions.

Multi-Year View

Annual cost alone may be misleading.

For example:

Renew 3 Years

€1.8M TCV.

Replace

€1.2M over 3 years + €250K migration.

Total:

€1.45M.

Potential difference:

€350K.

This improves decision quality.

Payback View

Replacement:

Migration cost:

€250K.

Annual saving:

€180K.

Payback:

approximately 17 months.

That may or may not fit strategy.

Decision and Budget

A decision should show:

Budget Impact

For example:

Renew:

+€80K over budget.

Reduce:

−€40K.

Replace:

Year 1 +€150K due to migration.

This gives finance useful context.

Decision and Supplier Performance

Supplier score can influence recommended options.

For example:

Score:

Recommendation:

Renew / Renegotiate.

Score:

Recommendation:

Replace / Terminate.

The score should inform—not dictate—the decision.

Decision and Business Value

Likewise:

High business value + poor supplier:

Replace.

Low business value + strong supplier:

Terminate may still be correct.

The decision must combine both dimensions.

Decision Matrix

A useful model:

This is a strong starting framework.

Add Commercial Competitiveness

A third dimension improves the model.

For example:

High Value.

High Performance.

Poor Pricing.

Recommendation:

Renegotiate

rather than simple renewal.

Add Dependency

High Value.

Poor Supplier.

High Dependency.

Immediate replacement may be unrealistic.

Recommendation:

Short-Term Renew + Remediation + Replacement Plan

This is more nuanced.

Decision Rules Can Assist, Not Replace Judgment

The system may generate:

Suggested Decision

based on policy and evidence.

But the authorized human remains responsible for the actual decision.

This is especially important for strategic contracts.

AI-Assisted Decision Recommendation

The assistant might say:

Based on 94% utilization, strong supplier performance, and pricing 18% above the internal benchmark, the evidence supports continued use but suggests renegotiation rather than renewal as-is.

That is useful and explainable.

Ask AI: What Are Our Options?

For example:

You have three realistic options:

1. Renew for 12 months at approximately €620K.
2. Reduce scope to €520K.
3. Replace, requiring approximately six months of migration and €180K one-time cost.

The user can compare tradeoffs.

Ask AI: Why Are You Recommending Reduce?

The assistant might answer:

Current utilization is 63%, the business forecast indicates no growth, and 140 licenses have not been used in six months. Reducing quantity appears lower risk than changing supplier.

This makes the recommendation transparent.

Ask AI: Why Not Terminate?

For example:

The service supports a critical month-end finance process and no replacement has been validated. Termination would create high operational risk.

This prevents simplistic optimization.

Ask AI: Why Extend Instead of Renew?

Replacement migration is expected to complete in eight months, while the supplier is proposing a 36-month renewal. A 12-month extension preserves continuity while avoiding unnecessary long-term lock-in.

This is an excellent decision-support use case.

AI Should Show Missing Information

For example:

I cannot reliably compare Renew vs Replace because replacement implementation cost has not been estimated.

This prompts the right next action.

Next-Best Evidence

The AI can recommend:

Obtain migration-cost estimate.

rather than pretending a final decision is possible.

This makes the assistant more useful.

Decision Workflow by Outcome

Once the decision is recorded, workflow changes automatically.

Renew

Approval → execution.

Renegotiate

Procurement negotiation.

Reduce

Demand confirmation → negotiation.

Replace

Sourcing / migration → termination.

Extend

Bridge negotiation.

Terminate

Termination workflow.

This is where structured decisions create operational value.

Decision-to-Workflow Routing

IF decision = RENEW
THEN start renewal_approval_workflow
IF decision = RENEGOTIATE
THEN start negotiation_workflow
IF decision = TERMINATE
THEN start termination_workflow

This turns strategy into action immediately.

Replacement Workflow

IF decision = REPLACE
THEN
  create sourcing_task
  create transition_plan
  create termination_readiness_check

This coordinates several workstreams.

Reduce Workflow

IF decision = REDUCE
THEN
  require target_quantity
  calculate expected_savings
  notify procurement

The decision becomes specific.

Extend Workflow

IF decision = EXTEND
THEN
  require extension_term
  require extension_reason
  require exit_plan

This prevents vague bridge decisions.

Decision Approvals

Some decisions may themselves require approval before execution.

For example:

Terminate Critical Supplier

Executive approval.

Replace Core Platform

CIO + Finance.

Renew €5M Contract

CFO.

The decision engine can route the appropriate approval.

Decision and Delegated Authority

A business owner may recommend:

Replace.

But the executive committee may have final authority.

The tracker should distinguish:

Recommended Decision

from:

Approved Decision

This provides clearer governance.

Recommended vs Approved Decision

For example:

Business Recommendation:

Terminate.

Procurement Recommendation:

Replace.

Executive Decision:

Extend 12 months.

The system should preserve each role’s input.

This is realistic for strategic contracts.

Multi-Stakeholder Decisions

Some decisions involve several functions.

Possible views:

Business

Procurement

Legal

Finance

Then:

Final decision owner.

This avoids forcing consensus into one opaque field.

Decision Disagreement

Suppose:

Business:

Renew.

Procurement:

Replace.

Risk:

Extend.

This should be visible.

The system can trigger:

Decision Alignment Meeting

rather than hiding disagreement.

Decision Alignment

A workflow might require:

all required functional recommendations

before:

executive decision.

This is appropriate for major contracts.

Decision Voting

For some committees, the platform may support:

• recommendations;
• votes.

But commercial governance should follow organizational policy rather than generic voting logic.

Decision Notes

Users should record concise rationale.

For example:

Renew for 24 months because migration economics are unattractive and supplier performance remains above SLA. Renegotiate escalation cap from 7% to ≤3%.

This becomes future institutional memory.

Decision Summary Template

A useful structure:

Decision

Rationale

Financial Impact

Primary Risk

Required Next Action

This is enough for most users.

Decision Audit Trail

The system should preserve:

• who proposed;
• who approved;
• when;
• evidence.

This makes the decision defensible.

Example Decision History

July 1:

Business recommends Reduce.

July 4:

Procurement validates.

July 8:

Finance confirms €120K annual impact.

July 10:

Decision approved.

This provides clean traceability.

Decision Expiry

Long-running renewals may require reconfirmation.

For example:

Decision made:

January.

Execution:

August.

If significant circumstances change, the system may request:

Decision Revalidation

This prevents stale commitments.

Trigger Decision Revalidation When

• price changes materially;
• supplier risk increases;
• business usage changes;
• strategic roadmap changes.

This makes the decision adaptive.

Example

Original decision:

Renew.

Then supplier suffers:

major security incident.

The system can reopen:

Renewal Decision Review

This is safer than blindly proceeding.

Material Change Rules

For example:

IF supplier_risk_change >= threshold
AND decision_status = APPROVED
THEN decision_revalidation_required = TRUE

This keeps governance current.

Decision KPIs

Useful metrics include:

Decision Coverage

Undecided Value

Average Time to Decision

Decision Reversal Rate

Renew / Reduce / Replace / Terminate Mix

Late Decision Rate

These show how effectively the organization makes renewal choices.

Undecided Value

This remains one of the strongest KPIs.

For example:

Upcoming 90-day renewal value:

€12M.

Undecided:

€2.2M.

Management knows where uncertainty sits.

Late Decision Rate

Formula:

Decisions Made After Internal Decision Deadline ÷ Total Decisions

For example:

14%.

Target:

<5%.

This is a useful leading indicator.

Decision Cycle Time

Measure:

Business Review Start → Final Decision

For example:

18 days.

This can be compared by:

• contract tier;
• business unit.

Decision Reversal Rate

If decisions frequently change:

• evidence may be arriving too late;
• decisions may happen prematurely.

For example:

20%.

This may warrant process redesign.

Decision Outcome Mix

Example:

Renew:

45%.

Renegotiate:

24%.

Reduce:

14%.

Replace:

5%.

Extend:

4%.

Terminate:

8%.

This gives leadership insight into renewal behavior.

Passive Renewal Rate

A particularly useful metric:

Percentage of contracts renewed without an explicit recorded decision.

Target:

0% for material contracts.

This directly measures governance maturity.

Savings by Decision Type

For example:

Reduce:

€800K.

Terminate:

€620K.

Renegotiate:

€1.2M.

Replace:

€450K net annual benefit.

This shows where financial value is created.

Risk by Decision Type

Replace decisions may have:

higher transition risk.

Renew decisions:

higher lock-in risk.

The dashboard can show these patterns.

Decision Quality Analysis

Over time, the system may evaluate whether past decisions performed as expected.

For example:

Renew decisions later associated with:

• poor supplier performance;
• unexpected spend.

This can create feedback for future decisions.

Post-Renewal Decision Review

For major contracts:

6–12 months later, ask:

Did the decision deliver the expected outcome?

This helps improve the decision model.

Example

Decision:

Reduce to 700 licenses.

Actual need:

Good forecast.

Another:

Reduce to 500.

Emergency purchase later:

200 additional.

Decision underestimated demand.

These lessons can improve future reviews.

Decision Learning

The system can learn:

• which evidence predicts good outcomes;
• where forecasts are weak.

Again, AI should assist rather than autonomously govern.

AI Decision Evaluation

A future AI model could compare:

current decision context

with:

historically similar renewals.

For example:

Similar contracts with utilization below 50% and strong alternatives resulted in reduction or termination in 72% of prior cases.

This is useful context.

Historical Similarity Should Be Transparent

The assistant should say:

based on:

12 comparable contracts.

This helps the user judge relevance.

Do Not Turn Historical Patterns into Automatic Policy

Prior decisions can inform.

They should not automatically dictate new decisions.

Contract context remains unique.

Decision Management for Small Businesses

The workflow can remain simple:

Keep

Reduce

Cancel

For many smaller customers, that may be enough.

The product does not need to expose enterprise complexity everywhere.

Mid-Market Decision Model

Add:

• renegotiate;
• replace;
• extend.

This supports more mature procurement.

Enterprise Decision Model

Add:

• multi-stakeholder recommendations;
• conditional decisions;
• formal approvals;
• revalidation.

The platform scales with customer complexity.

Decision Management and User Experience

The decision screen should summarize:

What do we know?

Then:

What are your options?

Then:

What happens next?

This keeps the product intuitive.

Example Decision Screen

AnalyticsPro

Annual Spend:

€500K.

Utilization:

61%.

Supplier Score:

Supplier Proposal:

+9%.

Internal Overlap:

Yes.

Select Strategy

• Renew
• Renegotiate
• Reduce
• Replace
• Extend
• Terminate

Each choice can show its expected consequence.

Decision Preview

Before selecting Terminate:

This will create a legal notice workflow and requires notice by September 1.

Before Replace:

This will create sourcing and transition tasks.

This makes decisions more concrete.

Decision Simulation

A future feature could show:

If you choose Reduce, expected annual spend is approximately €380K.

If you choose Renew As-Is, expected spend is €545K.

This helps users understand financial impact.

Decision Governance Without Bureaucracy

Low-risk decisions should remain fast.

High-risk decisions should receive more scrutiny.

The platform should automatically determine how much governance is required.

That is the essence of scalable renewal decision management.

Contract Renewal Tracker as a Decision Platform

This is a major product evolution.

A reminder tool asks:

When does the contract renew?

A workflow tool asks:

What needs to happen?

A decision platform asks:

What should we actually do with this contract—and why?

That is much closer to the core business problem.

From Evidence to Decision to Action

The full model becomes:

Contract Terms

Usage

Supplier Performance

Financial Data

Risk

↓

Decision

↓

Workflow

↓

Approval

↓

Execution

This is the renewal operating system.

Ready to Replace “Renew: Yes/No” with a Real Decision Process?

Contract renewals deserve more than a checkbox.

Contract Renewal Tracker is designed to help organizations turn renewal evidence into explicit, governed decisions that immediately drive the right next workflow.

Use Contract Renewal Tracker to:

• structure renew/renegotiate/reduce/replace/extend/terminate decisions;
• define decision deadlines;
• assign decision ownership;
• attach supporting evidence;
• quantify financial impact;
• manage conditional decisions;
• track decision confidence;
• preserve decision reversals;
• trigger the correct downstream workflow;
• require approvals for material decisions;
• revalidate decisions when circumstances change;
• measure decision KPIs;
• use AI to explain options and recommend next-best actions.

The objective is to move from:

“We think we’re probably renewing.”

to:

“We have reviewed the evidence, selected a strategy, recorded why, quantified the impact, and the correct workflow has already started.”

Start Your Contract Renewal Tracker Subscription →

Final Thoughts

The renewal decision is the pivot point of the entire process.

Before it:

the organization gathers evidence.

After it:

the organization acts.

The model is:

Understand

↓

Choose

↓

Authorize

↓

Execute

A well-designed Contract Renewal Tracker should make that choice:

explicit,

explainable,

measurable,

and:

actionable.

This creates a much stronger outcome than a simple:

Renew? Yes / No

field.

For prospects, that creates another compelling reason to use Contract Renewal Tracker: the product can become the place where renewal decisions are not merely recorded after the fact, but structured and governed before the organization creates its next contractual commitment.

Next Article in the Contract Renewal Tracker Series

Article 63 — “Contract Renewal Termination Management: How to Send Notices on Time, Preserve Evidence, Track Acknowledgments, and Avoid Invalid Cancellations”

The next article will go deep into one of the highest-risk outcomes in the entire renewal lifecycle: termination execution. It will cover notice requirements, contractual delivery methods, correct recipients, notice templates, legal review, signature authority, proof of delivery, acknowledgment tracking, failed delivery, notice withdrawal, partial termination, data return, transition obligations, final invoices, termination checklists, audit evidence, and AI-assisted termination preparation.

This should be another strong prospect-conversion article because missing a renewal is costly—but deciding to terminate and then failing to execute a valid notice can be even worse.