home / use cases / scheduling and calendar / daily-agenda-briefing

A morning briefing with the context attached

Every morning your Aivell reads today's calendar, then does the homework for each meeting — the latest email exchange with the attendees, the client's file from the knowledge base, the open questions nobody answered. You get one short email per person before the day starts, prepared entirely behind your firewall.

Watch the demo

starts when: The Schedule fires at 7:00, before the first coffee

The problem

The first hour of the day is spent finding out what the day is. Calendar open in one window, inbox in another, the client folder somewhere else — reconstructing, for each meeting, what was last said and what you owe them. It is pure preparation, it produces nothing, and it repeats every single morning; researchers put 62% of employee time on repetitive tasks of exactly this shape.

Skipping it is worse. Walking into a client review without noticing their two unanswered emails is how trust erodes — the client remembers the question they asked; you meet them holding only a calendar entry that says their name.

How your Aivell does it

The homework still gets done — just not by you, and before you wake:

  1. The Schedule fires at 7:00. No trigger email, no button. The chore runs because it is morning.
  2. The day’s calendar is read for each recipient. Every meeting, its attendees, its location — plus a sanity check that flags overlaps and missing rooms at the top of the brief.
  3. The context is gathered per meeting. The latest thread with those attendees from the mailbox, the client’s file from the knowledge base — last decisions, open items, promises with your name on them.
  4. One short email per person. Under a page, in each recipient’s language, sorted by meeting time. Paolo’s version and yours describe the same day differently, because the chore says so.
  5. It lands before the coffee does. By 7:30 the reconstruction hour is already over, and it took nobody’s morning to produce.

The guardrails make it a reporter, not an actor: the calendar is read-only, the brief can reach exactly two inboxes, and the knowledge base folders it may quote are listed by name. What goes into the brief, and for whom, stays a paragraph of plain language you sharpen as the weeks go by.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · send the morning brief ● active

at 7 sharp, read today's calendar for me and for Paolo

for each meeting, find the latest email thread with the attendees

pull the client file from the knowledge base — open items, last decisions

flag anything owed — a document promised, a question left unanswered

overlapping meetings or a missing location go as a warning at the top

write one email per person — their meetings, their context, under a page

empty day? one line saying so, plus tomorrow's first appointment

deliver by 7:30 — Paolo's in Italian, mine in English

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Schedule kicks off the brief every workday
Calendar reads everyone's meetings for the day
Email digs up threads, delivers the brief
Knowledge Base pulls client files and open items

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Calendar Read-only in this chore. It reports the day; it never creates, moves or deletes anything.
Knowledge Base May cite only the client-files folder; HR and finance folders are not readable by this chore.
Email The brief goes to two named recipients. No other outbound mail from this chore, ever.

Questions, answered.

What kind of context actually shows up under each meeting? +

Whatever a good assistant would print out — the last email exchanged with those attendees, what was decided last time, what you promised and haven't sent, open invoices or deadlines from the client file. Enough to walk in current, not a dossier to wade through.

Isn't this just my calendar notifications, rearranged? +

No — notifications tell you when, the brief tells you what. The 9:30 slot saying "Bianchi review" is useless; the brief under it saying "they asked twice about the revised offer, you owe them the draft since Tuesday" is the part that saves the meeting.

The brief reads my mail and client files. Where does that happen? +

On the box, in your office. Mail stays on your mail server, files stay in your knowledge base, and the model that reads and summarizes them runs onboard. Nothing about your clients or your inbox is sent to any outside service to write a summary.

Can different people get differently shaped briefs? +

Yes. The chore says who gets what, in which language, at what depth — Paolo wants one line per meeting in Italian, you want open items in English. It is plain language, so each person's format is a sentence.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee