Which meetings are worth preparing this way?
Use the workflow where preparation currently means searching several places under time pressure: a client review, supplier escalation, partner discussion, project governance meeting, investor conversation or senior external call. The best first candidate has a clear owner, repeated briefing structure and enough relevant history to produce something more useful than a generic company profile.
What should be in the finished briefing?
The brief should help the meeting owner decide what matters before joining the call. It names the purpose and decision required, summarises only the permitted history, separates facts from suggestions and keeps citations beside external claims. It also says when the source material is too thin or contradictory to support a conclusion.
- Meeting purpose, desired decision, attendees, roles and any known sensitivities.
- Previous emails, meeting records, commitments, decisions and open actions the meeting owner is allowed to see.
- Relevant SharePoint documents or project records with direct links rather than detached summaries.
- Current company, project, planning or sector facts with publisher, date and a link to the lawful public source.
- Conflicting information, missing answers and a short list of questions the meeting owner may want to ask.
What does the finished workflow look like on a normal day?
An agreed calendar event triggers preparation at the chosen lead time. The workflow reads only the permitted related history, checks the named public sources and builds the briefing in the client's format. Each source is linked, gaps stay visible and conflicting facts are placed side by side. The meeting owner receives the draft, removes irrelevant material, checks the claims and approves the version they will use.
What does Attenta Partners set up?
Attenta defines the eligible meeting types, trigger time, internal source boundaries, public research list, briefing template, reviewer and deletion rules. The pilot tests a meeting with strong history, one with little related material, a name collision, a stale company fact and an inaccessible document. The handover records which sources were connected, how citations work and when the workflow must return 'not enough information'.
- Choose one recurring meeting type and agree who owns the briefing.
- Map the relevant Outlook, Teams and SharePoint context without granting access to unrelated mailboxes or sites.
- Agree lawful public sources, blocked sources and the citation information every external claim must keep.
- Build the briefing format around the decision, history, open actions, current facts and questions the user actually needs.
- Test source quality, access failures, duplicate names, conflicting facts and the review route before live use.
Can it use Outlook, Teams and SharePoint?
Yes, where the Microsoft licence and company policy allow it. Microsoft states that meeting preparation summarises related content the signed-in user may access, and different attendees can receive different summaries because their permissions differ. A tailored workflow can add a fixed briefing format and cited public research without opening access to unrelated client or company information.
Official guidance: Microsoft guidance on preparing for meetings with Copilot.
How do we stop invented facts?
Every public claim keeps the page, publisher and date it came from. Internal summaries link back to the permitted email, meeting or file. Missing and conflicting information is shown rather than completed. AI can suggest a fact, connection or question, but the meeting owner accepts, edits or rejects it before using it in a conversation or project record.