Combine tasks into a source-linked work list
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 is the bounded source for this route. Other task products require their own documented acquisition path before inclusion.
- Owner-approved priority policy and review cutoff; approved mapping if records from other systems are supplied.
- 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
- Native export covers Clio tasks only, with completed and outstanding records exported separately. It is not a universal cross-system task collector.
- Do not fabricate source IDs, updated_at, timezones or due times missing from the export; inspect the original task or mark unknown. Source-local IDs are never assumed globally unique.

DECLARED INPUT CONTRACT
tasks.csv: source_system, source_id, task_id, matter_alias, exact_instruction, owner_alias, explicit_due_datetime, timezone, status, updated_at
priority-policy.txt

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 selected task 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.

Set source_system to Clio Manage. Preserve an actual source_id if visible; otherwise assign a source-row reference tied to the retained export and clearly label it local. Assign task_id aliases, then map actual instruction, assignee, status and due date after checking full task detail. Fill updated_at only from observed evidence. Enter timezone and date precision explicitly in Scope. Paste priority-policy.txt into a visible Policy worksheet. Keep rows from multiple exports and systems separate until identity is proven. Create named tables for Tasks. Put the policy and review scope in visible worksheets or paste them into the next prompt.

Expected output: tasks.csv plus visible Policy and Scope. If an additional system has no verified extraction, list it as excluded.
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 approved policy fields and review duplicate/conflicting source keys manually.

PASTE THIS PROMPT
Using Tasks, Policy and Scope, draft one review queue with source_system/source_id/task_id, matter_alias, exact_instruction, owner_alias, explicit_due_datetime, timezone, status and cited source rows. Apply only the supplied priority policy. Flag missing owner/date/timezone, conflicting versions and potential duplicates; never collapse tasks merely because wording is similar. Updated_at alone is not authority to replace an instruction. Preserve date-only precision. Do not calculate legal deadlines, edit tasks or send reminders.

Expected output: Source-linked queue with conflicts and acquisition gaps.
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 task owner checks every conflict against the source task, confirms scope exclusions and approves the queue. Keep any unacquired source system in the visible coverage note.

Expected output: Reviewed task queue, not an all-systems completeness certificate.
Use it next: Any external message, source change, payment or deletion requires its own authorized process.
Check: Never treat an empty export as proof that no tasks exist; check filters, permissions and separate completed scope.
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.
