Do sub-consultants own their sheets in the architect's drawing set?

Do consultants own their sheets in the architect's set?#

Consultants generally own their own sheets in the architect's drawing set under standard AIA terms. AIA B101-2017 Section 7.2 deems the architect and the architect's consultants the authors and owners of their respective instruments of service, each reserving its rights, including copyright.

So a set with one cover sheet is not one owner's work. The structural engineer's framing plans and calculations, the MEP engineer's duct layouts and panel schedules, the civil engineer's grading plans and the landscape architect's planting plans each belong to the firm that prepared them, subject to the agreements on that project.

AIA A201-2017 carries the point onto the construction side. Section 1.5.1 names the architect and its consultants as owners of the instruments of service, and Section 1.5.2 limits contractors to using them for the work and bars use on other projects without written consent from the owner, the architect and the consultants.

What the consultant agreement can change#

The consultant agreement can change the default, so the executed agreement for each project decides who owns each sheet. The AIA C401 architect-consultant form has its own ownership and license provisions, and many firms use their own consultant agreements or edit the form heavily.

Look for whether the consultant assigned its documents to the architect, granted the architect a license and for what purposes, or flowed down the owner agreement's terms. Also note which engineers were employees rather than outside consultants: under copyright law, work an employee creates as part of regular duties is a work made for hire owned by the employer, so in-house engineering belongs to the firm.

Check for flow-down language too. Many consultant agreements bind the consultant to the terms of the architect's owner agreement, which can add the owner's confidentiality and use restrictions on top of the consultant's own rights.

Older projects may have no consultant agreement on file at all, or only a proposal accepted by email. Record those gaps instead of guessing; an unclear agreement is a reason to carve out, not to include.

Whose work is on which sheet#

Discipline prefixes give a first pass at authorship, but mixed sheets and shared models need a closer look. The table gives the usual author and default treatment for each kind of sheet or file in a combined set.

Watch for sheets the architect drew from consultant information. Reflected ceiling plans that place the engineer's diffusers and fixtures, enlarged plans with coordinated MEP routing and life safety plans built on the fire protection design can mix two firms' work on one architect-numbered sheet.

Steps to tag sheets by discipline author#

Tagging sheets by discipline author is a one-time pass per project that makes every later decision faster. The output is a sheet-level register linked to the consultant agreement for each discipline.

Store the register with the project record rather than in a one-off spreadsheet, so the next rights review, closeout or records request can reuse it instead of starting again.

• 1Pull the final sheet index from the issued set or the document management system.
• 2Map each discipline prefix to the consultant firm and the agreement on file.
• 3Check title blocks for consultant names and seals, and flag sheets that combine disciplines.
• 4Identify linked models, calculation packages and specification sections by author.
• 5Mark architect-authored redlines and coordination notes on consultant sheets separately.
• 6Record the agreement terms for each consultant: assignment, license or silence.
• 7Decide per consultant whether to carve out, seek written sign-off or exclude the project.

Carve out or ask for sign-off?#

Carving out consultant work is the default, and asking for sign-off makes sense only when the value lies in coordination between disciplines. A package of architectural RFIs, internal QA comments and code research rarely needs the MEP engineer's sheets.

Where cross-discipline coordination is the point, for example clash resolution logs or RFI threads where the architect and engineers resolve a conflict together, written consent from each consultant whose work appears is the cleaner route. The consent should name the records, the permitted use and whether the consultant's name will be removed.

Illustrative: a COO builds an authorship register#

Illustrative: a fictional architecture firm designs offices, labs and multifamily buildings with a regular bench of structural, MEP and civil consultants. Its COO wants to understand what a licensable package could hold.

Using sheet index exports from the document management system and consultant agreements stored with project records in Deltek, the COO's team tags each sheet by author. Most consultant agreements are silent on new uses, so all consultant sheets, calculations and linked models are carved out. One structural consultant assigned its documents to the architect, but only for use on the project, so those sheets are carved out too.

The candidate package becomes architectural RFIs, internal design review comments and the firm's own specification edits, with consultant names removed from correspondence. The register shows, for every excluded sheet, which consultant authored it and why it was left out.

How SourceX handles mixed-author drawing sets#

SourceX handles mixed-author drawing sets by tracing authorship before anything is prepared. In the Rights step of the SourceX five-step transaction, owner agreements and consultant agreements are read together, and consultant work is carved out unless a written sign-off covers it.

The SourceX Evidence Packet records provenance at the discipline level, the licensing rights relied on, permitted use, the privacy record and release authorization, including any consultant consent letters. The architecture firm approves the final scope.