Build a decision-ready meeting brief in Teams
Give each meeting the current decision, evidence, prior commitments, open risks, and one explicit ask before the attendees enter the room.
A useful meeting brief states why the meeting exists, which decision is due, what evidence supports it, which prior commitments remain open, and what the attendees should resolve. Post it before the meeting in the agreed Microsoft Teams location and keep the durable brief in the approved company record.
ALEK, the AI chief of staff, is the current fidelic agent whose published work covers meeting preparation. ALEK can prepare the brief from approved priorities, decisions, calendars, commitments, risks, and project records. The owner keeps direction, people decisions, and the authority to speak for the company.
Require a decision, not a biography of the attendees
A decision-ready brief keeps five parts visible
The brief uses only information needed for the meeting's stated purpose.
| Part | Required content | Acceptance check |
|---|---|---|
| Purpose | The decision, review, or coordination result expected from the meeting | The meeting can be canceled if no result is needed |
| Current state | Verified facts, prior decisions, commitments, owners, dates, and material changes | Each material statement links to an approved source |
| Decision packet | Options, constraints, assumptions, trade-offs, and the accountable decision-maker | Unknowns remain marked rather than guessed |
| Open risks | Conflicts, missing evidence, overdue work, and affected downstream owners | Each item has an owner or explicit unassigned state |
| Agenda | The smallest sequence needed to reach the stated result | Time is not filled with status that could be read beforehand |
Personal profiles and unrelated private history do not belong in the brief merely because the system can retrieve them.
Microsoft says Teams meeting notes can include an agenda, shared notes, and tasks. Microsoft's recap guidance places transcripts, files, notes, agenda, and follow-up tasks together after the meeting. Those features support the meeting-local record. ALEK's role covers the operating work around the meeting, including the decision and commitment record before and after it.
“The meeting brief should make the decision easier to make, not make the meeting look well researched.”
Limit every source to the meeting's purpose
The source record should list the calendar event, decision register, current project or finance records, prior meeting record, and approved supporting documents. Exclude unrelated chats, private mailboxes, personnel records, customer files, and broad tenant resources unless the exact meeting purpose requires them and the accountable owner approves access.
Microsoft documents resource-specific consent for certain Teams app permissions tied to a specific team, chat, or user. Support depends on the permission and app design. The actual grant must be inspected rather than inferred from the phrase “works in Teams.”
The Microsoft Teams integration guide covers the wider application, permission, posting, and retention arrangement. The security page carries current provider boundaries.
Prepare the brief from current records
One meeting moves from decision request to accepted record
Preparation and follow-through remain connected to the same business decision.
- 1
State the meeting result
Write the decision, review, or coordination outcome and the person accountable for it.
Owner: Meeting owner
- 2
Approve the source set
List the calendar event, prior decisions, commitments, current records, exclusions, and source owners.
Owner: Meeting owner and administrator
- 3
Prepare the decision brief
Reconcile facts, options, assumptions, commitments, risks, contradictions, and missing evidence.
Owner: ALEK
- 4
Post before the meeting
Send the durable brief link, decision due, key change, risk, and missing input to the agreed Teams destination.
Owner: ALEK
- 5
Update after the meeting
Record approved decisions, accepted commitments, open questions, corrections, and next dates in the durable record.
Owner: ALEK and accountable owner
Test freshness, absence, and conflict
A meeting brief can be polished and still wrong because it used an old plan or omitted a late change. Test one outdated source, one missing source, and one pair of conflicting dates. The brief should display each issue and ask the source owner to resolve it.
Test an attendee who should not be visible, a private meeting outside the approved source set, and a denied Teams destination. No content should cross those boundaries. Test revocation before business-critical use.
The trigger catalog can define when preparation begins. A calendar event at a set interval before the meeting may start the work, but only when the event, source window, excluded meetings, destination, and completion check are explicit.
Keep sensitive meetings human-led
Employment decisions, legal advice, financing terms, acquisitions, board matters, investigations, and unfamiliar executive judgments may require a qualified person to frame the issue and control the record. ALEK can prepare approved facts and commitments. ALEK does not make those decisions or speak for the owner.
The agent constitution guide records the action, review, escalation, and refusal boundaries. The outcome guide keeps the finish line observable.
Follow the connected questions
Start and work together includes this decision and the questions that usually change it.
Which systems should an AI agent connect to?
Connect the smallest set of systems needed to read the source, write the work product, and preserve the record the business already uses.
Inspect supported integrations →What data should an AI agent be allowed to access?
Grant only the systems and records required for the role. Keep credentials, customer boundaries, logs, and approval rules explicit.
Where should an AI agent’s work appear?
Use the environment where the right people can see the result, inspect the source trail, correct it, and make the next decision.
What should you do next?
Choose one routine internal meeting. Write the decision due, five required brief sections, source set, exclusions, reviewer, Teams destination, durable destination, and revocation test. Run one preparation cycle, then inspect ALEK's current rates if the accepted result reduces avoidable meeting work.