Inputs you need for attorney fee calculations in United States (Federal)
6 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
To run attorney fee calculations in United States (Federal) using DocketMath (calculator: attorney-fee), you’ll typically enter inputs that determine: (1) the number of compensable hours, (2) the reasonable hourly rate, and (3) any adjustments or multipliers your workflow applies. Before you use DocketMath, gather the items below so your inputs match your billing records and methodology.
Core inputs (most common)
- ☐ Billing period dates (start and end dates)
- ☐ Attorney/role identifiers (who performed the work—e.g., partner, associate, paralegal)
- ☐ **Hours by time entry (or totals)
- ☐ Total hours per role (if you’re summarizing) or
- ☐ Hours per entry (if you’re itemizing)
- ☐ Hourly rate by role (or by individual attorney)
- ☐ Rate type / methodology selection (the basis you’re using for “reasonable hourly rate” in your workflow)
- ☐ Task category mapping (optional, if your DocketMath workflow separates legal work types)
Practical note: The “reasonable” calculation is only as consistent as the mapping between hours, roles, and rates you provide. If those labels don’t line up, totals can become inaccurate.
Common Federal fee components (depending on your workflow)
- ☐ Lodestar vs. enhanced amount (whether you’re calculating only lodestar or lodestar plus an enhancement)
- ☐ Multipliers / adjustment factors (if applicable in your workflow)
- ☐ Exclusions / reductions
Examples you may encode:- ☐ Unreasonable time reduction
- ☐ Clerical time exclusion
- ☐ Block-billed time allocation (if you have it separated)
- ☐ Prevailing party fee standard selection (if the calculator flow prompts for it)
- ☐ Costs handling method (fees-only vs. fees plus recoverable costs)
Pitfall to avoid: A frequent cause of incorrect totals is mixing rates intended for one period/year with hours billed in another, or using a rate intended for one role on a different role’s hours. Even modest mismatches can materially change the result.
Gentle disclaimer: This checklist is for workflow planning and organization. It’s not legal advice, and it can’t guarantee how a specific court will apply fee methodology.
Where to find each input
The goal is consistency. Your timekeeping and rate assumptions should be the same assumptions that drive every DocketMath run you do for United States (Federal) fee calculations.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
1) Billing period dates
- ☐ Source: timekeeping export, billing narrative header, invoice cover sheet, or a compiled billing summary
- ☐ Why it matters: if DocketMath (or your internal method) applies settings based on date range, your start/end dates should match your billing records exactly.
2) Hours (time entries or totals)
- ☐ Source:
- ☐ billing software export (CSV/PDF) from your matter
- ☐ spreadsheet summary derived from docket/claim spreadsheets
- ☐ Checklist to verify:
- ☐ Hours include only the compensable legal work you intend to claim for the selected period
- ☐ Paralegal vs. attorney time is labeled correctly (if roles are separated)
- ☐ “Write-off” or non-billable time is not accidentally included as billed hours
3) Hourly rates by role
- ☐ Source:
- ☐ your firm’s billing rate card (as used in your matter)
- ☐ affidavit/exhibit exhibits you’re preparing for the fee application
- ☐ an internal spreadsheet of proposed reasonable rates
- ☐ Consistency rule: if you have multiple rates for the same role across years (e.g., associate rate increases), match:
- the correct rate to the correct billing period, or
- use a clearly documented averaging approach that your workflow supports.
4) Rate type / methodology selection
- ☐ Source: your calculation approach document (even a brief internal memo is enough)
- ☐ Why it matters: different methodologies treat the “reasonable hourly rate” differently. DocketMath will reflect the approach you select, so the output changes when you change the method.
5) Multipliers or adjustments
- ☐ Source: your case strategy spreadsheet or fee methodology notes
- ☐ Common triggers that affect the multiplier input (workflow-dependent):
- ☐ scope complexity
- ☐ delay
- ☐ risk or exceptional success factors (if your process includes them)
- Reminder: Only enter a multiplier if your workflow is actually using one. If your workflow is lodestar-only, a multiplier input can unintentionally double-count adjustments.
6) Reductions / exclusions
- ☐ Source: review notes on billing entries
- ☐ markups showing excluded categories
- ☐ item-level rationale for reductions
- Tip: Apply exclusions at the same granularity as your inputs:
- if you’re entering entry-level hours, exclude at entry level
- if you’re entering total-level hours, reductions should be reflected in your totals consistently
Run it
Once your inputs are ready, run the calculation in DocketMath using:
- Primary CTA: /tools/attorney-fee
Enter the inputs in DocketMath and run the Attorney Fee calculation to generate a clean breakdown: Run the calculator.
Before the first run (quick setup checklist)
How outputs change when you modify inputs
Use this “cause-and-effect” map to sanity-check results:
| Input you change | Typical effect on output |
|---|---|
| Increase hourly rate for associates | Total fee increases proportionally with associate hours |
| Add excluded hours back into totals | Total fee increases immediately (check whether reductions were already applied) |
| Use a higher/lower multiplier | Lodestar-based total scales upward/downward depending on multiplier entry |
| Switch from fees-only to fees + costs | Final total increases by the recoverable costs amount (if costs are included) |
| Move work from one role to another (e.g., associate → partner) | Total shifts because rates usually differ by role |
Warning: After you re-run, keep a short changelog (for example: “updated associate rate from $450 to $475 for Jan–Mar 2026”). Without it, it’s easy to lose track of which run corresponds to the “final” figure for your fee application workflow.
Related reading
- Worked example: attorney fee calculations in Vermont — Worked example with real statute citations
