Prepare the attorney review queue
Get the source data and prepare the review

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

WHAT WAS CHECKED
Official documentation checked; all routes are proposed and have not been run in a product account. No client data, account access, installs or account writes used. Native column names are distinguished from editorial kit contracts. Missing source evidence blocks completeness claims.

BEFORE YOU START
- Clio Manage task access for the selected review work, including authorized visibility of private tasks.
- Maintained attorney-review requests and a staff-approved escalation policy with conditions, owner and cadence.
- 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.

DATA ACQUISITION LIMITS
- The native task export does not establish submitted_at, acknowledged_at, blocker or last_reminder_at. Obtain those from the actual review request and acknowledgment records; absence is unknown.
- No general-purpose Clio Grow data-query chat is established. This route uses Manage's actual task export; no inferred review deadline or escalation authority.

DECLARED INPUT CONTRACT
reviews.csv: request_id, matter_alias, reviewer_role, decision_needed, approved_review_by, submitted_at, acknowledged_at, status, blocker, last_reminder_at
escalation-policy.csv: rule_id, condition, approved_owner, cadence

STEP 1: Collect the actual task list
Tool: Clio Manage
Open: Tasks > Outstanding (then Completed if required) > Filters > Apply filters > bottom Export > CSV > Export
Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested.

Choose the authorized users, matters and date range for the attorney review queue. 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.
Use it next: Keep the raw files restricted; prepare the alias-based input in the next step.
Check: 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.
Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises.
Source documentation:
https://help.clio.com/hc/en-us/articles/9204982812699-Filter-and-Export-Tasks
https://help.clio.com/hc/en-us/articles/9204917906971-Manage-Tasks-in-Clio-Manage

STEP 2: Map the observed records to the starter input
Tool: Excel and authorized staff
Open: Separate analysis workbook > Home > Format as Table
Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested.

Assign request_id and matter_alias. Copy reviewer_role from the actual assignment; copy decision_needed from the full request. Use the approved review-by instruction, not a legal deadline inferred from a document. For each request, inspect the actual submitted message, acknowledgment and reminder log locally and enter only observed timestamps/status/blocker. In escalation-policy.csv copy the approved rule_id, condition, approved_owner and cadence; include the reviewer cutoff/timezone in Scope. Create named tables for Reviews and EscalationPolicy. Put the policy and review scope in visible worksheets or paste them into the next prompt.

Expected output: reviews.csv and escalation-policy.csv in the supplied kit contracts. Keep a restricted source crosswalk from request_id to task/message evidence.
Use it next: Check the mapping against each original source before using AI.
Check: 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.
Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises.
Source documentation:
https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model

STEP 3: Review the bounded evidence with Copilot
Tool: Excel Copilot, optional
Open: Approved analysis workbook > Copilot icon at lower right > Chat only
Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested.

Use Chat only and submit the prompt. Without Copilot: sort by supplied review-by and status, then apply the supplied escalation table row by row.

PASTE THIS PROMPT
Using Reviews, EscalationPolicy and Scope only, return request_id, reviewer_role, decision_needed, approved_review_by, status, blocker, suggested_queue_position, matching_rule_id and reason with worksheet row references. Separate missing acknowledgment, overdue approved review-by, missing required facts, paused/completed and not-yet-due. Apply only the supplied cadence and last_reminder_at; unknown reminder history blocks a recommendation to send. Do not invent deadlines, urgency, delegation or legal advice. Draft a neutral internal reminder only where the supplied rule permits; do not send or edit.

Expected output: Prioritized attorney-review queue and optional rule-supported reminder drafts.
Use it next: Copy the draft exception list to the reviewer; retain row references.
Check: Check every flagged row and the scope. A fluent answer is not evidence of completeness; no automatic workbook or source-system edits.
Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises.
Source documentation:
https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel
https://support.microsoft.com/en-us/excel/copilot/frequently-asked-questions-about-copilot-in-excel

STEP 4: Approve the review result
Tool: Responsible staff reviewer
Open: Reviewed local worksheet
Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested.

The supervising attorney verifies dates, decision requests, ownership and whether an acknowledgment or reminder occurred elsewhere. Approve a queue and resolve missing evidence before any reminder is sent.

Expected output: Approved review queue with unresolved rows preserved.
Use it next: Any external message, source change, payment or deletion requires its own authorized process.
Check: A task due date is not automatically the approved review-by date; completion and silence are not acknowledgments.
Documentation limit: Editorial human-review gate; linked Excel documentation supports the worksheet used, not legal or accounting conclusions.
Source documentation:
https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- Actual account access, plan and source-data completeness have not been tested.

USING THE FILES IN THIS KIT
Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs.

The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.