Legal Services Offshore blog

Run a litigation funding draw request register that records each approval

A draw request register that records the funding agreement, the approved budget, the request, the approval, and the disbursement while counsel keeps the case strategy.

Run a litigation funding draw request register that records each approval editorial illustration
Defined workflowAttorney review gatesPractical escalation

Key takeaways

A litigation funding draw is a request to release money under a funding agreement, and it usually depends on an approved budget and a documented case expense. The register records the agreement, the budget line, the request date, the amount, the approver, and the disbursement receipt. It also records the source document for each expense. A request without support is a wish, not a draw.

The request, the approval, and the disbursement are separate events. A funder may approve an amount and release it days later, and a partial release is common. Record each date and each amount separately. A register that treats approval as payment will misstate the available balance.

The budget line and the case strategy are not the same thing. The register records the approved category and the invoice or expense that supports the draw. It does not decide whether the expense is reasonable or likely to help the case. Those questions belong to counsel and the funder.

Counsel decides strategy, settlement, and what to request. The support lane maintains the register, the budget crosswalk, and the receipt trail. That division keeps a finance log from becoming a case judgment. Every exception should name the lawyer who will resolve it.

Identify the funding agreement and the draw terms

Record the funding agreement date, the parties, the case or portfolio covered, and the commitment amount. Copy the defined terms exactly as the agreement uses them. A draw under one case may not be available under another. The reviewer should be able to match the request to the agreement.

Record the approved budget and the categories that are eligible for funding. Note the version of the budget and the date it was approved. A budget line that is not eligible should be marked as such. The register should show the source of each eligibility rule.

Record the conditions the agreement places on a draw, such as a minimum amount, a notice period, or a supporting invoice. Note where each condition is documented. A request that skips a condition may be rejected. The log should show the condition and the evidence.

Record the funder contact, the submission channel, and the expected response time. Note any portal or form the funder requires. A request sent to the wrong contact can sit unanswered. The register should show where the request actually went.

Record each draw request and its support

Create one row for each draw request and record the request date, the amount, the budget line, and the case expense. Attach the invoice, the vendor statement, or the cost estimate that supports the request. A request that cites a category without a document is incomplete. The reviewer should see the support beside the amount.

Record the period the expense covers and the date the cost was incurred. Note whether the expense has already been paid or is expected. A reimbursement and a direct payment are different requests. The register should label the type clearly.

Record the running total requested against the commitment and the remaining balance. Recalculate the balance from the register rather than from memory. A request that exceeds the remaining commitment should be flagged before submission. The funder should not be the first to notice.

Record any supporting narrative the funder requires, such as a case update or a budget variance explanation. Note who approved the narrative and the date. Keep the submitted version with the request. The register should show what the funder actually received.

Track the approval and the disbursement

Record the funder response date, the approved amount, and any condition attached to the approval. A partial approval is not a denial, and the register should show both the requested and the approved amount. Note the person who communicated the decision. The lawyer decides whether to accept a condition.

Record the disbursement date, the amount received, the receiving account, and the bank reference. Attach the remittance advice or the bank record. An approval without a receipt is not cash. The register should show the payment separately from the approval.

Record any fee, reserve, or holdback the funder applies to the draw. Note the basis in the agreement and the amount. A net receipt that is lower than the approved amount should be explained. The reviewer should be able to reconcile the difference.

Record the application of the funds to the case expense or the operating account. Note the date and the person who posted it. Keep the accounting entry with the request. The register should show the full path from request to use.

Separate the draw record from the case strategy

Keep request dates, amounts, approvals, and receipts in the register. Keep the analysis of case value, settlement prospects, and funding risk in counsel work product. A support note should not state that an expense is worthwhile. That question belongs to the lawyer and the client.

Record a client or funder instruction about a draw, but do not draft the legal basis for the expense. Note the instruction date and the lawyer who approved it. Keep the communication with the matter record. The register should show who decided and when.

Record any budget variance or scope change by reference to the approval, not by conclusion. Note the source and the question for counsel. A variance may require a funder consent before the next draw. The lawyer decides how to present it.

Record privileged or confidential case material by reference and keep it out of the general finance folder. Note the access list and the approval date. A draw register is not a safe place for a case assessment. The entry should point to the protected file.

Handle a rejected or amended draw

When a draw is rejected, record the decision date, the stated reason, and the amount affected. Route the response to counsel the same day. Record the lawyer instruction and the next step. Do not resubmit the same request without addressing the reason.

When a draw is amended, record the new amount, the changed budget line, and the date. Keep the earlier request visible and link the two entries. Note whether the funder approved the amendment. The register should show the sequence of requests.

When a request is withdrawn, record the date, the person who withdrew it, and the reason in neutral terms. Keep the original row rather than deleting it. Record any effect on the budget or the next request. The history should show what happened.

When a funder requests additional support, record the request date, the missing item, and the due date. Assign the response to a named person. A support request that sits unanswered can delay the case. The register should show the request and the reply together.

Review the register before the next draw

Run a review before the next draw and confirm that every prior draw has an approval and a receipt. Reconcile the running total to the funder statement. Record the reviewer and the date. A late review leaves no time to correct a missing receipt.

Confirm that every open condition has a named owner and a due date. A condition without an owner tends to be discovered at the next request. Record the assignment and the follow-up. The register should show the condition before the funder asks again.

Sample a few rows and trace each amount back to the invoice or the bank record. A transcription error in an amount or a date is easy to catch before a report. Record the sample result and any correction. The sample is a control check, not a performance score.

Record the review result and the next review date in the register. Keep the reviewed version with the matter record so the next draw starts from the same source. A recurring review prevents the balance from drifting. The next request should need fewer corrections.

A supervised support lane can keep the draw register, the budget crosswalk, and the receipt trail while the lawyer decides strategy and what to request. Explore billing and time-entry support.

Sources

  1. American Bar Association, Model Rules of Professional Conduct

  2. Cornell Legal Information Institute, Federal Rules of Civil Procedure

  3. GAO, Standards for Internal Control in the Federal Government

  4. NIST Cybersecurity Framework 2.0

Bring the messy task list

We will help turn it into one clear legal support role.

Share the work, tools, hours, and review needs. The next step is a practical staffing scope, not a public rate card.