Leaders walk into meetings having had no time to look back at the last conversation, what was promised or who else will be there. The improved process prepares a short pack before each external meeting from your own records: who is attending, the last contact, open items and promises, and a draft agenda.
The pack is for the leader's eyes. Anything it suggests sending, such as an agenda to the other side, is only sent when a person approves it.
The job today
Ten minutes before a meeting, the managing director searches their inbox for the last email thread, asks a colleague what happened last time and tries to remember who the other attendees are. Open items from the last meeting surface halfway through, or not at all.
Where it breaks
- Preparation depends on how much time there is before the meeting, which is usually none.
- Promises from the last meeting are forgotten, which damages trust.
- Information is spread across email, the CRM and colleagues' heads.
- Agendas are rarely sent in advance, so meetings drift.
The improved process, step by step
- Spot the meetings that need a packEach morning the system checks the calendar for external meetings in the next day or two.
- Gather what you already knowIt collects the client record, the last few contacts, open items and any promises made, from your CRM, notes and shared mailbox.
- Draft the pack AI preparesAn assistant drafts a one-page pack: who is attending and their role, the last contact, open items, and points to raise. Every item links to its source.
- Draft an agenda AI preparesIt suggests a short agenda based on the open items and the purpose of the meeting.
- A person approves anything sent A person approvesThe leader or their assistant reads the pack. If the agenda is to go to the other attendees, a person approves it before it is sent.
- Capture what happenedAfter the meeting, the pack becomes the place to note outcomes and new promises, ready for next time.
Where a person must approve
The pack is private preparation. Anything that sends, changes or cannot be undone, such as sending an agenda or updating a record, waits for a person's approval.
The system never accepts, moves or declines meetings on anyone's behalf.
The data boundary
- The system reads the leader's calendar, the CRM and notes chosen for this purpose. It does not read private calendars or personal email.
- Information about people comes only from your own records and their business role, not from searching their private lives.
- It cannot send email or change calendar entries on its own.
- Every pack and anything sent from it is logged.
Checklist before you start
- Our calendars show which meetings are external.
- Client history is kept somewhere the system can read.
- We agree what a useful one-page pack contains.
- We know how far ahead packs should arrive.
- We know who approves agendas before they go out.
- We have agreed where notes from meetings are saved.
This is an illustrative walkthrough of a common pattern. It is not a client case study, and the details will differ in your organisation.