Start from the decision the meeting must reach
A meeting packet should begin with the decision the meeting is meant to reach. Write one sentence that names the choice, the deadline, and the person who will decide. A packet without that sentence becomes a pile of background material. The assistant can then leave out anything that does not help the decision.
Ask the meeting owner to confirm the sentence before the assistant gathers evidence. A short confirmation prevents a packet built on the wrong question. Record the answer in the invitation so every attendee sees the same purpose. The decision sentence is the anchor for every later page.
Gather material from source systems
Collect facts from the systems that own them rather than from forwarded summaries. Pull the current contract from the document store, the latest numbers from the account system, and the open issues from the queue. Save a link to each source beside the fact it supports. The reader can then check the original instead of trusting the packet.
Label anything that is a draft, an estimate, or a secondhand report. A number without a source and a date is a rumor. Ask the owner to confirm the figures that will appear in the room. The packet should make uncertainty visible rather than smoothing it away.
Write the one-page brief
Keep the opening brief to one page with four parts: the decision, the background, the options, and the recommendation. Write the background in short paragraphs that a reader can scan. Put the options in a table with the cost and the risk for each. The recommendation should say what the assistant or owner believes and why.
Leave out the history that does not change the choice. A long recap of how the project started often crowds out the information that matters now. Use plain language and define any internal label. The reader should understand the trade-off without opening another document.
List the questions and risks
Add a short list of questions the meeting should answer, ordered by importance. Include the question the owner is most afraid to ask, because that is often the one that decides the outcome. Mark which questions need a client answer and which the team can settle alone. A prepared question list keeps the conversation from drifting.
Name the risks in concrete terms rather than as general concerns. A risk might be a renewal notice that expires before the next meeting or a dependency on a single approver. Add the early warning sign and the person who watches for it. The meeting can then decide whether to accept the risk or change the plan.
Set the post-meeting record
Prepare the note template before the meeting so the record is captured in the same shape every time. Include decisions, owners, dates, open questions, and the next meeting. The assistant should fill it during or immediately after the call. A template prepared in advance is more likely to be used than one created afterward.
Send the draft record to the meeting owner within the day for correction. Ask the owner to confirm the decisions rather than rewrite the whole note. Store the approved version with the packet and the source links. The record then becomes the handoff for anyone who joins the work later.
Test the packet on a real meeting
Test the packet on one recurring meeting and ask the attendees what they used. If no one opened the background section, shorten it or remove it. If the decision sentence was wrong, fix the intake question. The test measures usefulness rather than completeness.
Compare the packet with the notes from the same meeting. A decision that appears in the notes but not in the packet shows a gap in the preparation. A question in the packet that no one answered shows a gap in the meeting. Use both findings to adjust the next packet.
Sources
Open the original publisher and confirm the current version, definition, and scope before using a source for a business decision.
Turn the reading into a role brief
Bring the recurring tasks, tools, schedule, access limits, and owner-only decisions. Start with one work sample and one clear review path.
Plan a Philippines-based role