When decisions conflict, record which one supersedes

When two meeting decisions conflict, do not edit the older record until it appears to agree. Create a supersession entry that names the active decision, the decision it replaces, the overlapping scope, the authority for the change, the reason and the effective time.

Then notify the people whose work changes.

That preserves an honest history while giving the team one current instruction. Without the link, both records keep looking valid and people follow whichever one they saw last.

First prove there is a real conflict

Two decisions are not necessarily inconsistent because they sound different.

Compare their scope:

• Do they govern the same product, customer, region or project?
• Do they apply during the same period?
• Do they direct the same people or resources?
• Can a team comply with both at once?
• Was one a principle while the other was a bounded exception?

For example:

Monday: All pilot customers receive weekly progress reports.

Thursday: The healthcare pilot receives reports only after compliance review.

These decisions can coexist if Thursday is an authorised exception for one customer group. But if Thursday says no pilot report may be sent before compliance review, the rules overlap and point in different directions.

Write the conflict in one sentence before trying to resolve it:

Monday requires a weekly report for the healthcare pilot; Thursday prevents that report from being sent until compliance approves it.

If you cannot state the incompatible actions, the problem may be unclear wording rather than competing decisions.

Stop asking chronology to decide authority

The newer decision is not automatically the controlling one.

A small project meeting held on Friday may not have authority to overturn a security decision made on Wednesday. A leadership decision may set a company-wide rule while a later delivery meeting chooses only how to operate inside it. Timestamps tell you order, not permission.

Identify:

• the decision owner for each record;
• the scope each owner was authorised to decide;
• any policy, contract or external requirement that limits both;
• the person who has authority across the overlapping scope.

If the Thursday room deliberately changed Monday's decision and had authority to do so, record a supersession. If it lacked that authority, treat Thursday's outcome as a proposed change and return it to the right owner.

When authority is genuinely unclear, pause the conflicting action. Do not let each team select the record that makes its work easier.

Create a new record instead of rewriting history

An older decision may explain work that was reasonable at the time. Deleting it or changing its wording makes that work look careless and removes the reasoning behind the change.

Keep three layers:

1. the original decision, unchanged;
2. the later decision, with its own reasoning;
3. a link that says which record now controls the overlap.

A useful supersession entry looks like this:

Active decision: Healthcare pilot reports require compliance approval before sending.

Supersedes: “All pilot customers receive weekly progress reports,” for the healthcare pilot only.

Effective: 18 September at 14:00.

Authority: Mira, pilot decision owner, with compliance approval.

Reason: The original cadence did not account for protected information in this pilot.

Notice that the old decision still applies to other pilots. “Replaced” without a scope could accidentally cancel more than the new room intended.

State what happens to work already in motion

Changing the rule does not automatically reconcile the work created under it.

List the affected commitments:

• work that continues unchanged;
• work that must stop;
• work that needs review before it continues;
• promises already made to customers or partners;
• files, templates or instructions that still carry the old rule.

For the reporting example, the team might decide:

The draft healthcare report stays in review and must not be sent. Reports for the other pilots continue. Leon updates the reporting checklist today. Priya tells the healthcare sponsor that this week's report is pending compliance review.

This is where supersession becomes operational. A clean decision log with an unchanged checklist still produces the wrong behaviour.

Turn each required correction into an owned action with a date. If an existing commitment is no longer valid, close or replace it with a note pointing to the superseding decision. Do not leave the owner to infer that their task disappeared.

Notify the people whose next move changed

Do not broadcast every decision change to the whole organisation. Notify the people who:

• own affected action items;
• approve, send or publish the affected result;
• rely on the old decision for a downstream commitment;
• maintain a template, checklist or workflow that encodes it;
• received an external promise under the previous rule.

The message should identify the change, not merely link to minutes:

The healthcare pilot is now an exception to the weekly-report rule. Compliance approval is required before sending, effective today at 14:00. The draft remains in review. Other pilot reports continue unchanged. See the supersession entry for the reason and owners.

A notification is complete only when the affected record also changes. Otherwise the message fades while the old instruction remains searchable and apparently active.

Distinguish supersession from reopening

Reopening asks whether an existing decision should change. Supersession records the authorised answer after it has changed.

Use the decision trigger to prevent casual relitigation. Once the trigger occurs and the owner chooses a new path, create the supersession link so readers can move between the old and current records.

Do not label an unresolved disagreement as supersession. If one room says “ship” and another says “wait,” and nobody with authority has resolved the overlap, the honest state is conflict. Record:

• both instructions;
• the affected scope;
• the temporary safe action;
• the resolving owner;
• the resolution deadline.

That may mean pausing one release, holding one message or continuing only work that is valid under both possibilities.

Keep one current path into the history

A person searching later should not need to compare dates and infer which decision won.

From the old record, point forward: “Superseded for the healthcare pilot by [new decision], effective 18 September.”

From the new record, point back: “Replaces [old decision] for the healthcare pilot; the original remains active elsewhere.”

In Scripta, teams can review extracted decisions, edit their wording and reasoning, and keep them with the source meeting. Minutes history and connected action items help preserve the surrounding record. Scripta does not automatically judge conflicts or select the stronger authority. A human decision owner must resolve the overlap and write the link clearly.

This is also why a decision log must be findable. Retrieval is useful only if each result tells the reader whether it is still the instruction to follow.

Use this supersession template

Record:

Active decision: [the instruction to follow now].

Supersedes: [the older decision and exact overlapping scope].

Effective: [date and time, when timing matters].

Authority: [the owner who can decide across the overlap].

Reason: [the new evidence, constraint or priority].

Work affected: [stop, continue, review and notify].

Then add a forward link to the old record and a backward link to the new one.

Teams do not need a perfectly tidy past. They need an honest past and one unambiguous present. Supersession provides both.