Skip to content
OperatorNest

Daily morning brief from your open work

Get a daily brief of completed work, urgent decisions, schedule changes, and source links at the time you choose, with gaps called out.

Copy-ready brief

Every workday at [local time], send me a morning brief in [channel]. Check [calendar], [inbox scope], [task list], and receipts from work completed since my last brief. Keep it under [word limit]. Use four sections: completed, today, decisions waiting, and blocked or unknown. Give the source or receipt link for each material item. Distinguish a draft from a sent action. If a source is unavailable, name the gap and do not imply that the check completed. Hold any new send, booking, or deletion for my approval.

Illustrative example

Example output

Example brief for illustration only:
Completed: Research shortlist drafted overnight. Three candidate records are linked; no outreach sent.
Today: Brackenwold Studio call at 14:00. Meeting brief is ready from calendar and the prior email thread.
Decisions waiting: Approve or edit two follow-up drafts. Recipients and full text are attached.
Blocked: Invoice source did not respond at 06:45. No payment status is claimed; retry set for 07:15.
Receipt: [task receipt link].

Trigger and cadence

Trigger
The daily delivery time arrives.
Cadence
Every workday at the reader's chosen local time.

Inputs

  • Calendar, selected inbox scope, and active task list.
  • Overnight task receipts and items waiting for approval.
  • Priority people, deadlines, and brief length.

Steps

  • Read the named sources and recent task outcomes.
  • Separate completed work from pending decisions and blocked items.
  • Check today's calendar and deadlines for changes.
  • Link each important item to its source or task receipt.
  • Deliver the brief in the selected channel at the set time.

Approval boundary

The brief may report work; any proposed send, booking, or deletion stays held.

Stop conditions

  • A connected source is unavailable and its status would affect a claim.
  • A task says complete but lacks a receipt or verifiable output.
  • An item requires a decision outside the reader's standing rules.

Expected output

A short morning brief with completed work, today's commitments, decisions, and gaps.

Receipt fields

  • Sources checked and time of the brief.
  • Tasks included, held actions, missing sources, and delivery status.

Recovery when it fails

  • Deliver a partial brief with named gaps when one source fails.
  • Send a corrected brief only when a material item changes, clearly labeled as a correction.
On this page

A brief that tells you what happened and what needs you

A daily morning brief should separate completed work from decisions that still need you. It should also show today’s commitments and any source that could not be checked. OperatorNest can gather those items on a schedule and send a concise result at your chosen time. The example output is illustrative, not a captured task run.

Give the brief a clear boundary. A calendar check, a selected inbox label, and recent task receipts may be enough. Adding every message, document, and web page makes the result hard to scan. Name the sources that answer your morning questions.

Put status ahead of activity

“Researched 18 pages” describes effort. “Shortlist ready with three candidates and two verification gaps” tells you what you can use. The brief should lead with finished outputs and point to the receipt for detailed steps. When a task stopped, say where it stopped and what decision would restart it.

For example, Sam asks for a 7:00 brief. An overnight research task finished a shortlist, two follow-up messages are drafted, and a payment source failed at 6:45. The brief should mark the shortlist complete, the messages held, and the payment status unknown. It should not compress those three states into “all tasks handled.”

Today’s section should include commitments that changed since the last brief. A moved meeting, a due date, or an unanswered request from a priority contact may belong there. A calendar item with no change can be a simple line. The goal is a morning reading surface, not a second copy of the calendar.

Keep every decision visible

Place approval requests in one section with the action, destination, and link to the full proposal. “Two messages waiting” is insufficient when one is to a client and the other is to a colleague. The brief should make it possible to choose which decision to open first, while the full message remains available for review.

The approvals feature explains where your operator pauses. In this workflow, the brief reports those pauses; it does not approve them. A send, booking, deletion, or other consequential step remains held until you decide.

Name gaps and correct material errors

A source can fail, return partial data, or disagree with a task’s status. Record that in the blocked or unknown section. If the inbox check failed, say when it failed and when it will retry. Avoid “no urgent email” unless the inbox check completed.

If a late retry changes an important item, send a correction labeled as such. For example, “Correction to 7:00 brief: the invoice check completed at 7:15 and found one overdue item.” Minor details can remain in the receipt. A second unlabeled brief would leave the reader unsure which version to trust.

Review the brief after a few days. Remove sections that never help a decision and add a source only when its absence caused a real gap. A brief stays useful when it reflects the work you delegate and the actions you still own.

Run it on a schedule

Plan the timing and missed-run behavior with the recurring task planner. For documented schedule controls across assistants, read scheduled AI tasks compared.

  • Recurring task planner

    Map repeat work to a week or month, estimate monthly hours, decide what to delegate, and download calendar events with recurrence rules.

  • AI task brief generator

    Turn a rough request into a task brief with a goal, needed inputs, steps, approval points, receipt details, and a repeat schedule.

  • AI agent receipt template

    Make a task receipt with the request, actions, sources, approvals, uncertain steps, result, model usage, and cost. Copy or download it.

Common questions

Should every overnight event appear in the brief?

No. Put completed outcomes, decisions, and failures in the brief. Keep routine steps in the linked receipts.

What if one connected source is down?

Deliver the parts that can be verified and name the missing source. Do not describe an unchecked inbox or payment record as clear.

Can the brief include drafts awaiting approval?

Yes. Label each draft as held, show the recipient or destination, and keep the actual action separate from the brief.

Hand off your first task tonight.

Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.