Where to find it | Sidebar → People → Employee Pulse |
Who can see it | Admins and above, for the whole company. A Team Lead with direct reports sees their own team. |
Can you change data here? | No — check-ins are submitted in Nova, not Signal |
How fresh is it? | Near real-time. Submissions take between about 15 minutes and a few hours to arrive. |
Not to be confused with Client Pulse
This page is about employees: how they're feeling, how stretched they are, and hours spent per client — submitted in Nova.
Client Pulse — the separate nav section with Submit Pulse Data, My Submissions and Pulse Summary — is about clients, and is submitted in Signal.
Same word, different data, different audience, different system. If you're looking for client sentiment, you want the other one.
What it's for
Every week, delivery employees submit a check-in in Nova: how they're feeling, how loaded they are, and how many hours they spent on each client. That self-reported data feeds client profitability, capacity planning and people-health monitoring — and it's only trustworthy if people actually submit it.
So this page does two things:
Compliance — who submitted, who didn't, and the coverage percentage against a carefully defined denominator of people who are actually expected to submit.
People health — each person's rolling four-week sentiment and workload averages next to their most recent week, so a dip is visible early rather than at an exit interview.
The Pulse week runs Tuesday to Monday, with a Monday evening deadline. So the natural rhythm is checking on Tuesday or Wednesday for the week that just finished.
What you'll see
Coverage tab
Coverage cards — this week's coverage percentage and the monthly average.
Submitted / Not Submitted panels — with an hours figure and per-client chips for everyone who submitted.
Week pills and a month picker for moving between weeks.
Filters by division, department and name, plus Excel export.
Sentiment & Bandwidth tab
Per person, and aggregated:
Sentiment — a 0–5 scale where higher is better. Green from 4, amber from 3, red below.
Bandwidth — a 0–10 scale where higher means more stretched, so worse. Red from 7, amber from 5, green below.
Each shown as a four-week average and for the last completed week, so you can see whether last week was better or worse than someone's norm.
Number of check-ins in the last four weeks, and the date of the most recent one.
The colour thresholds are interface guides to draw your eye, not official targets.
How to use it
Weekly chase, Tuesday or Wednesday. The page opens on the most recently completed week. Read the coverage percentage, sort the Not Submitted panel by department, and send reminders — or export the list for a manager thread.
Hold teams accountable. Filter by division and then department, and compare the monthly average across teams. A chronically low group needs a process change, not more reminders.
Scan for burnout. On the Sentiment & Bandwidth tab, sort last week's bandwidth descending to find people redlining, or four-week sentiment ascending for sustained morale problems. Compare last week against the four-week average to catch sudden drops — those are the urgent ones.
Report monthly. Select a month, note the average coverage and the sentiment and bandwidth aggregates, and export both tabs as the evidence pack for a People Ops or leadership readout.
Investigate "but I did submit it." Search the person by name. It's almost always one of the three causes in the questions below.
Spot-check data quality. Scan the hours column for implausible values. These same hours drive delivery-cost estimates on Client Profitability — bad hours there become a bad margin.
Good to know
Not everyone is expected to submit, and the denominator reflects that. It deliberately excludes Revenue, Sales, Accounting, Finance, Corporate and the Nova product team, plus leadership titles (VP, SVP, Head, Executive, Chief, President and senior director grades), test accounts, and a small People Ops exclusion list. So a missing VP is correct, not a gap.
The week is Tuesday to Monday, not a calendar week. A Monday evening submission belongs to the week that's ending.
The page opens on the last completed week, not the current one — the in-progress week would look misleadingly empty.
Some people have two Nova accounts. Signal merges them by name so nobody is double-counted, though an unusual name variant can occasionally slip through.
Hours per client are capped within a single check-in, as a typo guard. That's why a wild number gets trimmed.
The four-week window counts back from today while "last week" is the previous completed Tuesday-to-Monday week. They overlap on purpose.
The exclusion rules live in the app, not in a policy document. They can change without notice. If you think someone is wrongly in or out of the denominator, ask People Ops rather than assuming it's a bug.
Common questions
Someone says they submitted but shows as Not Submitted. Three usual causes: (1) their submission hasn't replicated yet — allow up to a few hours; (2) the Tuesday-to-Monday boundary, so check the adjacent week pill; (3) a duplicate Nova account with an unusual name variant. If none of those explain it, ask the Signal team to run a diagnostic.
Why is a VP or someone in Finance missing from the count? Deliberately excluded — they aren't expected to submit. See "Good to know" above.
Which direction is bad? Sentiment 0–5, higher is better. Bandwidth 0–10, higher is worse — it means more stretched. That inversion catches people out.
What's the difference between the four-week and last-week columns? Four-week is the average of everything in the trailing four weeks from today. Last week is the previous completed Tuesday-to-Monday week only, with the exact dates shown in the panel header. Comparing them shows the trend.
Why does it open on a week that isn't the current one? Because the current week is usually still in progress. It picks the most recent week with a meaningful number of submissions — in practice, the last completed one.
Is the coverage percentage an official target? The colours change at 50% and 75%, but those are interface guides rather than a documented company goal. Ask People Ops whether a formal target exists.
Can I enter or correct a check-in here? No. This page only reports. Check-ins are created in Nova.
The hours don't match what someone remembers entering. Two mechanics: per-client hours are capped within one check-in as a typo guard, and the hours column sums all client hours plus non-client hours across every check-in that person made in the week.
Is this the same as Client Pulse? No — see the top of this page.
Related
Client Profitability — uses these hours to estimate delivery cost, so coverage here directly affects accuracy there
Employees — the per-person hours breakdown and company benchmark
Submit Pulse Data — the client check-in, which is a different thing
Growth: People & Performance Radar — shows the same sentiment and bandwidth badges alongside compensation
Glossary — the two Pulses, disambiguated