--- title: "Law Firm Capacity Planning Without the Guesswork | Woven Legal" description: "Plan law firm capacity with workload signals, role clarity, repeatable processes, and support options that prevent growth from becoming chaos." url: https://wovenlegal.multisites.ai/guides/law-firm-capacity-planning publisher: Woven Legal phone: quote: https://wovenlegal.multisites.ai/contact --- # Law Firm Capacity Planning Without the Guesswork Capacity planning compares the work a firm expects with the time and skills available to complete it. Count active work, recurring tasks, deadlines, review effort, and interruptions. Then choose whether to remove work, improve the process, shift ownership, or add support. Recheck the plan as demand and priorities change. Capacity planning is the practice of matching expected work with the time, skills, and attention available to complete it. It helps a firm decide whether the next move is to remove work, improve a process, delegate preparation, hire, or add fractional support. It is not a promise that every week will be predictable. It is a way to make tradeoffs visible before growth turns into late nights and missed handoffs. ## Count work in a way the team can repeat Start with work units the firm recognizes: new inquiries, open matters, hearings, filings, drafts, client updates, invoices, and closed files. Count the units by week or month. Add the recurring operating work that does not appear in a matter count, such as meetings, training, billing review, and system maintenance. If the measure ignores that work, the plan will overstate available time. Use a small sample to estimate effort. Record active minutes and elapsed time separately. A document may take an hour to draft but wait two days for facts or review. Mark interruptions that are part of the role and interruptions caused by an unclear process. Label estimates as estimates and update them when the firm has better records. ## Make role capacity visible For each role, write the work the person owns, supports, reviews, and cannot perform. Include skills that matter for the current queue. An attorney with open court deadlines has different capacity from an attorney with only internal projects, even when both work the same number of hours. A paralegal with a full drafting queue cannot also absorb every intake follow up without a tradeoff. Include review capacity. Work is not complete when a draft exists if the attorney must still read and approve it. A queue that grows faster than the review slot is a bottleneck even when the support person has time. Put the reviewer's capacity in the plan and protect the review rhythm. This is often where a good delegation plan fails. ## Map demand and deadline risk List known demand for the next four to eight weeks. Separate committed work from possible work. Mark court or client deadlines, work that depends on outside information, and work that can move without consequence. A simple risk view shows where the firm needs to act before demand becomes a late emergency. Do not plan only for the average week. Include a reasonable peak and one absence. Ask which work would stop first if a key person were unavailable. If the answer is unclear, the firm has a coverage and documentation gap. The capacity plan should include a trigger for reviewing the queue when new work arrives, not only a monthly meeting. ## Choose the right response to a gap A capacity gap has several possible responses. Remove low value work, simplify the process, delegate preparation, change the deadline, add a tool, or add people. Choose the least complex response that protects the result. More software cannot solve a missing owner. More hours cannot solve a process that creates the same rework every week. Write the decision and the reason. If the firm adds a fractional paralegal, state the scope, hours, systems, reviewer, and time for reassessment. If the firm delays work, communicate the change. If it removes a task, record what will no longer happen. Capacity planning is a leadership tool when the team can see the tradeoff. ## Use a weekly capacity review A weekly review can be short. Look at the queue, deadlines, blocked work, new requests, and available review time. Ask what changed since the last plan. Move tasks to the person who can perform them, postpone tasks that do not protect a commitment, and escalate decisions that need attorney judgment. Keep the review focused on decisions rather than a status recital. Track a few signals over time: overdue tasks, queue age, attorney review time, client follow up volume, unplanned work, and rework. A trend matters more than one bad day. If the same signal worsens for several weeks, run a workflow audit. The plan should point to the process that needs attention. ## Use technology to make capacity visible A practice management system can show tasks, owners, deadlines, and status. It can also hide capacity if the team does not update it or if every task has the same priority. Define the fields that matter and make the next action visible. A dashboard is useful when it changes a decision, not when it adds another report nobody reads. Automated workflows can create tasks, send reminders, and record runs. They cannot decide whether the queue has enough review capacity unless the firm defines that rule. Start with a manual capacity review, then automate a predictable signal such as overdue tasks or an incomplete handoff. Keep a person responsible for interpreting the signal. ## Build capacity by documenting repeatable work A process that lives in one person's head is not capacity. Document recurring work with the trigger, inputs, sequence, owner, review, exception path, and finished result. Teach a second person to follow it with a safe example. This creates coverage and makes delegation possible. It also shows which work is too unclear to transfer. The documentation should be short enough to use in the queue. Link to approved templates and the source record. Review it when the same question appears twice or when the tool changes. A process document is part of capacity planning because it reduces the time needed to add or cover a role. ## Know when to add fractional support Fractional support can fit a temporary or uneven demand pattern when the firm can define the work and supervise it. It may support intake, document preparation, research organization, client updates, billing preparation, or other approved tasks. Decide whether the need is a short peak, a recurring monthly load, or a process that first needs redesign. Woven Legal publishes a model that combines workflow improvement with fractional U.S. based legal support. Ask how the team matches the person, how the relationship is managed, and how the firm reviews the work. Bring capacity data rather than a general feeling of being busy. A clear queue makes the right support easier to choose. ## Make the change stick Before you change the capacity plan, write down the current path in enough detail that another person can explain it. Record the trigger, the first owner, the handoffs, the waits, the review points, and the finished result. Use a safe sample when the process touches client information. The sample should include one ordinary case and one case that needs clarification. This baseline prevents the team from comparing a polished example with a messy real one. It also gives the person leading the change a way to answer questions without relying on memory. , During the first cycle, make the new behavior easy to see. Keep one queue, one status vocabulary, and one place for the next action. Ask the owner to note a blocked item instead of working around it in a private message. The purpose is to learn where a queue that grows faster than review time appears. If a person solves the issue with an unrecorded shortcut, capture the shortcut and decide whether it belongs in the standard process. A visible exception is a design input. A hidden exception becomes a surprise later. , Use a small review sample rather than waiting for a complaint. Check work units, active time, waits, and role capacity and compare the record with the definition of done. Look for missing inputs, duplicate entry, unclear ownership, and work that appears complete but still needs a decision. Ask the person who receives the work whether it was usable without another explanation. That question often finds a quality issue sooner than a manager reviewing the dashboard. Keep client facts out of general notes and keep the review tied to the approved matter system. , If the first result is mixed, keep the useful part and change one variable. You might clarify a required field, move the review earlier, change the queue owner, or shorten the template. Do not add three new tools to compensate for one unclear rule. A process becomes harder to learn each time the team creates a special path. Write the change, the reason, and the date. The next review should test whether the next capacity decision is now easier to complete and easier to check. , Teach the revised process to a second person before you call it stable. Ask that person to follow the instructions with a safe example and to explain what they would do when demand arrives outside the committed plan. Notice where the person pauses, asks for a missing decision, or chooses the wrong record. Those moments show where the instructions need a clearer rule. Teaching is also a capacity test. If only the original owner can perform the work, the firm has documented a dependency, not created resilience. , At the review date, decide whether to keep, revise, or stop the change. Keep the evidence with the process owner and record the next check. A good operating decision can be modest. The firm may decide that the new path saves review time but needs a better intake field, or that a support role should own the queue while the attorney keeps approval. The important result is a shared decision based on the weekly signal and its trend. That record makes the next improvement faster and prevents the team from reopening the same debate. , Keep the final decision visible to the people who perform the work. A short note in the queue or process page is enough when it names the owner, effective date, and next review. Visibility turns a one time project into a shared operating habit. ## Use this worksheet with your team Swipe or scroll to see all columns → Question Evidence to collect Decision What work is expected? Units, active time, elapsed time Separate committed and possible work Where is the bottleneck? Review time, queue age, rework Fix the constrained step first What response fits? Remove, simplify, delegate, support Choose the least complex safe response When do we recheck? Weekly signals and trigger Make the plan a living practice ## Seven checks before you change the process - Count matter work and recurring operating work. - Separate active time, waiting time, and review time. - Map role ownership and single points of failure. - Include demand, deadlines, and one absence scenario. - Record the tradeoff for every capacity decision. - Review a small set of signals each week. - Use support only after the scope and supervision are clear. ## Choose the next practical step If your firm is busy but cannot explain where the time goes, schedule a Woven Legal capacity audit. Bring the next month of work, current roles, and the signal that worries you most. Keep the operating language consistent as you improve the process. Start with [workflow](https://wovenlegal.multisites.ai/glossary/workflow), then define the handoff in [client intake](https://wovenlegal.multisites.ai/glossary/client-intake) or [delegation](https://wovenlegal.multisites.ai/glossary/delegation). Record the repeatable method in a [standard operating procedure](https://wovenlegal.multisites.ai/glossary/standard-operating-procedure). When extra capacity is the answer, compare a [fractional paralegal](https://wovenlegal.multisites.ai/glossary/fractional-paralegal) model. Add a [quality assurance](https://wovenlegal.multisites.ai/glossary/quality-assurance) check, then use [document automation](https://wovenlegal.multisites.ai/glossary/document-automation) and [capacity planning](https://wovenlegal.multisites.ai/glossary/capacity-planning) only where they reduce work without hiding responsibility. ### Sources - [Woven Legal homepage](https://wovenlegal.com/) - [Woven Legal mid-year operations audit](https://wovenlegal.com/midyearaudit/) - [Clio: Get Started With Workflows](https://help.clio.com/hc/en-150/articles/40497576076699-Get-Started-With-Workflows) ## Your next chapter starts with a little clarity. Find out where your firm can save time, reduce payroll pressure, and make room for more. [Schedule a free strategy call](https://meetings.hubspot.com/dpriday) No obligation. No pressure. Just a clear next step.