Who hired your supply business? Build a project contract-chain record
Separate the property owner, contractor and buyer, verify who hired whom, and record uncertain relationships before checking supplier lien deadlines.
A supplier's customer account tells you who is billed. It may not tell you who owns the property, who holds the direct construction contract, or where your buyer sits in the hiring chain. Establish those relationships before selecting “owner,” “contractor,” or “subcontractor” in a deadline workflow. A familiar trading name, email signature or delivery contact is a lead to verify, not a legal classification.
The useful output is a short project record: named entities, the relationships between them, evidence for each relationship, and explicit questions where the chain is incomplete. This article focuses on that record. The preliminary notice intake checklist covers the broader intake, and the supplier proof-of-delivery checklist covers matching shipments and balances to a job.
Separate four identities
Keep these fields distinct even when two turn out to name the same entity:
| Field | Question to answer | Evidence to seek |
|---|---|---|
| Property owner or relevant property-interest holder | Whose interest is being improved? | Property record, project contract and relevant recorded project notice |
| Direct contractor | Who contracted with that owner for this improvement? | Direct contract or a reliable project record identifying the relationship |
| Contractual buyer | Which legal entity ordered your materials under the supply agreement? | Accepted quote, purchase order, contract or order confirmation |
| Buyer's upstream party | Who hired your buyer for its project scope? | Subcontract, project notice or written confirmation tied to the job |
Record the legal entity and any trading name separately. “Northside Builders” on an account and “Northside Interiors LLC” on a purchase order may require reconciliation. A shared office address does not establish that they are the same contracting party.
Record relationships, not just a list of names
A list containing the owner, GC and customer is incomplete until you know how they connect. Write one sentence for each link: “The owner hired the direct contractor”; “the direct contractor hired the buyer”; “the buyer ordered materials from us.” Mark each link confirmed, unknown, or needs review, with the record and date supporting that status.
Florida illustrates why this matters. Its definition of a lienor includes a materialman contracting with the owner, contractor, subcontractor or sub-subcontractor, and excludes other persons under that part (§713.01(19)). That is a Florida rule, not a nationwide tier limit. The same section defines the relationships; do not assign a statutory role solely from a company's marketing description.
The relationship can also affect notice recipients. Florida's §713.06(2)(a) requires specified higher-tier copies for certain supplier relationships. A clean customer name therefore does not finish the service list.
Worked example: the name on the invoice is not the owner
This fictional job begins with a credit account labeled “Harbor Construction.” A purchase order for the Elm Street renovation identifies Harbor Interiors LLC. The project's recorded notice names Elm Property LLC as owner and Summit Build LLC as contractor. A salesperson remembers Summit supervising deliveries.
Do not select “hired by owner” because Harbor is the customer, or “hired by contractor” because Summit's superintendent signed a ticket. The purchase order supports Harbor Interiors as the buyer; it does not establish Harbor's upstream relationship.
The credit manager asks Harbor for the subcontract or written confirmation of who hired it on Elm Street. If the response establishes that Summit hired Harbor Interiors, the working chain becomes Elm Property → Summit Build → Harbor Interiors → supplier. The project record names the evidence for each link and flags any remaining ownership question. If the response instead identifies a materials reseller, that is a materially different fact requiring review.
Resolve gaps with specific requests
Ask for the missing relationship, not a generic “lien information” packet:
- Confirm the exact entity that placed and accepted the order.
- Ask which entity hired that buyer for this specific project and scope.
- Compare the response with the contract, recorded notice and property information.
- Preserve conflicts rather than choosing the answer that yields the preferred result.
- Assign a person to obtain clarification and a follow-up date before any known notice or filing concern.
If the project involves a tenant, developer affiliate, purchasing agent or public authority, refer the property interest and contract relationships for qualified review. A chain drawing organizes facts; it does not decide whether a lien can attach.
Use the record in the calculation
In the supplier calculator, start with the state, project type and verified hiring relationship, then confirm the relevant furnishing and event facts. Current support is determined for that scope. If the available categories do not accurately describe the relationship, do not force it into the closest label to obtain a date.
Read the preliminary-notice and lien-filing outcomes separately. Keep the contract-chain record available when a result needs review, and use the state lien guides as cited references rather than substitutes for a project result.
Can I use the customer name from accounting?
Use it as a starting point. Check the legal buyer on the accepted order and its project relationship; billing aliases and shared accounts can hide differences.
What if the buyer will not provide its subcontract?
Record the request, the response and the remaining uncertainty. Send known facts for timely review rather than guessing the relationship or waiting until a deadline is close.
This is operational guidance, not legal advice. Use counsel-approved policies for final notice and lien decisions.