Legal Services Offshore research · legal-support-governance
Where does delay accumulate between a litigation funding draw request and the receipt?
A measurement method for comparing the request date, the approval date, and the disbursement date for each funding draw, without deciding whether the expense was reasonable.

Research context
This research brief is designed for legal operations planning. Use the findings to ask better workflow questions. Test any proposed process against the firm’s jurisdiction, professional duties, systems, and client commitments. Treat every local result as a starting point for review rather than a universal benchmark.
Key takeaways
This study measures where time accumulates between a litigation funding draw request and the receipt of funds. The unit is one draw request, and the evidence is the request, the approval, and the bank record. The comparison describes the handoff sequence rather than whether the expense was reasonable. A slow draw can still fund a sound expense.
The request, the approval, and the disbursement are separate events with separate dates. A funder may approve quickly and pay slowly, or the reverse. Treating approval as payment hides the stage where the delay occurred. The study compares all three dates.
A delay may reflect an incomplete request, a funder question, a missing budget line, or a payment process outside the firm. The study records the stage where the lag appeared when the file supports it. That detail matters because the repairs differ. One calls for a support checklist, another for a funder contact.
The result is descriptive for one firm, one funder, and one review window. It should not be used to compare individual staff or to imply that a case was underfunded. The practical value is a dated baseline and a better question about which handoff slows down. A later review can repeat the comparison on a new window.
Question and scope
This study asks what share of funding draw requests in the review window have a recorded receipt date in the draw register. It treats one funding draw requests as the unit and the funding agreement and bank record as the primary evidence. The scope is one firm, a defined set of matters, and a fixed review window. The result describes that setting and does not decide the legal question behind the record.
Funding draw requests with no draw register entry at all are excluded from the share and reported as a separate category. Funding draw requests with a receipt date but no source are reported as unverified rather than complete. A receipt date that appears only in an email is not a draw register entry for this study. Record these rules before the review so the denominator stays stable.
The study includes every funding draw requests that meets the inclusion rule, and it reports the types separately where the firm uses more than one. It excludes funding draw requests that were withdrawn before the draw register entry was due. Each included item should have a source date and a draw register record. The inclusion decision belongs to the reviewer who assembles the list.
Report the channel for each funding draw requests because the draw register path varies. An item received through one channel may reach the draw register differently from an item received through another. Grouping all channels into one rate hides that variation. The report should show the channel beside the result.
Definitions and evidence standard
Define the receipt date as the dated value recorded in the draw register for the funding draw requests. A placeholder or a blank field is not a recorded value. Record the source of the value and the person who entered it. Use the first dated entry, not a later update.
Define a sourced receipt date as one that points to an order, a notice, a rule, or an approved instruction. A value copied from another matter is not sourced for this one. A value confirmed only by memory is recorded as unverified. The evidence should include the document and the date.
Define the lag as the number of calendar days between the request date and the receipt date entry. Report the lag in whole days and in categories such as same week, next week, and after a reminder. Precise hours would imply more accuracy than the records support. Keep the raw dates in the working file.
Define a missing entry as no recorded value within the review window. A missing entry is not the same as a late one, and it may indicate that the item was never processed. Report missing entries separately and route them to the owner. The study should not guess what happened.
Sampling and measurement
Select funding draw requests that entered the draw register during the review window and freeze the list before checking the receipt date. Include more than one matter type and more than one owner where the firm uses them. If one person handles most of the items, report that group separately. The sample should reflect the work the firm actually performs.
Measure the number of funding draw requests with the receipt date recorded before the request date, after it, and not at all. Add the number excluded for a missing draw register entry. Report each count with the total so the reader can see the base. A percentage without the count is easy to misread.
Record whether a reminder was sent and the date it went out for each item. A late entry with no reminder is a different finding from a late entry after two reminders. Report the reminder status beside the lag. The comparison is more useful than a single average.
Check a sample of entries against the source document to confirm the date and the owner. A draw register note may record a value that the source does not support. Record the check and any discrepancy. The measurement is only as good as the value it relies on.
Findings and interpretation
Present the distribution by item type and owner before suggesting a cause. A cluster of missing entries in one type may point to a form or a field problem rather than an individual. A cluster in one channel may point to a routing gap. Report the pattern and the counts rather than a single average.
Compare items with a named owner with those handled through a general queue. A lower missing rate in the owned group may point to the value of a single handoff. Report the two groups separately. That comparison is often the most useful part of the result.
Read the items with no entry and check whether a reminder was sent. An item with no reminder is a process gap, while an item with reminders and no entry may need an owner call. Report both counts. The difference shows whether the team reached the item at all.
Compare the result with the firm checklist and the person who owns it. A checklist that ends at intake may not prompt anyone to enter the receipt date. The study can show whether the field is missing from the process. Record that observation without assigning fault to an individual.
Limitations
The study measures the presence and timing of a record, not whether the underlying action was correct. A late entry can still be followed by a valid filing or a valid decision. Those questions need a review of the source document and the responsible lawyer. Keep the timing result separate from the legal question.
The window may include a holiday period, a staff change, or a system migration that affects entries. If the process changed during the period, the items may not be comparable. Record those limits with the result and keep the source extracts. A later review should know which conditions applied.
The study cannot establish that a missing entry caused a loss or a missed deadline. It also cannot decide whether the firm met a professional duty. A record observation is an administrative finding, not a legal conclusion. The responsible lawyer should review any item with an unclear record.
The sample is local and should not be generalized to other firms, courts, or jurisdictions. A different court or client mix can produce a different result on the same day. Report the sample size and the definitions with the result. The reader should be able to judge whether the setting resembles their own.
Practical next step
Choose one repair that matches the most common gap, such as a required field at intake or a reminder at a set interval. Write the change, the owner, and the start date. Define the measure that will show whether it helped, using the same categories. Keep the working list separate from the official matter record.
Test the repair on the next set of items before applying it to every matter. Record the test group and the result. If the repair adds a step without improving the record, simplify it rather than adding another layer. A small test is enough to show whether entries are arriving earlier.
Review the result with the lawyer who owns the practice area, not only with the support team. Ask whether the process still matches the way the records actually arrive. Adjust the process only with the lawyer agreement. The goal is a path that accounts for the record step.
Record the review date and the next review date in the checklist. A recurring review prevents the result from becoming a one-time report. Record the owner and the measures to repeat. The next window should use the same definitions unless a change is documented.
What the evidence does not show
The study does not show that a missing entry changed the legal outcome or that a party waived a right. It shows the gap between the source and the record. The legal effect remains with the responsible lawyer and the applicable rules. Keep the language neutral and avoid conclusions the data cannot support.
Do not use the result to promise a client that every item will be recorded or that a late entry is harmless. Do not publish party names, amounts, or privileged content. Keep the sample size and definitions with the result. Use the same categories across review periods so the comparison stays honest.
If the firm needs to know whether a specific item was recorded, it should review the source document and contact the owner through an approved channel. This study is a planning tool for the record path. Review the finding with the person who owns the next step before the process changes. A short note in the matter log can preserve the context for the next review.
Sources and method
Open each source to confirm its scope, publication date, and applicability before relying on it for a legal workflow decision.