Imagine waking up to a tidy summary already waiting in your inbox — your calendar for the day, the emails that actually matter, the one task you need to push forward, and the weather so you dress right. No scrolling. No digging. Just the signal, no noise. Here's how to set that up.
Before touching any tool, write down the 3–5 things you want to know every morning. Be specific. "What's happening today" is too vague. "My calendar events and anything due by noon" is actionable.
The most useful morning briefings cover some combination of these:
Start with 3 sections. You can always add more. Briefings that try to cover everything become walls of text you stop reading. Pick the 3 things that, if you knew them before anything else, would make your day go better.
Your AI assistant can only summarize information it can actually reach. Here's what "connecting a source" looks like in plain terms — it's just giving your assistant read access to the right places.
Most AI assistant platforms connect directly to Google Calendar or Outlook Calendar. You'll log in once and authorize it. After that, your assistant can read your upcoming events whenever it runs.
Similarly, you'll connect Gmail or Outlook and tell the assistant which emails matter. A useful filter: "emails from anyone I've replied to in the last 30 days" or "emails with the words urgent, invoice, or decision." You don't need to read everything — just flag the ones that need you.
If you use Todoist, Notion, or a similar tool, most platforms can connect to these as well. If you keep a simpler list — even just a text file or a notes app — you can paste it in manually each week as a standing reference.
Each connected source adds complexity and potential confusion. If your assistant can see your entire email archive, it might surface things you don't care about. Start narrow — just the last 24 hours of email and today's calendar — then expand if you need more.
This is the part most people overthink. You don't need to be technical. You just need to write clear instructions, the same way you'd explain the job to a smart new assistant on their first day.
Here's a real example of instructions you could paste in and start with:
Notice what this does well: it tells the assistant exactly what to check, exactly what to include, how to format it, and how long to make it. The more specific you are, the better the output.
Your briefing should arrive before you start your day — not after you've already started reacting to things. For most people that's somewhere between 6:00 and 7:30 AM.
Think about your actual morning rhythm:
The goal is that when you look at it, you're in "absorb information" mode, not already in "respond to chaos" mode. Earlier is usually better.
Consider a lighter version on weekends — just calendar events, no email summary. You don't need work information on a Saturday morning. Set up two schedules: one for weekdays, one for weekends.
Where do you want to receive your briefing? You have a few options, and the best one is wherever you naturally look first thing in the morning.
Your briefing arrives as an email, usually from your assistant's own address. Easy to archive, search, and reference later. Works well if your inbox is the first thing you open.
If you use Slack for work, a message from your assistant waiting in a dedicated channel can feel less cluttered than email. Some people set up a private "briefings" channel just for this.
Some platforms can push the briefing as a notification. This works well if your morning check-in happens on your phone. Be careful though — notifications can interrupt a routine rather than anchor it.
Some people prefer to open a web page or app as part of their morning ritual, rather than having things pushed to them. If that's you, most platforms can write the briefing to a page you visit on your own schedule.
Run your briefing for one week before deciding if it's working. The first version is almost never perfect, and that's fine. Watch for these common issues:
After a week, you'll know exactly what to adjust. Most people land on a version they like within two or three iterations.
You find yourself looking forward to your briefing — because it reliably tells you something useful before you've had to figure it out yourself. That's the goal. Not automation for its own sake, but starting your day already oriented.
Here's a realistic example of what your AI assistant might deliver at 6:45 AM on a Tuesday:
That's 180 words. Takes 45 seconds to read. And you walk into your day knowing exactly what matters.
A briefing that takes more than 2 minutes to read defeats the purpose. If you find yourself skimming it, it's too long. Cut the sections you're skimming — they're not adding value.
Spend one week writing your ideal briefing by hand. Every morning, jot down the 3–5 things you wish you'd known at the start of the day. After a week, you'll have a clear picture of what to automate — and your instructions will be much sharper.
Your briefing should evolve as your life does. Check in once a month: is it still covering what matters? Did something new become important? Spend 5 minutes updating your instructions. It takes less time than a week of mediocre briefings.
The Library includes tested morning briefing setups you can copy, paste, and adjust in minutes — plus dozens of other AI assistant playbooks for email triage, weekly reviews, and more.
Get Library Access — $9/mo →