How to write meeting notes as Small HR Teams
You run HR for 150 people with one other person. Every all-hands, every manager 1:1, every benefits Q&A call, every onboarding check-in produces decisions and action items that live in someone's head or a half-finished Slack message. You're the one who has to remember that Marcus's offer letter discussion landed on a May 1 start date, that three managers agreed to submit their review calibrations by the 15th, and that someone raised a PTO policy question that legal still hasn't answered. You don't have an EA. You don't have a dedicated note-taker. You have a Zoom recording that nobody watches and a Notion doc that's already three months stale.
What you'll set up
Apps, data, and prompts
The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.
Meeting Notes runs as a standalone Starch app — connect your Google Calendar (Starch syncs your Google Calendar data on a schedule, pulling events 12 months back and 3 months ahead) so it knows which calls to capture. Task Manager stores action items extracted from meeting transcripts. Knowledge Management connects to Notion from Starch's integration catalog, querying it live so finalized decisions can cross-reference and update your existing docs. Gmail is also synced directly by Starch, so any meeting follow-up emails thread back into the same action item history.
Step-by-step
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
April 2026 Q2 Review Calibration Kickoff
| Attendees | 7 |
| Action items extracted | 11 |
| Action items assigned to managers | 8 |
| Action items assigned to HR | 3 |
| Decisions logged to Knowledge Base | 4 |
| Time spent on post-meeting admin | 12 |
You ran the Q2 calibration kickoff with seven managers across Engineering, Sales, and Ops — a 50-minute call that would normally produce a Zoom recording link and a frantic Slack message afterward trying to reconstruct who agreed to what. Instead, Meeting Notes transcribed the whole session, flagged the four policy decisions (calibration deadline of May 15, forced distribution waived for teams under 5, Engineering exempt from the new 9-box this cycle, HR to send the rating scale template by EOW), and extracted 11 action items with owners. You spent 12 minutes after the call confirming the task assignments and pushing the four decisions into Knowledge Management under 'Performance Review Process — Q2 2026.' When an Engineering manager emailed three days later claiming the May 15 deadline was 'news to him,' you pulled the exact transcript timestamp in under a minute and forwarded it. The deadline held.
How you'll know it's working
What this replaces
The other ways teams handle this today, and how the Starch version compares.
One platform — meeting notes, task manager, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.
Try it on Starch →Frequently asked questions
Does Starch record video or just audio/transcript?
We use Google Meet for most calls and Zoom for external interviews. Does Meeting Notes work with both?
What happens if someone joins late or there's a crosstalk problem — does the action item extraction break?
We store a lot of sensitive HR information — compensation discussions, PIPs, medical leave. Is this secure?
Can I use this for confidential 1:1s between HR and an employee — performance issues, accommodations, that kind of thing?
Our managers don't use Starch. Can they still receive their action items?
How is this different from just using the AI summary feature built into Zoom or Google Meet?
Related guides for Small HR Teams
A customer knowledge base is the document — or collection of documents — that answers the questions your customers ask repeatedly.
Read guide →SOC 2 evidence collection is the part of an audit where you prove that your controls actually work — not just that they're written down somewhere.
Read guide →A Slack announcement sounds simple — you're just telling your team something.
Read guide →Benefits enrollment is one of those operator workflows that looks manageable until it isn't.
Read guide →Write Meeting Notes for other operators
The AI stack built for the founder's office.
Read guide →The AI stack built for small finance teams.
Read guide →The AI stack built for small RevOps teams.
Read guide →The AI stack built for small marketing teams.
Read guide →Ready to run write meeting notes on Starch?
Request closed-beta access. Everything is free during beta.