Prepare a coverage handoff before leave

Practice relevance

Cross-practice idea · A general operational method. Review the stated tool and jurisdiction limits before use.

The problem

List upcoming work, assigned coverage and missing acknowledgments.

Why it matters: Work can be missed when the original owner is away and coverage has not been accepted. A clear handoff shows who has actually agreed to each task and where a supervisor still needs to decide.

Sources & evidence

Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified.

What’s been verified

Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result.

What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed.

Pain evidence: I shouldn’t be surprised ↗I shouldn’t be surprised, 2026-06-18, older. OP and comments describe last-minute assignments and handoffs immediately before leave despite earlier planning.
Method: Clio task filtering/export ↗Clio task filtering/export supports task exports and owner/date filters. This is a prepared-file workflow, not an automatic cross-calendar integration.

Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. We wrote these prompts. The adapted workflow hasn’t been tested.

Suggested approach

Start when: Approved leave starts within the firm's review interval

consolidate open tasks, explicit dates and blockers
Keep source references and report unknowns instead of filling gaps.
The responsible reviewer checks the report before any separately approved action.

Limits and review

The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included.

Who reviews it: Departing staff and cover owner review and acknowledge; supervisor resolves gaps. Test a task with no owner and a new item arriving after packet creation.

What you need

Your firm-approved AI assistant · prepared files

Clio Manage task access and a defined absence window with timezone.
Actual, explicit cover assignments and acknowledgment records; a role label alone is not acceptance of responsibility.
Firm-approved Excel; optional Copilot entitlement and tenant approval for the exact minimized data. Native Excel analysis can be done manually if Copilot is absent.
Keep raw exports and identifying source pointers in a separate restricted location. The AI workbook contains only approved alias-based tables and visible policy/scope text, never raw client records on another tab.
Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details.

How to use

Documentation-checked proposed route; source collection and human approval required

Before you start

Task export does not supply a complete coverage rota or prove that a cover lawyer accepted a task. Off-system work and private tasks need separate review.
This route prepares a handoff; it never reassigns tasks or recalculates deadlines.

Check access and setup

Actual account access, plan and source-data completeness have not been tested.

Collect the actual task list
Clio Manage · Tasks > Outstanding (then Completed if required) > Filters > Apply filters > bottom Export > CSV > Export
Choose the authorized users, matters and date range for the absence handoff, including overdue and undated outstanding work. Include undated tasks when the scope requires them. Export Outstanding and Completed separately; note filters, capture time and visible record count. Use Expand rows or Print task from the task row menu to inspect full instructions where necessary.
Expected output
Native task CSV file(s), plus a scope note. Exact CSV headers must be inspected; the kit headers are not promised native fields.
Next step
Keep the raw files restricted; prepare the alias-based input in the next step.
Check before continuing
Private tasks may be invisible. Task export is only the selected scope; exporting does not prove all review requests or off-system obligations exist here.
Step documentation 1 ↗Step documentation 2 ↗
Map the observed records to the starter input
Excel and authorized staff · Separate analysis workbook > Home > Format as Table
Map each actual task to task_id and matter_alias; preserve observed status and owner_role. Copy next_explicit_action, blocker and approved_due_datetime from the task/request after staff verification. Record a secure_internal_link_id that resolves only in a separate restricted crosswalk. From the approved rota and actual replies enter absence_start, absence_end, task_id, explicitly_assigned_cover_role and acknowledgment_status into Coverage. Date-only deadlines remain date-only with timezone/precision noted in Scope; do not fabricate midnight. Create named tables for Tasks and Coverage. Put the policy and review scope in visible worksheets or paste them into the next prompt.
Expected output
tasks.csv and coverage.csv; both editorial mapped inputs.
Next step
Check the mapping against each original source before using AI.
Check before continuing
Aliases and missing policy fields are staff-created; do not relabel a native export as the kit schema. Unknown stays blank/unknown, not false or zero.
Step documentation 1 ↗
Review the bounded evidence with Copilot
Excel Copilot, optional · Approved analysis workbook > Copilot icon at lower right > Chat only
Use Chat only and submit the prompt. Without Copilot: filter by the absence window and inspect each task against its coverage record.
Excel Copilot, optional promptRead Tasks, Coverage and Scope. Build a coverage handoff grouped by explicitly_assigned_cover_role, listing task_id, matter_alias, exact next action, supplied due date/time, blocker, acknowledgment status and secure_internal_link_id. Flag unassigned cover, missing acknowledgment, conflicting assignments, undated items and tasks due before/during the absence. Cite input rows. Do not infer legal deadlines or assign responsibility. Unknown cover is uncovered, not delegated. Do not send or edit.
Expected output
Handoff draft plus an uncovered/unacknowledged-task checklist.
Next step
Copy the draft exception list to the reviewer; retain row references.
Check before continuing
Check every flagged row and the scope. A fluent answer is not evidence of completeness; no automatic workbook or source-system edits.
Step documentation 1 ↗Step documentation 2 ↗
Approve the review result
Final human review
Responsible staff reviewer · Reviewed local worksheet
The outgoing owner and supervising lawyer confirm the scope, inspect original task instructions and obtain explicit acceptance through the firm’s normal process. Mark the handoff approved only when the actual acknowledgments are checked.
Expected output
Reviewed handoff and unresolved coverage exceptions.
Next step
Any external message, source change, payment or deletion requires its own authorized process.
Check before continuing
Keep missing acknowledgment visible. The draft itself is not notice, acceptance or a reassignment.
Step documentation 1 ↗

What you’ll get

Approved assistant workspace; coverage-handoff.md and unanswered-ownership.csv. Human reviewers acknowledge in their existing tool.

Inputs and a sample test Synthetic example · not a measured result

Input files

tasks.csv: task_id, matter_alias, status, next_explicit_action, approved_due_datetime, owner_role, blocker, secure_internal_link_id. coverage.csv: absence_start, absence_end, task_id, explicitly_assigned_cover_role, acknowledgment_status.

Synthetic example

Synthetic inputs are included in the starter kit.
tasks-example.csv
coverage-example.csv

Expected output

Task T3 falls within leave and has no assigned cover → owner gap highlighted. Do not nominate an available colleague as if assignment were authorized.

Test a failure

Departing staff and cover owner review and acknowledge; supervisor resolves gaps. Test a task with no owner and a new item arriving after packet creation.

Try with the sample files

Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.

Download inputs and checklist 8 files

Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.

Download starter kit All inputs, synthetic examples and review notes in one ZIP. No automation is installed.
Start here: get the sources and prepare the review Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits
Setup and review checklist Required inputs, file use, review steps and limits
Tasks blank CSV Blank input headers for tasks.csv
Tasks synthetic example Synthetic test records for tasks.csv
Coverage blank CSV Blank input headers for coverage.csv
Coverage synthetic example Synthetic test records for coverage.csv
Synthetic example expected results Compare a pilot result with the planted exceptions

Optional full review prompt for prepared inputs

Prepared-input review prompt with Your firm-approved AI assistant · prepared files

Create a coverage handoff for this supplied absence period. For each open matter include task ID, latest approved status, next explicit action, approved due date, named cover owner and missing information. Separate tasks due during leave from later work. Do not assign new responsibility, infer legal deadlines or mark anything handed off without acknowledgment.

INPUTS
tasks.csv: task_id, matter_alias, status, next_explicit_action, approved_due_datetime, owner_role, blocker, secure_internal_link_id. coverage.csv: absence_start, absence_end, task_id, explicitly_assigned_cover_role, acknowledgment_status.

OUTPUT
Approved assistant workspace; coverage-handoff.md and unanswered-ownership.csv. Human reviewers acknowledge in their existing tool.

Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing.

Proposed / not tested · editorial prompt. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.

Read original method Read pain evidence