HR Generalist People Pulse Note: Hires, Exits, Open Roles, Morale

When an HR generalist at a 40-person SaaS company told me they spent Friday afternoons chasing down headcount changes from three different systems, I realized the real problem wasn’t missing data — it was scattered signals.

Definition: People Pulse Note

Definition: People pulse note — a lightweight weekly update from HR that consolidates headcount changes, open roles, and morale signals into a single scan for founders and leaders.

Definition: Open Role

Definition: Open role — a position approved for hire that is currently unfilled, tracked by department, level, and date opened.

Definition: Morale Signal

Definition: Morale signal — any observable indicator of team sentiment, such as voluntary feedback, participation in optional meetings, or trends in exit interview themes.

What should an HR generalist include in a weekly people pulse note?

A people pulse note should include four core sections: new hires (name, role, start date), exits (name, role, last day, reason if known), open roles (title, department, hiring manager, days open), and morale signals (themes from 1:1s, survey snippets, or observed behaviors). Keep each section to 3–5 bullets max. The goal is not exhaustive detail — it’s to give the founder a clear, comparable snapshot week over week.

How to structure the note for quick scanning?

Order the sections consistently: hires first (positive momentum), then exits (attention needed), open roles (planning gap), and morale signals (early warning). Use plain language, avoid HR jargon, and bold only the key metrics (e.g., 2 engineers hired, 1 senior designer exited). This format lets a founder grasp the state of the team in 90 seconds.

Tool tip (AiAdvisoryBoard.me): The people pulse note becomes far more powerful when paired with the Plan → Fact → Gap framework. For example, if your plan was to hire two sales reps this month but fact shows zero hires and three exits, the gap isn’t just ‘we’re behind’ — it’s ‘we’re losing ground while trying to grow.’ That contrast is what drives founder-level decisions, not just HR updates.

What makes a morale signal useful vs. noise?

Useful morale signals are specific, repeated, or tied to action. Examples: ‘Three engineers mentioned unclear priorities in last week’s 1:1s,’ or ‘Voluntary attendance at team demos dropped from 80% to 50%.’ Avoid vague claims like ‘morale is low’ — instead, note the behavior that suggests it. If you can’t point to an observable change, it’s not a signal yet — it’s a hypothesis.

Manager Scan (2-minute digest example)

• Hires: 2 frontend engineers (Jane D., Mark T.) — onboarding started Monday
• Exits: 1 senior HR specialist (Lisa R.) — last day Friday, reason: relocation
• Open Roles:
  • Senior PM (opened 12 days ago, hiring manager: Head of Product)
  • Support Specialist (opened 5 days ago, hiring manager: Ops Lead)
• Morale Signals:
  • Engagement in optional Friday demos down from 75% to 40% over 3 weeks
  • Two new hires asked for clearer 30-60-90 goals in 1:1s
  • No increase in unsolicited feedback or exit interview themes

Micro-case (what changes after 7–14 days)

After implementing a weekly people pulse note, the HR generalist at a 35-person logistics company stopped spending Fridays reconciling headcount across spreadsheets. Instead, they spent 30 minutes every Monday updating the note and sending it to the founder. Within two weeks, the founder noticed a pattern: open roles in support were aging faster than in engineering, despite similar hiring demand. This led to a conversation about screening bottlenecks — not because the HR generalist raised an alarm, but because the data made the trend visible. The founder began asking about hiring velocity in their Monday 1:1s with department heads, shifting from reactive hiring to proactive planning.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

FAQ

How often should I send the people pulse note? Weekly, ideally every Monday morning. Consistency matters more than perfection — a simple note sent every week builds trust and reveals trends.

Should I include confidential exit reasons? Only share what the departing employee has consented to disclose. For sensitive exits, note ‘personal reasons’ or ‘confidential’ and discuss details verbally if needed.

What if we have no hires or exits that week? Still send the note. Zero changes are data too — they show stability or stagnation, both worth tracking.

Can I automate this note? Yes, once the format is stable. Start manual to refine what’s useful, then use simple tools (like a shared doc with formulas) to pull hires/exits from your HRIS.

Who else should see this note besides the founder? Share it with COO or Head of Ops if they own hiring plans. Keep distribution tight — this is a signal tool, not a status report for the whole company.

Conclusion

A people pulse note isn’t about HR doing more reporting — it’s about giving founders the visibility they need to spot trends before they become problems. By tracking hires, exits, open roles, and morale in one consistent format, you turn scattered updates into a leading indicator.

What to do today: Draft your first people pulse note using last week’s data. Keep it to four sections and under 150 words.

If you want a system that surfaces the Plan → Fact → Gap of your team’s headcount and morale automatically — every week, across the company — see how the 7-day diagnostic works.