Architecture, Engineering & AEC Workspace Pack

Built Environment

A workspace starter for architecture firms, engineering consultancies, AEC design teams, multidisciplinary studios, and owner-side design delivery groups that need a stronger operating system for winning the right work, delivering coordinated documents, controlling risk, managing construction administration, and protecting profitability.

What this pack launches

2 departments, 13 atoms, 6 objectives, 12 draft projects, 48 starter tasks for a vertical-specific Supanova workspace.

Best fit

Architecture firms
Engineering consultancies
Multidisciplinary AEC studios
Owner-side design delivery teams

Starter objectives

Qualify profitable client work
Standardize scope, contract, and project startup
Strengthen design coordination and information management
Improve code, permitting, quality, and document control
Stabilize construction administration, change, and cashflow
Build resource, risk, and learning system

Starter atoms

AEC Operations Director - Firm Operations
Client Pursuit & Capture Lead - Business Development
Scope, Fee & Contract Manager - Commercial Setup
Design Project Manager - Design Delivery
Discipline Coordination Lead - Technical Coordination
BIM & Information Management Lead - Digital Practice
Specifications & Product Selection Lead - Specifications
Code, Permitting & Accessibility Coordinator - Regulatory Coordination

Draft projects

Build firm project intake and delivery cadence
Create pursuit go/no-go and proposal system
Build scope, fee, contract, and risk baseline
Create project kickoff, owner requirements, and delivery plan
Stand up BIM/CAD standards and information management
Build design phase deliverables and discipline coordination
Create code, permitting, accessibility, and authority review
Build specifications, product data, and cost alignment

Research spine

Research Notes

The pack is designed around the operating reality of AEC professional services: selecting the right work, writing clear scope, planning project phases, coordinating disciplines, controlling design information, managing code and permit review, running QA/QC, administering construction, tracking changes, protecting cashflow, and learning from each project.

Sources Used

AIA, AIA Best Practices: https://www.aia.org/aia-best-practices

- Implication: the pack should include firm management, project delivery, project management, quality management, technology use, contracts, and risk management rather than only design tasks.

AIA Contract Documents, B101-2017 Summary: https://help.aiacontracts.com/hc/en-us/articles/1500010280541-Summary-B101-2017-Standard-Form-of-Agreement-Between-Owner-and-Architect

- Implication: design workflows should reflect common basic service phases: schematic design, design development, construction documents, procurement, and construction.

AIA, A primer on project delivery terms: https://www.aia.org/resource-center/primer-project-delivery-terms

- Implication: the pack needs delivery-method awareness because design-bid-build, CM at risk, and design-build change responsibilities, risk allocation, and communication paths.

EJCDC, Engineers Joint Contract Documents Committee: https://ejcdc.org/

- Implication: engineering-led AEC work needs contract, consultant, owner, contractor, risk allocation, and legal-review awareness, especially for infrastructure and public/private engineering projects.

Autodesk, 2025 State of Design & Make - AECO industry insights: https://www.autodesk.com/design-make/research/state-of-design-and-make-2025/industry

- Implication: the pack should emphasize cost control, talent capacity, digital transformation, AI caution, data effectiveness, and resilience to uncertainty.

NIBS, Project BIM Requirements Standard: https://nibs.org/nbims/v4/pbr

- Implication: BIM workflows should begin with owner and project information requirements, not just model production.

NIBS, Project BIM Execution Planning Standard: https://nibs.org/nbims/v4/bep/

- Implication: the pack needs BEP workflows for BIM goals, roles, model uses, information exchanges, coordination, quality management, and technology infrastructure.

buildingSMART, openBIM: https://www.buildingsmart.org/about/openbim/

- Implication: model and information workflows should support IFC, IDS, BCF, and data interoperability where clients or delivery partners require open information exchange.

CSI, MasterFormat 2026: https://www.csiresources.org/standards/masterformat2026

- Implication: specification workflows should align drawings, specs, estimates, contracts, product data, change orders, and modern sustainability or compliance classification needs.

ICC, The International Codes: https://www.iccsafe.org/products-and-services/i-codes/the-i-codes/

- Implication: code and permitting workflows need jurisdiction, applicable model codes, local amendments, and authority having jurisdiction review tracking.

ADA.gov, 2010 ADA Standards for Accessible Design: https://www.ada.gov/law-and-regs/design-standards/2010-stds/

- Implication: accessibility should be a formal review workflow with applicable standard, scoping, technical requirements, and qualified review rather than an afterthought.

NSPE, Code of Ethics for Engineers: https://www.nspe.org/career-growth/nspe-code-ethics-engineers

- Implication: engineering workflows need public health, safety, welfare, competence, truthful statements, faithful client service, conflict disclosure, and signing/sealing responsibility boundaries.

ASCE, Code of Ethics: https://www.asce.org/career-growth/ethics/code-of-ethics

- Implication: civil and infrastructure workflows need public welfare, sustainability, competence, conflict disclosure, responsible charge, and honest professional communication.

CMAA, Construction Management Standards of Practice: https://www.cmaanet.org/bookstore/book/construction-management-standards-practice

- Implication: construction administration and project controls should address time, cost, quality, safety, risk, technology, claims, contract administration, and closeout.

Construction Industry Institute, Scope Control and Change Management: https://www.construction-institute.org/scope-control-and-change-management

- Implication: change management should start early and cover scope control, baseline discipline, change recognition, impacts, authorization, and claim-sensitive evidence.

Design Translation

Pursuits, Design Delivery & Technical Standards exists because AEC firms win or lose operationally before design starts: client fit, scope, phase planning, BIM, coordination, specifications, and QA/QC need a shared rhythm.
Project Controls, Construction Admin & Risk exists because profitability and liability often break during permitting, CA, changes, invoices, and closeout, not only during design production.
The atom roster intentionally combines principals, project managers, BIM, specs, permitting, QA/QC, CA, project controls, and commercial risk because the workspace needs both creative delivery and operational discipline.
Projects are draft because the pack provides structured operating state while preserving human ownership for licensed design, code interpretation, permit submissions, engineering calculations, seal decisions, legal review, and professional liability questions.