6 ways to automate pre-shift huddles

#1 - The basic check-in

Who it's for: Small teams starting a daily huddle habit, where one person runs the morning gather and nobody has written it down before.

What it is: A pre-shift huddle is a short team gather before the doors open, and this is the bare version that records it. Four steps on a phone: pick which shift it is, type who is on today, set the focus, and flag anything the team needs to know up front. Each completion is one stamped record of that shift's huddle. The shift lead runs the canvas once at the start of every shift, and the trail is the list of completed huddles over the week.

In practice: Take a three-van plumbing firm. The lead opens the canvas at 7am, picks "Morning", types the two names on today plus the apprentice covering the south round, sets the focus as "the boiler swap in Croft Road has to be done by noon", and flags that the parts van is in for service so everyone shares the smaller vehicle. Submit. Server timestamp captured. The next morning the lead does it again. Two stamped huddles, no whiteboard photo, no group chat scroll to dig through later.

Why it works: The huddle is the alignment. Saying it out loud is what gets the team pointed the same way, and writing it down is what makes it survive past the conversation. What changes here is that the focus and the flags now live in a stamped record instead of in someone's memory. If a job slips, the manager can see what the stated focus actually was that morning, not what people remember it being.

Steps included:

• 1 single-choice step (which shift: Morning, Afternoon, Evening, Night)
• 1 text input (who is on today)
• 1 text input (today's focus)
• 1 text input (anything to flag)

#2 - With written guidance

Who it's for: Sites with rotating shift leads who all need to run the huddle the same way, whoever is on the early.

What it is: The basic check-in plus two guidance panels woven through the canvas. One panel sits at the top and tells the lead how to run a tight huddle: five minutes, standing up, before the doors open. The other sits at the bottom and reminds them what to cover every time, ending by asking if anyone has something to raise. A stand-in lead on their first morning runs it the same way a duty manager would, without anyone briefing them in person.

In practice: Take a 30-room hotel with three department heads who take turns opening. The front-of-house lead opens on Monday, the housekeeping lead opens on Tuesday, a duty supervisor covers the weekend. Before the guidance went in, each one ran the huddle differently: one rambled for fifteen minutes, one barely spoke. Now the top panel sets the five-minute rule, and the bottom panel prompts the same closing question every time: "anything anyone wants to raise?" The supervisor reads it the first morning they cover and runs a tight huddle that matches the regulars.

What it adds to the basic check-in:

1. A "how to run a tight huddle" panel at the top, setting the five-minute, stand-up, before-doors-open rule
2. A "what to cover every time" panel at the bottom, prompting who is on, the focus, what changed, and the closing question
3. A consistent shape across every shift lead, so the huddle does not get longer or thinner depending on who is running it

Why it works: Written guidance sits inline at the moment the lead is about to act. The stand-in reads the five-minute rule the first time they open the canvas, and the closing prompt is right there at the bottom before they submit. It is not a one-off briefing they half-remember from their first week. It is on the screen at the moment of the huddle, every single morning.

Steps included:

• 1 guidance note (how to run a tight huddle, five minutes standing up before doors open)
• 1 single-choice step (which shift)
• 1 text input (who is on today)
• 1 text input (today's focus)
• 1 text input (anything to flag)
• 1 guidance note (what to cover every time, and closing question for raises)

#3 - With a signature

Who it's for: Businesses where the huddle needs a name against it, signed at the time by the person who ran it.

What it is: The basic check-in plus a signature captured at the end. The shift lead signs to confirm the huddle happened. That puts three things on one record: the timestamp, the typed focus and flags, and a signature naming who ran it. For a team that needs accountability, it answers "did the huddle happen and who ran it?" in one record, captured in seconds.

In practice: Take a regional cleaning contractor with eight depots, each starting at 6am. The depot lead runs the huddle, and signs at the bottom before the crews head out. When head office reviews the week, they pull the huddles for every depot and see a signed entry for each morning, named to the lead who ran it. The two depots that skipped a huddle show a gap with no signature, so the conversation is about those two mornings, not a vague sense that "some sites don't bother".

What it adds to the basic check-in:

1. A signature step at the end, naming the person who ran the huddle
2. A record that ties who ran it to when it happened
3. A clear accountability trail: a missing signature is a missing huddle, with the responsible lead already named

Why it works: The signature is what closes the loop. The timestamp and the notes say a huddle happened at this time with this focus. The signature adds: and this named person ran it. Captured on the same device, at the same moment, in the same record, the three together turn a habit into something a manager or an auditor can stand behind.

Steps included:

• 1 single-choice step (which shift)
• 1 text input (who is on today)
• 1 text input (today's focus)
• 1 text input (anything to flag)
• 1 signature (shift-lead sign-off)

#4 - With photo evidence

Who it's for: Teams that want a photo of the team gathered for the huddle or the board on record, not just the typed notes.

What it is: The basic check-in plus a photo step at the end. The lead takes a shot of the team standing together, or of the specials board or target board, and it lands in the record alongside the typed focus and flags. One photo per huddle, stamped to the same record. For a business running several sites, it turns each morning huddle into a record a regional manager can scan at a glance instead of reading every line.

In practice: Take a three-site garden centre. Each site lead runs the huddle at 8am and finishes by photographing the target board, where the day's plant-sale push and the café's covers target are chalked up. The regional manager opens the rollup mid-morning and sees three photos: the boards are filled in at two sites, blank at the third. One phone call later the third site has its targets up. The photo did in five seconds what reading three sets of notes would not have flagged as fast.

What it adds to the basic check-in:

1. A photo of the team gathered for the huddle, captured at the time
2. A visual record that the team was there and aligned, which the typed notes alone do not give
3. A faster scan for a multi-site manager, who can glance at the photos across sites instead of reading every entry

Why it works: Typed notes are data. A photo is a glance. The two together tell a regional manager more than either alone. The notes say what the focus was; the photo shows the team was actually there and the board was actually set. Captured at the same moment, on the same device, the photo cannot be staged after the fact to cover a huddle that was skipped.

Steps included:

• 1 single-choice step (which shift)
• 1 text input (who is on today)
• 1 text input (today's focus)
• 1 text input (anything to flag)
• 1 photo of the team gathered for the huddle

#5 - With Poppi checking the photo

Who it's for: Teams where the huddle photo gets taken but nobody reviews it. Multi-site groups where head office can't look at every site's photos every morning.

What it is: A photo-checked huddle is the basic check-in plus a photo of the team gathered for the huddle that Poppi (AI) reviews the moment it's saved. Poppi answers one question about that photo, set by you: does the photo show the team gathered for the huddle? A single named spot is something an AI can actually judge, where a vague shot of the whole room is not. If the answer is no, Poppi posts what it spotted to the team chat, so the problem gets fixed before everyone moves on.

In practice: A three-site hospitality group opens at 11am, with a huddle at 10:50 at each site. The site lead takes the huddle photo as always. Poppi reads the photo: the team is gathered, ready to go. Verdict yes, and nothing changes. On a rushed Friday at one site, everyone is scattered and only two people are in frame. Poppi answers no and posts the reason to the team chat ("The photo does not show the team gathered for the huddle"). The lead calls everyone back to group for the photo while still in the building.

What it adds to the basic check-in:

1. A photo of the team that gets checked the moment it's saved, not just stored
2. A team chat message with Poppi's reason the moment a photo fails the check
3. The manager stops being the only person who ever looks at closing photos

Why it works: The check happens in the seconds between the photo being taken and the team dispersing. That's the only moment the problem is still cheap to fix. A manager reviewing photos later can only record that the team was scattered; Poppi catching it at the moment flags it to everyone who can still gather back together.

Steps included:

• 1 single-choice step (which shift)
• 1 text input (who is on today)
• 1 text input (today's focus)
• 1 text input (anything to flag)
• 1 photo of the team gathered for the huddle
• 1 Poppi decision (judges the photo against your question)
• 1 Poppi action (posts to the team chat if the photo fails the check)

#6 - With a team alert when the shift starts

Who it's for: Huddles with a fixed start time that has to be hit. Morning briefings at hospitality venues, retail opening huddles, dispatch team briefings before shift clocks in.

What it is: A team alert at shift start is the basic check-in plus a Poppi (AI) action set to the workflow's start time. When the huddle is due to begin, Poppi posts a message in the Pilla team chat so whoever is running the briefing starts straight away. It fires on the start time, not on a completed step, so the nudge lands even if nobody has opened the huddle canvas yet. This is the version to add when the problem isn't how the huddle is run, but whether it gets started on time.

In practice: A 50-seat pub opens at 11am, with a seven-minute huddle at 10:55 to brief the floor team on covers, VIPs, and any table issues. On a quiet Tuesday the duty manager runs five minutes late. With this version, at 10:55 the team chat gets a message that the huddle is due, so the lead sees it on their phone and the brief starts on time rather than at 11:05 in a scramble.

What it adds to the basic check-in:

1. A message in the team chat the moment the huddle is due to start
2. A nudge that lands even when nobody has opened the huddle canvas yet
3. A record of when the huddle should have begun, next to when it did
4. One less thing for the manager to chase by text every morning

Why it works: The alert is tied to the start time itself, not to someone remembering to open the canvas. It turns "did anyone start the huddle?" from a thing the manager has to chase into a thing that checks itself.

Steps included:

• 1 single-choice step (which shift)
• 1 text input (who is on today)
• 1 text input (today's focus)
• 1 text input (anything to flag)
• 1 Poppi action (posts to the team chat when the shift huddle is due to start)

How to pick the right version

You don't need to know our product to choose. Every version here is the basic check-in plus one addition, so pick the additions your team actually needs.

Do other people run the huddle, or is it always the same person?

If you run every huddle yourself and know what to cover, the plain check-in is enough: #1. The moment the huddle rotates between shift leads, written guidance needs to be on the screen: #2.

Does the huddle need a name against it?

If recording that a huddle happened is enough, skip this one. If you need to prove who ran it and tie that to when it happened, #3 adds a signature.

Do you need a photo as proof?

A typed checklist says the work was done; a photo shows it. If you want visual proof the team was there, #4 adds a photo of the team gathered for the huddle.

Does anyone actually look at the photos?

If a manager genuinely reviews every photo, #4's record is enough. If photos get taken and filed unseen, #5 has Poppi (AI) check each one as it's saved, and tell the team chat when the team is not fully gathered.

Does your huddle have to start at a set time?

If a tired team sometimes skips the huddle or starts late, #6 posts a message to the team chat when the start time passes with the huddle not yet begun.

Need more than one addition? Open the version with the addition that matters most in the playground and add the others as steps. That's how the product works anyway: every option here is one step added to the same list.

Related workflows

• Lone worker check-ins
• Job completion sign-off
• Delivery received
• Daily cash count
• Stock count

Conclusion

A pre-shift huddle is a stamped record run at the start of every shift: who is on, the focus, and what to flag. Every version above is the same basic check-in plus one addition: written guidance, a signature, a photo, an AI check on the photo, or a start-time alert. Pick the ones your team needs and combine them in the playground.

→ Build your own pre-shift huddle on Pilla.