What the CMAA Standards of Practice Actually Cover
The Construction Management Association of America publishes a set of Standards of Practice that most construction managers either reference constantly or ignore until a contract dispute forces them to open the document. It isn't a legal requirement on its own, but it functions as the industry baseline for what a professional construction manager is expected to deliver across project phases. Clients, especially smaller owners who haven't worked with CMs before, often use it as a framing document when writing scope of services into a contract. The standards break down into core areas: project definition and planning, estimating and cost control, scheduling, procurement and contracting, construction phase oversight, and project closeout. Each section describes responsibilities rather than dictating methods, which is intentional. The document assumes you already know how to schedule a project or negotiate a subcontractor change order. It tells you that you should, not how.
Construction Management Standards Of Practice Cmaa
When people ask for the document, the official copy lives on the CMAA website and is available to members for free. Non-members can purchase it directly from their store. Several firm templates and checklists circulate online that claim to be derived from the standards, but they are almost always watered-down versions missing the nuance in the advisory language. If you want the real thing, go to cmaa.org and download the current edition. I ran a mid-rise renovation last year where the owner's architectural team delivered drawings that completely conflicted with the existing structural conditions. The contract didn't reference CMAA standards at all, so the team had no clear expectation of who was responsible for field-verification coordination before procurement began. I pulled up section 2.3 from the standards and pointed out that constructability review and field verification fall under preconstruction services. The architect pushed back because their scope had technically been "design development complete" on paper. We ended up using the standard as leverage in a scope clarification meeting rather than as a contractual obligation, and it got the owner to fund a three-week field verification phase before any procurement happened. The standard doesn't carry legal weight unless someone incorporates it into a contract, but it does carry weight in disputes because every serious construction management firm references it. That's the practical reality.
Where the Standards Fall Short
The document is deliberately high-level. It won't tell you how to handle a situation where a design-bid-build owner insists on competitive bids but your team has already identified three substitute materials that would save six weeks. The standards assume you're operating under an agency CM or CM-at-risk delivery method. If you're working as a consultant without contractual authority, citing the standards during a conflict won't give you leverage unless the owner cares about professional norms. It won't override a poorly drafted agreement. Another gap: the standards don't address digital delivery workflows. There's nothing about BIM coordination processes, laser scanning for as-built verification, or cloud-based submittal tracking. A lot of the language reads like it was written in an era when submittals were paper boxes and schedule updates happened in weekly meetings. You have to map those expectations onto modern tools yourself. The responsibility section still applies, but the method section is absent.
Get the Full Details
Practical Way to Use This Document
Start by embedding the relevant sections into your management plan at project kickoff. Reference section numbers when you communicate scope boundaries to owners. When someone asks you to do something outside normal CM responsibilities, point to the specific standard that defines the boundary. It takes about ten minutes to pull the right section and cite it in an email, and it usually stops scope creep before it becomes a conversation. Use the closeout section as a checklist, not just guidance. I've seen projects stall for months because the standards language was treated as a suggestion rather than a required deliverable sequence. The difference between a clean closeout and a messy one usually comes down to whether the CM enforced the order of final inspections, O&M submission review, and punch item resolution before releasing final payment. The standards spell that out clearly if you actually read the closeout section. Most firms don't track compliance against the standards internally, which is a missed opportunity. Running a quarterly audit of your own project files against the relevant sections will expose gaps faster than any software tool. You'll find submittal logs that don't match the tracking standard, schedule updates that skip the documentation step, and change order packets missing the approval chain the standards expect. It's tedious work. It also prevents two-hour phone calls with a client's lawyer three years later.
The document itself is around forty pages. Reading it once takes about an hour. Revisiting it at the start of each new project phase takes fifteen minutes and prevents most of the miscommunication that drives change orders and delays. That's the practical value, nothing more.
