Skip to content

Bottleneck 02 · Rate capping

Rates move by date, not by matter.

A bill can only claim the rate in force on the day the work was done. On a matter running from 2019 to 2024 that means several tables, two regions and four bands, resolved per entry rather than per spreadsheet.

Interface previewDesktop

Good to know

  • Date-matched capping
  • London or National
  • Agreed rates override
Tables
2010 – 2026+
Bands
A, B, C, D
Regions
London · National

Where it hurts

The rate is a property of the date, not the file.

Capping by hand means rebuilding the same lookup in a spreadsheet, then trusting it across revisions, regions and fee earners — with the paying party checking the arithmetic afterwards.

  • 01

    Date matching, entry by entry

    Every entry needs the table in force on its own date, not the one in force when you came to draft.

  • 02

    Two regions, four bands

    London and National rates differ, and band is a property of the fee earner. The wrong column is quietly wrong.

  • 03

    Agreed rates in writing

    Where a rate is agreed between the parties, it displaces the guideline on those entries — and has to survive the capping pass.

  • 04

    A library nobody owns

    A pasted rate column has no version, no source and no update path. It is only as current as the last person who edited it.

What it costs

One stale column is a line in a points of dispute.

Capping errors cut both ways: a rate too high invites reduction across the entries it touched, a rate too low gives away fee you were entitled to claim. Either way it is found after service, by someone with no reason to give you the benefit of the doubt.

The guideline rate is a starting point, never a ceiling agreed in advance.

The cure

Capped on each entry's own date, from a maintained library.

The rate work stops being a spreadsheet and becomes a property of each entry.

  1. 01

    The date decides the table

    Each time entry is capped against the guideline rate in force when the work was done, in the region the matter sits, by the fee earner's band.

  2. 02

    Agreed rates are respected

    Where a rate is agreed in writing, the override applies to the entries it covers; the guideline governs the rest, and the difference stays visible.

  3. 03

    The library ships with the app

    Rates come from the application's maintained library and update with it — no pasted columns, and no single spreadsheet holding the truth.

17
years of tables covered
4
bands, per region
Per entry
date-matched, not per file

Questions

Asked at this point in the file.

The application works from a maintained rate library that ships and updates with it. Figures shown on this website are illustrative; the library in the app is the one that applies to a bill, and a rate agreed in writing always overrides the guideline.

Next step

Try it on a matter that spans rate years.

The clearest test is a bill you have already drafted by hand: cap the same entries and compare the two.

Start the 14-day evaluation

Rate capping

The date decides the rate. Every time.

Feed Costs Engine a four-year ledger and it caps each entry against the table in force on its own date, London or National, band by band.

One reply, one call, one decision. We will not add you to a sequence.

Try live demo