The AEC Crash Course

What the architecture, engineering, and construction industry actually is, who does what, and the acronyms you need to survive a meeting.

Who this is for

You work in tech. Someone in your network says they do "AEC tech," or a job posting mentions "construction technology," or you just closed a deal with a company whose customers wear hard hats. You nodded along. You have no idea what a submittal is.

This is the primer. Thirty minutes of reading gets you to the point where you can follow an industry conversation, ask a competent question, and know what you don't know.

It is not a course. It is not a certification. It is the vocabulary and the mental model.

---

1. What AEC means

AEC stands for Architecture, Engineering, and Construction. It is the umbrella term for everyone involved in designing and building the physical environment: buildings, roads, bridges, water systems, data centers, hospitals, warehouses.

You will also see AECO, where the O is Owner or Operations. That fourth letter matters more than it looks. A building costs money to design and build once, then costs money to run for the next fifty years. The people who operate it have different software, different priorities, and often no relationship at all with the people who built it. Adding the O is an acknowledgment that the handoff between construction and operations is one of the industry's genuine unsolved problems.

Adjacent terms you will encounter:

The industry in five facts

1. It is enormous. Construction is roughly 6–7% of GDP in developed economies and around 13% of global GDP when you include the full built environment. It employs more people than almost any other sector.
2. It is extraordinarily fragmented. There is no Amazon of construction. In the US, the largest contractor holds low single-digit market share. Most firms are small, regional, and family-owned. This is the single most important fact for anyone selling into the industry.
3. Every project is a prototype. Software ships the same binary to a million users. Construction designs and builds one thing, once, on a specific piece of dirt, under a specific jurisdiction's rules, with a team assembled for that project and dissolved afterward. There is no economy of scale in the way tech assumes.
4. Margins are thin. General contractors often run 2–5% net. A single bad project can erase a year. This makes the industry risk-obsessed and conservative, which is frequently mistaken for being backward.
5. Productivity has been roughly flat for decades. Manufacturing productivity has climbed steeply since 1945. Construction has not. Every serious person in the industry has a theory about why. This is the animating problem behind most AEC technology.

The mental model: A construction project is a temporary company. It is capitalized (financing), staffed (design team, contractor, subs), given a product spec (drawings and specifications), run for 12 to 48 months, and then liquidated. Everyone on it works for a different employer with a different contract and a different incentive. Understand that and most of the industry's strange behavior becomes legible.

---

2. The lifecycle

This is the spine. Nearly everything in AEC is easier to understand once you know where in this sequence it happens.

The phase names below follow the industry's standard framing, which comes largely from CSI (the Construction Specifications Institute) and AIA (the American Institute of Architects). Different firms use slightly different labels, but the shape is universal.

Phase 0 - Site and feasibility

Before anyone draws anything, somebody has to decide that a project should exist and that it works financially.

• Site selection and due diligence. Is the land buildable? What is the zoning? Are there wetlands, easements, contamination, bad soil?
• Entitlements. Legal permission to build what you want to build. Rezoning, variances, use permits, planning commission hearings. This can take years and can kill a project outright.
• Pro forma. The financial model. Costs in, revenue out.
• Programming. How much of what? 200 units, 40,000 square feet of retail, 12 operating rooms.

Key documents here: LOI (letter of intent), PSA (purchase and sale agreement), ALTA survey, Phase I ESA (environmental site assessment).

Phase 1 - Design

Design proceeds in escalating levels of detail. Each phase ends with a package the owner reviews and approves before spending more money.

Software analogy, used once and then dropped: SD is the design doc, DD is the technical spec with interfaces defined, CD is the actual codebase. Permitting is a compliance review by a regulator who can block your release.

The output of design is not "a blueprint." It is a set of contract documents, which is a legally operative artifact. More on that in section 4.

Phase 2 - Procurement

The owner needs a builder and a price.

• Bidding. The project is advertised or invited. Contractors receive the documents and prepare pricing.
• Takeoff and estimating. Contractors measure quantities off the drawings and price them. This is genuinely hard, high-stakes work done under a deadline.
• Addenda. Formal changes to the bid documents issued during the bid period.
• Bid day. Numbers come in, usually in the last thirty minutes, often by fax. Yes, still.
• Award and buyout. The winner is selected and then goes out to subcontractors to lock in the trade pricing they estimated.
• NTP. Notice to proceed. Work can begin.

Phase 3 - Construction

The longest and most visible phase. The paperwork here is the part outsiders never anticipate.

• Mobilization. Site fencing, trailers, utilities, safety plan.
• Submittals. The contractor formally submits product data, shop drawings, and samples proving that what they intend to install matches what was specified. The design team reviews and approves. Thousands of these on a large project.
• RFIs. Requests for information. When the drawings are unclear, contradictory, or hit reality wrong, the contractor asks a formal written question and the architect or engineer answers in writing. The RFI log is a running record and, later, evidence.
• Change orders. Formal modifications to scope, price, or schedule. The most contentious document in the industry.
• Pay applications. Monthly billing based on percentage of work complete, reviewed and certified before payment.
• Inspections. The local jurisdiction inspects at defined milestones. Fail one and work stops.
• OAC meetings. Owner-Architect-Contractor. The recurring project standup.

Phase 4 - Closeout and occupancy

• Punch list. The walkthrough list of incomplete or defective items.
• Substantial completion. The legal milestone where the owner can occupy and use the building for its intended purpose. Triggers warranty periods and the release of retained money.
• Commissioning (Cx). Systematic verification that the building's systems actually work as designed. Increasingly its own discipline.
• Certificate of Occupancy (CO). The jurisdiction's legal permission to occupy.
• O&M turnover. Manuals, warranties, as-built drawings, asset data handed to whoever will operate the building.
• Warranty period. Typically one year for general work, longer for roofs and major systems.

Then the building operates for 30, 50, 100 years. That period is where the overwhelming majority of the total cost lives, and it is the least digitized part of the whole lifecycle.

---

3. Who's who

Titles vary by firm and region. What follows is the working reality: what the role does, who pays them, and what they are optimizing for.

Owner side

Owner / Developer. Pays for everything and bears the risk. May be a REIT, a private developer, a corporation building for its own use, a hospital system, a school district, a government agency. Optimizing for: return, schedule, and not getting sued.

Owner's Representative ("Owner's Rep"). Hired by the owner to manage the project on their behalf, especially when the owner does not build often. Acts as the owner's technical brain.

Development Manager. Runs the project from the business side. Entitlements, financing, pro forma, leasing coordination.

Facilities / Asset Manager. Inherits the building. Frequently not consulted during design, which is a recurring and well-documented failure mode.

Design side

Architect. Designs the building, coordinates the consultant team, produces the drawings and specifications, and typically administers the construction contract on the owner's behalf. Legally licensed and personally liable.

Architect of Record (AOR). The licensed entity that stamps the drawings and carries the liability. On large projects, a "design architect" may do the concept while a separate AOR produces the documents.

Structural Engineer (SE). Foundations, framing, load paths, seismic and wind. Makes sure it stands up.

MEP Engineer. Mechanical, electrical, plumbing. Often includes FP (fire protection), giving you MEPF. Heating, cooling, ventilation, power, data, water, waste, sprinklers. Usually the most spatially complex coordination problem in a building.

Civil Engineer. Site work. Grading, drainage, stormwater, utilities to the building, parking, roads.

Landscape Architect, Interior Designer, Lighting Designer, Acoustician, Envelope Consultant, Code Consultant. Specialty consultants brought in as needed. Larger and more technical projects have more of them.

Engineer of Record (EOR). Same idea as AOR, for a given engineering discipline.

BIM Manager / VDC Manager. Owns the digital model, the modeling standards, and clash detection. This is where a lot of AEC-tech conversations actually land.

Construction side

General Contractor (GC). Holds the contract with the owner to build the project. Manages the site, the schedule, the money, and the subcontractors. Self-performs some work or none at all.

Construction Manager (CM). Similar function, different contractual posture. Under CMAR (CM at Risk) they carry the same risk as a GC. Under CM Agency they advise the owner without holding trade contracts.

Subcontractor ("sub"). The firm that actually performs a trade: concrete, steel, drywall, electrical, mechanical, roofing, glazing. Most physical work on a jobsite is performed by subs, not by the GC.

Project Executive (PX). Oversees several projects, owns the client relationship and the profit.

Project Manager (PM). Owns one project's budget, contracts, schedule, and paperwork. Usually office-based with regular site presence.

Superintendent ("Super"). Runs the field. Sequencing, crews, safety, quality, daily execution. On most jobs the Super and the PM are co-equal, and the Super's opinion on constructability is final.

Project Engineer (PE) / Field Engineer / Assistant PM. The engine room. Processes submittals and RFIs, tracks logs, chases documentation. The industry's standard entry-level role.

Estimator. Prices the work. Takeoff, unit costs, subcontractor solicitation, bid assembly.

Scheduler. Builds and maintains the CPM schedule. On large projects, a full-time specialist.

Foreman / Crew / Trades. The people installing the building. Carpenters, ironworkers, electricians, pipefitters, operators, laborers. In union markets, organized by trade and dispatched from a hall.

Safety Manager (EHS). Enforces the safety program. Has authority to stop work.

Third parties

AHJ - Authority Having Jurisdiction. The government body enforcing code. Usually the city or county building department, plus the fire marshal. The AHJ's interpretation of code is the interpretation that counts, and it varies from town to town.

Inspector. Verifies work in the field. May be municipal, or a third-party special inspector for structural and life-safety items.

Commissioning Authority (CxA). Independent verification that systems perform.

Lender, Insurer, Surety. The surety issues the bonds that guarantee the contractor will finish (performance bond) and pay their subs (payment bond). A contractor's bonding capacity effectively caps the size of work they can pursue.

---

4. The documents

If you take one thing from this primer, take this: in AEC, the documents are the product. Design firms do not sell buildings. They sell a legally binding, coordinated instruction set. Understanding the document structure explains a startling amount of industry behavior.

Contract documents

The set that legally defines the work. Typically:

• The agreement (owner-contractor contract)
• General and supplementary conditions (the rules of engagement)
• Drawings (the graphic instructions)
• Specifications (the written instructions: quality, materials, execution, standards)
• Addenda and modifications

Drawings and specifications are complementary, not redundant. Roughly: drawings show quantity and location, specifications state quality and procedure. When they conflict, the contract states an order of precedence, and arguing about that order is a whole legal subspecialty.

MasterFormat

MasterFormat is CSI's standard numbering system for organizing specifications and cost data by work result. Fifty divisions, hierarchical numbering. It is the industry's shared taxonomy, and it is everywhere: spec books, estimates, cost databases, product catalogs, accounting codes.

A partial map of the divisions you will hear most:

Division 01 deserves special mention. It contains the administrative and procedural requirements that apply to the entire project: submittal procedures, quality control, temporary facilities, closeout. Experienced people read Division 01 first because it governs how everything else gets executed.

Other classification systems

• UniFormat organizes by building element (foundations, superstructure, exterior enclosure) rather than by work result. Better suited to early design and conceptual estimating, when you know you need a roof but not what kind.
• OmniClass is a broader multi-table classification covering spaces, phases, disciplines, and products.

The distinction between MasterFormat and UniFormat is a reliable signal of whether someone actually knows the industry.

The construction paper trail

That paper trail exists because the industry runs on contract and liability. It is not bureaucracy for its own sake. Every one of those documents is there because somebody once lost a lawsuit for lack of it.

---

5. How the money and risk are arranged

Two separate questions, frequently confused:

1. Delivery method - who holds which contracts, and when the builder joins the team.

2. Contract type - how the price is set.

Money mechanics worth knowing

• Retainage. The owner withholds a percentage (commonly 5–10%) of each payment until the work is complete. It flows down to subs. It is a constant source of cash-flow pain and an active area of state legislation.
• Contingency. Money set aside for the unknown. Owner contingency and contractor contingency are different pots with different rules.
• Allowance. A placeholder dollar amount for scope not yet defined.
• General conditions vs. general requirements. GCs (the cost category) are the project's overhead: supervision, trailers, temp power, cleanup. Confusingly abbreviated the same as General Contractor.
• Value engineering (VE). Formally, substituting lower-cost approaches while preserving function. In practice, the phase where the good materials get cut.
• Mechanic's lien. A statutory claim against the property by anyone who furnished labor or materials and did not get paid. Powerful, deadline-driven, and the reason lien waivers accompany nearly every payment.
• Float. Schedule slack. The critical path is the sequence with zero float, where any delay delays the project. Who "owns" float is worth real money in a delay claim.

---

6. Codes and standards

Code compliance shapes the design more than most outsiders expect. A short orientation:

• Model codes are written by the ICC (International Code Council) and published as the I-Codes: IBC (building), IRC (residential), IFC (fire), IECC (energy), IMC/IPC (mechanical, plumbing) and others. They are model documents with no force on their own.
• States and municipalities adopt them, usually with amendments, and usually a version or two behind the current edition. So "the code" in Denver, Dallas, and Boston is not the same document.
• Referenced standards do the technical heavy lifting. The code says a concrete structure shall comply with ACI 318; the code says steel shall comply with AISC 360; energy modeling leans on ASHRAE 90.1; fire and life safety pulls from NFPA. Materials testing points to ASTM. These are written by professional societies and incorporated by reference.
• Accessibility runs on a separate track: the ADA is federal civil rights law, not building code, and it coexists with ANSI A117.1 as adopted by the code. They are not identical, and complying with one does not guarantee compliance with the other.
• Zoning is not building code. Zoning governs what you may build on a site (use, height, setbacks, density, parking, FAR). Building code governs how you must build it. Different documents, different reviewers, different failure modes.
• The AHJ has final interpretive authority. Two plan reviewers in adjacent jurisdictions can read identical language differently, and both are correct within their jurisdiction.

Green and performance frameworks are voluntary overlays on top of this: LEED, WELL, Passive House, Living Building Challenge, plus jurisdiction-specific energy and carbon ordinances that are increasingly mandatory rather than optional.

---

7. The technology landscape, in categories

Named without endorsement, and grouped by where in the lifecycle they sit. Categories matter more than logos.

• CAD / BIM authoring. Where the model gets made. Revit, ArchiCAD, Vectorworks, Rhino, Civil 3D, Tekla, and the ongoing rise of browser-native challengers.
• BIM coordination and clash detection. Combining discipline models and finding where the ductwork runs through the beam before it is built. Navisworks, Solibri, and cloud common data environments.
• Reality capture. Laser scanning, photogrammetry, 360 cameras, drones. Producing point clouds and progress documentation.
• Estimating and takeoff. Quantity measurement and pricing. Increasingly automated off models and PDFs.
• Scheduling. CPM tools, plus a growing lean-construction school built on pull planning and last-planner methods.
• Project management / common data environment. Document control, RFIs, submittals, drawings, daily reports. The system of record on most jobsites.
• Field execution. Punch lists, safety, quality inspections, layout, equipment tracking.
• Financials and ERP. Job cost accounting, payroll, AP/AR, work-in-progress reporting. Deeply unglamorous, deeply entrenched.
• Preconstruction and site selection. Feasibility, zoning and entitlement analysis, market and real estate data.
• Facilities and asset management. Where the building lives after handoff, and where the data handed over is usually worse than it should be.

Two interoperability concepts you should recognize:

• IFC (Industry Foundation Classes) - the open, vendor-neutral data schema for building models, maintained by buildingSMART. Note the acronym collision with International Fire Code and Issued For Construction.
• COBie - a structured spreadsheet format for delivering asset and equipment data from construction to operations.

---

8. Things that surprise people coming from tech

Liability is the organizing principle. Architects and engineers stamp drawings with a personal professional seal. If a building hurts someone, individuals are named. That fact explains conservatism, documentation volume, and reluctance to trust automated output that nobody will stamp.

The customer is a temporary organization. You are not selling to a company so much as to a project team that will not exist in three years. Adoption does not compound the way it does in SaaS unless it lands at the enterprise level.

Fragmentation defeats network effects. A GC, sixty subs, four design firms, and an owner all use different systems and will not standardize because none of them can compel the others.

The field is not the office. Gloves, sunlight, no reliable connectivity, a foreman with thirty years of experience and no patience. Software that requires a desk chair does not get used.

Nothing is repeatable, but everything is patterned. Every project is unique, and yet the same twelve problems recur on all of them. That gap is the whole opportunity.

Being slow to adopt is often rational. Downside risk is asymmetric. A failed software rollout on a $200M project does not cost a sprint. It costs a schedule, and schedule costs real money.

---

9. Acronym reference

Grouped for scanning. This is not exhaustive. It is what actually comes up.

Roles and organizations

Industry bodies and standards writers

Codes

Phases and delivery

Documents and process

Cost and contract

Real estate and finance

Technology

Four collisions to watch

The industry reuses acronyms shamelessly. Context is the only disambiguator.

• CO - Change Order, or Certificate of Occupancy.
• PE - Project Engineer, or Professional Engineer. Very different things.
• GC - General Contractor, or General Conditions.
• IFC - International Fire Code, Issued For Construction, or Industry Foundation Classes.

---

10. Where to go from here

If you want to go deeper, in rough order of effort:

• AEC Environment Fundamentals, my free 522-page course, covers everything here in depth, plus more of the real estate side that happens before design, build, and occupation. It follows one project from site acquisition through closeout, and it details the tech landscape in AEC, where AI is actually in use, and the business math behind the whole industry.
• Read a real project manual. Many public agencies post full bid sets. Open one, read Division 01, then flip through a spec section and the corresponding drawings.
• Walk a jobsite. Ask someone. Most people will say yes, and thirty minutes on site teaches more than a month of reading.
• Learn the money. Read a pro forma and a schedule of values side by side. That is where the design decisions and the field decisions meet.

The industry rewards people who show up, ask specific questions, and admit what they do not know. It has very little patience for people who arrive certain they can fix it.