Automation for assistants and chiefs of staff · Runs every Friday at 14:00
Commitments to your principal
Open commitments made by or owed to your principal this week. Your assistant runs it every Friday at 14:00 and tells you when something needs your attention.
Commitments to your principal — Sep 18
Automation run • Sep 18
Commitments to your principal
Output
Sol, here is the commitments breakdown for Maya Calder and Harbor & Pine based on this week's Granola meeting notes cross-referenced against your Google Workspace sent mail.
Three commitments remain open as of Friday, September 18.
| Direction | Person | Commitment | Due Date | Status |
|---|---|---|---|---|
| Owed to Maya | Hale Morrow | Share board feedback on Q4 goals doc | Sep 17, 2026 | Overdue |
| Owed by Sol | Cal Brook | Send wholesale terms for Driftline Supply Co | Sep 16, 2026 | Overdue |
| Owed to Maya | Lena Vale | Confirm Mossbank Textiles fabric lead times | Sep 18, 2026 | Due today |
Details and verification
- Hale Morrow (Larchmont Ventures): In Monday's board sync, Hale agreed to review the Q4 goals doc and send notes by yesterday. No reply appears in your mail records.
- Cal Brook (Wholesale): During the sales pipeline review, you agreed to provide Cal with terms for the $18,400 Driftline Supply Co proposal. Your sent mailbox shows no message sent to Cal on this topic since September 14.
- Lena Vale (Operations): Lena agreed in the Monday buying review to check with Ada Fern regarding fabric restock dates. Lena has not sent an update today.
Uncertain item flagged
- Juno Pell (Recruiting): Juno mentioned sharing interview notes for the store manager search after meeting Dara Finch. The transcript records no firm deadline, but no follow-up message exists.
Automation steps. Your assistant follows these 5 steps each time it runs, using your connected email and calendar.
- 01
Each Friday afternoon, go through this week's meeting notes and transcripts and pull every commitment made: who owes what to whom, and by when.
- 02
Cover commitments I made and those made to my principal that I'm responsible for chasing.
- 03
Cross-check my sent email so anything already done drops off, and don't count a loop closed unless the mail proves it.
- 04
Rank what's left by how overdue it is and how much the relationship matters.
- 05
When unsure whether something was a real commitment, keep it and flag it.
Adjust the automation in chat
Tell your assistant what to do differently and it sets up that version for you.
- Only track commitments where the due date has already passed.
- Include commitments recorded in Fireflies instead of Granola.
- Flag any commitment involving board members as high priority.
Results arrive as a message from your assistant. Each run posts to your conversation with your assistant, and can email you too. The automation keeps a log in your knowledge base and reads it before each run to see what has changed.
Adjustable schedule
Runs every Friday at 14:00 by default. Pick another time when you add it, or ask in chat for a custom schedule.
Only useful reports
When nothing needs attention, the run says so in a line or stays quiet. When there are findings, you get them with a link to the full run.
What it does on its own
Reviews notes and sent mail to report open loops. Changes nothing and sends no messages. An automated run has no tool that sends, posts, shares, or deletes anything.
This automation reads your email and calendar. Connect Google Workspace or Microsoft 365 to Fieldwork. The automation uses whichever you connect. It also uses your meeting notes when connected.
More automations for assistants and chiefs of staff.
Questions about this automation.
- How do I set this up?
- Open your assistant on the Agents page in Fieldwork, locate this automation in the job library, and select Add. You can connect Google Workspace and your Granola account directly from the card, with the run schedule set to Fridays at 2:00 PM.
- What does it do on its own versus what waits for me?
- It reviews your meeting notes and sent messages to list unresolved obligations. It never sends emails, replies to colleagues, deletes threads, or modifies your calendar.
- Where do results arrive?
- Your summary appears as a message inside your Fieldwork conversation and can also be emailed to you. If there are no open commitments to report, your assistant notes that quickly or remains silent.
- How does the assistant verify that a commitment was completed?
- It searches your sent messages in Google Workspace for direct written confirmation that the promised file, note, or answer was delivered. If no sent email demonstrates completion, the item stays open on your report.
Security first
No training on your data
Neither we nor our model providers train on your data. Inference runs with zero retention wherever the provider supports it.
Access
Agents only see what the person asking can see. Conversations, files, apps and connections stay private until shared, and admins have no way into conversations.
Encryption and isolation
Data is encrypted at rest and in transit. Each user's code runs in its own microVM, and secrets reach models by name only.
Continuity
Continuous backups, replicated to a second region. Data is exported on request and deleted within 30 days of a contract's end.