When someone leaves, goes on vacation or changes sites, an admin usually spends an hour clicking through users, sites, units, schedules and corrective actions, and something still gets lost: an audit that keeps landing on a person who is gone, a corrective action nobody owns. With monitorQA connected to Claude, the admin describes the situation in one message and Claude does the rest.
The scenario
The admin writes in Claude: John Doe is leaving on Friday. Hand over his work so nothing gets lost.
What Claude does
1. Takes stock. Claude finds John in monitorQA and collects everything tied to him:
- open audits, grouped by site
- open corrective actions and issues where he is an assignee
- schedules that create audits for him, including schedules assigned to a whole unit he belongs to
- the sites he has access to, and whether that access is personal or comes from a unit
2. Shows who can take over. For each of John's sites Claude lists the auditors who already have access there, so the work goes to people who can open it right away.
3. Proposes a plan and waits for confirmation. Nothing changes until the admin agrees. For example:
John has 38 open audits on 3 sites, 5 corrective actions and 2 issues.
- Downtown Store → Maria Lopez (already has access)
- Riverside Mall, Airport Café → Tom Baker (already has access)
- The corrective actions and issues already have other assignees, so I'll just remove John from them.
- John gets audits from a schedule assigned to the "North Region" unit. I'll remove him from the unit, otherwise new audits will keep appearing on him. Shall I go ahead?
4. Hands over the work. Two ways, depending on the situation:
- One successor. If everything goes to one person, Claude transfers John's open audits, corrective actions and site access to the successor in a single step.
- Split by site. If the work is divided, Claude reassigns the audits site by site and grants access where it's missing.
5. Stops new work from reaching John. Claude removes him from schedules and units so that recurring audits are created for the right people from now on. This is the step that is easiest to forget by hand.
6. Closes access. Claude revokes John's access to sites. The user account is deleted only if the admin explicitly asks, which also frees a licence seat.
7. Reports. At the end Claude lists exactly what was handed over and to whom, and anything that needs a decision, for example corrective actions that are years overdue and should probably be closed rather than handed over.
Good to know
- Transfer vs. split. Transfer is the fastest option when one person replaces another. When the work is divided between several people, Claude reassigns it by site instead.
- Unit access is not personal. If John received audits through a unit, transferring his personal assignments is not enough: he also has to be removed from the unit. Claude checks this for you.
- You stay in control. In a chat, Claude always shows the plan before changing anything. Turn off Allow making changes in the connector if you want Claude to only report.
More things to ask
- "Anna is on vacation from 1 to 14 December. Give her audits to Mark and return them when she's back."
- "Add Alex Green, alex@company.com, as an auditor with the same sites as John."
- "Who has access to Downtown Store, and through which unit?"
- "Which auditors have more than 20 open audits? Suggest how to rebalance."
- "Are there audits or corrective actions assigned to people who no longer work here?"
What you need
- Admin role in monitorQA
- monitorQA connected to Claude with Allow making changes turned on