Who owns the plans and takeoffs a lumber yard prepares for builders?

Who owns the plans a builder sends to the yard?#

The plans a builder sends to a lumber yard usually belong to the architect or designer who prepared them, or to a plan service that licensed a stock design for a single build. The builder holds a right to use them for the project, and the yard receives them only to price and supply that work.

Standard construction forms say this directly. AIA A201-2017 Section 1.5.1 states that the architect and its consultants are the authors and owners of their instruments of service, including drawings and specifications, and that contractors, subcontractors and suppliers do not own or claim a copyright in them. Section 1.5.2 lets suppliers use and reproduce those documents only for performing the work, and bars use on other projects or for additions outside the scope of the work without the specific written consent of the owner, the architect and its consultants.

Many residential builders work without AIA forms, but the same principle tends to hold through plan copyright notices and plan service licenses. A yard that keeps plan PDFs in an estimating archive holds copies it was allowed to use for one purpose.

Who owns the takeoff and the estimate?#

The takeoff and estimate a yard's estimators produce are generally the dealer's own work product. The estimator reads the plans, applies the yard's methods, waste allowances and product choices, and creates a material list and price that did not exist before.

Where a takeoff has copyright protection at all, the employer is usually the owner. Under 17 U.S.C. 201(b), the employer is considered the author of a work made for hire and owns the copyright unless a signed written agreement says otherwise. Takeoffs from outside estimating contractors are different, and those agreements should include an assignment.

Copyright in a takeoff is thin in any case, because quantities and dimensions are largely facts drawn from someone else's design. Ownership disputes therefore turn on contracts: a builder supply agreement that says takeoffs belong to the builder, a paid takeoff service with its own terms, or a confidentiality agreement covering the builder's plans and pricing.

Builder plans versus dealer takeoffs at a glance#

Builder plans versus dealer takeoffs comes down to who created each record and which document limits it. The table separates the records an estimating department touches; the agreements on each account control.

Which terms limit reuse of takeoffs and plans?#

The terms that limit reuse sit in several documents, and production builders tend to have the most detailed ones. Before reusing a takeoff for another customer, or including takeoff history in a license, review each source below.

A quote that states takeoffs are prepared for the customer's use on a named project and otherwise remain the dealer's property is a simple protection. Many yards have never written one, which leaves the builder agreements to answer the question.

• 1Plan title blocks and copyright notices, which often prohibit reproduction beyond the permitted build.
• 2Builder supply agreements and purchase order terms, which may say takeoffs and pricing belong to the builder or are confidential.
• 3Paid takeoff or estimating service terms, if the builder paid separately for the takeoff.
• 4Non-disclosure agreements signed to bid subdivisions or commercial projects.
• 5Subcontract and supplier flow-down clauses that pass architect restrictions on to suppliers.
• 6Takeoff and plan management software terms, which govern files stored in a vendor's cloud.

What can be de-identified, and what must stay out#

De-identification can make takeoff history usable outside the original job, but plan images cannot be fixed that way. The architect's drawings stay out of any licensed package however they are masked, because the copyright sits in the drawing itself.

Takeoff and order records are different. Removing builder and subdivision names, lot numbers, street addresses, homeowner names and price fields, and generalizing house attributes such as size band, roof type and wall framing, leaves a record of what a type of house needed and what actually shipped. That record carries the yard's estimating expertise without exposing anyone's design or identity.

Keep a written map of the fields removed and the fields kept. That map becomes part of the privacy record a buyer or counsel will ask to see.

Illustrative: a dealer with an in-house estimating team#

Illustrative: a fictional lumber and building materials dealer with several yards runs an estimating department that has produced takeoffs for local custom builders and a handful of production builders for many years. Takeoffs are built in desktop takeoff software, quotes and orders live in the dealer's ERP, and plan PDFs sit on a shared drive organized by builder.

When the dealer considers licensing its estimating history, counsel reviews the production builders' supply agreements and finds one that treats takeoffs for its plans as builder confidential information. The dealer excludes that builder's records and every plan PDF, and keeps takeoff quantity lists, quotes with prices stripped, and order and return records for the rest.

The result shows how estimators turned plans into material lists and how those lists compared with what shipped, without any drawing, builder name or address. The dealer also adds an ownership sentence to its quote template for future work.

How SourceX approaches estimating records#

SourceX handles estimating records in the Rights and Preparation steps of the SourceX five-step transaction. Rights review separates designer-owned plans and component designs from dealer-made takeoffs, quotes and orders, and checks builder agreements for confidentiality terms. Preparation then removes names, addresses and pricing, and the dealer approves the result before anything moves.

Each package carries a SourceX Evidence Packet, so the exclusion of plan images and the treatment of each builder's records are documented as part of provenance, licensing rights, permitted use, the privacy record and release authorization. The initial fit check uses only a description of systems and record types; no plans or takeoffs are shared at that stage.