Legal Operations Annual Planning Guide

Definitions

Practical workflow

1. Set the planning mandate and calendar

   Define the planning year, fiscal calendar, scope, decision rights, required approvals, reporting currency, planning granularity, and dates for baseline collection, challenge sessions, approval, quarterly reforecast, and year-end review. State which legal entities, regions, practice areas, services, vendors, and initiatives are included or excluded.

2. Collect strategy inputs

   Gather the business strategy, growth and market assumptions, product and geographic plans, regulatory change, litigation or claims outlook, risk appetite, board or executive priorities, audit findings, control issues, client commitments, organizational changes, and service expectations. Record the source, owner, date, confidence, planning implication, and expected time horizon for every input.

3. Build the demand baseline

   Use a defined unit of work for each service, such as a request, matter, contract, obligation, filing, review, escalation, or initiative deliverable. Measure volume and standard effort by month or quarter, separate recurring from event-driven work, preserve unknowns, and reconcile system, finance, intake, matter, contract, compliance, and stakeholder evidence. Count a parent work item or its allocated substeps, not both.

4. Register obligations and fixed commitments

   List recurring filings, regulatory reviews, policy updates, audit support, board reporting, client or lender commitments, litigation deadlines, contract renewals, security reviews, records activities, training, access recertification, and other required work. Capture obligation ID, description, source, due date or cadence, effort estimate, criticality, owner, backup, evidence, dependency, status, and escalation path.

5. Define the service catalog and portfolio

   Group work into a stable service catalog such as advisory, disputes, contracting, compliance, entity work, legal requests, knowledge, reporting, and operations. Separate business-as-usual services, mandatory obligations, improvement initiatives, technology work, and discretionary investment so the portfolio shows what consumes capacity and cash. Assign a service owner and decision authority for each category.

6. Model capacity by role and period

   Create a role-based capacity view for lawyers, paralegals, legal-operations staff, analysts, administrators, contractors, and other declared resources. Record FTE or contracted hours, working calendar, leave, training, fixed non-legal work, planned reserve, allocation, skills, location, availability, and hiring or attrition assumptions. Keep available hours distinct from demand hours and from compensation or vendor spend.

7. Set the cash budget baseline

   Build an approved cash view by period, category, owner, vendor or matter where appropriate, currency, commitment status, and accounting treatment. Include external counsel, legal service providers, software, implementation, contractors, training, travel, subscriptions, and other cash categories that are in scope. Keep an internal capacity plan beside the cash budget; do not convert every hour into a saving or count the same cost in multiple categories.

8. Assess systems, data, and controls

   Inventory the systems and datasets needed to deliver or report the plan. For each important field, name the system of record, data owner, definition, refresh cadence, access rule, retention or evidence requirement, quality status, integration dependency, and reconciliation method. Identify duplicate registers, manual exports, missing identifiers, stale owners, inconsistent categories, and reporting limitations before using the data for targets or funding decisions.

9. Define initiatives and sequencing

   Turn prioritized problems into bounded initiatives with an objective, scope, non-goals, deliverables, milestones, required roles, effort by period, cash estimate, owner, approver, dependencies, risks, acceptance evidence, and decision gates. Sequence mandatory and enabling work before discretionary improvements when they protect deadlines, controls, data quality, or delivery capacity. Explicitly document work that is deferred or stopped.

10. Map benefits and measurement plans

    For every initiative, define the baseline, intended outcome, benefit type, measurement unit, eligible population, numerator and denominator where relevant, data source, owner, realization timing, confidence, and evidence required. Track service quality, cycle time, control completeness, risk exposure, capacity release, user effort, or cash spend according to the actual objective. A benefit can be operational without being a cash saving.

11. Register risks and dependencies

    Record risks and dependencies separately. A risk is an uncertain event or condition with probability, impact, response, owner, trigger, and review date. A dependency is a required input, decision, system, vendor, budget, skill, policy, or organizational action with a provider, recipient, due date, status, and escalation route. Show how each one affects obligations, demand, capacity, cash, delivery, or benefits.

12. Build comparable planning scenarios

    Prepare at least a baseline scenario and any decision-relevant alternatives, such as constrained capacity, higher demand, accelerated investment, delayed implementation, or a mandatory-control response. Keep the scope and time horizon consistent, state which assumptions change, and compare obligations met, demand covered, capacity gap, cash spend, initiative delivery, risks, dependencies, and expected benefits. Use ranges where evidence is weak and identify trigger points for switching scenarios.

13. Challenge, approve, and record decisions

    Run a cross-functional challenge with legal leadership, finance, business stakeholders, risk or compliance, technology, procurement, and accountable service owners as appropriate. Approve the baseline, assumptions, priorities, funding, capacity choices, risk responses, dependencies, and scenario triggers. Create a decision record for each material choice, including alternatives considered, evidence, dissent or uncertainty, expected impact, conditions, owner, approver, and next review date.

14. Launch the operating cadence

    Publish the approved plan, service commitments, initiative roadmap, obligation calendar, capacity view, cash budget, risk and dependency registers, benefits plan, owner list, and decision log. Use a monthly operating review for exceptions and delivery visibility, a quarterly reforecast for plan changes, and an annual close for outcomes, lessons, carryover, and next-year strategy inputs.

15. Run the quarterly reforecast

    At each quarter end, lock the prior actuals, update remaining demand and capacity from current evidence, refresh cash commitments and forecast, assess initiative delivery, review obligations, and update risks, dependencies, and benefit evidence. Preserve the original approved baseline, label changes as actual, forecast, assumption, or decision, and explain the reason and owner for each material variance. Reapprove changes that cross the agreed decision threshold.

16. Close the year and improve the model

    Compare plan, reforecasts, and actual results by service, obligation, role, initiative, cash category, and benefit. Explain variances without retroactively rewriting the baseline, close or carry forward decision records, verify realized benefits and unresolved risks, retire stale measures, and document lessons about demand definitions, capacity availability, budget treatment, data quality, and governance for the next planning cycle.

Comparison

Limitations and exceptions

• An annual plan is a decision and coordination instrument, not a guarantee that demand, budgets, staffing, legal outcomes, vendor prices, regulatory requirements, or benefits will follow the plan.
• Historical demand can understate work that was handled outside the recorded intake, absorbed by untracked overtime, deferred, declined, or hidden in business teams. Report data gaps and use sensitivity ranges instead of assigning unsupported precision.
• Capacity depends on the definition of productive time, role mix, skills, leave, training, fixed work, interruptions, supervision, and availability. FTE count alone does not establish usable capacity for a particular service.
• Capacity release is not cash savings. Internal hours may be redeployed to higher-value work, used as reserve, or absorbed by new demand without reducing any invoice, subscription, contractor payment, or other cash outflow.
• Budget variance can reflect timing, accruals, currency, committed but not invoiced spend, scope changes, accounting policy, or one-time transition costs. Label actual, committed, forecast, and approved values separately.
• A risk register and scenario model support decisions but do not predict legal outcomes, eliminate uncertainty, or replace professional judgment, control owners, financial review, security review, procurement, or required approvals.
• Benefits may be delayed, shared across initiatives, affected by external factors, or difficult to measure. Assign one primary attribution rule, disclose overlap, and do not count the same improvement as both a cash saving and a capacity release without separate evidence.

Primary sources

Methodology

The planning cadence, fields, formulas, scenario structure, and governance model in this guide are an organization-designed framework, not a universal legal-operations standard and not a prescription from the cited authorities. Start with a planning dictionary and a dated baseline. For every work item, record a unique ID, service category, work type, period, volume, standard effort in hours, source, owner, status, confidence, and whether it is recurring, event-driven, mandatory, discretionary, or already included in another work item. For demand in period p, use demand_hours_p = sum(volume_i,p x standard_effort_hours_i) across unique in-scope work items i. If a parent item is decomposed into substeps, allocate the parent effort across those substeps or keep the parent total, but never add both. Report known, estimated, unknown, and excluded demand separately. For capacity, choose one transparent method and keep its deductions non-overlapping. A gross-hours method is available_capacity_hours_p = sum(FTE_r,p x working_weeks_p x scheduled_hours_per_week_r) - leave_hours_p - mandatory_training_hours_p - fixed_non_legal_hours_p - planned_reserve_hours_p, where every term is in hours and each deduction is counted once. An allocation method can instead apply a declared legal-operations allocation to scheduled hours, but it must not also subtract the same fixed non-legal time. Capacity_gap_hours_p = available_capacity_hours_p - demand_hours_p; a negative value is a modeled shortfall and a positive value is modeled remaining capacity, not a service promise. For cash, use budget_variance_cash_p = actual_or_forecast_cash_spend_p - approved_cash_budget_p, with units of the stated currency, and budget_variance_percent_p = budget_variance_cash_p / approved_cash_budget_p x 100 only when the approved budget is non-zero. Keep approved, committed, invoiced, paid, forecast, accrual, currency, and one-time transition fields distinct. Capacity release is capacity_release_hours_p = comparable_baseline_demand_hours_p - post_change_demand_hours_p, measured in hours for the same scope, period, and work definition. For cash savings, define total_post_change_cash_spend = recurring_post_change_cash_spend + incremental_transition_cash_costs + replacement_cash_costs, then use confirmed_cash_savings = comparable_baseline_cash_spend - total_post_change_cash_spend. The total post-change term includes every comparable cash outflow for the same scope, period, currency, and accounting treatment, so transition and replacement costs are not deducted again. Numeric example: baseline cash spend 100, recurring post-change spend 70, transition cost 10, and replacement cost 0 produce total post-change spend 80 and confirmed cash savings 20. Do not convert internal hours into dollars without an approved costing policy, and do not claim a cash saving from redeployment, reduced effort, or a lower forecast alone. For benefits, define a baseline, unit, eligible population, owner, evidence source, realization date, attribution rule, and treatment of overlap; use one primary attribution rule when multiple initiatives affect the same result. Build scenarios from the same scope and units, change only named assumptions, show obligations and mandatory work first, and publish low, base, and high ranges when evidence is uncertain. Maintain standard fields for plan ID, planning year, source, as-of date, assumption, owner, approver, service, obligation, initiative, role, capacity hours, demand hours, cash category, currency, risk, dependency, benefit, scenario, status, decision, rationale, evidence, effective date, and next review. Each decision record should state what was decided, why, alternatives considered, evidence, dissent or uncertainty, impacts on demand, capacity, cash, risk, dependencies, and benefits, conditions, owner, approver, date, and review trigger. At each quarter, freeze actuals, refresh the remaining-year forecast, preserve the approved baseline, classify the change as actual, forecast, assumption, or decision, and reapprove material changes under the stated governance threshold.

FAQs

Related CaseDocker capabilities

Related guides and resources

• CaseDocker legal operations platform
• Case management information
• Compliance management information
• Legal operations benchmarks