Proof of delivery for a mechanics lien: a supplier's job-file checklist

A useful mechanics lien file lets a reviewer trace the materials you sold to a particular construction project, identify when they were furnished, and understand what remains unpaid. For a building material supplier, that means connecting orders, delivery tickets, invoices, returns, and payments. A customer aging report usually leaves some of those connections unfinished.

The difficult cases often look ordinary in accounting: two jobs share a credit account, one invoice covers several shipments, and a replacement ticket appears weeks after the original deliveries. This checklist shows how to assemble those records into a project file your credit manager, notice provider, or construction attorney can review. It is a documentation workflow; it does not determine lien eligibility, a filing deadline, or the amount legally recoverable.

What proof of delivery establishes

A delivery ticket can identify the goods, quantity, destination, delivery date, and person who acknowledged receipt. Its value depends on what the record actually shows. A signature beside a customer name leaves a different evidentiary gap than a ticket identifying the jobsite and the materials delivered there.

State law determines the legal effect. In Florida, delivery to the site of the improvement is prima facie evidence of incorporation under section 713.01(14): it supports incorporation, without conclusively establishing the whole lien claim. Do not apply that Florida rule nationally or assume a signed warehouse pickup ticket proves delivery to a particular property.

Florida's claim-of-lien statute also asks for the contracting party, property, owner, materials and value, first and last furnishing dates, unpaid amount, and applicable notice-service details. That explains why the delivery record belongs beside the commercial and notice records, rather than standing alone. See section 713.08(1). These Florida examples were checked against the published 2026 statutes in October 2026.

Build the connection from order to property

Give each project a consistent job identifier and use it to connect the source documents. Keep the customer's legal name, the project address, and the owner's identity in separate fields. A customer's billing address should not silently become the project address.

Preserve the originals. If a ticket says only “Oak job,” add a separate note explaining how you matched it to the project, with the supporting order or correspondence. Do not overwrite the original destination or turn a salesperson's recollection into a signed receipt.

For a new account, collect project details before the first shipment; the preliminary notice intake checklist covers that earlier handoff. For an existing balance, work backward from the invoice lines to the delivery records.

Worked example: one customer, two jobs, $12,000 outstanding

The following example is fictional. A supplier sells to the same contractor for the Oak Street clinic and River Road apartments. For simplicity, these records contain no taxes, freight, finance charges, or disputed prices.

The customer account shows $12,000 outstanding. The Oak records reconcile to $6,000: $12,000 billed, less the $1,000 credit and the $5,000 payment. River accounts for the other $6,000.

That gives the reviewer an explained Oak balance, not a conclusion that $6,000 is lienable. Eligibility, notice compliance, waivers, and the applicable law still need review. Organizing the records by job also does not decide whether the law permits or requires separate lien claims.

The dates need their own explanation. Invoice I-882 was issued on August 20, but its two deliveries occurred on August 4 and August 12. Preserve all three dates with their labels. The invoice date should not replace either delivery date.

Ticket D-522 deserves a visible question: What was replaced, and why? Obtain the original order reference, the replacement request, and any warranty or deficiency correspondence. Florida's definition of final furnishing excludes correction of deficiencies in previously supplied work or materials, under section 713.01(12). A later ticket therefore needs examination before anyone uses it to select a final-furnishing date.

The practical output is a $6,000 reconciled Oak balance, a delivery chronology, and one unresolved replacement issue, each linked to its source. The reviewer can see precisely what remains to be decided.

Handle missing and conflicting records explicitly

An unsigned ticket. Keep it and look for supporting evidence: the carrier's delivery confirmation, dispatch records, dated photographs, recipient correspondence, or a site log. Describe what each record shows. Do not manufacture a signature or decide from the missing signature alone whether the claim succeeds or fails.

A customer pickup or delivery to a warehouse. Record the actual pickup or delivery location. Ask for the onward delivery record and the order tying the materials to the intended project. Preserve any remaining gap between “the customer received it” and “these materials reached this improvement.”

A payment without clear instructions. Show the receipt, the existing accounting allocation, and the missing remittance information. Escalate any uncertain allocation rather than moving the payment between jobs just to produce a preferred claim balance. The example above works because the remittance expressly identifies I-882.

A return, replacement, or backorder. Give each event its own row and link it to the original order. Record what happened before deciding its legal significance. A zero-dollar ticket may still matter to the chronology; a credit memo may affect the balance without documenting a new furnishing event.

For each gap, assign a person and a specific request: “Dispatch to retrieve D-522 and the replacement request” is actionable. “Need proof” is not.

Send a short cover note with the supporting file

A reviewer should be able to understand the file before opening every attachment. Put these five items at the front:

1. Project and contract chain: property, owner, customer, and who hired whom, with unverified information marked.
2. Delivery chronology: each shipment's date, destination, order reference, and supporting record; flag uncertain furnishing classifications.
3. Balance reconciliation: invoices, credits, payments, allocation evidence, and disputed or unexplained items.
4. Notice and waiver history: copies, service records, amounts, periods, and any exceptions needing review.
5. Open questions and timing: the missing fact, responsible person, and any existing notice or lien deadline requiring attention.

Send the known records for timely review while the missing-document requests continue. Do not wait for a perfect packet before raising a deadline concern. The filing walkthrough explains the separate notice, recording, service, and enforcement steps.

Use the documented facts in your deadline review

Once the relevant furnishing facts are established, use them in the deadline workflow, keeping the supporting records available. If the dates remain uncertain, carry that uncertainty into the review instead of substituting the most recent invoice or ticket date.

LienDeadline's supplier calculator checks current calculation coverage from the state, project type, who hired you, and relevant furnishing and project-event facts. Read the preliminary-notice and lien-filing outcomes separately: supported facts may produce dates, while unresolved facts or unsupported conditions require review. The state lien guides cover all 50 states and DC; a guide is a reference, not a calculated result for your project.

Start with one open project. Match its invoice lines to the shipment records, explain the credits and payments, and list what you still cannot establish. That gives the next person a file they can work from.

This is operational guidance, not legal advice. Use counsel-approved policies for final notice and lien decisions.