Hire an AI team absence coverage reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A coverage change brief: what changed since last week, commitment by commitment
• A list of uncovered commitments: no accepted cover, or not enough hours
• Options for the manager when hours fall short: defer, reduce or add cover
• A draft handover for each commitment that changes hands, with its current state and next action
• MISSING lines for gaps, and a record for next week

How it does the job well

• Turn every request into owned actions: who, what and by when.
• Work from the real calendar, notes and lists. Never invent meetings, people or dates.
• Put the most important decision or deadline first, then the details.
• Prepare drafts and proposals. Sending, booking and changing records waits for approval.

Mistakes it avoids

• Repeating last week's gaps as new findings.
• Counting a verbal maybe as cover.
• Keeping personal details you do not need.
• Describing installation as a running automation.
• Losing commitments buried in long notes.
• Mixing confirmed facts with guesses about other people's plans.

What a good result looks like

An example, not your task: Two people on the same team are away in the same week.

• Changes since last review. Each commitment where an absence, a delivery date or an offer of cover changed.
• Commitments table. One row per critical commitment: owner, whether they are away, the cover person, whether cover is accepted, hours and status.
• Uncovered or short. Commitments with no accepted cover or too few hours, with defer, reduce and add-cover options for the manager.
• Draft handovers. A task-level handover for each commitment that changes hands: current state, next action and a source reference.
• Action list. Coverage actions with owners, dates, dependencies and acceptance still open.
• MISSING lines and CHECKS MISSED. Missing hours, owners or dates, and every check that could not run.

How the work is checked

• No proposed cover is described as accepted.
• Every critical commitment has an accepted cover owner or an explicit gap.
• Hours come from the sources, and a missing figure says MISSING.
• No absence reason, password or access detail appears in any file.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Read last week's record. Loads each commitment's ID, absence window, cover owner, whether they accepted, the next review and the source date. A first run builds a baseline with you.
• Find what changed. Flags any absence, delivery date or offer of cover that is new or different since the last record.
• Check every commitment. For each critical commitment, shows its owner as present or away, whether cover is accepted, and whether the cover owner's hours cover the hours needed.
• Weigh the gaps. When hours fall short, runs the Team capacity planner and lays out defer, reduce and add-cover options for the manager. It does not choose.
• Write handovers and actions. The Prepare a team absence handover workflow runs the Team capacity planner, the Handover note writer and the Executive action register keeper. Each handover has a source link, the current state and the next action.
• Check and save. Checks that no proposed cover is called accepted and that no access detail is written down. Saves the files, a run log and the new record, and keeps the old record.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id weekly-team-coverage-review-assistant only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/weekly-team-coverage-review-assistant/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Upcoming absence dates for each person, dates only (from your leave calendar)
• Critical commitments, each with an ID, a due date, an owner and the hours it needs (from your project or task list)
• Cover that people have offered or accepted, with each person's available hours
• The manager who decides on cover
• Last week's coverage record (optional, from the second week on)

Helpful context (optional)

• An export of your leave calendar, dates only.
• Your task or project list with owners and due dates.
• A note on each person's usual available hours.

Tools and access

• A capable chat AI with file support: Keeps the record between weeks. In a plain chat tool you paste the record in each time.
• A chat AI that reads files: It reads a task export and the person's notes together. It sends nothing and changes no tracker.
• Any good chat AI: It needs your numbers pasted in. A tracker or calendar connection saves typing.

Functions and deliverables

• Team absence coverage reviewer: Check who can cover critical work during absences. Get open gaps, time limits and draft handovers with owners still to confirm.
  • A coverage change brief: what changed since last week, commitment by commitment
  • A list of uncovered commitments: no accepted cover, or not enough hours
  • Options for the manager when hours fall short: defer, reduce or add cover
  • A draft handover for each commitment that changes hands, with its current state and next action
  • MISSING lines for gaps, and a record for next week
• Team absence handover planner: Share absence dates, current tasks and approved cover. Get a capacity check, task handovers, owners and open cover gaps.
  • A coverage map: each task, its deadline and its cover owner, or a named gap
  • A capacity check: where the cover is over or under
  • A handover note for each task, with current state, next action and links
  • An action list with owners, dates and whether each was accepted
  • An escalation list: who to call for what while the person is away
• Team capacity planner: Give it your team and projects. Get workload against people, who is overloaded, and whether you can take on more.
  • A table of hours available, hours used and percent full for each person
  • A list of who is over or under their target
  • Which coming projects fit and which leave a gap
  • Three to five options with the hours each one frees up
  • One recommendation, and what would change it
  • A list of assumptions and missing facts
  Source: Anthropic.
• Weekly work review planner: Review your lists, calendar and waiting-for items. Get open loops sorted, stalled projects flagged and next week planned.
  • Inventory of open loops
  • Each loop sorted to a list
  • Stalled projects flagged
  • Waiting-for follow-ups
  • Plan for next week
  Source: Alireza Rezvani.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• Two people on the same team are away in the same week.
• A delivery date moved earlier and the planned cover no longer fits.
• A cover person's hours were cut, or they said they cannot do it.
• Each week you want to know which critical commitments have no accepted cover.

Limits to check before starting

• A one-off cover request for a single task. Use the Handover note writer.
• You want a longer plan for hiring or workload. Use the Team capacity planner.
• You want to follow up on staff survey answers. Use the Employee feedback action reviewer.
• You need an end-of-shift note for a restaurant. Use the Restaurant shift handover reviewer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add the agent to Claude, ChatGPT or Gemini with its helpers, the Prepare a team absence handover workflow and the Team capacity planner. Or download the pack and attach it.
• Paste your absence dates, critical commitments with hours, and cover offers. Name the manager. From week two, paste last week's record.
• Read the uncovered list first. Check that every cover owner is marked accepted, not only proposed.
• Choose between defer, reduce and add cover yourself. Ask the people involved to confirm.
• Send each handover yourself. The agent only drafts.
• In a chat-only tool, copy the record it gives you and paste it in next week. Installing sets up no schedule, so you start each run.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/weekly-team-coverage-review-assistant for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.