These free CMAA study guides connect construction-management preparation with scope, project responsibilities, schedule assumptions and acceptance evidence. Use a fictional building-refurbishment project to practise written planning and review questions. The linked Premium catalogue entry uses CMM for its Certified Construction Manager resource; verify the resource details and your exact target before choosing it. Original exercises build management explanations without directing live construction work, prescribing site safety procedures or granting a professional credential.
Want free reference PDFs? Email freelearning@ciscoforall.com with your exam code and name. We will send an available older reference file free of charge. Availability varies. See the request section below.
Choose the learning direction closest to your role and current knowledge. These orientations help you organise practice; they are not official exam objective lists. Compare your chosen target with the exact current syllabus and record any additional topics you need.
| Learning path | Who it suits | Topics to understand | First practice task |
|---|---|---|---|
| Project foundations | Construction-management learners | Scope and role boundaries | Write a fictional project brief |
| Delivery review | Experienced learners revising concepts | Time, cost and change | Review a dependency and change case |
| Handover reasoning | Study groups and reviewers | Quality records and acceptance | Build a closeout evidence list |
Connect additional review material with a specific preparation gap. Open a relevant product to explore its details, confirm its code and version, and decide how it supports your learning goal.
| Premium resource | Preparation focus |
|---|---|
| CMM — Certified Construction Manager — Premium PDF | Construction-management scope, responsibilities, delivery and handover reasoning. |
The linked catalogue uses CMM for its Certified Construction Manager entry; the professional credential is commonly abbreviated CCM. Verify resource details and current target requirements. These independent written exercises do not grant a credential or provide live site instructions.
A project brief should identify the required output, boundary and interfaces with existing work. A detailed task list can still omit access, coordination or acceptance needs. Use a fictional refurbishment and mark assumptions before planning the sequence. Keep design and specialist technical questions separate from the manager’s written coordination exercise.
Practice task: Write a fictional refurbishment brief with inclusions, exclusions and two interfaces. Expected result: A scope record identifying coordination questions. Common mistake to avoid: Assuming a task list establishes every project boundary
A responsibility map needs decision authority, information ownership and handover expectations. The person requesting a change may not be authorised to approve it. Use fictional owner, designer and contractor roles to identify who supplies evidence and who reviews it. Preserve unresolved authority rather than inventing an agreement that the case does not provide.
Practice task: Map a fictional design-to-delivery handover with one unresolved decision owner. Expected result: A role map distinguishing request, review and approval. Common mistake to avoid: Treating every request as an authorised instruction
A schedule estimate needs prerequisites and a clear definition of completion. A delayed approval can affect later work even when the individual task duration is unchanged. Use fabricated activities to trace the dependency and state the assumptions behind a revised expectation. Do not present a planning exercise as an instruction to accelerate live site work.
Practice task: Trace five fictional activities after a delayed design review. Expected result: A schedule explanation showing the affected dependency path. Common mistake to avoid: Adding task durations without considering prerequisites
A cost comparison needs quantities, period and included work. A change request can affect interfaces and existing commitments as well as direct cost. Separate original baseline, assessed impact and authorised decision in a fictional record. A calculated amount answers a narrower question than whether the change is agreed or the project remains achievable.
Practice task: Assess a fictional added feature with cost assumptions and dependency effects. Expected result: A change record linking scope, impact and decision state. Common mistake to avoid: Treating an estimated change as an approved commitment
Quality-related study should state the requirement, relevant record and unresolved acceptance question. A completed visit or a closed task does not prove that every requirement was verified. Use fabricated records to practise evidence review while routing real technical and safety judgments to appropriately qualified roles and applicable procedures.
Practice task: Review a fictional acceptance pack with one missing verification record. Expected result: A checklist separating activity completion from requirement evidence. Common mistake to avoid: Equating a closed task with established acceptance
A useful handover identifies completed work, records, remaining actions and accountable owners. A final meeting alone does not establish readiness for every intended use. Review the fictional project brief alongside the closeout pack and preserve unresolved interfaces. A bounded completion statement is clearer than hiding exceptions behind a polished overall summary.
Practice task: Create a fictional closeout record with two open items and review owners. Expected result: A handover distinguishing established completion from unresolved work. Common mistake to avoid: Declaring complete closure while outstanding items remain undocumented
Complete these activities as written exercises or in an authorised practice environment with fictional data. Define the expected outcome before starting and save a brief explanation of what the result establishes. Verify version-specific steps for your selected technology.
| Activity | What to do | Expected result |
|---|---|---|
| Define project scope and interfaces | Write a fictional refurbishment brief with inclusions, exclusions and two interfaces. | A scope record identifying coordination questions. |
| Assign responsibilities across project stages | Map a fictional design-to-delivery handover with one unresolved decision owner. | A role map distinguishing request, review and approval. |
| Analyse dependencies before revising dates | Trace five fictional activities after a delayed design review. | A schedule explanation showing the affected dependency path. |
| Review cost and change with their scope basis | Assess a fictional added feature with cost assumptions and dependency effects. | A change record linking scope, impact and decision state. |
Use these comparisons to find an assumption worth revisiting. For each mistake, write a new example with different details and explain why the corrected principle still applies.
| Common mistake | Why it matters | Better approach |
|---|---|---|
| Treating an estimated change as an approved commitment | This assumption skips a relevant check in: Review cost and change with their scope basis. | Assess a fictional added feature with cost assumptions and dependency effects. Review the expected result: A change record linking scope, impact and decision state. |
| Equating a closed task with established acceptance | This assumption skips a relevant check in: Connect quality review with acceptance evidence. | Review a fictional acceptance pack with one missing verification record. Review the expected result: A checklist separating activity completion from requirement evidence. |
| Declaring complete closure while outstanding items remain undocumented | This assumption skips a relevant check in: Close out with open items visible. | Create a fictional closeout record with two open items and review owners. Review the expected result: A handover distinguishing established completion from unresolved work. |
Explanation: The completion statement supports a reported activity state. Compare the acceptance conditions and record the missing evidence with an appropriate review owner before drawing a broader completion conclusion.
Write your own answer before reading the explanation. Identify the evidence supporting it, then change one detail and decide whether your answer should change. This is an original learning exercise, not an actual exam question.
| Stage | Focus | Practice outcome |
|---|---|---|
| Week 1 | Select the target and foundations | Write a fictional refurbishment brief with inclusions, exclusions and two interfaces. A scope record identifying coordination questions. |
| Week 2 | Apply core concepts | Map a fictional design-to-delivery handover with one unresolved decision owner. A role map distinguishing request, review and approval. |
| Week 3 | Investigate weak topics | Trace five fictional activities after a delayed design review. A schedule explanation showing the affected dependency path. |
| Week 4 | Review mixed examples | Assess a fictional added feature with cost assumptions and dependency effects. A change record linking scope, impact and decision state. |
Four weeks is an example schedule, not a promise of readiness. Adjust each stage to your experience and available time. Extend a stage when you cannot explain the topic without the notes or apply it to a fresh scenario. Revisit the exact target objectives so a familiar topic does not replace a relevant topic you have not practised.
Create a tracker with target topic, initial explanation, practice activity, observed result and next review date. Separate a topic you recognise from a topic you can apply. A useful record makes the remaining gap visible and helps you choose the next activity instead of repeatedly rereading the same material.
When an answer is wrong, preserve the initial assumption, the contradicting evidence and the corrected principle. Create a second example using different details. If the explanation works only for the first example, return to the concept before adding more resources. Review recurring errors together: they may reveal a missing foundation rather than several unrelated weaknesses.
| Tracker field | Example entry to write | Review question |
|---|---|---|
| Requirement | Write a fictional refurbishment brief with inclusions, exclusions and two interfaces. | What outcome am I trying to establish? |
| Evidence | A scope record identifying coordination questions. | Which observation supports my explanation? |
| Limitation | State what the exercise did not establish. | Am I making a broader claim than the evidence allows? |
| Next activity | Map a fictional design-to-delivery handover with one unresolved decision owner. | What new example will test the principle? |
Email freelearning@ciscoforall.com with your exam code and name, the product or framework version if known, and the topics you need. We will send an available older reference file free of charge. Availability varies; a file may not be available for every target. The original notes, tables and exercises on this page are free to read without requesting a file.
Keep the code and version visible when using an older reference. Terminology, objectives and product behaviour may differ from your current target. Compare the material with the scope you intend to study and verify release-specific information before using it in a lab. We share only resources we are permitted to distribute. If you are unsure of the target name, include the learning goal so the request can be understood.
Use this guide to organise foundations and identify weaker topics. Then choose a relevant CMAA Premium PDF for additional review. Give the resource a clear purpose: explain a concept, compare alternatives or repeat a practical scenario. Track the exact target and version alongside your notes so useful older material is not mistaken for complete current coverage.
Build a preparation routine around topic review, original exercises and an error log. After reviewing a resource, close it and explain the principle in your own words. Apply that principle to an unfamiliar example and record any remaining uncertainty. The value comes from understanding and application, rather than the number of files collected.
Construction-management scope, responsibilities, delivery and handover reasoning. — Premium PDF
Yes. The learning notes, tables, study plan and original exercises here are free to read. Premium PDFs are available separately through the linked product pages.
CMM is the code used by the linked store listing. Certified Construction Manager is commonly abbreviated CCM. Confirm the product details, edition and intended target before selecting the reference.
Yes. Email freelearning@ciscoforall.com with your name, exact target and exam code. We will send an available older reference file free of charge. Availability varies.
It may explain useful foundations while describing an earlier version. Compare its code, objectives and product behaviour with your exact target before treating it as a complete preparation resource.
Use the product table to find a resource matching your target. Explore its details and version, then connect it with the concept or practice gap you want to strengthen.
No. Adjust the schedule to your experience, available time and practice results. Repeat a stage until you can explain its concepts and apply them to a different example.
No. The scenarios are original exercises for understanding and decision-making. They are designed to help you practise explanations and evidence-based reasoning.
No. Results depend on your knowledge, practical skills and preparation.
Complete one small activity today and record its result. For an available older reference, email freelearning@ciscoforall.com. For additional preparation, choose a relevant Premium PDF above or browse the vendor selection below.