Skip to content

Case notes · AI systems

Briefing assistant

An assistant that gathers the brief over the client’s sources, follows clear rules and hands off to a person.

Anonymous case note. No client names, no logos, no figures and no reserved terms — only publishable method.

Context

Where we started

The starting point

An organization handled every briefing request by hand: whoever received the question had to reconstruct which sources to consult, where to find them and who to involve. The result was slow, dependent on whoever was on duty, and prone to dropping details when the context was fragmented.

Why a change was needed

The useful information already existed, but it was scattered across documents, archives and earlier conversations. Without a single point of collection, every briefing started almost from scratch and the answers were not comparable to one another.

Challenge

The knots to untie

Gather the right sources

Work out, case by case, which materials are actually needed before answering, instead of asking for everything or settling for too little.

A request arrives with little context: the assistant has to know what to ask to complete it.

Stay within the rules

Every answer had to respect precise limits on what can be said, to whom and in what form, without improvising.

When a request touches a sensitive topic, the assistant stops and does not force an answer.

Know when to stop

Recognize the cases that exceed its own scope and pass them to a person, without pretending a competence it does not have.

Faced with an ambiguous or sensitive request, the case is forwarded to a human contact.
The process

How we got there

1
Map of the sources

Together with the client, we described which sources matter for each type of briefing and how to recognize them.

2
Explicit rules

We translated the internal policies into rules the assistant can read, so that every answer was born within a clear scope.

3
Handoff points

We defined the signals that trigger the handover to a person, before the assistant steps outside its remit.

4
Test and correct

We tested the assistant on real cases and refined rules and sources until the behavior became predictable.

In successive phases, with client review at each step.

What was built

The concrete result

A briefing assistant

An assistant that, once it receives a request, gathers the information about the client's sources, organizes it and prepares a coherent briefing, following the agreed rules.

A reliable handoff

When the request leaves the scope or touches a delicate point, the assistant does not insist: it passes the case to a person with the context already gathered, so the contact does not start from scratch.

Repeatable behavior

For the same request, the answer follows the same path: same sources consulted, same rules applied, same point at which to ask for human help.

TMM reading

What we take from it

Rules matter more than speed

A useful assistant is not the one that always answers, but the one that knows where its limits are. The handoff is not a failure: it is part of the project, designed with the same care as the rest.

Sources are chosen, not endured

The value is not in collecting everything, but in knowing what a given briefing needs. Selecting the sources is the real work, and it has to be built together with those who know the domain.

FAQ

Recurring questions

Does the assistant decide on its own what to say?

No. It works within agreed rules and, when a request exceeds them, it passes the case to a person instead of forcing an answer.

What happens if information is missing?

The assistant gathers the useful sources and, if gaps remain or the topic is delicate, it flags the case for human handoff with the context already prepared.

Can this case be traced to a specific client?

No. The description is deliberately anonymous: it tells the approach and the structure, without details that would allow anyone to identify the commissioner.

A similar problem?