Start from the decision the meeting must make
A meeting-prep packet is not a folder of everything the executive might want. It is a short, source-linked brief built around the decision, approval, or discussion the meeting is supposed to produce. Begin by writing the purpose in one sentence, then list the questions the executive must answer, the options on the table, and the person who owns each open item. If the purpose is still unclear, the correct output is a question to the meeting owner, not a thicker packet. A Philippines-based executive assistant can gather the calendar context, the prior decision record, the latest approved figures, and the names of the people attending. The assistant should not decide which option the executive will choose, promise an outcome to another attendee, or fill a gap in the record with a plausible guess. The packet makes the decision easier to make; it does not make the decision.
Use a fixed packet skeleton
A workable skeleton has seven parts: meeting identity, purpose and decision, attendee map, source-labelled facts, open questions, risks or constraints, and a recommended preparation sequence. Each fact carries a source name, a date observed, and a link or record identifier. Each open question carries an owner and the date an answer is needed. The assistant can complete the skeleton in a consistent order, which makes omissions visible during review. Keep the skeleton short enough to read before the meeting. A two-page brief with clear labels beats a twenty-page appendix nobody opens. Put detailed source material behind links or in an appendix, and mark clearly when a document is a draft, a signed version, or an earlier version kept only for history. The executive should be able to see within a minute what is settled, what is contested, and what still needs a decision.
Label provenance instead of smoothing it away
Meeting preparation often mixes facts from a calendar, a customer record, a finance export, a chat message, and someone's memory. Those sources do not carry equal authority. The packet should say which record is authoritative for each item and when it was read. If two sources disagree, preserve both entries and route the conflict to the owner instead of choosing the more convenient number. Version labels matter as much as source names. A signed contract, a draft contract, and an email describing the contract are three different objects. Record the version and the date, not only the file name. When the executive asks where a figure came from, the assistant should be able to open the exact source rather than reconstruct the answer from memory. That habit turns preparation into evidence rather than storytelling.
Protect confidential material before distribution
Executive calendars and pre-reads often contain personnel matters, commercial terms, legal advice, or customer information. Share only the sections each attendee needs, and keep the full packet in an approved location with named access. Do not forward a complete packet to a distribution list because it is faster than extracting the relevant page. The assistant should know which fields are sensitive and which recipients are approved before sending anything. A simple handling note on the first page can prevent accidental disclosure: who may receive the packet, whether it may be printed, where the current version lives, and who to contact about a suspected misdirected message. This is not legal advice and does not replace the company's security or privacy rules. It is an operating reminder that executive support handles material whose value and sensitivity are both high.
Work a realistic preparation cycle
Suppose a quarterly supplier review is scheduled for Thursday. On Monday the assistant collects the prior meeting minutes, the current contract summary, the latest spend extract, and the list of open corrective actions. The contract summary and the spend extract disagree on the billing unit, so the assistant records both, marks the discrepancy, and asks the finance owner to confirm which record controls. The packet is sent Tuesday with the discrepancy still visible and the decision clearly reserved. On Wednesday the supplier sends a new document. The assistant does not overwrite the Tuesday packet. A new version is created with a change note, the effective time, and the reason for the update. The executive can then see what changed after the original distribution. This small discipline prevents the common failure in which two attendees arrive with different packets and neither can tell which one is current.
Close the loop after the meeting
The packet has a second life after the meeting. Record the decisions actually made, the owner of each next action, the date promised, and any item deferred. Link the decision record back to the packet version that was used. If the meeting changed a fact that later packets depend on, update the source of truth rather than only the meeting notes. The next preparation cycle should begin from that record, not from a blank page. Review a sample of packets monthly. Check whether each fact had a source, whether open questions had owners, whether confidential sections were handled correctly, and whether the decision record matched the discussion. A repeated defect usually points to a template or intake problem, not to a careless assistant. Fix the template, retrain on the specific ambiguity, and keep the evidence of the change.
Sources and limits
The U.S. Small Business Administration offers general guidance on managing employees and business records, and the U.S. National Archives publishes records-management principles that help teams distinguish official records from convenience copies. NIST Privacy Framework and the U.S. Department of Labor provide useful context for handling personal information and employment records. These references do not decide a specific company's confidentiality rules or legal obligations. Sources: https://www.sba.gov/ https://www.archives.gov/records-mgmt https://www.nist.gov/privacy-framework https://www.dol.gov/