Start from the meeting sequence, not the binder
Build the briefing folder around the order of the meetings, not around the company's document archive. The CEO needs to find the next meeting quickly, not browse every file the team has produced. Put the meeting sequence at the front with the time, the participants, and the one decision or relationship at stake. A binder organized by department will fail when the schedule changes.
Group the material for each meeting into a short page and a supporting file. The short page should state who is attending, what they care about, the company's last interaction, and the three points the CEO may need to make. The supporting file holds the detailed evidence. This separation keeps the folder usable during a car ride or a short wait.
Check the sequence against the travel plan and the time zone. A meeting that looks fine in the folder may be impossible after a delayed flight. Mark the meetings that can move and the ones that cannot. The briefing should support the trip, not assume the trip will follow the plan.
Number the meeting pages in the order the CEO will use them, and add a one-line summary at the front. A table of contents built from the original plan will be wrong after the first schedule change. Update the order and the page numbers together. The CEO should never have to guess which page belongs to the next meeting.
Build one page per meeting
Write the participant names and roles exactly as the company expects to see them. Include the firm, the fund, the stage of the relationship, and the last contact. A CEO who confuses two investors loses credibility quickly. The page should make the relationship obvious without requiring a separate memory.
State the purpose of the meeting in one sentence. It may be an update, a diligence question, a relationship check, or a specific ask. The purpose determines which evidence belongs on the page. A folder that treats every meeting as a pitch will be too heavy for a relationship call and too thin for a diligence session.
Add the questions the CEO is likely to face and the approved answer for each. Keep the answers short and factual. Mark the questions that require a legal or financial review before the meeting. The page should help the CEO prepare, not encourage an improvised answer on a sensitive topic.
Include the pronunciation of unfamiliar names and the preferred form of address. A small detail like this protects the CEO's credibility in a short meeting. Keep the note discreet and factual. Do not add personal commentary that could be embarrassing if the page is seen by someone else.
Keep the evidence current and versioned
Use one version of the company metrics across every meeting page. If the numbers changed after the folder was built, update the source and the page together. A CEO who quotes an old figure can create a correction problem with an investor. The folder should show the date of the metrics and the person who approved them.
Separate public information from confidential material. An investor roadshow may involve material nonpublic information, and the rules depend on the company, the venue, and the participants. The assistant should follow counsel's instruction on what may be shared and record the boundary in the folder. Do not let a convenient page override the disclosure rule.
Check the supporting files for tracked changes, comments, and old footnotes before they travel. A stray comment can reveal an internal debate that was never meant to leave the company. Ask someone who did not build the folder to open it as an outsider. That reviewer is more likely to catch a version problem.
Put the date and the owner on every metrics page, even when the number is unchanged. A reader should know how old the figure is without opening the source file. If a number is an estimate, label it as an estimate. A folder that mixes confirmed and estimated figures without labels invites a correction.
Prepare the questions the CEO will face
Collect the questions from the last two meetings with each investor and from the current diligence list. Group them into financial, operational, governance, and relationship questions. The CEO should see the pattern rather than a random list. A question that keeps returning deserves a prepared answer.
Write the answer in the CEO's voice, not in the assistant's. Test it for length and for the facts it commits the company to. A short answer that names the evidence is stronger than a long answer that avoids the question. Mark any answer that needs counsel or the CFO to confirm.
Leave space for a question no one predicted. Give the CEO a short response that acknowledges the question, states what is known, and names the follow-up. A calm request for time is better than a rushed guess. The folder should make that option easy to use.
Keep the answer bank to the questions that are likely to be asked, not every question that could be imagined. A long list dilutes the preparation. Mark the three answers the CEO must know cold. The rest can stay in the supporting file for reference.
Rehearse retrieval under time pressure
Ask the CEO to find one meeting page, one metric, and one answer within a short window. Watch where the hand goes and which tab is missing. A folder that works on a desk may fail in a car or a waiting room. Rehearse the retrieval, not only the content.
Check the digital copy on the device the CEO will actually use. Confirm that the files open offline, that the page numbers match, and that the font is readable on a phone. A folder that depends on a network connection is a risk on a roadshow. Keep one offline copy with the CEO and one with the chief of staff.
Finish with a five-minute review of the next day: the first meeting, the key evidence, and the contact who can answer a follow-up. Write the three points on a single card. The card is not a replacement for the folder; it is the part the CEO can use when there is no time to open it. Keep the card updated when the meeting order changes.
Time the rehearsal and write down the result. A folder that takes two minutes to navigate may be fine in a waiting room and useless in a moving car. If the time is too long, simplify the index before adding more content. The rehearsal is a design test, not a test of the CEO.
Related resources
Read also: regulatory meeting preparation and document retrieval research.
Frequently asked questions
Should one assistant support the whole executive team?
Sometimes. It works when priorities are clear and executives share one operating rhythm.
What should happen before a consult?
List the meetings, inbox rules, recurring reports, and decisions that need support.
Ready to define the role?
Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.
Book a consultation