Build a source-checked client brief from iCloud Mail and Calendar

A useful meeting brief answers four questions: what is confirmed, what is due, what needs a decision, and where each statement came from. This proposed exercise is for consultants and small teams using iCloud. It has not been tested with your account.

OpenAI announced iCloud Mail and Calendar plugins on October 27, 2026, available across ChatGPT plans on web, desktop, and iOS. They support finding messages, reviewing schedules, and updating calendar events. This tutorial uses an existing connection for research and drafting; changing an event is a separate decision.

1. Connect the intended services

Open Settings → Plugins, choose iCloud Mail or Calendar, and follow the connection prompts. Connect the services separately if you need both. Use an Apple app-specific password only in the connection form. Mail needs your iCloud Mail address; Calendar needs your primary Apple Account email, which may differ. Never paste a password into a chat.

Follow the linked official connection instructions for your account. If the plugin is unavailable, check plan, region, surface, and workspace permissions. Use authorized information, or practice with a fictional packet instead of connecting a client account.

2. Define a narrow brief

Choose one client, one meeting, and a specific date range. State the intended account and timezone. For example: “Prepare a brief for the example Acorn Studio review on December 1, 2026 at 2 p.m. America/New_York, using relevant messages from the previous 14 days.” This is a fictional teaching example, not a real appointment.

3. Gather evidence before summarizing

Ask ChatGPT to find relevant correspondence and the matching event, then list the sources and dates. Open the important messages yourself. Check the latest reply, invite status, location or call link, and any revised commitments. If the meeting cannot be found, record that gap instead of accepting a guessed event.

4. Draft the one-page brief

Using only the relevant messages and calendar event from the account and date range I specify, prepare a one-page client brief. Include confirmed meeting details and timezone, agreed deliverables, stated deadlines, unresolved questions, and proposed discussion points. For each factual item, include an available source link or message subject and date. Separate explicit commitments from your suggestions. Flag conflicts and missing evidence. Do not send messages or create, edit, or delete events.

5. Review each commitment

Use this checklist before sharing:

• The client and provider account are correct.
• The meeting date, time, timezone, and invite status match the event.
• Every deadline points to an explicit statement.
• Superseded messages are identified.
• Unanswered questions remain questions.
• Suggestions are labeled and do not imply client approval.
• The final brief contains only information its audience needs.

A fictional conflict worth practicing

An earlier message asks for a December 4 draft, a later reply says the date is still under review, and the calendar contains a December 1 check-in. The correct brief keeps the check-in separate from the unconfirmed draft deadline. It should ask for a decision, not promote the older date into a promise.

6. Save a useful handoff

Keep the reviewed brief in your normal project workspace with its review date and owner. Use a simple structure: meeting details; confirmed commitments; unresolved questions; proposed agenda; sources. Share it only after checking the intended audience. Treat any invitation change or email send as its own reviewed action.

Connecting services does not guarantee that every relevant record will be retrieved or interpreted correctly. This exercise depends on source review, particularly for cancellations, forwarded threads, and conflicting dates.

For a practice packet without connecting an account, try the free client handoff workshop. For help adapting the process to real work, bring one recurring meeting-preparation task to an AI Teachers working session.