A meeting with no decision still needs a record

A meeting with no decision still needs a record. Write exactly what remains unresolved, why the room could not decide, who owns the next move and when the question returns.

Without that structure, “no decision” becomes “we talked about it.” Everyone leaves with a different impression of which option is leading, what information is missing and whether another conversation will happen at all.

The honest minutes are not forced consensus. They are a usable description of the gap.

Do not turn a discussion into a decision

Suppose a product team meets to choose whether a new import flow should launch to every customer or only to a pilot group.

The conversation leans toward a pilot. Support raises a concern about migration errors. Sales wants a broader release. Nobody has the failure-rate review that would settle the risk.

A weak summary says:

The team discussed launching the import flow with a pilot.

An overconfident summary says:

The team decided to launch a pilot.

Neither is useful. The first records a topic, not an outcome. The second upgrades a preference into approval.

A truthful record says:

Open decision: Pilot release or general release? Why unresolved: the migration-error review was not available. Decision owner: Mira. Next input: Leon provides the review by Thursday. Decision point: Mira decides Friday after support has commented.

The meeting produced real progress: it narrowed the question and identified the evidence that controls the answer. That is worth recording without pretending the answer already exists.

Name the exact question still open

“Pricing unresolved” is too broad. So is “need more data.” A future reader needs to know what choice the missing information will affect.

Write the open question as alternatives whenever possible:

• launch to the pilot group or all customers;
• keep the current renewal date or move it by one month;
• repair the existing integration or replace it;
• approve the scope now or remove the reporting module.

Alternatives expose whether the group is actually discussing one decision. If one person is debating timing while another is debating whether to proceed at all, the apparent disagreement may be two different questions collapsed into one conversation.

Keep the current position of each option brief and factual. Record material support and objections, but do not turn the minutes into a transcript. The standard is the same as recording disagreement without reopening a decision: preserve the reasoning that changes how the outcome should be understood.

Replace “more information” with a missing fact

Requests for more data can postpone a decision indefinitely because they do not define what would be sufficient.

Ask three questions before closing the meeting:

1. What fact is missing? “Migration errors from the last 20 imports,” not “more technical detail.”
2. Who will produce or obtain it? One person, not a department.
3. How will it change the choice? “If any error can overwrite customer data, use the pilot.”

The third question is the important one. It tests whether the requested evidence is decision-relevant or merely comforting. If the group cannot explain how the answer would affect the options, more research may not be the next move. The decision owner may simply need to make the trade-off with the uncertainty already visible.

Give the decision an owner, not another audience

An unresolved decision still needs one person accountable for closure. “The team will revisit” schedules another audience; it does not identify who can make the call.

The decision owner does not have to gather every input personally. They do need to:

• say what evidence is sufficient;
• hear the required perspectives;
• choose or explicitly defer;
• update the record when the outcome changes;
• explain the next step if the question remains open.

This is different from assigning the research task. Leon may own the migration review while Mira owns the launch decision. Combining those responsibilities can make the evidence collector feel responsible for a trade-off they were never authorised to make.

If nobody in the room has authority, record the escalation route: who will take the question to the actual decision-maker, what recommendation travels with it and when the group expects an answer.

Choose a decision point or a real trigger

“Revisit later” is where open questions disappear. Give the decision a return path.

Use a date when the missing input has a credible delivery date:

Leon posts the review Thursday; Mira records the decision Friday.

Use a trigger when timing is outside the team's control:

Mira decides within one business day of legal returning the assessment.

The trigger must be observable, and someone must watch for it. “When we know more” is not observable. “When legal returns a written assessment of the clause” is.

Do not schedule another full meeting by default. If the decision owner can read the evidence, consult the affected people and record the call asynchronously, a calendar event adds delay rather than judgment. Meet again only when the remaining work needs genuine discussion.

Make uncertainty visible in the summary

The summary should distinguish three states:

• Decided: the owner made the call and the outcome is accepted.
• Open: the options and closure path are known, but no call has been made.
• Not addressed: the meeting never reached the question.

These states should not blur together. “No objections were raised” is not a decision if the owner never asked for or made one. A topic omitted because time ran out is not an open decision unless someone accepts responsibility for bringing it back.

Scripta can structure a transcript or rough notes into a meeting summary, decisions and next steps for review. The important constraint is that an unanswered question must stay unanswered: generated minutes should not promote discussion into agreement. A person reviews what the source supports before treating it as the record, as explained in why AI meeting notes should show their work.

Use a four-line closeout

Before everyone leaves, read back four lines:

Open decision: Pilot or general release.

Missing evidence: Migration-error review.

Owners: Leon supplies the evidence; Mira decides.

Return: Friday, after support comments.

Ask the decision owner and evidence owner to confirm their parts. This takes less time than another round of “where did we land?” messages and prevents the strongest opinion in the room from being mistaken for the outcome.

Some meetings should end without a decision. A legal constraint may be unknown. The affected person may be absent. The options may not be ready. Refusing false closure is good judgment.

But absence of closure is not absence of documentation. Record the question, the missing fact, the owner and the return path. Then the next conversation can begin where this one ended instead of reconstructing why nothing happened.