Spreadsheet checks before running attorney fee calculations in Vermont

What the checker catches

Before you run attorney-fee calculations in Vermont, it’s worth sanity-checking the spreadsheet that drives the numbers. Even if your final methodology is correct, spreadsheet errors can quietly distort outputs—especially when you’re dealing with hours, rates, multipliers, deductions, and date logic.

DocketMath’s attorney-fee calculator can help you compute reliably, but the spreadsheet itself can still introduce issues. A “spreadsheet checker” typically catches problems in four areas:

1) Time math and sign errors

Common failure points include:

• Minutes-to-hours conversion mistakes (e.g., treating 45 minutes as 45 hours, or dividing by 100 instead of 60)
• Negative or duplicate entries (e.g., a “correction” row with the wrong sign, or the same task captured twice)
• Row-level totals not matching column-level totals (formula references drift as you insert rows)

Quick check: ensure hours aren’t negative unless you explicitly intend credit reversals, and ensure the sum of line items matches the “total hours” cell used by the fee calculation.

2) Rate logic and unit mismatches

Fee spreadsheets often mix:

• hourly rates (e.g., $350/hour)
• flat fees or bundled amounts
• blended rates derived from multiple team members

A checker looks for:

• Rate columns used in the wrong units (e.g., rate multiplied by minutes instead of hours)
• Blended-rate formulas that double count (e.g., adding rate twice across columns)
• Rate changes by date not reflected in the correct effective-date logic

Output impact: the same number of hours can produce very different totals if the spreadsheet uses the wrong rate bracket for the work date.

3) Date handling and “wrong bucket” errors

Date-driven logic is a top cause of spreadsheet drift:

• work dates stored as text (leading zeros, mixed formats)
• inclusive/exclusive day boundaries handled inconsistently
• filters that exclude entries accidentally due to locale settings

A checker can verify:

• dates are real date values (not strings)
• each row lands in the correct time window or category
• totals don’t change unexpectedly after sorting/filtering

4) Spreadsheet coverage vs. Vermont time limits (SOL)

Even though your calculator focuses on computing fees, the dataset scope still matters. Vermont’s general/default statute of limitations period is 1 year. The provided material references a general calendar document and does not identify a claim-type-specific sub-rule—so treat 1 year as the general/default period, not a special rule for a specific fee claim.

Source: https://legislature.vermont.gov/Documents/2020/Docs/CALENDAR/hc200226.pdf

When to run it

Run the spreadsheet checker at moments when changes are most likely to break the logic:

Run the checker before importing a spreadsheet into the Attorney Fee workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Before you calculate

• First run after building the sheet structure (columns, mapping tables, categories)
• After you import data from billing exports or invoices

After any structural edits

• you add a new category (e.g., “research,” “drafting,” “court appearance”)
• you change conversion logic (minutes → hours)
• you adjust date filters or effective-date lookups

After reconciliation

• you compare “total billed hours” vs. “total hours in spreadsheet”
• you compare sum of line items vs. a subtotals panel
• you update rates for a subset of dates

When you get an unexpectedly large/small result

A checker is especially useful when:

• one outlier task drives an outsized total
• the output is wildly inconsistent with your billing narrative
• totals change when you sort/filter

Practical workflow: treat this like a test suite. Run it before trusting computed attorney-fee output, then rerun it after every meaningful edit.

Try the checker

You can sanity-check your inputs in a repeatable way using DocketMath with the attorney-fee calculator: start here.

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

Suggested setup (spreadsheet-side)

Use these guardrails before feeding totals into DocketMath:

• If you store minutes: hours = minutes / 60
• line_amount = hours * rate (or your chosen structure)

How outputs change when inputs change

Do a few targeted tests to see whether the sheet behaves logically:

1. Change one row’s minutes by +15

   • If the sheet is correct, total hours should rise by 0.25 (15/60)
   • total fees should rise by 0.25 × the applicable rate

2. Change a work date across a rate boundary

   • If the rate lookup is date-aware, the line amount should switch to the new applicable rate bracket

3. Sort/filter rows without altering totals

   • If totals change after filtering, formulas likely reference only visible rows or use brittle ranges

Apply the 1-year scope sanity check

Because the general/default limitations period is 1 year, verify whether your spreadsheet includes work older than 365 days relative to your chosen calculation reference point (for example, the filing date you’re modeling).

Gentle disclaimer: A checker can’t determine legal eligibility for your specific situation. It can only highlight whether your spreadsheet inputs include work outside the general/default 1-year scope indicated by the provided Vermont reference.

Primary CTA

Start from: /tools/attorney-fee
Run your values through DocketMath, then validate that the spreadsheet totals you’re relying on are consistent with the checker’s flags. If the checker catches an issue, fix it at the spreadsheet level first, then rerun the calculation so you can trace the impact to a specific correction.

Related reading

• Attorney Fees Guide for Alaska
• Attorney Fees Guide for American Samoa
• Attorney Fees Guide for Arkansas