Assess Reasonableness Of Staffing Levels On Litigation Invoice

---
name: assess-reasonableness-of-staffing-levels-on-litigation-invoice
task_id: litigation-dispute-resolution/assess-reasonableness-of-staffing-levels-on-litigation-invoice
description: Reviewing litigation staffing on an invoice requires comparing each timekeeper's role and hours against the approved staffing plan, billing guidelines, and case phase to identify over-staffing, rate issues, and task-level mismatches.
activates_for: [planner, solver, checker]
---

# Skill: Assess Reasonableness of Staffing Levels on Litigation Invoice

## 1. Subject-matter triage

- Start by identifying the invoice period, the billed matter phase, and whether the record set contains a staffing plan, billing guidelines, staffing emails, and a case status summary.
- Determine whether the invoice is a single-period review or spans multiple periods, phases, or teams; if multiple, analyze each period or phase separately rather than blending them.
- Treat the staffing plan as the baseline authorization, the billing guidelines as the rule set, the staffing emails as evidence of approvals or expectations, and the case summary as the operational context.
- If the source materials do not support a particular comparison, say so explicitly and avoid guessing.

## 2. Failure modes the skill is correcting

- Flagging staffing issues in the abstract without cross-referencing the approved staffing plan to confirm which timekeepers and roles were authorized
- Noting billing-guideline issues without tying each deviation to the affected entry and its practical billing impact
- Overlooking the case phase dimension: staffing appropriate for intensive motion practice or trial preparation may be excessive during routine discovery and vice versa
- Conflating rate-related issues with staffing-level issues, which require different analytical treatment
- Treating approval emails as blanket authority rather than checking their scope, timing, and subject matter
- Collapsing multiple timekeepers, events, or billing periods into one generalized conclusion
- Describing a problem without stating how it scales, what document interaction drives it, and what consequence it creates for the client
- Issuing a memo that identifies defects but never translates them into line-item reductions or other billing adjustments

## 3. Legal frameworks / domain conventions that apply

- Approved staffing plans establish the baseline: roles, timekeeper levels, and headcount authorized for the matter; any deviation should be analyzed against client approval requirements
- Billing guidelines commonly govern rate caps by timekeeper level, prohibited billing practices, and pre-approval requirements for budget overages
- Block billing — recording multiple tasks in a single time entry — impedes assessment of individual task reasonableness and is disfavored; standard treatment is to evaluate whether the entry can be meaningfully reviewed or should be reduced
- Senior timekeepers performing tasks appropriate to junior timekeepers should be analyzed against the rate applicable to the task rather than simply the timekeeper's usual rate
- Multiple timekeepers attending the same event (deposition, hearing, call) requires justification; absent complexity warranting it, the staffing should be evaluated for excess headcount
- Administrative and clerical tasks (scheduling, document filing, photocopying) are overhead and generally not billable under most billing guidelines
- Budget overages beyond the guideline threshold require prior written approval; retroactive approval, if asserted, should be evaluated cautiously
- If the materials cite specific client billing rules, apply those rules first; use general billing norms only to fill gaps, not to override document-specific instructions

## 4. Analytical scaffolds

- Read the staffing plan first to establish which roles and timekeepers were authorized for the billing period.
- Read the billing guidelines next to identify rate caps, prohibited practices, pre-approval thresholds, and any staffing-specific limits.
- Read the staffing emails for evidence of express approvals, staffing changes, role substitutions, or objections, and check whether any approval is limited by date, project, phase, or task.
- Read the case status summary to understand what litigation activities were occurring during the invoice period, providing context for evaluating staffing levels.
- Enumerate the relevant billing periods, phases, timekeepers, and recurring event types before analysis when more than one appears in the source set.
- For each billing entry or timekeeper, assess in this order: authorized role, rate compliance, task-to-level fit, reviewability of the entry, and staffing density for the event or phase.
- For each identified issue, close the analysis by stating: the scale of the deviation in context, the document or rule interaction that makes it problematic, and the downstream billing consequence.
- Distinguish clear guideline violations from judgment-call issues; assign a severity to each and separate hard reductions from discretionary reductions.
- Quantify the impact of each deviation where possible and present a line-item reduction schedule or adjustment analysis.
- If the invoice is supported by more than one plausible reduction theory, identify them separately and avoid double-counting the same hours.

## 5. Vertical / structural / temporal relationships

- Compare staffing against the litigation phase at the time the work was performed; reasonable staffing in an intensive stage may be excessive in a routine stage.
- Compare seniority of the timekeeper with the complexity of the task; overskilled work may warrant a rate adjustment even when the time itself is necessary.
- Compare contemporaneous staffing emails with later invoice entries; an email can support approval only if it actually covers the billed work and time period.
- Compare repeated attendance patterns across depositions, hearings, meetings, and calls; a one-off support lawyer may be justified, while recurring duplication may indicate excess headcount.
- Compare invoice entries against each other to spot duplicated attendance, redundant review, or overlapping workstreams.
- If a task spans multiple phases or documents, analyze whether the staffing remained proportional as the matter evolved.

## 6. Output structure conventions

- Use an issue-by-issue memo format with a short executive summary, a methodology section, a findings section, a reduction schedule, and a closing recommendations section.
- Define a simple ordinal severity scale once at the top and apply it consistently to every issue entry.
- For each entry include: invoice line reference, timekeeper, issue type, severity, governing source, factual basis, analysis, recommended reduction, and resulting billing impact.
- Organize findings by deviation category such as unauthorized timekeepers, rate-related issues, task-level mismatches, administrative work, multi-timekeeper events, block-billed entries, and budget approval gaps.
- When several entries share the same defect pattern, provide a grouped explanation and then list the affected line items underneath it.
- Include a summary table of reductions by category and a separate total where the source materials permit arithmetic.
- End with an explicit Recommended Actions section that states the action, the responsible role, and the timing anchor drawn from the record; if no timing is stated, use the next practical litigation milestone or invoice review deadline.
- Keep the tone audit-ready and document-based; do not assert a staffing defect without naming the rule, the supporting source, and the billing consequence.