How to build a reviewer rota for casework team

Give each case an allocated caseworker, add a daily duty desk for urgent and safeguarding holds, and put a second reviewer on every adverse decision before it goes out. Set response targets around the deadlines the team owes the people it serves. The rota should never let one person both draft-approve and second-check a decision that goes against someone.

What is the casework rota for?

Casework agents read applications and evidence, request missing documents, check eligibility against the rules and draft decisions and letters. They hold what needs a person: adverse decisions, cases with conflicting evidence, anything that suggests a risk to someone's safety, and requests to depart from the rules. The rota decides who handles each of those, and how quickly.

Casework has a feature most queues lack: the person affected may be vulnerable, and the decision may shape their housing, income or status. Where the organisation is a public body, it also faces transparency and fairness duties, and in the EU some public uses of AI are classed as high-risk. Under GDPR, a decision with legal or similarly significant effect should not rest solely on automated processing; meaningful human review is the safeguard, and the rota is how that review is staffed. The casework manager owns the rota. The guide to AI agent skills by role sets out what caseworkers need to know.

What are the steps?

1. Agent, depth 1: reports holds by type, age and deadline. Adverse decisions, conflicting evidence, safeguarding flags, exception requests.
2. Person (casework manager): allocates cases. Each case has one caseworker so the person dealing with the team has continuity.
3. Person (casework manager): names a duty caseworker each day, with a backup. The duty desk takes safeguarding flags, urgent requests and allocated cases whose caseworker is away.
4. Person (casework manager): sets response targets. Safeguarding flags within hours; urgent hardship the same day; other holds well inside the deadline the organisation owes.
5. Agent, depth 2: drafts decisions and letters. With the rule applied, the evidence relied on, and the provenance of each fact.
6. Person (allocated caseworker): decides each held case. Approve, edit, request evidence or refer.
7. Person (second reviewer): checks every adverse decision before it is sent. Named on the rota by day.
8. Person (casework manager): reviews the rota weekly against targets and the second-review backlog.

What skills mix does each day need?

Three kinds of cover, every working day. Allocated caseworkers for their own cases. A duty caseworker trained in safeguarding referral. A second reviewer for adverse decisions, who must be a different person from the caseworker who decided. Exceptions to the rules go to the manager or a named senior with that authority; the approver authority matrix for the casework team sets who may grant what.

The second-reviewer line is where rotas most often fail. If only seniors can do it, they become the bottleneck and adverse decisions queue. The AI agent competency matrix for the casework team shows how experienced caseworkers can be brought onto that line.

Which controls matter, and what evidence do they leave?

• Allocation is recorded. Evidence: each case names its caseworker, and handovers are logged.
• Adverse decisions have two names. Evidence: the deciding caseworker and the second reviewer on the verdict.
• Safeguarding has a duty owner every day. Evidence: the rota and the time from flag to action.
• Facts are weighed by provenance. A document from the issuing authority is stronger than an applicant's statement; both may be legitimate. Evidence: the draft lists each fact's provenance and the caseworker's reason for relying on it.
• Exceptions are refused by the agent and decided by a person. Evidence: the refused verdict and the person's decision.

What should be measured?

• Holds decided inside the deadline owed.
• Safeguarding flags actioned within target.
• Second-review backlog and its age.
• Adverse decisions changed at second review, by reason; a high count points to a training need or a weak rule in the agent's brief.
• Cases handled by someone other than the allocated caseworker without a recorded handover: the target is none.

Where does it go wrong?

The duty desk absorbs everything. If allocated caseworkers push hard cases to the duty desk, the duty caseworker drowns and safeguarding waits. Keep the duty desk for what it is for.

Second review becomes a signature. A second reviewer clearing twenty adverse decisions in an hour is not reviewing. Cap the load per day on the rota.

Peaks are ignored. Casework often peaks after rule changes, at deadlines for applications and after public announcements. Look at the agent's hold history and staff for them.

Onboarding and procurement teams staff their queues with the same method; see the rotas for the onboarding team and the procurement team. This is an explanation of the rules, not legal advice; confirm how they apply to you with counsel.

Where the Academy fits

The Academy's Operator track trains the people who review a live workspace, with module tests set in the learner's own industry and role, so caseworkers are tested on casework. Certified Pryme Operator includes a two-week practicum signed off by a Pryme assessor. An organisation can choose to put only certified caseworkers on the second-reviewer line.