See SquadBear in action.
A walkthrough of leave, timesheets, attendance, team health and onboarding.
Explore example Claude workflows
Choose a prepared scenario to see how an assistant could check policies, balances, calendars and issue trackers through SquadBear MCP. These examples use illustrative data and do not query a live workspace.
What do you need from people ops?
Choose a sample workflow with Claude and SquadBear
How many annual leave days do I have left, and will I lose any soon?
get_my_leave_balancesme · annual · as of today14.5 days available · 3 expire 31 Mar
Three days expire on 31 March. I can suggest dates that use those first.
Book me Mon–Wed next week, if Engineering stays covered.
get_coverage_risksEngineering · Mon-Wed · 3 daysSafe · 2 of 8 out · no critical gap
preview_leave_requestannual · Mon-Wed · balance after: 11.5 daysMon–Wed · 11.5 days left · approver Leo
Two of eight teammates would be out. Your balance would be 11.5 days, and Leo is the approver.
Show me every leave request that is stuck and who can unblock it.
list_pending_leave_requestsall teams · waiting > 0 days7 open · 3 overdue · oldest 5 days
get_approver_statusLeo NovakLeo out Thu · Tomas covering
Seven are open; three have waited over three days with Leo. He is off Thursday, and Tomas has accepted cover.
Emily starts Monday. Start the New joiner onboarding process for her.
start_processprocessId joiner · employeeId emp_emily · anchorDate 2026-07-13canCommit: false · MCP bearer cannot approve · reviewUrl /agents?approval=… · nothing started
I prepared a plan to start Emily’s joiner process. Open the review link in your browser where you’re logged into SquadBear and approve it.
get_approval_statusapprovalId from the reviewapproved · canCommit true
start_processsame arguments + approvalIdrun created · New joiner onboarding · 7 actions
You approved the exact proposal while signed in to SquadBear. Only then could I commit it. HR laptop is due Thursday; manager 1:1 is Monday.
Where is Engineering short next week, and who needs a heads-up?
get_team_absencesEngineering · next Mon-Fri4 of 18 out · peak Tue (3) · Platform hit hardest
get_coverage_risksEngineering · next weekPlatform Tue tight · no approver gaps
Four of 18 people are out next week; three overlap on Tuesday. No approver gaps.
What is our quarter-end PTO liability, and where is it concentrated?
get_pto_liabilityas of quarter-end · EUR€48.2k open · 12 people above 15 days
list_high_balancesmin 15 days · top 3Emily 22d · Marcus 19d · Mila 17d
Twelve people hold more than 15 days; the top three balances are Emily 22, Marcus 19 and Mila 17.
Is sick leave climbing this quarter, and which teams are driving the change?
get_absence_summarysick · Q2 vs Q1 · by teamSick Q2 +18% vs Q1 · 142 days · Engineering +31%
get_team_health_signalsEngineering · last 30 daysPlatform + Growth · elevated load · eNPS dip -4
Engineering accounts for the largest change (+31%). Platform and Growth also show lower eNPS, so workload is worth reviewing before drawing conclusions.
Give me our ISO 27001 Annex A people-control status before next week's surveillance audit.
list_policy_acknowledgementsA.6.1-A.6.4 · active staff + B2B · current SHA-25696% signed · 2 B2B contractors still on Acceptable Use v2.3
list_process_runsA.6.5 leaver checklist · last 90 days4 of 4 completed · all access revocation steps timestamped
All four offboardings in the last 90 days have completed access-revocation checklists. Two B2B contractors still need to acknowledge Acceptable Use v2.4 before the audit.
Why did Engineering ship 28% fewer story points in Sprint 8?
get_team_absencesEngineering · Sprint 8 (14 days)22 person-days out · 2 senior reviewers on leave in week 2
get_sprint_velocityjira · board ENG · Sprint 8 vs Sprint 734 of 47 pts shipped (-28%) · 13 pts stalled in review
get_pr_review_latencygithub · repo core · Sprint 8median first review 6h -> 31h during week 2 leave overlap
Output per available engineer-day held steady. Two senior reviewers were off in week two, pushing median PR review wait from 6h to 31h and stalling 13 points in code review.
Draft my manager review for Maya's Q4 round. Search the GitHub repo and Linear project I name. I pick every rating.
get_review_contextresp_maya_q4_manager · part goals2 goals frozen at open · later check-ins do not change them
get_review_contextresp_maya_q4_manager · part inputsPeer 1 by submission order · no name · upward not included
save_review_draftexpectedDraftRevision 0Draft saved · mentoring gap flagged · not submitted
Draft saved next to your answers. The goals were frozen when the round opened, and Peer 1 had no name. I flagged a thin mentoring example from the repos you named. You pick every rating and submit in SquadBear.
Less admin. More time for people.
Let your assistant handle routine leave, time and HR admin. Make room for the conversations and support your team needs.



