A useful AI daily briefing tells you what deserves attention today, what changed and what is still uncertain. If it merely repeats every appointment and unread message, you have another inbox to process before starting work.
The design problem is deciding what earns a place in the brief. A changed meeting can matter more than a new message. An unanswered approval can matter more than a full calendar. And a missing data source can matter more than a reassuring sentence saying everything is clear.
Build the brief around decisions you will make in the next day. The example below is illustrative; it is not an actual Today output or a measured customer result.
Set the Window Before Choosing the Content
“Today” needs a date and time zone. Specify the local day you want covered, especially when traveling or working with people elsewhere. Also distinguish when the brief is prepared from the time range it describes. A brief prepared at 8:00 cannot account for a reply that arrives at 8:15 unless it is refreshed.
Give the assistant a short source list: the relevant calendar, selected conversations and a small set of current priorities. Include the previous brief only if you want a comparison. Without a prior snapshot or other reliable change history, the assistant can report the current situation, but it should not claim to know what changed overnight.
Decide how far ahead to look for preparation. A brief can cover today's commitments while mentioning tomorrow's deadline when work must begin now. That is different from filling the page with everything happening this month.
Rank Consequences, Not Message Volume
An effective brief does not need a complicated scoring system. Give it a few concrete priorities: protect the submission deadline, prepare for the client review, leave a lunch break and avoid moving an agreed appointment without asking.
Then have it explain why an item matters. “Review deck before 11:00 because the client meeting moved to 14:00” is actionable. “You have a busy day” is not. If two items compete, the assistant should expose the tradeoff: a review may fit before the meeting only if the optional research block moves.
Keep an important distinction visible throughout: a confirmed commitment is evidence about your schedule; a recommended priority is a judgment about how to use it. The brief can make that judgment useful by stating its reason, but it should not disguise a suggestion as something you already agreed to do.
A Worked Morning Brief
Imagine this fictional situation. Your calendar shows a client review at 14:00 and a protected writing block at 10:00. A selected email thread confirms that the client review moved from 16:00. Your project note says the proposal needs an approved pricing sheet before submission tomorrow. The latest thread contains a request for approval, but no approval response. Your personal calendar could not be checked.
Here is a compact brief built from those inputs:
Thursday, October 8 — Europe/London. Prepared at 08:00. The decision today: Finish a reviewable proposal before the 14:00 client call. Pricing approval is still unconfirmed in the supplied thread. Changed: The client review moved from 16:00 to 14:00. The latest invitation and client reply agree on the new time. Prepare: Use part of the 10:00 writing block to check the proposal. This is a suggestion, not a calendar change. Waiting on: Pricing approval. Consider asking for an update before completing the pricing section; no reminder has been sent. Not checked: Personal calendar unavailable. This brief cannot confirm that the proposed work block is free of personal commitments.
The brief stays short by omitting routine messages and unchanged background. It still preserves the uncertainty that could alter the plan. A real version should include links or source references next to the meeting change and approval status when the tool can provide them.
Notice that “approval unconfirmed” is narrower than “approval has not happened.” The latter would require checking every place an approval could have arrived. A useful brief makes its evidence boundary legible.
Ask for the Format, Not Just a Summary
You can adapt this request for an assistant that can read your supplied or connected sources:
Prepare a daily brief for [date] in [time zone], using [sources]. My priorities are [priorities]. Cover today's commitments and anything I must prepare today for tomorrow. Lead with the decision that most needs my attention. Separate confirmed events, proposed priorities and unresolved questions. Compare with [previous brief] only where the sources support a change. Include the source for important dates and decisions. List unavailable or outdated sources. Do not send messages or move events. Keep it short enough to review before I start work.
If the result is still too long, exclude categories explicitly. “Leave out newsletters and routine confirmations unless they change today's plan” gives the assistant a better rule than “be concise.” If it keeps overlooking a recurring responsibility, add the relevant source or priority rather than asking for a more comprehensive summary of everything.
Handle Quiet Days and Broken Inputs Differently
A quiet day can produce a very short brief: no material changes, one confirmed commitment and one optional focus suggestion. The assistant should not invent urgency to justify its output.
A failed input is different. If the calendar cannot be read, the brief should say so and avoid asserting there are no conflicts. If an email source is stale, identify the last checked period when known. If the whole run fails, an old brief should not appear to be today's plan simply because its layout still looks current.
Before relying on a recurring brief, deliberately try a missing-source case. Does the output preserve the gap, or fill it with a plausible story? This small check tells you something a polished normal-day example cannot.
Decide When Another Brief Is Worth Reading
Start with an on-demand version so you can refine the contents. If the assistant supports scheduled runs, choose a time when the brief will influence a decision, not merely when a notification is convenient. Confirm the schedule's time zone and reconsider it when you travel.
An afternoon refresh should earn its interruption. A canceled appointment, a changed deadline or a reply that unblocks today's work may justify one. A routine message usually does not. Define that threshold explicitly if your tool supports change-based checks; otherwise request a refresh when you need it.
Generation, delivery and reading are separate events. A system may prepare a brief without sending a notification, or send a notification you never see. During setup, check where the result actually appears and what you will do if the expected brief is missing.
Making the Brief Personal in Today
Today offers personal briefs that can draw on relevant context and authorized information. Our introduction to Today provides the broader product context; the design above is a suggested way to shape a brief, not a promise that every field is a configurable setting in every client.
Begin by asking Today for one day's brief using a few confirmed priorities. Review its selection before making the routine recurring. Check the timing and result in the controls available to you, and do not assume an absent notification means nothing needs attention.
After several runs, ask a practical question: did the brief change a decision or help you prepare? Keep the parts that did. Remove the parts you skimmed repeatedly. The right brief is the smallest one that still protects the decisions your day depends on.