AI search across meetings should return evidence, not just answers

“What did we decide about pricing?”

In most teams, that question starts a small investigation. Search Slack. Open several documents. Scroll old meeting notes. Ask the person most likely to remember. Reconstruct the answer from fragments.

AI search promises a better experience: ask the question in natural language and receive an answer from across the team's meeting history.

That promise is valuable. It is also incomplete.

The safest answer is not the sentence that arrives fastest. It is the one that shows where it came from, when it was true and whether anything later changed it.

A plausible answer is not organizational memory

Imagine the search returns:

The team decided to keep annual pricing.

The sentence is clear, but the reader still needs to know:

• Which meeting produced the decision?
• On what date?
• Who owned the call?
• What reasoning supported it?
• Was the decision final or tentative?
• Did a later meeting supersede it?

Without those details, AI has reduced the effort of searching but not the risk of acting on the wrong information.

This is the same problem that appears in generated minutes. Fluency can make an interpretation look more settled than the underlying conversation. Search raises the stakes because it can combine information from many meetings the reader never attended.

Return the source passage, not only the meeting

A link to a ninety-minute transcript is technically a citation and practically another search task.

Useful meeting search should take the reader close to the evidence:

• the decision record;
• the relevant transcript passage;
• the action item and owner;
• the surrounding exchange that resolves ambiguity.

Consider a conversation where someone proposes Tuesday, another person hesitates, and the team finally agrees on Thursday. A result that highlights only the first mention will be wrong even though it found the right keyword in the right meeting.

The surrounding context is what separates evidence retrieval from text matching.

Until evidence-aware AI search exists, use the same standard manually: record the decision separately, name its meeting and date, and preserve the passage or reasoning that supports it.

Time changes the answer

Meeting knowledge has a sequence.

The team may choose annual pricing in March, test a monthly option in May and replace the original decision in July. Search cannot treat those three records as equally current.

A trustworthy answer should distinguish:

• the original decision;
• later evidence or objections;
• the current decision;
• the record that superseded the earlier one.

This requires more than semantic similarity. It requires the meeting system to preserve dates, relationships and decision state before the search question is ever asked.

That is why good decision records need to remain findable. Search quality begins with record quality.

When a decision changes, do not silently rewrite the old entry. Add the new decision and mark which earlier record it replaced. That gives people a current answer without erasing how the team arrived there.

Show uncertainty instead of hiding it

Some meetings do not contain a clean answer.

The team may discuss pricing without deciding. Two speakers may leave with different interpretations. A deadline may be proposed but never accepted.

In those cases, the correct result is not a polished guess. It may be:

• no final decision was recorded;
• two conflicting positions remain;
• the answer appears tentative;
• the available meetings do not contain enough evidence.

An AI search experience earns trust by declining to manufacture closure.

It should also let the reader correct the record. If the answer exposes an undocumented decision or contradiction, the team needs a path to resolve it rather than repeatedly receiving the same ambiguity.

Use three honest outcomes when reviewing meeting knowledge: decided, still open, or insufficient evidence. If the record cannot support the first, do not promote discussion into a decision.

Respect the meeting's access boundary

Cross-meeting search must not become a shortcut around permissions.

A person asking about pricing should only receive evidence from meetings and workspaces they are allowed to access. The answer should not reveal that a restricted meeting exists, quote a private client conversation or combine confidential context into an otherwise harmless response.

Permission-aware retrieval is part of answer quality, not a separate security feature. An accurate answer drawn from material the reader should not see is still a failed answer.

The answer should improve the next decision

The goal of meeting search is not merely to find old sentences. It is to help the team act without rebuilding its history.

A strong result should give the reader:

1. A concise answer.
2. The meeting and date.
3. The supporting passage or structured record.
4. The decision owner and reasoning when relevant.
5. Any later record that changed the answer.
6. A clear signal when the evidence is incomplete.

Scripta does not yet provide natural-language question answering across every meeting. Today, teams can organize and find their meeting records through the existing history and filters. We are publishing this standard because “simply ask” is not enough of a product promise.

Teams can prepare for trustworthy search now by giving decisions clear titles, dates, owners, reasoning and links to the meeting that produced them. Better retrieval starts with better records.

When AI search arrives, it should not ask the team to trade buried knowledge for unsupported confidence.

Knowledge should be searchable. Evidence should travel with the answer.