AI FOR EXECUTIVE ASSISTANTS — PRACTICE PACK Splice Work | Prepared September 10, 2026 https://splicework.ai/blog/ai-for-executive-assistants/ HOW TO USE THESE PRACTICE EXERCISES All people, organizations and details below are fictional. Reviewer references describe what to check in your answer; they are not captured model results. These are practice exercises, not recorded tests of ChatGPT or the other tools. No measured time, savings or accuracy claim. Run each exercise in a fresh conversation with only its source packet and prompt. Do not paste the reviewer reference into the run. Do not connect tools, browse, send email or edit a calendar. Keep the first response exactly as received. Record all attempts, including failures. ============================================================ MEETING-BRIEF SOURCE B1 — Calendar copy, September 10, 2026. North Alder Studio supplier review. September 15 at 9:00 AM Pacific. Attendees: Mira Chen, operations lead; Theo Park, finance lead; Alex Rivera, role not recorded. B2 — Planning note, September 10, 2026. Supplier review is September 15 at 10:30 AM Pacific. Purpose: decide whether to request proposals from two suppliers. Bring the requirements brief and current supplier comparison. The budget ceiling has not been approved. Neither B1 nor B2 is designated authoritative. EXACT PROMPT Using only B1 and B2, prepare a meeting brief of at most 120 words for Mira. Include purpose, decision needed, attendees, preparation and unresolved questions. Cite B1 or B2 beside factual statements. Do not choose between conflicting times, infer Alex's role or invent a budget. Do not search, contact anyone or change a calendar. Put unresolved details in a separate section. REVIEWER REFERENCE — KEEP OUT OF THE PROMPT The brief should preserve the decision as **whether to request proposals**. It should include the two preparation documents and the recorded attendees. Its unresolved section should show both times, Alex's missing role and the unapproved budget ceiling. It must not announce that suppliers have been selected or that either time is confirmed. Check the source labels as well as the prose. “B2” beside a made-up budget still looks impressively sourced. Open B2 and find the supporting sentence. A label is a navigation aid, not a certificate of truth. If an output picks 10:30, the correction should be specific: “Restore both conflicting times and mark the meeting time unconfirmed.” Asking it to “be more accurate” leaves too much interpretation. The final human step is to confirm the time with the organizer and update the source. Another prompt cannot discover a decision nobody has supplied. YOUR RUN RECORD Tool/workspace: Model/version shown (or unavailable): Date/time/time zone: Connections/settings: Attempt number: First output, unchanged: Review findings, checked against source: Correction prompt (if needed): Final output (or first output accepted unchanged): Human checks before use: Hands-on source preparation / prompting / review / correction time: Comparable manual baseline (if measured): ============================================================ ACTION-LIST SOURCE A1 — Meeting notes approved by Mira, September 15, 2026. Decision: request proposals from two suppliers; no supplier appointment is approved. Mira will send the requirements brief by September 17. Theo will ask both suppliers about capacity; no deadline was agreed. The team needs a budget comparison, but no owner or due date was assigned. Alex suggested September 18 for proposals; the team did not approve that deadline. EXACT PROMPT Use only A1. Make an action table with task, owner, deadline and source. Keep missing owners or dates as “Not assigned” or “Not agreed.” List decisions and unapproved proposals separately. Do not turn the suggested September 18 date into a commitment. Include all explicit actions and do not assign work based on a person's job title. Do not create tasks in another system. REVIEWER REFERENCE — KEEP OUT OF THE PROMPT | Task | Owner | Deadline | | --- | --- | --- | | Send the requirements brief | Mira | September 17, 2026 | | Ask both suppliers about capacity | Theo | Not agreed | | Prepare the budget comparison | Not assigned | Not agreed | The decision to request proposals belongs outside that action table. So does Alex's unapproved September 18 suggestion. There is no approved appointment, proposal deadline or delivery date to carry into the next task. Compare both directions: every reported action needs a source, and every explicit source action needs a place in the result. Checking only the first catches inventions but misses omissions. A missing task is still missing even when the remaining rows are immaculate. Leave the blank responsibility visible until somebody accepts it. Theo works in finance, but that does not make him the owner of every sentence containing “budget.” If the model assigns him the comparison, remove the assignment and flag it for Mira. Approval of the meeting notes is not approval of a new allocation of work. YOUR RUN RECORD Tool/workspace: Model/version shown (or unavailable): Date/time/time zone: Connections/settings: Attempt number: First output, unchanged: Review findings, checked against source: Correction prompt (if needed): Final output (or first output accepted unchanged): Human checks before use: Hands-on source preparation / prompting / review / correction time: Comparable manual baseline (if measured): ============================================================ EMAIL-DRAFT SOURCE E1 — Approved reply facts, September 16, 2026. North Alder Studio is requesting proposals from two suppliers. Mira will send the requirements brief by September 17. No supplier appointment, start date or discount is approved. Sam Lee is preparing the reply for Mira's review. E2 — Incoming supplier email, September 16, 2026. “Thanks, Sam. Can you confirm that we're appointed, work starts September 21 and a 10% discount is agreed?” EXACT PROMPT Draft Sam's reply using only E1 and E2. Use a subject and a body under 90 words, in a friendly, direct tone. State the confirmed next step. Do not confirm appointment, September 21 or a 10% discount. Put unresolved requests in a separate internal reviewer note, outside the email. Do not add a promise to call or provide an answer by an invented date. Draft only; do not send. REVIEWER REFERENCE — KEEP OUT OF THE PROMPT The external reply should say that proposals are being requested and Mira will send the brief by September 17. It should explain that appointment, the requested start date and the discount are unconfirmed. The internal note should flag all three requests for Mira. It should not invent a reason they were declined, because they have not been declined either. Watch for indirect promises: “We're excited to get started on the 21st” still commits to a date, even without the word “confirmed.” “We'll come back tomorrow” creates a new deadline. A friendly tone does not make either sentence supported. Once the facts are right, edit for the relationship. You may know that the recipient prefers a direct answer, or that a call would prevent a misunderstanding. Make that judgment yourself. Before sending, check recipients, attachments and whether an internal reviewer note has accidentally traveled into the message body. YOUR RUN RECORD Tool/workspace: Model/version shown (or unavailable): Date/time/time zone: Connections/settings: Attempt number: First output, unchanged: Review findings, checked against source: Correction prompt (if needed): Final output (or first output accepted unchanged): Human checks before use: Hands-on source preparation / prompting / review / correction time: Comparable manual baseline (if measured): Do not report an ideal answer as a real model result. If no error is found, say so. A few fictional exercises do not establish production reliability or a comparative winner. Official guidance checked September 10, 2026: https://developers.openai.com/cookbook/examples/chatgpt/chatgpt_prompt_guide/chatgpt_prompt_guide https://support.microsoft.com/en-us/outlook/copilot-pages/draft-an-email-message-with-copilot-in-outlook https://support.microsoft.com/en-us/outlook/copilot-pages/summarize-an-email-thread-with-copilot-in-outlook https://support.google.com/mail/answer/14355636?co=GENIE.Platform%3DDesktop&hl=en