Home / Research / Trust accounting

What share of trust replenishment requests arrive after the retainer runs out?

A timing study that measures how often a client is asked to replenish trust only after the balance has already fallen below the work in progress.

Legal Billing Assistant Editorial Team · Published

Editorial illustration representing What share of trust replenishment requests arrive after the retainer runs out?
Table of contents

Method note: this brief proposes a source-led review approach. It does not claim that private client or firm data has been collected.

Question and scope

This protocol asks what share of trust replenishment requests are sent after the retainer balance has already been exhausted. The unit is a replenishment event, and the measure is whether the request date precedes or follows the date the available trust balance reached zero. The study covers retainer-based matters that were active during the period. It does not evaluate whether the retainer amount was appropriate at the start.

Scope the study to matters with a written retainer agreement and a trust ledger that records both deposits and withdrawals. Include matters that received one request, several requests, and no request at all so the denominator reflects the full portfolio. Exclude matters with no trust activity and record the number excluded. State the trust system, the billing system, and the owner of the analysis.

Defining the event

Define a replenishment request as a written communication that asks the client to deposit additional funds into trust. The request date is the date it was sent, not the date it was drafted or discussed. Define exhaustion as the point when the available trust balance for the matter reaches zero after applying approved transfers. A request sent on the same day as exhaustion counts as late for this study.

Distinguish a scheduled replenishment from a reactive one. A scheduled request follows the retainer agreement, such as a monthly top-up, while a reactive request follows a balance alert or a refused transfer. Code the two separately because the process fix differs. A matter can have both types over its life, so code each event on its own.

Population and denominator

The population is every replenishment event on an included matter during the period. Report the number of matters, the number of events, the number excluded, and the number in the final sample. If a matter received several requests, count each one separately or state the rule used. Keep the unit stable across periods so the timing rate is comparable.

Report the share of requests sent before exhaustion, on the day of exhaustion, and after exhaustion. Also report the median number of days between exhaustion and the request. A single late request on a large matter can matter more than several on small matters, so report the trust amount beside the count. Report the trust balance at each request so the timing can be read beside the amount.

Evidence sources

Use the trust ledger, the retainer agreement, the client communication, and the billing system as the primary evidence. Compare the request date with the balance history and record the date each source was observed. If the ledger is incomplete, mark the event as unverified rather than estimating the balance. The evidence log should let a second reviewer repeat the timeline.

Rank the sources so reviewers know what to trust first. A contemporaneous trust ledger is stronger than a later reconciliation, and a sent message is stronger than a note that a call occurred. A retainer agreement is stronger than an internal assumption about the client's obligation. Record the evidence type for each event.

Sampling

Sample across clients, matter sizes, and relationship ages so one large client does not define the result. Include matters with a single retainer and matters with recurring replenishments. Draw the sample before reading the outcome so the selection is not biased toward the late cases. If the population is small, review every event and extend the period.

Stratify the sample by whether the matter had a documented balance alert or a scheduled review. A matter with a working alert should produce earlier requests than one without. Report the timing rate for each stratum rather than pooling them. The reader should be able to see whether the trigger or the client behavior explains the delay.

Coding the record

Use a short code list that points to a specific repair. Code each event as before exhaustion, same day, after exhaustion, or unknown, and record the trigger such as a scheduled review, a balance alert, a refused transfer, or a client request. Add the number of days late and the trust balance at the request date. Keep the code list short enough that two reviewers can apply it consistently.

Have a second reviewer code a sample and compare the results. Resolve disagreements by returning to the ledger and the sent message, not by majority vote. Report the agreement rate and revise any code that is applied inconsistently. If the reviewers cannot agree on the exhaustion date, stop and fix the definition before continuing.

Measuring the variable

Measure the share of late requests by event and by trust value. Report the median and the range for the days late so a few extreme cases are visible. Measure the time from the last approved transfer to the request, because that interval shows how quickly the balance was consumed. Keep the raw entries with the analysis file.

Do not convert the late days to a cost figure without an approved labor rate and a clear statement that it is an internal estimate. The study measures timing, not the cost of carrying the work. If the firm wants a cost view, run it separately with the finance owner. A precise number built on assumed rates is less useful than a clear distribution.

Analysis and reporting

Report the overall late rate, the median days late, and the number of events behind each figure. Show the results by trigger type and by matter size. Compare only groups with similar retainer terms and billing cycles. Include the events that arrived early so the report shows the full distribution.

Give the reader one table that answers the main question and put the coding detail in an appendix. Write the finding in plain language before presenting the technical definition. Include the cases that contradict the pattern rather than hiding them in an average. A report that cannot be acted on is just another record of the past.

Limits and sources of error

A late request is not proof that the firm failed to notice the balance, and an early request is not proof that the process is healthy. Report the completeness of the ledger before drawing a conclusion. Small samples, manual transfers, and changing retainer terms can all limit interpretation. A client who pays slowly may receive a request earlier by design.

Avoid comparing matters that differ in write-off policy or trust activity. A matter with many small costs will consume trust differently from one with a single large fee. Describe the context beside the rate and avoid ranking individual billers. The purpose is to improve the trigger, not to judge professional worth.

Privacy and retention

Store the trust ledgers, retainer agreements, and client messages in a controlled folder with access limited to the study team. Remove client names, balances, and matter details from the analysis file when they are not needed. If an example is shared, use a role label and redact the client and the amount. Keep the unredacted ledger in a separate restricted location.

Do not circulate a client-level list about late replenishment outside the management context. Aggregate the results before sharing them more broadly, and check that a small group cannot be re-identified. The same rule applies to screenshots of the trust system and to quoted messages. Privacy is part of the method, not an afterthought added at the end.

Applying the result

Choose one change that matches the most common trigger. If the alert is missing, add a threshold notification at a set percentage of the retainer. If the review is manual, put a balance check on the weekly billing calendar. If the request is late because the invoice is late, fix the prebill timeline first.

A lower late rate is not the only useful outcome. Fewer refused transfers and a smoother client conversation can improve the relationship even when the rate stays similar. Report the direct result and the service result separately. Stop the change if it produces more alerts than the team can act on.

Review cadence

Repeat the study each quarter and after any change to the retainer terms, the trust system, or the billing calendar. Keep the definitions and the unit stable so periods can be compared. Report the events that were excluded or still open beside the main rate. Review the coding guide after the first repetition and keep the changes visible.

Review the result with the billing manager and the bookkeeper, not only with the preparer. Ask which fix is easiest to sustain and which delay creates the most client friction. Set one change and a follow-up date, then check whether the change held. The next study should test the repair, not just repeat the same count.

Authoritative sources

These public references inform the operating questions in this article. They do not replace legal, ethics, privacy, financial, or client-specific advice.

  1. American Bar Association Model Rules of Professional Conduct
  2. U.S. Government Accountability Office Green Book
  3. Internal Revenue Service recordkeeping guidance
  4. Federal Trade Commission data security guidance
  5. U.S. Bureau of Labor Statistics
  6. U.S. Small Business Administration

Put the guidance to work

Choose one recurring billing workflow, identify its authoritative source records, and name the owner who reviews exceptions. We can help turn that boundary into a focused support role.

Discuss your workflow