Automation for assistants and chiefs of staff · Runs after a meeting is transcribed
Leadership decision log
A running log of leadership decisions, owners, and deadlines. Your assistant runs it after a meeting is transcribed and tells you when something needs your attention.
Leadership decision log — Sep 17
Automation run • Sep 17
Leadership decision log
Output
Three new decisions were added to the running log following this morning's Harbor & Pine leadership meeting, and one open commitment remains overdue.
New decisions
| Date | Meeting | Decision | Owner | Next step and deadline |
|---|---|---|---|---|
| Sep 17 | Leadership | Move candidate Dara Finch to final interview for Portland store manager | Lena Vale | Schedule panel by Sep 22 |
| Sep 17 | Leadership | Pause wholesale discount exceptions outside standard terms | Cal Brook | Update Driftline Supply Co proposal by Sep 18 |
| Sep 17 | Leadership | Finalize Q4 goals document ahead of October board review | Sol Varga | Circulate updated draft by Sep 25 |
Carried forward open item
- Senior ecommerce engineer hiring: Ezra Holt has not submitted the technical evaluation for Ines Calloway. This was due September 15 and is two days overdue.
Summary of changes
No earlier decisions were reversed during this discussion. Cal Brook's pricing decision clarifies discounting limits for open pipeline accounts, and Lena Vale's hiring step keeps the store manager timeline on schedule. Your running log in notes has been updated with these new items at the top.
Automation steps. Your assistant follows these 5 steps each time it runs, using your connected email and calendar.
- 01
After our leadership meeting, pull the decisions made, each one's owner, and any due date or next step, and add them to one running decisions log, newest first, with the date and meeting.
- 02
Flag anything that reverses or contradicts an earlier decision, and anything that should be resolved by now but is still open, and carry open items forward.
- 03
Deduplicate against what's already logged.
- 04
Record decisions and commitments, not minutes.
- 05
Then summarize what changed.
Adjust the automation in chat
Tell your assistant what to do differently and it sets up that version for you.
- Only log decisions from meetings titled Leadership or Board Review.
- Flag any open commitment that is more than three days past its due date.
- Group new decisions by owner instead of listing them in a table.
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.
What starts this automation
Runs after a meeting is transcribed.
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
Maintains the decision log and summary in your notes. Shares nothing with anyone else. 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 Leadership decision log in the library, and click Add. If your calendar in Google Workspace or Microsoft 365 is not linked yet, the setup card prompts you to connect it. The automation starts running as soon as a meeting transcript is ready, which you can adjust during setup.
- What does it do on its own versus waiting for me?
- It updates your decision log and notes automatically after each transcribed call. It never shares entries with coworkers, emails attendees, or changes calendar events, leaving all communication to you.
- Where do the results arrive?
- Your assistant posts the summary and logged entries directly in your Fieldwork chat, and it can send them to your email inbox as well. If a meeting produces no concrete decisions or action items, the assistant tells you briefly.
- How does it capture transcripts from Granola or Fireflies?
- Fieldwork uses its own meeting recordings by default, but it can read from Granola or Fireflies when you connect those accounts. Once connected, it checks each completed transcript against your existing log to catch conflicting commitments and carry open work forward.
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.