Engineering and architecture
Records from public-sector projects: what A/E firms can reuse
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
On public-sector projects, an engineering firm usually cannot reuse the deliverables: plans, specifications and reports are commonly owned by the agency under the consultant contract. What may be reusable are the firm's internal records, such as QA/QC logs, staffing plans and review histories, once counsel confirms the contract allows it and identifying details are removed.
Key takeaways
- Treat public-client deliverables as agency-owned and excluded unless counsel confirms otherwise.
- Internal QA, staffing and review process records may be separable from the deliverables.
- A document's availability under a public records law does not grant a right to license it.
- Infrastructure security, federal funding terms and retention clauses add checks beyond ownership.
What can A/E firms reuse from public-sector projects?#
A/E firms can usually reuse only the internal process records from public-sector projects, not the deliverables. Public owners such as state DOTs, counties, cities and utilities commonly write consultant contracts so that plans, specifications, reports and data produced for the project belong to the agency.
The first-pass decision rule is simple: exclude public-client deliverables, then ask whether the firm's internal records from those projects can be separated, de-identified and cleared by counsel. Those records include QA/QC logs, staffing and schedule histories and internal review notes that were never delivered to the agency.
Many civil firms have mostly public clients, so this rule shapes their whole archive. It does not make the archive worthless. It changes which part of it matters.
Decision table: public project record types#
The decision table assumes typical public consultant terms. Your executed contract governs: some agencies grant consultants broad reuse rights, while others restrict even internal records through confidentiality and audit clauses.
| Record type | Usual position on public projects | Typical treatment |
|---|---|---|
| Plans, specifications and reports delivered to the agency | Agency-owned under most contracts | Exclude |
| Survey, geotechnical and testing data paid for by the agency | Agency-owned; may include third-party data | Exclude |
| Design calculations | Often a deliverable or subject to audit | Exclude unless the contract confirms otherwise |
| Internal QA/QC comment logs and checklists | Firm process records; check the contract | May be separable after review |
| Staffing plans, hours and schedule histories | Firm records containing employee data | May be separable after pseudonymization |
| Proposals and statements of qualifications | Firm-authored; may become public after award | Case by case |
| Agency correspondence and meeting minutes | Mixed authorship; may be public records | Usually exclude or summarize |
| Security-sensitive infrastructure details | Restricted by contract or law | Exclude |
What DOT and municipal consultant contracts typically say#
DOT and municipal consultant contracts typically address ownership, reuse, confidentiality, records retention and audit access, and each clause bears on reuse. Ownership clauses often vest documents in the agency on creation or on payment. Reuse clauses often let the agency reuse documents at its own risk while restricting what the consultant may do.
Confidentiality clauses may cover all project information, not only deliverables, and some agencies apply them to working files. Retention and audit clauses require the firm to keep records for a set period and make them available to the agency or its auditors, so the firm holds those records under obligations. Federally funded projects can add funding-agreement terms that flow down to consultants.
Agencies often adapt standard forms, such as EJCDC agreements, with their own ownership language. Read the signed version and its supplementary conditions, not the published form.
Why public availability is not permission#
Public availability is not permission to license, because public records laws govern what an agency must disclose, not what a consultant may do with the same documents under its contract. A drawing anyone can obtain through a records request is still governed by the firm's agreement with the agency, and some infrastructure records are withheld from disclosure for security reasons.
There is also a client relationship to protect. Many public owners select engineers through qualifications-based selection, and a firm that surprises an agency with a licensing arrangement risks future work. Where internal records are scoped, many firms remove agency-identifying details completely, and some inform the client as a courtesy even when the contract does not require it.
Which laws may apply, including state public records acts, security-information rules and any federal funding terms, is assessed project by project with counsel.
Process records that may be separable#
Process records that may be separable are those that show how the firm works rather than what it designed for the agency. Each still needs counsel's review against the contract, and the firm decides what to include.
- QA/QC comment logs, checklists and backcheck records, with project and agency identifiers removed.
- Staffing plans and resource histories, reduced to roles and pseudonymized.
- Schedule histories comparing planned and actual milestones.
- Internal design review notes and lessons learned.
- Proposal development records, such as go or no-go decisions, with agency names removed.
How retention policy shapes the archive#
Retention policy shapes what a firm can ever consider reusing, because records destroyed on schedule are gone, and records kept long past their purpose may carry risk without benefit. Public contracts often set minimum retention for audit purposes, and many firms layer their own schedule on top for professional liability reasons.
A workable approach is to classify by record type rather than by project. Deliverables follow the agency's rules and the firm's liability schedule. Internal process records, such as review logs and staffing histories, can follow a separate schedule the firm sets with counsel, which makes it possible to keep de-identified versions without holding full project files indefinitely.
- Map each record type to the clause or law that sets its minimum retention.
- Note where the agency holds audit rights and when they end.
- Separate internal process records from deliverables in the archive structure.
- Decide with counsel whether de-identified process records may be kept after source files are destroyed.
- Log each destruction so the archive's contents can be described accurately later.
Illustrative: a civil firm with mostly public clients#
Illustrative: a fictional civil engineering firm designs roads, bridges and water infrastructure for state DOTs, counties and municipal utilities. Its records sit in Deltek Vantagepoint, Bentley ProjectWise and an aging file server, and its retention policy has kept closed projects for years with no plan for them.
The CEO asks whether anything can be licensed. Counsel reviews a sample of contracts and finds deliverables agency-owned on all of them, confidentiality clauses reaching internal files on some, and silence about internal records on others.
The firm excludes all deliverables, and all water system and bridge projects for security reasons. It scopes QA logs and pseudonymized staffing histories from transportation projects whose contracts are silent on internal records, subject to counsel's sign-off, and it documents which contract families were reviewed.
How SourceX approaches public-sector project records#
SourceX treats public-sector archives conservatively. In the Rights step of the SourceX five-step transaction, each contract family is reviewed, deliverables are excluded by default, and only internal process records with a documented rights basis move on to Preparation.
The SourceX Evidence Packet for any resulting package records the contract basis, what was excluded and why, and the release authorization from the firm's signer. The opening fit check needs only metadata about systems, project types and contract forms, and no project files change hands at that stage.
Frequently asked questions
Can we use a public records request to get our own drawings back?
You may be able to obtain copies the way any member of the public can, subject to the agency's exemptions. Obtaining a copy does not change who owns the documents or what your contract allows you to do with them.
Do we need agency consent to license internal QA records?
Sometimes. If the contract's confidentiality or ownership clauses reach internal working files, consent may be required, or the records may need to be excluded. If the contract is silent, counsel can advise whether consent is needed or advisable for the relationship.
Do federally funded projects add requirements?
They can. Federal funding agreements may carry terms on records, data and intellectual property that flow down to consultants. Identify which projects had federal funding and have counsel review those terms before scoping any records from them.
Should we destroy old public project files instead of keeping them?
Follow your contracts and retention policy first, since agreements and laws often require records to be kept for set periods, and destroying them early can breach those duties. Once retention obligations end, whether to keep or destroy internal process records is a business decision best made with counsel.
Do private-sector projects at the same firm follow the same rule?
Not necessarily. Private owner agreements vary more widely, and many leave internal records with the firm. Each contract family is reviewed separately, so a firm's private work can follow a different path from its public work.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.