How to set up an AI morning briefing from email, calendar and notes

Choose the sources and the finish

Start with one calendar, selected mailbox labels or threads, and five recent meeting notes. Ask the assistant to demonstrate that it can read each source and save a private register. File creation, persistent storage, scheduling and delivery are separate requirements. If a connection is unavailable, supply an export and identify its cutoff time.

Request a two-page brief with today's commitments, three priorities, decisions you owe, unfinished work and meaningful changes. Limit the first pass to 30 relevant threads. Report excluded material so a tidy PDF does not imply complete coverage. Keep source instructions as information to analyze; they cannot expand the routine's permissions.

Define what 6am means

Specify briefing days and a named timezone, such as America/Denver. Decide whether travel changes that timezone. Distinguish a 6am start from a brief ready for review at 6am; the latter needs a supported earlier start and an honest allowance for processing. Confirm the saved schedule and notification destination.

Use today's calendar plus deadlines in the next seven days. Check email and notes from each source's last successful cutoff, with a small overlap to catch boundary items; deduplication removes repeats. Google’s Gmail search guide warns that date-only API searches use Pacific Standard Time. Ask for explicit time boundaries in your chosen timezone and have the tool translate them correctly.

OpenAI’s dot help guide documents recurring checks and a Scheduled view. That is a place to verify a saved task, not a guarantee of this workflow's exact timing or source access. Without a supported scheduler, keep a manual morning run.

Keep a register behind the brief

Use one row per action, with a stable ID, agreed owner, next action, confirmed deadline or suggested review date, status, source references, last checked time and completion evidence. Keep the full register outside the PDF. Something omitted from today's two pages must remain in the record.

Use open, waiting, blocked, completed, canceled and parked states. Waiting describes a dependency; blocked describes an obstacle. Preserve completed and canceled records. Parked work stays outside the daily priority list until its agreed review date. The miniature below is illustrative, not an observed execution.

Merge three mentions into one action

Imagine an email requesting a proposal, a meeting note repeating that request, and a forwarded copy of the email. Google’s Gmail message reference documents message and conversation identifiers; use them when exposed. Across email and notes, compare the actual deliverable, owner and agreed timing. Similar subject lines alone do not establish a duplicate.

1. Match the three mentions to A-17 and retain all source references. Keep a separate action if one asks for a different deliverable.
2. Read the latest explicit agreement. If the email says Thursday and the note says Friday, show the conflict until resolved; do not choose the newest timestamp mechanically.
3. Carry A-17 forward with its next move. Ask for completion confirmation when evidence is ambiguous. A past meeting, an archived thread or silence cannot close it.
4. When you confirm completion, record who confirmed it, when and the supporting reference. An old forward cannot reopen it. Link genuinely new revision work to A-17 and explain why it is new.

Keep missing sources visibly missing

Record each source's last successful check separately. If notes cannot load today, mark their coverage stale and retain the earlier cutoff for the next attempt. Email can still advance if its check succeeded. Do not report no changes for a source you could not inspect, or silently clear actions because their source disappeared.

Recheck today's events before publishing. Google’s Calendar event reference distinguishes canceled events and individual recurring occurrences. A moved meeting should update the relevant occurrence; a cancellation should remove the commitment from today's agenda while preserving unresolved follow-up work. Keep conflicting or inaccessible event details visible.

Separate the PDF from its delivery

An illustrative miniature could read: 9am proposal review — calendar C-4; priority A-17 — confirm scope before sending; waiting A-18 — no new figures; completed A-12 — confirmed yesterday; coverage — email and calendar checked 5:45am, notes last checked yesterday. In a real brief, each label should open the approved private source.

Save a dated PDF and verify that it opens. If PDF creation fails, return a readable document or message with the same content and coverage warning. If delivery fails, retain the artifact and report that failure. Confirm the private recipient before enabling automatic delivery; do not substitute a different address or channel.

Keep one run record per briefing date and destination, including artifact and delivery status. Check it before retrying so a failed notification does not create duplicate briefs. A saved file, an email accepted for sending and confirmed delivery are different states.

Check a small trial before relying on it

Try one repeated thread, one completed action, one moved event and one inaccessible note. Inspect whether the brief merges, preserves, updates and flags them correctly. These are proposed checks, not results reproduced across assistants. Use the morning-briefing prompt below to start; add inbox drafting or meeting preparation only when you want those separate outcomes.