The short answer: Associates can take breaks without asking permission — just check the Coverage Status Canvas in Slack first. 🟢 go, 🟡 note if late, 🔴 check with the Duty Lead.
How the Coverage Status Canvas Works
A Slack Canvas is pinned in the team channel and shows a single status that the Duty Lead keeps current. Associates check it before every break — no approval needed unless coverage is tight.
| Status | What it means / what to do |
|---|---|
| 🟢 OK | Coverage is fine. Post in #gimmie-a-break when you leave and when you're back — no approval needed. |
| 🟡 Tight | Coverage is close to the line. If your break is running 5+ minutes late, drop a quick note in #gimmie-a-break before heading out. |
| 🔴 Low | Coverage is short. Check with the Duty Lead before signing off. |
The Canvas is intentionally simple during this pilot — a status line only, no per-person breakdown or running notes, so it stays quick to maintain.
For Support Associates
1. Before Your Break
Before heading to break, check the Coverage Status Canvas in the team channel:
- 🟢 OK: Take your break at your scheduled time. No approval needed.
- 🟡 Tight: You can still go — but if you're running 5+ minutes behind schedule, post a quick note in #gimmie-a-break before you head out.
- 🔴 Low: Message the Duty Lead before signing off and wait for a quick thumbs-up.
2. When You Leave
Post in #gimmie-a-break (message or emoji) immediately before heading to break, as usual.
3. When You're Back
Post a message or emoji in the thread to confirm you're back.
4. If You Flagged a 🟡/🔴 Break and Don't Hear Back
Wait about 2 minutes. If there's no response, go ahead and take your break — note in the thread that you proceeded after waiting. You shouldn't be stuck waiting indefinitely for a reply.
General Mindfulness
Glance at recent messages before you post, just to get a feel for how many peers are currently out. This is a courtesy, not a requirement to calculate coverage yourself.
For Team Leads
Keeping the Status Current
Update the Coverage Status Canvas whenever coverage meaningfully changes — not on a fixed timer. Base the status on real signals:
- Number of people currently out on break
- Queue depth and wait times
- Known gaps — call-outs, meetings, etc.
Edit the existing status line in the Canvas rather than posting new messages. One source of truth, always.
Suggested Thresholds
Adjust these to fit your team's actual staffing level:
- 🟢 OK: Normal staffing, no unusual queue pressure.
- 🟡 Tight: At or near your team's comfortable break-coverage limit.
- 🔴 Low: Below minimum coverage — further breaks need a direct check-in first.
When Someone Flags a Late Break Under 🟡/🔴
Respond quickly — either confirm it's fine, or ask them to hold a few minutes until someone returns. If you can't respond within ~2 minutes, that's okay. The associate will proceed and note it themselves. This is expected, not a failure on your part.
What NOT to Do During This Pilot
- Don't require approval for every late break — only 🟡/🔴 situations need a check-in.
- Don't turn the Canvas into a detailed log — no per-person tables or running commentary. Keep it to the single status line so it stays fast to maintain.
Summary Checklist
- Check the Coverage Status Canvas before every break.
- 🟢 OK — go at your scheduled time, no approval needed.
- 🟡 Tight — post in #gimmie-a-break if you're running 5+ minutes late.
- 🔴 Low — message the Duty Lead and wait for the go-ahead.
- Post in #gimmie-a-break when you leave and when you're back.
- No response after 2 minutes on a 🟡/🔴 flag? Proceed and note it in the thread.
Updated