Client changes: keep your team up to date with EVA Brain

There are two days until the event. On the latest call, the client suggests bringing the leadership presentation forward and using the slot to introduce a product. You are thinking about the running order; Ana is thinking about the slides; Javier is still preparing the sound check using yesterday’s briefing.

The idea may make sense. The difficult part is turning it into a clear change for the whole team: what has been approved, what still needs confirmation and which parts of the event are affected. Meanwhile, an email arrives with another version, followed by a supplier’s question.

With EVA Brain, information received through connected sources becomes part of a shared project memory. The team can consult that history and request work based on the current context. Bringing the pieces together no longer depends entirely on one person remembering every conversation.

A client change affects more than one document

Moving a presentation can alter the running order, screen content and time available for another activity. If each person receives only a fragment, the team can end up working from different versions of the same event.

The problem can arise even when everyone does their part. The account team remembers the idea raised on the call; production has the original running order; design finds a new presentation without knowing whether it has been approved. A shared reference for the change’s status is missing.

In our example, bringing the presentation forward has a condition: leadership must first confirm that the product can be introduced. Treating the proposal as settled would mean preparing material that may never be used. Acting as though it had never been raised would not help anticipate the work, either.

Brain can retain that context so the next enquiry starts from information the project has already received. Both the change and its condition need to be recorded.

The call and email enter the same context

EVA Brain relates what it receives from project meetings, emails and documents to its available memory. You can invite the assistant to a client call to incorporate the transcript and connect or forward relevant communications, depending on the configuration.

That avoids someone having to reconstruct a separate explanation from memory for each colleague after every meeting. The conversation enters project knowledge and can be consulted alongside earlier agreements.

Suppose the client sends an email after the call confirming the presentation’s new time but leaving the product announcement pending. Brain then has two related inputs: the proposal from the meeting and the partial confirmation from the email.

When Ana asks what to prepare, that sequence matters. The new time is confirmed; the extra content is still pending. A summary simply saying “leadership presents the product earlier” would lose the distinction production needs.

Information arrives through sources the system receives. A private conversation that is not incorporated remains outside it. If the client decides something at the end of a venue visit, add the agreement to the project or use a configured route to collect it. Near-automatic updates begin with access to the work you want to retain.

Ask what has changed since the last briefing

Asking about differences helps the team identify what to review before continuing. Instead of requesting the whole history again, you can specify a period or reference document.

Ana: What has changed since yesterday’s briefing, and what still needs confirming?

EVA Brain: The email sent after the meeting confirms that the leadership presentation is moving earlier. The new product announcement is still awaiting approval. The running order needs reviewing with the new time, and the time available for the next activity needs checking.

Ana: Prepare a production list separating confirmed changes, pending proposals and checks we need to make.

That separation helps the work because it distinguishes facts with different consequences. The list can relate each point to its source for checking when something does not fit.

The team still resolves questions requiring a decision. If two emails conflict and neither clarifies which replaces the other, Brain can help locate the contradiction; the responsible person needs to confirm the current agreement. A convincing answer is not equivalent to client approval.

Keep proposal, approval and completion separate

A change’s status must be retained when preparing the next document. “The client suggested it”, “the client confirmed it” and “the team has done it” describe three different situations.

Information received	Status the team needs to recognise	Next work
The call raises a product announcement	Pending proposal	Review implications without treating the content as approved
The email confirms an earlier presentation	Confirmed change	Update affected plans and coordinate the new time
Ana shares a revised presentation	Document prepared	Review and approve it through the project’s process
Javier confirms the technical rehearsal with the new order	Work confirmed by its owner	Incorporate that confirmation and check outstanding items

The table can guide your review of the memory and documents you request from Brain. The system brings information together and helps produce work; the team remains responsible for approving and carrying out decisions.

An update to the context does not show that everyone has read it, either. For a change affecting the build, you need to communicate it to the people involved and confirm receipt through the project’s usual channel. Having information available is one part of coordination.

The revised briefing draws on the whole team’s work

EVA Brain can prepare a briefing using current agreements and available background, adapted to the agency’s or client’s brand. Its value is that the document draws on shared context, including conditions affecting the change.

In our example, you can ask it to keep the confirmed new time, leave the product content pending and include production checks. You can also specify who will use it: a technical rehearsal briefing needs different details from an update for the client.

Instruction: Prepare the technical rehearsal briefing using the current running order. Include confirmed changes since yesterday, material needing review and items awaiting approval. Adapt it to our brand and retain references to the agreements.

Before sharing it, review production details and the sources behind decisions. If Javier’s confirmation arrived after the document was prepared, the earlier briefing needs another review. An updated memory does not make every copy already sent up to date.

The same context remains available for other tasks. The person preparing the presentation can consult the client’s priorities; the person coordinating suppliers can review changes to the rehearsal. Each uses what they need without asking the account team to retell the whole call.

Reduce the burden of remembering without losing team judgement

Brain simplifies reconstructing what happened and locating relevant information. You can ask it for background, differences between points in the project or a document based on agreements it has already received.

That is particularly useful when several changes arrive in succession. The team retains a history it can consult: what was first proposed, what was later approved and what remains open. From a mobile or computer, people can ask about the same project with the access that applies to them.

The change goes beyond drafting a briefing faster. Ana can prepare her material knowing the condition attached to the new content; Javier can review the rehearsal order using the same agreement; you can answer the client from a shared understanding without gathering every fragment again.

Judgement remains with the agency. Bringing the presentation forward may require shortening an activity, and you may need to propose an alternative. Brain provides context for considering that decision, but does not replace negotiation with the client or checking what is feasible during delivery.

Try it with the next change you receive

Start with an active project and a recent change that has passed through more than one conversation. Bring together the reference briefing, the meeting or email introducing the change and subsequent confirmations.

Ask two team members to consult what is confirmed and what remains pending. Then use that context to prepare a document you already need: the production update, new running order or explanation you will send the client.

Review three things: whether the answer uses the correct source, whether it retains the change’s conditions and whether the document distinguishes approved items from outstanding ones. When something is unclear, incorporate the clarification into the project so it is available in later enquiries.

Your test of EVA Brain should start with a situation that currently forces you to reconstruct the history. The result you want is for the team to explain the event’s current status and prepare its work using the same agreements, without every question having to pass through you.

Frequently asked questions

Does EVA Brain update all our documents when the client makes a change?

Memory incorporates the information it receives, and you can request new documents based on that context. It does not mean every copy or external file updates automatically. Review and replace affected versions through your team’s process.

What if the client confirms something only on a call?

If the assistant participates and the information is incorporated into the project, the conversation remains available as a source. If the call does not reach the system, you need to add the agreement through a configured route.

Can I request a briefing using my agency’s brand?

Yes, you can prepare documentation adapted to your brand using project context. Review the content before sharing it, particularly decisions affecting budget, production or commitments to the client.

Does updated memory guarantee the team knows about a change?

No. It makes the change available to consult and work with. For changes affecting other people, communicate the update and confirm what is needed with those responsible.