Interstate AEC projects do not usually fall apart because of one obvious mistake. The real trouble often starts in quieter places: a license that does not travel, a contract clause copied from the last job, a public-records issue nobody flagged, or project data scattered across too many systems.
This checklist helps multi-state teams catch those risks while the project is still flexible. Use it before kickoff to make compliance easier, cleaner, and far less stressful later.
1. Professional Licensing
Professional licensing should be checked before anyone markets, stamps, or manages regulated work across state lines. According to NCARB, each of the 55 U.S. jurisdictions sets its own requirements for architectural licensure. That means one active license may not cover every role, project location, or firm responsibility.
Review individual licenses, firm certificates of authorization, renewal dates, responsible-charge rules, and title restrictions. Also, confirm what happens if the qualifying architect or engineer leaves during the project.
2. Out-of-State Subpoena Protocol
Legal discovery across state lines can quickly complicate multi-state AEC operations. Projects often involve owners, contractors, consultants, and records located across multiple jurisdictions, meaning a legal request may originate outside the state where your firm is based. When handling an out-of-state subpoena in New York, for example, your team needs a clear response plan before project files become evidence. Managing cross-jurisdiction records requires establishing standard procedures early:
- Route incoming legal notices to counsel immediately
- Pause ordinary data deletion and enforce holds
- Identify key document custodians across the firm
- Track strict jurisdictional deadlines and response windows
These safeguards prevent procedural errors during time-sensitive requests. They ensure your team remains compliant while minimizing the administrative burden of discovery.
3. Code Conflicts
Code conflicts can hide behind familiar model-code language. A project may reference the International Building Code, yet the adopted edition, local amendments, energy code, and fire review process may differ by jurisdiction. The International Code Council adoption chart shows why state and local confirmation still matters.
Confirm the authority having jurisdiction early. Then keep a written code matrix, so design teams don’t rely on memory or assumptions from a prior state.
4. Contract Venue Clauses
Venue and governing-law clauses deserve a fresh read on every interstate job. A reused contract may point disputes to one state while the project, owner, witnesses, and public records sit somewhere else. That mismatch can create a fight about where the fight should happen.
Check venue, governing law, arbitration location, notice periods, indemnity, insurance, and flow-down language. Make sure subconsultant and subcontract terms do not quietly contradict the prime agreement.
5. Data Retention and Litigation Holds
Data retention works best when the team maps systems before pressure hits. AEC records can include emails, RFIs, schedules, photos, models, meeting recordings, markups, chat messages, and platform comments. Once a dispute is reasonably expected, ordinary deletion rules may need to stop.
Assign clear roles to legal, IT, and project leadership. The hold process should explain who triggers it, who receives it, and how compliance gets documented.
6. CDE Governance
A common data environment is not just a shared folder with better branding. Without governance, teams can upload duplicates, issue old revisions, or lose the approval trail behind a design decision. Before files start moving, define the controls that keep everyone working from the same record:
- Naming rules
- Revision controls
- Suitability status
- Access rights
- Archive rules
Good CDE rules protect coordination during design and construction. They also make future audits, claims, and document reviews easier to manage.
7. Public Records Exposure
Public records exposure can surprise private teams working on public or publicly funded projects. Drawings, procurement materials, emails, meeting notes, and contracts may become part of an agency file. Once records enter that environment, disclosure may depend on public records law instead of private preference.
Flag trade secrets, security-sensitive drawings, proprietary pricing, and confidential methods before submission. Follow the owner’s marking and exemption process rather than assuming confidentiality language will handle it later.
Keep Interstate AEC Compliance Boring
Interstate AEC compliance works best when everyone knows the rules before pressure hits. Put licensing, subpoenas, codes, contracts, records, CDE rules, and public records into the startup checklist for every multi-state job.
Revisit the checklist whenever a new jurisdiction, consultant, owner, or platform enters the project. The goal is not to make compliance complicated. It is to make the team calm, ready, and harder to surprise.
