How to run attorney fee calculations in DocketMath for United States (Federal)

Step-by-step

Run this scenario in DocketMath using the Attorney Fee calculator.

This guide walks you through running attorney fee calculations in DocketMath for United States (Federal) matters using the attorney-fee calculator. The goal is to help you generate a repeatable number you can reference in your workflow (for example, for internal review, budgeting, or drafting your own calculations). This is not legal advice—treat outputs as calculation scaffolding and validate against the governing fee statute, contract, or court order in your case file.

1) Start the calculator and select the right jurisdiction

1. Open DocketMath’s Attorney Fee calculator at /tools/attorney-fee.
2. Confirm the jurisdiction is set to United States (Federal) (code: US-FED).

Why this matters: Federal fee frameworks often follow different rate assumptions, structure, and allowable cost categories than state or local systems. DocketMath’s Federal mode is designed to match that structure.

2) Choose the fee basis your scenario matches

In the attorney-fee calculator, select the calculation approach that best matches your case posture. Common options you’ll see in fee workflows include:

• Lodestar / reasonable hours × reasonable rate (typical for many federal fee regimes)
• Multiplier-based adjustments (when your worksheet supports enhancement or reduction)
• Statute-specific formatting (if the calculator includes toggles for formatting outputs)

If you’re not sure, pick the option that most closely matches the document you’re trying to replicate (for example, a court-style lodestar table). Then, if needed, run a second pass using a different adjustment method and compare outputs so you can see how sensitive the total is to that modeling choice.

3) Enter time and rate inputs (the “hours × rate” engine)

Most attorney fee calculations rely on two core inputs:

• Billable hours (by task or category)
• Hourly rate (by timekeeper role, or sometimes by date range)

Use the calculator’s input fields to add entries such as:

• Hours for research
• Hours for drafting
• Hours for hearings
• Hours for motions/practice
• Hours for communications/administration (if included in your billable rationale)

Then set:

• Rate per hour (or a rate schedule by timekeeper, if available in the tool)
• Any blended rate settings if the calculator supports them

How outputs change

• Increasing hours increases the base fee linearly.
• Increasing rate increases the base fee linearly.
• When you enter multiple categories, DocketMath typically aggregates them, producing outputs such as:

  • Subtotal by category
  • Total lodestar/base amount
  • Any additional adjustment line items

4) Apply adjustments using the calculator’s adjustment controls

Federal attorney fee math often includes adjustments to reflect limitations or reductions such as:

• clerical work
• duplication
• excessive time
• insufficient specificity
• allocation limitations based on partial success

Depending on what the tool offers, DocketMath may let you apply reductions via:

• percentage reductions
• specific adjustment fields
• multiplier settings

A practical approach is to run at least two modes:

• Gross lodestar (before reductions)
• Net lodestar (after reductions/adjustments)

This makes it easier to explain your final number because you can show the difference created by your adjustment assumptions.

5) Confirm whether “partial success” or caps apply (if supported)

Some federal fee approaches incorporate success-based limitations or proportionality concepts. If the attorney-fee calculator includes toggles such as:

• success percentage
• cap amount
• allocation by claim type

Set them deliberately, then re-run totals.

Sanity-check: If you apply a 50% success rate, your final often moves roughly toward half of the applicable base (after any reductions you chose). If it doesn’t, review what the model is applying that success toggle to (base only, adjustments only, or both).

6) Review the output breakdown before exporting or using it

After DocketMath calculates results, review the output sections (names may vary, but the structure is consistent):

• Category breakdown (hours, rate, category subtotal)
• Total base fee
• Adjustments (reductions/multiplier/caps)
• Final attorney’s fees total

Then verify:

• Did the entered hours reflect what you intended (e.g., no double-counting across categories)?
• Does the final incorporate the reductions you intended (and are they applied to the correct scope)?
• Are the adjustments shown as separate line items you can cite in your internal notes?

7) Run a second scenario to model uncertainty (recommended)

Even with careful input entry, you may want a range. Do at least one comparison run:

• Scenario A: conservative assumptions
• Scenario B: your base assumptions
• Scenario C: aggressive assumptions (useful for range-based budgeting)

Typical variables to test:

• a higher/lower rate assumption
• a different reduction percentage
• a different allocation across categories

DocketMath’s value is strongest when you can quickly show how sensitive the total is to input changes.

Common pitfalls

Avoid these issues—most are input-related and show up as “wrong” totals even when the calculator is working correctly.

• Mixing blended and timekeeper-specific rates
  Example: using a blended rate but also entering category-specific rates for some entries.
• Entering hours twice
  Example workflow error: transferring time from one billing table and then also manually adding overlap.
• Applying reductions to the wrong base
  If DocketMath applies reductions to an aggregated hours subtotal but you intended to reduce only certain categories, the net number can change materially.
• Forgetting multiple timekeeper roles
  If the tool supports role-based rates (e.g., attorney vs. paralegal) and you fail to split hours accordingly, totals can be overstated or understated.
• Using inconsistent rounding
  Rounding hours or rates early can create noticeable differences. Keep full precision until the final display/export step.
• Assuming success-based limitations without matching the model
  If you choose a proportional-success toggle, verify how the calculator applies it (base only vs. base + adjustments).
• Not capturing a before/after adjustment view
  If you only enter a final adjusted figure, you lose the audit trail needed to explain how you arrived at the total.

Pitfall (common theme): the most frequent “calculation failure” isn’t a bug—it’s an assumption mismatch. If your reductions are meant to apply only to certain tasks, reflect that granularity in how you enter categories instead of applying one broad reduction after aggregation.

Try it

1. Go to the DocketMath attorney fee calculator: /tools/attorney-fee.
2. Set Jurisdiction = United States (Federal) (US-FED).
3. Enter at least:

   • 2–3 time categories (for example, research, drafting, hearings)
   • 1 rate (or multiple rates if the tool supports roles)
4. Apply one adjustment (for example, a modest reduction percentage) and compare:

   • Base total vs. Adjusted total
5. Change only one input and re-run:

   • Increase hours by 10% and confirm the total increases by roughly 10% (after any reductions, if reductions apply consistently)
6. Export or copy the breakdown into your case notes or internal spreadsheet, keeping:

   • the category table
   • the adjustment line items
   • the final total

If you want to move faster, start with an intentionally simple structure (fewer categories, a single blended rate), then refine into task-level granularity once the totals behave as expected.

Related reading

• Worked example: attorney fee calculations in Vermont — Worked example with real statute citations
• Attorney Fees Guide for Alaska
• Attorney Fees Guide for American Samoa