Skip to main content

Return-to-work conversations

A return-to-work conversation is a brief, structured check-in with an employee after they have been absent. It is one of the most effective tools for reducing repeat absences, catching early signs of workplace issues, and demonstrating that you care about your team's wellbeing.

StaffBrik automates the tracking and prompting of return-to-work conversations so nothing slips through the cracks - even during your busiest service periods.

When is a return-to-work conversation needed?​

A sickness absence (Standard sick, Disability related or Approved medical) that lasts at least the Return-to-work threshold needs a return-to-work conversation once the person is back: the absence has ended, so its end date is before today. From the next day it shows Return-to-work needed on the Absences page. By default the threshold is 3 days, but you can change it in StaffBrik Settings.

info

The threshold is measured in calendar days, not working days. A Friday-to-Sunday absence counts as 3 days even if the employee was only scheduled to work on Friday.

Some operators choose to hold a return-to-work conversation after every sickness absence, however short. You can set the threshold to 1 day if you prefer this approach. With a 1-day threshold, a day someone went home sick partway through a shift needs a return-to-work from the day after.

While someone is still off, there is nothing to prepare or record yet: an absence that hasn't ended shows no Return-to-work needed, no Prepare return-to-work or Record return-to-work options, and no dashboard alert. That includes an absence booked ahead, such as an operation next month. If you try to record one early, StaffBrik says "You can record the return-to-work once {name} is back."

What the return-to-work conversation covers​

StaffBrik gives you two things for each return-to-work, both from the absence's actions menu on the Absences page:

  • Prepare return-to-work opens Prepare return-to-work conversation: talking points and questions for this absence, to read before you sit down together (see AI-assisted return-to-work guidance). It is optional.
  • Record return-to-work opens the Return-to-work conversation, where you record the conversation once you have had it.

The Return-to-work conversation shows the absence (who, how many days, the dates) and a short Conversation checklist:

  1. Reason for absence discussed - you have talked about the reason for the absence with the employee. This one must be ticked before you can record the return-to-work.
  2. Support offered - you have offered any support or adjustments to help them.
  3. Follow-up needed - a follow-up meeting or check-in is needed.

Notes is for anything important from the conversation, for example that a kitchen porter returning after a back injury will avoid heavy lifting for a week.

Owners, admins and members can prepare and record a return-to-work. Viewers cannot. Who can read a recorded one back is narrower: see Who can read a return-to-work.

The guidance never mentions anyone's Bradford score. For a disability-related or approved medical absence, it does not show any pattern alerts either, and the saved return-to-work summary never records them. Those absences do not count towards the Bradford Factor, so they have no place in the conversation.

tip

Keep return-to-work conversations supportive, not interrogative. A cafe team member who has been off with flu does not need a formal interview - a five-minute chat over a cup of tea is fine. The checklist ensures you cover the essentials without making it feel like a disciplinary process.

AI-assisted return-to-work guidance​

Prepare return-to-work (or Prepare on the employee's Absences tab) opens Prepare return-to-work conversation, with AI-generated guidance for this absence. Nothing is prepared until you ask: click Prepare guidance and StaffBrik writes it for you. It is kept on the absence, so it is there when you come back. It has:

  • Talking points - a few points to cover, starting with a welcome back and covering the absence, the support you can offer and any follow-up. Each is tagged with its topic (such as Welcome back or Support offer) and its tone.
  • Suggested questions - open questions to ask, each with why it helps and follow-up topics that might come up.
  • Context summary - Earlier return-to-work notes available (how many earlier conversations with saved notes it drew on, up to five) and any pattern alerts. The guidance uses those notes, so one conversation follows on from the next. For an owner or admin it draws on every earlier conversation with this person. For a member it draws only on the conversations they recorded themselves, so nobody's guidance repeats a conversation they can't read.
  • Fairness reminder - points to keep the conversation fair, where there are any.

You can edit or delete any talking point or question, or add your own with Add point and Add question. Save changes keeps your edits for next time. Continue to return-to-work checklist saves your edits first, then takes you to the Return-to-work conversation when you are ready to record it. If a point or question you are still typing hasn't been added yet, it asks "Discard the open edit?" first. Closing with unsaved edits asks "Discard your changes?".

If someone else prepares the guidance again while you are editing it, your save is refused rather than written over theirs: "This guidance was replaced while you were editing. Reload it to see the current version. Your changes won't be kept." Click Reload to see the current guidance.

info

The AI guidance is advisory only. It does not replace professional HR or legal advice. For complex situations - such as long-term sickness, disability adjustments, or performance management - consult your HR provider.

Guidance prepared before an update to StaffBrik reads "This guidance was prepared before an update. Prepare it again." Click Prepare again to make fresh guidance. If you had edited the old guidance and try to save it, StaffBrik asks you to prepare it again first, and those edits are not kept.

If the AI is unavailable, you can still record the return-to-work: StaffBrik uses a standard template for the summary instead. Guidance made while the AI was unavailable says so, with Prepare again to make it afresh, unless you have edited it. If saving your edited guidance fails, a message says so.

If the absence changes while the guidance is being prepared (someone edits its dates, say), it isn't saved: "The absence changed while the guidance was being prepared. Prepare it again."

Recording the return-to-work​

Once you have had the conversation:

  1. Navigate to StaffBrik > Absences and find the absence record.
  2. Open the absence's actions menu and choose Record return-to-work to open the Return-to-work conversation. On an employee's Absences tab, use Record return-to-work in the Return-to-work needed panel. If you prepared guidance first, Continue to return-to-work checklist brings you to the same place.
  3. Tick Reason for absence discussed, and Support offered and Follow-up needed if they apply. Add any notes.
  4. Click Record return-to-work.

Saved guidance you can read sits above the checklist, under Your talking points and questions, to have to hand during the conversation. Closing the checklist with answers entered asks "Discard your changes?" first. If you are offline when you save, the checklist says "You're offline. We'll save this when you're back online." and saves once you are, and the same line shows when you save edited guidance offline.

The return-to-work is saved on the absence: the ticks, your notes, who recorded it and when. The absence then shows Return-to-work done instead of Return-to-work needed. If you prepared guidance and left Notes empty, StaffBrik writes a short summary of the conversation into the notes for you, from the guidance and your ticks. Recording every return-to-work the same way builds a fair, consistent record of how you manage absence.

A return-to-work is recorded once. Recording it again says "This return-to-work has already been recorded." If the absence changes while you are recording (someone edits its dates, say), StaffBrik says "The absence changed while you were recording this. Check it and save again."

When a recorded return-to-work is cleared. Extending a recorded absence, or changing its dates so it hasn't ended yet, means the person is off again. The recorded conversation and its guidance are cleared, and a new return-to-work is needed once they are back.

When prepared guidance is cleared. Changing an absence's category before its return-to-work is recorded clears any guidance prepared for it, so prepare it again for the new category. Guidance prepared for an ordinary sickness, for example, never carries into a disability-related conversation.

Reading a recorded return-to-work​

Open a recorded return-to-work from any of these:

  • View return-to-work in the absence's actions menu on the Absences page.
  • A link to the absence, for example from the rota or a report. An absence with a recorded return-to-work opens on its record.
  • View return-to-work under a completed absence in the employee's absence history, on their profile's Absences tab.

The Return-to-work panel shows "Completed by {name} on {date}", the three checklist answers, the notes and the talking points and questions used. It is read-only: Edit absence opens the absence itself, for anyone who can edit absences.

Who can read a return-to-work​

A recorded return-to-work holds personal conversations, so not everyone who can see the absence can read it. This covers the notes, the checklist answers and the guidance.

RoleCan read
Owner and adminEvery recorded return-to-work
MemberThe ones they recorded themselves, and guidance they prepared until the conversation is recorded
ViewerNone

Members can still prepare and record a return-to-work as before. A member who opens guidance someone else prepared sees "There's no guidance for you to use yet." and can click Prepare guidance to make their own, which replaces it. If a member records a return-to-work with guidance they couldn't read, that guidance isn't kept with the record.

A return-to-work recorded before StaffBrik kept track of who recorded it can be read by owners and admins only. So can guidance prepared before StaffBrik kept track of who prepared it.

Anyone who isn't allowed to read a record sees "Only owners, admins and the person who held this conversation can read it." in its place, never an empty record.

Return-to-work needed tracking​

Return-to-work conversations still to do appear as dashboard alerts in StaffBrik. This ensures they are not forgotten - which can easily happen in a busy restaurant or bakery where managers are juggling service, deliveries, and staffing.

The dashboard shows:

  • Employee name and the absence dates.
  • How long - for example "5 day absence ended 2 days ago".
  • A Record return-to-work link to the checklist.

Nothing is flagged while the person is still off, or for an absence booked ahead: an absence appears here the day after it ends.

On the Absences page, the Return-to-work needed card counts them. Clicking the card of the same name on the StaffBrik dashboard opens the Absences page with only those absences listed, and Show all brings everything back.

Staff who have left are not included. Once someone is archived, their outstanding return-to-work conversations drop off the alerts and the Return-to-work needed count and list, because there is nobody to have the conversation with.

caution

Outstanding return-to-work conversations should be recorded as soon as practically possible after the employee returns - ideally on their first shift back. The longer you leave it, the less useful the conversation becomes, and it weakens your position if absence management escalates to a formal process later.

Overdue reminders​

A return-to-work falls due three days after the absence ends. If it is still not recorded after that, StaffBrik sends an in-app notification, for example "Return-to-work overdue: Sam Patel", saying how many days overdue it is and when the absence ended. Its Record return-to-work link opens the checklist for that absence. Reminders sent before this wording changed still say "RTW overdue" and Complete RTW, and work the same way.

Reminders are spaced out so they stay useful rather than noisy:

  • The first one arrives on the return-to-work's first overdue day.
  • After that, at most one a week while the return-to-work is still open.
  • They stop once the absence ended more than 30 days ago, so an absence gets four reminders at most. The return-to-work stays on the dashboard and the Absences page until you record it.

Recording the return-to-work, or deleting the absence, archives its reminders. Reminders are only sent for absences that need a return-to-work conversation (standard sick, disability-related and approved medical absences at or above your return-to-work threshold), and never for staff who have been archived.

Why return-to-work conversations matter​

Research consistently shows that organisations that conduct return-to-work conversations see a measurable reduction in short-term absence rates. In hospitality, where margins are tight and every missing team member means someone else picks up the slack, this is time well invested.

A good return-to-work conversation:

  • Shows your team you notice and care when they are absent.
  • Catches early signs of burnout, workplace conflict, or health issues.
  • Creates a fair and consistent record if formal action becomes necessary.
  • Reduces repeat short-term absences by up to 30% (CIPD data).