Skip to content
On this page
Executive Operations

·RemoteExecutiveSupport Editorial Team

An executive meeting prep packet that fits on one page

An executive meeting prep packet that fits on one page

A meeting starts and the executive asks for the background. The assistant has three documents, two threads, and a slide deck, but no one-page summary. The first ten minutes are spent reconstructing context that could have been read.

A one-page prep packet fixes that. It gives the executive the objective, the people, the decision, and the open questions in a format that can be read in three minutes.

Lead with the objective

Open with one sentence: why the meeting exists and what a good outcome looks like. A packet that starts with the attendee list makes the executive search for the purpose.

If the objective is unclear, that is the first finding. Ask the organiser before writing the rest, and record the answer in the packet.

Name the decision

State the decision the executive is expected to make, or say that the meeting is informational. A meeting without a decision still needs to know what it is for.

For a decision, add the options and the recommendation. The executive may choose differently, but the packet should show that the choice was framed.

Summarise the history

Give the minimum history needed to follow the discussion: what happened, what was tried, and what changed. Keep it to a few sentences and link to the detail.

A packet that repeats the full history is not a summary. The executive can ask for more, but should not have to read the archive first.

List the people and their positions

For each key attendee, record their role and their likely position on the decision. The position matters more than the title.

Be careful with speculation. If the position is unknown, say so and suggest a question to ask. A false prediction is worse than a blank.

Surface the open questions

List the questions that remain unanswered and who can answer them. These are the points where the meeting may stall, and the executive should see them before the call.

Where possible, resolve a question before the meeting. A packet that arrives with three unresolved questions often produces a follow-up meeting.

Keep it to one page

Use short lines and clear headings. The one-page limit forces the assistant to prioritise and makes the packet usable on a phone.

Put the detail in links or an appendix. The packet is the entry point; the appendix is for the deep dive.

Send it early enough

Agree a send time with the executive, usually the evening before or the morning of the meeting. A packet sent five minutes before the call will not be read.

If the packet is late, send the decision and the open questions first. A partial packet on time is more useful than a complete one after the meeting.

Attendee roles

List the people whose presence changes the meeting, with their role and the reason they are there. A complete attendee list is less useful than a short list of the people who matter.

If a key person is missing, say so. The executive may want to reschedule or ask for a follow-up.

Materials to bring

Note the documents the executive may need to reference: the contract, the budget, the previous decision. Put the links in one line.

Do not paste the documents into the packet. The packet is for orientation; the documents are for detail.

The ask

Where the meeting needs something from the executive, state it plainly: a decision, a signature, a message, or a name. An ask that is implied is often missed.

Record the ask at the top of the packet, not only in the body. The executive should see it before reading the context.

Follow-up

Note who will capture the outcomes and when the notes will be circulated. A meeting without an owner for the follow-up produces a second meeting.

Record the follow-up owner in the packet so the executive knows who to ask.

A worked example

A meeting with a vendor needs a decision on a renewal. The packet states the decision, the two options, the recommendation, and the deadline.

The history is three sentences with a link to the contract. The open question is the price for the second year. The packet is read in two minutes, and the meeting starts with the decision.

Timing

Send the packet at the agreed time and confirm it was received. A packet that arrives during another meeting is effectively late.

If the meeting moves, update the packet and resend only the changed fields. A full resend for a time change adds noise.

Review the packet after the meeting

Ask whether the packet helped and what was missing. A repeated gap is a template change, not a one-off.

Record the feedback and update the template. The packet should improve with each cycle, not stay the same while the meetings change.

What the packet does not do

The packet does not replace the meeting or the executive's judgement. It prepares the ground for a better conversation.

It also does not replace the assistant's live support during the call. The packet is the pre-read, not the whole service.

Related Articles