4 ways to automate staff check-ins

#1 - The basic check-in

Who it's for: A single manager who wants a simple regular read on how their team is feeling, without setting up anything elaborate.

What it is: A staff check-in is a short, repeated set of scored questions each person answers about how their work is going. This version is four rating scales, how they feel about their role, their workload, whether they feel recognised, and how supported they feel, plus one open comment. You can run it at whatever cadence suits, monthly works well for most teams, so everyone gets the same prompt at the same point each cycle and you build a picture over time.

In practice: A cafe with eight staff runs it on the first Monday of the month. Each person scores the four questions in under two minutes on their phone and adds a line if they want. The manager reads eight short check-ins instead of guessing who is quietly unhappy.

Why it works: Because it is scored and repeated, you are comparing a person to their own past answers, not to a vague sense of the room. A 4 sliding to a 2 is visible even when the person says they are fine.

Steps included:

• 4 rating scales (how you feel about your role, workload, feeling recognised, support from your manager), each 1 to 5
• 1 open comment (optional)

When to upgrade:

1. Other managers run it too and you want everyone asked the same way
2. You want a low score to flag a follow-up automatically, rather than relying on spotting it
3. You have too many responses to read every one each cycle

#2 - With written prompts

Who it's for: Teams where more than one manager runs the check-in, or where you want every person to read the questions the same way.

What it is: The basic check-in with a short written prompt under each rating, plus a fifth question on whether the person can see a path forward. The prompts tell people what to consider, a normal week rather than one bad day, so a score means the same thing across everyone.

What it adds to the previous template:

1. A written prompt on each question, so scores are consistent whoever answers
2. A fifth dimension, a path forward, which is one of the quietest reasons good people leave
3. A short intro that sets the tone: answer honestly, there are no wrong answers

Why it works: A rating with no guidance gets read differently by everyone, so the numbers stop comparing. The prompt sits inline at the moment of answering, so each score is anchored to the same thing for the whole team.

Steps included:

• 1 guidance note (how to answer)
• 5 rating scales (role, workload, recognition, support, a path forward), each 1 to 5
• 1 open comment (optional)

When to upgrade: When you want a low or dropping score to flag a follow-up automatically (Staff check-in #3), or Poppi to triage the responses for you (Staff check-in #4).

#3 - With a manager summary

Who it's for: Managers who want a read on every response without opening each form.

What it is: The guided check-in plus a Poppi (AI) action that, on every submission, sends the manager a short summary: the overall picture from the ratings, anything notable in the comment, and whether a follow-up looks needed. You get a two-line message per person rather than a folder of forms to work through.

In practice: A multi-site operator with three site managers gets one short DM per person as the check-ins land. The site manager reads a two-line summary that says the scores held up but recognition dipped and the comment mentioned cover being short, instead of opening thirty forms to find it.

What it adds to the previous template:

1. A Poppi summary of every response, sent straight to the manager
2. A read that scales, a message per person instead of a stack of forms
3. The ratings and the comment distilled into what actually needs attention

Why it works: Reading thirty raw check-ins is how the one that mattered gets lost in the pile. A summary of each one, delivered as it comes in, puts the manager's attention on what changed rather than on data entry.

Steps included:

• 1 guidance note (how to answer)
• 5 rating scales, each 1 to 5
• 1 open comment
• 1 Poppi action (sends the manager a summary of every response)

When to upgrade: When you want to be alerted the moment a single answer drops, not just summarised (Staff check-in #4).

#4 - With low-score alerts

Who it's for: Managers who want to hear about a dip the moment it happens, on any single question.

What it is: The guided check-in where each rating carries its own Poppi (AI) decision asking whether the score came in below 3. When one does, Poppi messages the manager about that specific answer, naming the dimension that dropped, so a low score on any question surfaces on its own without waiting for a summary or a read.

In practice: A larger operator wants to catch the single sliding answer, not the average. Someone scores support a 2 while everything else holds at 4, and the manager gets a DM naming support as the dip before the next round, rather than it averaging out to "fine".

What it adds to the previous template:

1. A per-question check on every rating, not just an overall read
2. An alert that names the exact dimension that dropped
3. Nothing waits on a summary or a manager getting to the form

Why it works: The earliest signs hide in a single low answer among otherwise fine ones, which is exactly what an average or a glance misses. Watching each rating on its own is what catches the one dimension sliding while the rest hold.

Steps included:

• 1 guidance note (how to answer)
• 5 rating scales, each 1 to 5
• 1 open comment
• 5 Poppi decisions (one per rating: is the score below 3?)
• 5 Poppi actions (message the manager about the low score) on each decision's yes

When to upgrade: Versions that roll several rounds into a trend view for the whole team are coming in the next post update.

How to pick the right version

You don't need to know our product to choose. Just answer three questions about how the check-in runs.

Is it just you running this, or do other managers run it too?

A check-in only compares across people if everyone reads the questions the same way. If it is just you, a plain set of scored questions is enough. The moment other managers run it, the prompts need to be on the screen so a 3 means the same thing on every team. If it is just you, #1 is fine. If others run it, start at #2.

Do you want to read the results yourself, or have them summarised for you?

Reading each response works while the team is small. Past a certain size it stops scaling and the one that mattered gets lost in the pile. If you are happy to open the forms, #2 is enough. If you want Poppi to send you a short summary of every response, #3 adds the manager summary.

Do you want a summary of the whole response, or an alert on any single low answer?

A summary tells you the overall picture per person. An alert fires on one dimension slipping, even when the rest hold, which is where the earliest signs hide. If the summary is enough, #3 covers it. If you want to be messaged the moment any rating comes in below 3, #4 adds the per-question alerts.

Related workflows

• Anonymous feedback - for what people won't say with their name on it
• Performance reviews - the deeper conversation the check-in feeds
• Staff onboarding - starting the relationship the check-in protects

Conclusion

A staff check-in is a short, repeated set of scored questions that makes a change in how someone feels about their work visible before they decide to leave. The versions above move from a simple pulse to a check-in that summarises every response and alerts a manager the moment any single answer dips, so the earliest signs reach someone while there is still time to act on them.

Further versions that roll several rounds into a team trend view are coming in the next refresh. They need more review time and will land separately.

→ Build your own staff check-in workflow on Pilla.