Morning Briefing Email: What to Put In It and How to Set It Up
Morning Briefing Email: What to Put In It and How to Set It Up

A good morning briefing email is a one-screen plan for your day, not a news digest. It pulls from your calendar, your inbox and the promises you have made, then ranks them so you know what to do first. This guide covers what belongs in it, how long it should be, how to set it up this week, and where a human still has to decide.
TL;DR
- Build the briefing around three questions: what is on my calendar, what needs a reply today, and what are the 3 most important things to move forward.
- Keep it to one screen or a 2 to 4 minute read, in a stable layout you can scan in seconds.
- Include commitments you made out loud in meetings, not only what sits in your inbox and calendar.
- Let the briefing suggest actions, but keep sending, scheduling and task creation behind your approval.
- Tune it for a week, then leave it on a schedule.
Table of Contents
- What a morning briefing email actually is
- What to include: four sections that earn their place
- How long it should be
- A layout you can steal
- How a briefing connects calendar, email and follow-ups
- Set one up in five steps
- Why a briefing built from one tool falls short
- Permissions, privacy and accuracy
- Perspective
- Where Otto fits
- FAQ
- Sources
What a morning briefing email actually is
Two things share this name. The first is a newsletter from a publisher: top stories, delivered at dawn. The second is a personal briefing about your own work, and that is the one this article is about. It answers a single question: what should I focus on today?
The personal version only works if it sees across your tools. Your calendar knows when you are busy. Your inbox knows who is waiting on you. Your meeting notes know what you promised on a call. A briefing that reads only one of those is a partial view, and you end up filling the gaps from memory.
What to include: four sections that earn their place
Start from a proven structure rather than a blank page. The University of Maryland’s AI Leadership Training exercise specifies a briefing with four sections and a total reading time of 2 to 4 minutes:
- Today’s meetings, in chronological order, with a sentence or two on each and flags for decisions, personnel matters, or budget.
- Priority emails, marked as needing a reply today, same-day awareness, or follow-up this week.
- Items to watch, such as recurring themes and approaching deadlines.
- Top priorities today, ending with the 3 to 5 most important actions.
The last block is the one that matters. Everything above it is context. This is the part that tells you what to do.
Add commitments at risk
Most briefings stop at schedule and inbox. The more useful ones add a block for promises. A Consultevo guide on AI morning briefs suggests including commitments at risk, one to three highest-leverage priorities, blockers and waiting points, calendar pressure, and a recommended first action. It describes the ideal result as a sharp two-minute handoff.
That “commitments at risk” block is where most people lose out. A promise made in a meeting (“I’ll send you the revised numbers Thursday”) never appears in your inbox until you write the email. If nothing captured it, nothing will remind you.
Add what changed since yesterday
The Scrum.org post Use AI to Plan Your Day recommends starting each morning with three requests: summarize what changed since yesterday, grouped as Actions for me, FYI and Risks; identify the top 3 priorities with a recommended next step for each; and list commitments due today or this week with owner and deadline. Grouping by action type is a small change with a big effect, because it separates what needs you from what only needs your awareness.
How long it should be
Short enough that you read it. The sources above land in a narrow range:
| Format | Suggested limit | Source idea |
|---|---|---|
| Executive briefing | 2 to 4 minute read | University of Maryland exercise |
| Personal brief | Two-minute handoff | Consultevo guide |
| Agent-built brief | At most 12 lines | Lastres guide |
| Daily focus briefing | One screen | TLDL guide |
If yours runs longer, cut. A briefing you skim past on day three has failed, however complete it is.
A layout you can steal
The TLDL guide recommends a stable three-block output: Today (what is scheduled), Needs you (the smallest set of actions that unblock the day), and FYI (one watch item, at most). Stability matters as much as brevity. When the layout never changes, your eye learns where to look.
Here is a version that adds the commitment ledger:
- Today: meetings in order, each with one line of prep and a flag if a decision is expected.
- Needs you: replies due today, promises due today or overdue, and anything someone is waiting on.
- Top 3: the three things that move your most important work forward, each with a suggested first step.
- Watch: one item at most, such as a deadline later this week or a thread going quiet.
How a briefing connects calendar, email and follow-ups
The order of operations matters. According to the Agent Stack Library guide, a good briefing reads the calendar first to set the structure of the day, then scans email for changes that affect it. It links messages to meetings by participant or project name, pulls prep notes for each important event, and puts conflicts and waiting items above general summaries. The output is a ranked plan, not a raw digest.

Ranking is where tools differ. One open-source example, the RheingoldAI daily briefing agent, sorts action items into four tiers: Critical for explicit deadlines, High for requests from leadership or items appearing in several channels, Medium for recent unresolved items, and Low for the rest. You can borrow the tiers for a manual routine. An item that shows up in your calendar, your inbox and a meeting is almost always more urgent than one that shows up once.
If your team works mainly in Microsoft’s suite, what Microsoft 365 includes shows which calendar, mail and chat sources a briefing could draw from.
Set one up in five steps
- Write your three questions. Lastres suggests fixing them in advance: what is on my calendar and what needs prep, which messages need a reply today, and what are the three most important things to move forward.
- Pick the calendar as your main input. TLDL explains why: it is already curated and bounded by time. Add one enrichment source, such as yesterday’s open loops.
- Choose a delivery time you can tolerate. The University of Maryland exercise schedules its briefing for 6:30 AM on weekdays. Pick whatever time lands before you open your inbox, not after.
- Cap the length. One screen. Decide now what gets cut when it runs long.
- Correct it for a week. Each day, note what was missing and what was noise, then adjust. After a week, leave it on schedule.
Getting the email to arrive reliably without burying you is a delivery problem as much as a content one. Email automations that run on schedule cover the same principle: a few well-timed messages beat a flood.
A prompt to start with
If you are building this by hand with an AI assistant that has read-only access, adapt the Scrum.org approach:
From my email and calendar, summarize what changed since yesterday, grouped as Actions for me, FYI and Risks. List my top 3 priorities today with a recommended next step for each. List deliverables or commitments due today or this week, with owner and deadline. Use bullet points and as few words as possible.
The result will be decent. It will also be limited by what the assistant can see, which brings us to the main weakness of any briefing.
Why a briefing built from one tool falls short
A briefing is only as good as its inputs. An AI notetaker summarizes your meetings but has never seen your inbox. An email assistant sorts your messages but does not know what you said on a call. A contact tool knows people but not your schedule. Each is useful inside its box, and each leaves you to join the pieces yourself.
That joining is real work. Agent Sidequests’ guide to AI morning briefings makes a practical point: keep a register behind the brief with one row per action, including a stable ID, agreed owner, next action, confirmed deadline, status, source references, last-checked time and completion evidence. It also advises reporting what was excluded, so a tidy page does not imply complete coverage. Both ideas describe a ledger, and a ledger needs one place that sees everything.
For more on closing the loop after a meeting, see our guide to AI meeting summaries that map notes to tasks and our piece on stopping missed follow-ups.

Permissions, privacy and accuracy
A briefing reads your most sensitive data, so set it up carefully.
Grant the narrowest access that works. Google’s documentation on Gmail API scopes lists separate scopes for viewing messages and for sending email on your behalf, and flags the broadest ones as restricted. Read access is enough to build a briefing. Sending should be a separate decision.
Put a human before every outbound action. The Agent Stack Library guide puts the review point before creating tasks, sending replies or changing calendar events. It suggests starting with suggestions and only allowing automatic task creation for low-risk commitments with a clear owner and due date, once the briefing proves reliable.
Check the briefing against the source. For the first weeks, open the original email or meeting note behind any item you act on. If you see a wrong deadline or a misattributed promise, correct the setup. Our checklist on AI email mistakes to catch before you send covers the same habit for drafts.
Keep your own judgment in the loop. Consultevo’s author argues a brief should support judgment, not replace it. Some context is always human: a delicate client relationship, a strategic worry, your own energy that day. The brief narrows the decision. You still make it.
Perspective
We built Otto because the briefing problem is really a memory problem. Most tools write a decent summary of the box they live in. The trouble is that your day does not respect those boxes, so you become the person copying context from one tool to the next.
Our view is that the useful morning answer comes from one shared memory: email, calendar, meetings and commitments together. When Otto listens in a meeting, reads your inbox and calendar, and records every promise into a single ledger it keeps chasing until it is closed, the question “what should I focus on today?” can finally be answered from the full picture.
We also think approval is non-negotiable. Otto drafts, you decide. Nothing is sent or finalized without your explicit sign-off, which is what lets you trust a briefing enough to act on it before your first coffee is cold.
Eddie
Where Otto fits
Otto is an AI chief of staff for founders, operators and chiefs of staff whose work is scattered across many tools. It reads email and calendar, listens in meetings, captures promises into one ledger, and helps you decide what to focus on each morning. It integrates with over 130 tools, including Gmail, Google Calendar, Slack, Notion, GitHub and Todoist.
Plans, as published on our site: Free at $0 per month, Upgraded at $20 per month, and Max at $50 per month. You can start with Otto on the free plan and see what your first briefing looks like.

If you want templates for an assistant or chief of staff to run for someone else, our executive daily briefing playbook has three. To see how the pieces connect, read about email triage with calendars linked and reminders versus tasks for founders.
FAQ
What should a morning briefing email include?
At minimum: today’s meetings with a line of prep each, the emails that need a reply today, commitments due or at risk, and the top 3 priorities with a suggested first step. Add one watch item for something coming later in the week. Cut anything that does not change what you do first.
How long should a daily briefing email be?
One screen, or a read of two to four minutes. The sources we reviewed range from a two-minute handoff to a 12-line limit. If you keep scrolling, it is too long.
Can an AI morning briefing send emails or change my calendar for me?
It can draft, but the safer pattern is to keep sending replies, creating tasks and changing events behind your approval. Start with suggestions and loosen that only for low-risk items with a clear owner and date. In Otto, nothing goes out without your explicit approval.
What time should the briefing arrive?
Whenever you will read it before opening your inbox. One example exercise schedules it for 6:30 AM on weekdays. Pick a time you can keep, run it for a week, and adjust.
Sources
- Daily Briefing Exercise, AI Leadership Training (University of Maryland)
- Use AI to Plan Your Day (Scrum.org)
- How to Build an AI Morning Brief That Actually Changes the Day (Consultevo)
- How to Build a Morning Briefing Agent with Claude Code (Lastres)
- AI Morning Briefing That Doesn’t Turn Into Doomscrolling (TLDL)
- AI Daily Briefing from Email and Calendar (Agent Stack Library)
- RheingoldAI daily-briefing-agent (GitHub)
- AI morning briefing: email, calendar, notes and unfinished work (Agent Sidequests)
- Choose Gmail API scopes (Google for Developers)