# Find gaps in recorded time Canonical page: https://agents.paretoid.com/workflows/find-gaps-in-recorded-time/ Category: Operations & Reporting Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Compare activity records with time entries without guessing how long work took. Status: Proposed / not tested. The public discussion supports the problem; the method source supports only the documented features. No outcome from this adapted recipe has been verified. Verification: The linked sources support the complaint and documented method components. We have not run this recipe or verified its results. The example below is synthetic, not a customer result. ## The problem Compare activity records with time entries without guessing how long work took. Why it matters: Small tasks can go unrecorded, while overlapping records can duplicate time. A reconciliation gives timekeepers questions to resolve from actual work records without inventing duration or billability. ## Sources and evidence - pain: [Pain evidence: Billable hours feel impossible](https://www.reddit.com/r/paralegal/comments/1umlr4s/billable_hours_feel_impossible/) Billable hours feel impossible, 2026-07-03, older. OP describes working on 15+ matters with small tasks and forgetting to start/stop timers. This supports a missing-record check, not automatic estimates of billable duration. - method: [Method: Clio time entries](https://help.clio.com/hc/en-us/articles/9289741706779-Time-Entries) Clio time entries documents entries associated with tasks, communications and other activities; Clio reports/export documents CSV/PDF reports and report-specific date caveats. - method: [Method: Clio reports/export](https://help.clio.com/hc/en-us/articles/9290078155803-Clio-Manage-Reports-Presets-and-History) Additional official capability reference. It does not validate the complete proposed recipe. Source checked: October 15, 2026. Pain reports are self-reported and identities are unverified. Method documentation supports components, not a tested end-to-end workflow. ## Suggested approach Start when: Day-end review 1. compare approved activity metadata with existing entries 2. Keep row or page references and mark missing or ambiguous evidence. Do not apply the suggested changes. 3. The responsible staff member checks the draft against the source records and approves any separate action. ## What you need - Clio Manage with access to the selected matters; Manage AI entitlement only for the optional AI Actions view. - Timekeeper review is mandatory. Actual durations come only from contemporaneous recorded evidence, never AI estimation. - 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 - AI Actions update overnight and activity suggestions concern the prior 24 hours. This is a candidate-finding aid, not a complete historical audit. - A communication, document or completed task does not establish billable work or duration. No unrecorded minutes are reconstructed. Access and setup: - Actual account access, plan and source-data completeness have not been tested. ### 1. Inspect native unlogged-activity suggestions Tool: Clio Manage AI, optional Location: Matters > chosen matter > Dashboard > AI Actions card Review suggestions for unlogged communications, notes or completed tasks. Open the cited source to check that the activity exists; do not accept or save a suggested entry. No prompt is required for this native proactive feature. Without AI, inspect the matter’s Communications, Notes and Tasks subtabs directly for the bounded period. Expected output: Candidate source activities with actual timestamps and source references, not proposed billable time. Next step: Create a reviewed activity ledger in the next step. Check before continuing: AI suggestions are refreshed overnight and limited in scope. No suggestion and no visible time entry is not proof of missing work. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://help.clio.com/hc/en-us/articles/29765932267675-Plan-With-Proactive-AI-Actions https://help.clio.com/hc/en-us/articles/9285920226075-Get-Started-With-Matters ### 2. Check existing recorded time Tool: Clio Manage Location: Selected matter > Activities; main Activities table for date/user filtering Read matching time entries for the same matter, person and period. Use actual recorded time and work description; distinguish hourly duration from flat-rate quantity. Keep any source link between an activity and entry only when explicit. For details use the entry’s existing detail/Edit view without changing or saving it. Expected output: Reviewed entries with recorded duration, actor and source reference. This route uses bounded manual capture; a general activity CSV export schema is not verified. Next step: Keep source pointers restricted; map alias-based Activities and Entries tables. Check before continuing: Different timestamps or wording do not prove distinct work; a single entry may legitimately cover multiple activities. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://help.clio.com/hc/en-us/articles/9289741706779-Time-Entries https://help.clio.com/hc/en-us/articles/9290390462875-Navigate-Clio-Manage ### 3. Map the observed records to the starter input Tool: Excel and authorized staff Location: Separate analysis workbook > Home > Format as Table Populate activities.csv with activity_id,matter_alias,actor_alias,activity_datetime,activity_type and actual_duration_minutes_if_recorded. Leave duration unknown unless actually recorded. Populate entries.csv with entry_id, an explicitly known activity_id_if_known, matter_alias,actor_alias,recorded_minutes and a safe narrative_category. Add reviewed period, timezone and coverage exclusions to Scope. Create named tables for Activities and Entries. Put the policy and review scope in visible worksheets or paste them into the next prompt. Expected output: Two staff-created tables retaining actual source evidence, with no invented time. 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. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model ### 4. Review the bounded evidence with Copilot Tool: Excel Copilot, optional Location: Approved analysis workbook > Copilot icon at lower right > Chat only Use Chat only and submit the prompt. Without Copilot: compare explicit activity IDs, then manually inspect ambiguous matters/persons/dates without adding time. Prompt: ```text Compare Activities and Entries within Scope. First list exact explicit activity_id matches. Then list unmatched activities or ambiguous possible matches as review candidates, citing source row IDs. Return activity_id, candidate_entry_ids, finding and missing_evidence. Never estimate duration, convert timestamps into worked minutes, decide billability or create a charge. A missing activity link is not necessarily missing billed time. Preserve all recorded minutes unchanged. ``` Expected output: Timekeeper-review candidates, not time entries to post. 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. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step 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 ### 5. Approve the review result Tool: Responsible staff reviewer Location: Reviewed local worksheet The actual timekeeper checks contemporaneous records and decides whether any entry is missing or wrong under the firm’s billing rules. Close a candidate as already captured, unresolved or requiring a separately approved correction. Expected output: Reviewed gap checklist with no inferred billable minutes. Next step: Any external message, source change, payment or deletion requires its own authorized process. Check before continuing: Do not use AI-generated duration or a default minimum charge. The workflow stops before posting time. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model ## What you will get Approved assistant workspace for matching; output time-review.csv with activity_id, candidate_entry_ids, match_status, duration_evidence, question. ## Human review and limits Timekeeper confirms actual work, duration and matter; billing reviewer determines treatment. Test overlapping activities and a non-billable task to ensure neither becomes fabricated billable time. 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. What to measure: During the pilot, count findings confirmed by the reviewer, false alarms, and missing-input cases. Do not infer time or money saved. ## Original prepared-input schema activities.csv: activity_id, matter_alias, actor_alias, activity_datetime, activity_type, actual_duration_minutes_if_recorded. entries.csv: entry_id, activity_id_if_known, matter_alias, actor_alias, recorded_minutes, narrative_category. Synthetic example input: ```text ACT1: no entry, duration not recorded ACT2: two entries claim the same activity ACT3: non-billable activity with recorded minutes ``` Expected synthetic output: ```text ACT1: duration unknown, ask timekeeper ACT2: possible duplicate ACT3: preserve minutes and supplied non-billable status ``` Failure check: Timekeeper confirms actual work, duration and matter; billing reviewer determines treatment. Test overlapping activities and a non-billable task to ensure neither becomes fabricated billable time. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/a04-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/a04/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/a04/README.txt) — Required inputs, file use, review steps and limits - [Activities blank CSV](https://agents.paretoid.com/assets/starter-kits/a04/activities-template.csv) — Blank input headers for activities.csv - [Activities synthetic example](https://agents.paretoid.com/assets/starter-kits/a04/activities-example.csv) — Synthetic test records for activities.csv - [Entries blank CSV](https://agents.paretoid.com/assets/starter-kits/a04/entries-template.csv) — Blank input headers for entries.csv - [Entries synthetic example](https://agents.paretoid.com/assets/starter-kits/a04/entries-example.csv) — Synthetic test records for entries.csv - [Synthetic example expected results](https://agents.paretoid.com/assets/starter-kits/a04/expected-results.txt) — Compare a pilot result with the planted exceptions ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Compare the supplied activity ledger and time-entry export. Identify activities without a plausible entry and entries apparently duplicated. Cite source IDs. Preserve actual recorded durations exactly; where duration is unknown, write ‘timekeeper confirmation required.’ Do not treat elapsed email timestamps as work duration, infer billability, round time, inflate descriptions or post entries. INPUTS activities.csv: activity_id, matter_alias, actor_alias, activity_datetime, activity_type, actual_duration_minutes_if_recorded. entries.csv: entry_id, activity_id_if_known, matter_alias, actor_alias, recorded_minutes, narrative_category. OUTPUT Approved assistant workspace for matching; output time-review.csv with activity_id, candidate_entry_ids, match_status, duration_evidence, question. Use only the supplied synthetic or firm-approved inputs. Cite source row or page IDs for each finding. Keep unknowns unresolved. Return a draft for the responsible staff reviewer. Do not send messages, connect accounts, change records, move money, or make legal decisions. Keep source files unchanged. If an input or permission is missing, list what is needed and stop that check. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.