Build a morning brief that is on your desk before you are

What a brief is for

A morning brief is not a report. Reports describe; a brief prepares. The test of a good one is brutal and simple: after three minutes of reading, do you know what today requires of you that yesterday did not? Everything in the brief either serves that test or gets cut.

The structure that follows from the test: exceptions first, always. The thing that changed, the thing that is late, the thing that needs a decision - before the schedule, before the numbers. A brief that opens with routine information trains you to skim it, and a skimmed brief is a dead brief. Yours will open with the two or three lines that would otherwise have ambushed you at 4pm.

Your AskEleven Employee assembles it from the systems you already run - inbox, calendar, books, bookings - on a schedule, in a fixed shape, every morning including the ones you are traveling. You will design it once with the prompts below, then spend two weeks tuning it against real mornings. After that it is simply how your day starts.

Before you start: decide what belongs

One decision session before any prompting. Go source by source and ask of each: what from here changes what I do today?

• The inbox (Gmail or Outlook). Not a summary of all mail - just what arrived overnight that needs you: new inquiries, replies you were waiting on, anything from a name on your VIP list.
• The calendar. Today's commitments, plus the look-ahead trap: anything tomorrow or this week that needs preparation today.
• The money (QuickBooks). Payments in and out since yesterday, invoices that crossed an aging threshold, anything unusual in size. Not the full P&L - the movement.
• The business's own pulse. Whatever system holds your forward book: OpenTable covers tonight and the weekend for a restaurant, the reservation system holds occupancy and arrivals for an inn, HubSpot holds the pipeline for a practice. Today's picture plus the pace against normal.
• The watch list. The quiet things you want an eye kept on: a client gone silent, a supplier cost, a review score, a hire's first week. This section is where the brief earns its keep, because these are exactly the things a busy human stops checking.

Connect each chosen source through your AskEleven dashboard before step 1. The brief can only be as good as what it can see.

Step 1: The design prompt

Design the brief as a fixed shape - same sections, same order, every day, so your eye learns where everything lives:

What to expect: a first draft built from your actual overnight data, which makes the tuning real instead of hypothetical. React specifically: "the covers number goes in the top line," "I do not need payments under $200 itemized," "add a flag when any invoice crosses 30 days." Every reaction becomes a standing rule. Expect the first draft to be too long - they always are - and cut without mercy toward the three-minute test.

Step 2: The schedule and the standing instruction

Now make it automatic:

What to expect: the reply-to-act loop quietly becomes the best part of the system. The brief stops being reading material and becomes a control surface: you read the line about the aging invoice, reply "chase it," and tomorrow's brief confirms the reminder went. The [still open, day 3] tag is deliberately mildly annoying - it is the brief keeping you honest, which is part of its job.

A worked example: Tuesday, 6:45am

A fourteen-room inn. Tuesday's brief, verbatim in shape:

NEEDS YOU (2): The Camden Row wedding party (7 rooms, first weekend of October) asked last night about a full buyout - above the auto-reply threshold, draft response ready for your review. Linen supplier's renewal is up Friday; the new rate is 9 percent over last year - approve or renegotiate. CHANGED OVERNIGHT: Two new bookings (Thursday, 2 nights; Saturday, 1 night). One cancellation for tonight - room resold from the waitlist by the concierge at 11pm. $3,840 in payments landed in QuickBooks. TODAY: Four arrivals, one flagged returning guest (third stay - the Meyers, garden room). Chimney inspection at 2pm. Tomorrow's food delivery needs the revised count by 5pm today. WATCHING: October pace now 71 percent of last year - third week below trend. The dishwasher repair invoice hit day 32. Numbers: cash $58,200; week ahead 81 percent booked, normal for the season.

Three minutes, and the owner knows the two decisions today actually contains - the buyout and the linen contract - plus the thing she would never have checked on her own: October is quietly soft, three weeks running, and it is still early enough to do something about it. She replies "chase the dishwasher invoice, and show me October week by week." Both are done before her second coffee. That reply line is the entire system working.

Quality tests

• The three-minute test. Time yourself for a week. Any brief over three minutes gets a cut - remove a whole item, do not compress everything into denser prose.
• The so-what test. For each line, ask: could this change what I do today? A line that fails three days running gets demoted to the weekly summary or deleted. Most first drafts carry two or three passengers.
• The ambush test. The real one. Each time something surprises you at 4pm, ask whether the brief could have seen it at 6:45. If the data existed in a connected system, add the rule; if the source is not connected, that is your case for connecting it. A quarter of ambush-driven tuning produces a brief that is genuinely hard to blindside.
• The truth test. Once in the first week, check three of the brief's numbers against the source systems yourself. Trust in the brief is total or it is nothing - a brief you feel you must verify is worse than no brief.

The tuning fortnight, and after

Give it two weeks of active tuning: read every brief with a critic's eye, reply with structural corrections as they occur to you ("weather goes above arrivals on turnover days," "stop reporting the pipeline on Mondays, HubSpot is stale from the weekend"), and let each correction become permanent. Briefs improve the way knives sharpen - a few strokes a day, and by week three there is nothing left to say.

Two habits after that. When the season changes, tell it - what you watch in October is not what you watch in June, and the WATCHING section should turn over accordingly. And once a quarter, ask for a meta-review: "Looking at ninety days of briefs, what did I consistently act on, what did I consistently ignore, and what would you change?" The answer is usually one deletion and one promotion - the brief slowly reshaping itself around how you actually run the business, which is the point. The first hour of the day goes back to being yours; the picture is waiting on the desk when you sit down.