Separate delivery, review and billing events
A supplier can record delivery before the firm has reviewed the packet. A firm can acknowledge receipt while acceptance remains pending. An invoice can reference a separate billable event. Put each event in its own field so a single status such as “received” cannot silently mean all three.
This guide proposes an operational specification for a review period. It does not state CaseLead’s terms or determine what an existing agreement requires. Use the handoff checklist to decide packet contents; use this specification to explain when those contents start a clock and how exceptions affect it.
Write the clock specification before delivery begins
Have the buyer and supplier walk through the same hypothetical packet and calculate the same deadline. If they get different answers, a phrase such as “five business days from delivery” has not yet become a usable operating rule.
| Field | Decision to record | Ambiguity to remove |
|---|---|---|
| Start event | Successful receipt, complete packet receipt or another agreed event | Upload, notification and reviewer access are not identical |
| Duration | Elapsed hours or named business-day calculation | Whether the delivery day is counted |
| Time zone and calendar | Named time zone, working days and holiday calendar | Whose local time governs |
| End boundary | Exact due time and whether notice at that instant qualifies | “By Friday” leaves the hour unresolved |
| Notice destination | Authorized inbox or portal, required fields and backup route | Sending to a salesperson may not reach the review queue |
| Receipt evidence | Accepted proof of submission and acknowledgment process | Sent messages and received notices are different records |
Define completeness independently of acceptance
List required-at-delivery items, items permitted to remain pending and items owned by the firm. For each required item, state what satisfies it: a document, a reported answer, a source reference or an explicit unknown allowed by the agreed profile. Completeness is a packet test, not a favorable merits assessment.
Choose the clock consequence of a missing required item explicitly. Possibilities to discuss include a clock that has not started, a clock that continues while correction is requested, or a documented suspension after acknowledgment. These are alternatives to agree, not rights created by this guide.
Preserve the first-received version, missing-item list and each correction timestamp. If a later packet is complete, identify the version and event that changed the deadline. Do not overwrite the first receipt time or restart the clock merely because a file was resent.
Distinguish missing delivery evidence from later investigation
A signed file may contain a reported answer while supporting material remains outstanding. Determine before launch whether that material is required at handoff or is work the firm expects to complete later. A pending document does not have the same commercial meaning in both situations.
Give each unresolved item an owner, next action and due date. Keep the firm’s acceptance state pending when that is the actual decision. Do not infer that pending status extends the supplier’s review period or that requesting more information pauses it.
If an extension is needed, record the request, supplier response, revised deadline and delivery IDs covered. Retain the original deadline as history. When no change is confirmed, continue tracking the last agreed deadline and escalate the open question to the designated commercial owner.
Classify a delivery defect separately from a firm decline
A firm’s decision not to accept a matter and its request for a supplier remedy need separate reason fields. The file may satisfy the purchased criteria even though the firm declines it. Conversely, a missing promised item may need correction while the firm keeps the matter under review.
| Situation | Operational classification | What the record should show |
|---|---|---|
| Required agreement version absent | Possible delivery defect | Requirement, packet version and missing item |
| Required location contradicts agreed profile | Possible criteria exception | Applicable criteria version and sourced discrepancy |
| Firm changes its preferred profile after receipt | Later preference change | Earlier criteria and new effective date |
| Supporting document permitted to arrive later | Permitted pending work | Assigned owner and follow-up |
| Firm declines a complete packet | Firm decision; assess remedy separately | Decision reason and any supported exception |
Work through a fictional review-clock dispute
Assume a fictional agreement specifies 72 elapsed hours after receipt of a complete packet, using America/New_York time. It defines a complete packet as including the designated agreement version and a signing record. This invented rule is not a suggested standard or a CaseLead policy.
Packet v1 arrives Tuesday, November 10, 2026, at 10:00 a.m. The signing record is missing. Intake records the omission at 10:20 a.m. Packet v2 supplies it Wednesday, November 11, at 2:00 p.m. Under the stated fictional rule, the deadline is Saturday, November 14, at 2:00 p.m.; a weekend does not stop an elapsed-hours clock.
Under a different rule starting at first receipt regardless of completeness, the same 72 hours would end Friday, November 13, at 10:00 a.m. The difference is 28 hours. Neither calculation establishes which rule applies to a real purchase; the agreement and event evidence must answer that.
Suppose notice is submitted Friday at 4:00 p.m. and acknowledged Saturday at 9:00 a.m. Preserve both timestamps. Whether submission or acknowledgment satisfies the deadline depends on the notice rule; the team should not choose whichever timestamp produces the preferred result afterward.
Make the deadline visible before it becomes an escalation
Put the computed deadline beside the delivery ID, clock rule, packet version and assigned reviewer. Give a backup access to the queue. Set reminders around the firm’s review capacity, leaving time to gather evidence and resolve submission failures; this guide sets no universal reminder interval.
Before notice is sent, check the recipient, delivery ID, specific requirement, supporting reference and requested action. Store the submission result and any acknowledgment. If the approved route fails, use the agreed backup and retain the error evidence rather than treating attempted transmission as confirmed receipt.
Track “notice submitted,” “supplier acknowledged,” “under review” and “remedy decided” separately. Acknowledgment confirms a communication event; it does not by itself approve the credit or accept the firm’s reasoning.
Finish with a traceable remedy, not a closed email thread
Link each approved remedy to the original delivery and invoice line it affects. Show requested, approved and posted credit amounts separately. For a replacement, retain its delivery ID, the original it remedies and the new review deadline under the agreed rules.
In a fictional ledger, a $6,000 invoice has a $1,000 credit requested. Supplier approval alone leaves it in approved-but-unposted status. When the credit posts, the reconciled net becomes $5,000. If the remedy is a replacement instead, do not also deduct $1,000 unless a separate credit actually posts.
Close the commercial exception when the promised correction, posted credit or replacement treatment reconciles. Keep the firm’s acceptance decision and ongoing matter work independent. A resolved invoice dispute does not resolve every outstanding intake task.
Questions law firms ask
Does the review period start when the supplier sends an email?
Only if the agreed start event makes that the trigger. Specify successful receipt, packet completeness and acknowledgment separately, with evidence for each event.
Does asking for missing information pause the clock?
Do not assume it does. Record the agreed missing-item rule or a confirmed deadline change; a request and an approved extension are different events.
Does declining a signed file automatically earn a replacement?
No automatic entitlement is proposed here. Record the firm’s decision and separately assess the remedy request against applicable criteria and terms.
Should replacement files receive a new review period?
Specify that treatment before purchase, including the start event and duration. Keep original and replacement records linked so neither the review history nor billing treatment is lost.
Sources and further reading
Tell us which cases your firm wants.
Share your states, case criteria and review capacity. We’ll put the price, billable event and review terms in a written proposal you can check against this guide.
Discuss your case criteria