Prepare for the CACM by studying decision chains rather than definitions: an RFI asks, a submittal approves before installation, a change order modifies the contract, and a daily report records it all. Read schedules against total float and the critical path, approve cost only against verified and compliant work, route hazards to the competent person, and rehearse each decision type through worked scenarios until the record-keeping becomes automatic.
Which Document Does What: RFI, Submittal, Change Order, and Daily Report
Each construction document has a distinct job: an RFI asks a question, a submittal gets materials approved before installation, a change order modifies the contract, and a daily report records what happened. Confusing them breaks the whole administrative chain.
An RFI asks a question about a gap or conflict in the contract documents; the answer may lead somewhere, but the RFI itself authorizes nothing. If the response changes cost or time, that change moves through a change order under the contract's change provisions. A submittal sits upstream of installation: shop drawings, product data, and samples are approved before the work is built, so work installed against an unapproved submittal is noncompliant even when the work itself looks fine.
The daily report is the contemporaneous record that lets you reconstruct any of these decisions later, and it is also where confusion creeps in. A report entry should state what happened, who was involved, and what action was taken; arguments and conclusions belong in formal correspondence. Contracts that require notice treat notice as its own step, so a report can record that notice was given on a given date, but it does not replace the notice itself.
| Document | What it changes or establishes | Typically initiated by | What it does not do |
|---|---|---|---|
| RFI | Clarifies a gap or conflict in the contract documents | Contractor, designer, or CM | Authorize extra cost or time by itself |
| Submittal | Documents proposed materials and methods before installation | Contractor, for review | Retroactively approve work already installed |
| Change order | Modifies contract scope, price, or time by agreement | Owner, CM, or architect depending on the contract | Remove the need for records and notices |
| Daily report | Establishes a contemporaneous record of site events | CM or field staff | Substitute for notice required by the contract |
| Notice | Triggers contractual rights or obligations on a deadline | A party seeking relief or giving a required warning | Resolve the underlying issue by itself |
Schedule Updates: Float, the Critical Path, and What Justifies a Time Extension
A schedule update is read against the critical path and total float. Delay that stays inside float does not move completion; delay to a critical activity does. Approval decisions follow that distinction, not the size of the delay.
Total float is the amount an activity can slip without moving the project completion date, assuming the schedule logic holds. The critical path is the chain of activities with the least float, so any delay there pushes completion. When you review an update, first compare the new completion date with the contractual one, then check total float on the delayed activity. This converts a raw delay story into a testable claim: did completion move, or did float absorb the hit?
Scenario: a mock update shows a steel delivery slipping ten days, but the steel activity carries twelve days of total float and the completion date does not move; the contractor requests a ten-day extension. The tempting call is to approve because a delay clearly happened. The better decision is to compare the delay against the float on that path: completion has not moved, so record the float consumption in the daily report and decline the extension. Granting it shifts the contractual completion date and invites later delay-cost claims; denying a real critical-path delay without documenting it leaves the project late and disputed.
Pay Applications and Change Orders: Approving Cost Only Where It Is Supported
A pay application approves completed, compliant work, not billed quantities. Check each line against approved submittals, field verification, and executed change orders before approving, and hold unsupported amounts pending resolution.
The cost cycle runs from the schedule of values through periodic pay applications, with retainage withheld per the contract and approved change orders folded in once executed. A pay application line should represent work in place that you have verified in the field and that rests on an approved submittal. In many standard contract processes, unapproved change work follows its own approval path rather than riding inside a pay application, so change-related billing without an executed change is a flag to investigate.
Scenario: a pay application includes a full line for lighting fixtures installed last week, but that submittal was returned revise and resubmit. The tempting call is to approve the line because the work visibly exists and the subcontractor promises the resubmittal is coming. The better decision is to pay only verified, compliant work in place: hold the fixture line until the submittal is approved, re-verify the work, and note the hold in your review. Paying noncompliant work makes recovery awkward and undermines the submittal system's authority — the same interpretation you should rehearse on paper cases.
Safety Judgments on Paper: Competent Person, Qualified Person, and the Reporting Chain
A competent person can identify hazards and has authority to correct them; a qualified person has recognized expertise to design or evaluate. In scenarios, route hazards to the competent person, verify the correction, and record the event.
In general United States construction usage, a competent person is capable of identifying existing and predictable hazards and has the employer's authority to take prompt corrective measures; a qualified person holds a degree, certificate, professional standing, or extensive experience that lets them solve problems in the subject — for example, designing an engineered protective system. Inspection and correction belong to the competent person; design and evaluation belong to the qualified person. Exact definitions vary by standard, so check the one your project adopts.
Scenario: on a paper site walk you see a scaffold with a missing guardrail section and workers on the deck above. The tempting call is to tell the workers to be careful, or to direct a fix yourself. The better decision is to have the affected work stopped through the superintendent and the designated competent person, notify per the safety plan, verify the correction before work resumes, and record the observation, the notification, and the correction in the daily report. A documented hazard with no verified correction is a worse record than none; the CM's role is to make the compliance system operate, not to substitute for the designated people.
The Daily Report Drill: Turning Observations into Records That Support Decisions
Practice writing daily reports that separate observation from opinion: what happened, who was involved, what action you took, and what notice was given. Records written this way support schedule and cost interpretations months later.
Exercise: you are handed one mock day — a concrete pour held two hours by a pump breakdown, an RFI issued on a dimension conflict, a near-miss where a crane load swung close to workers, and two crews working short-staffed. Write the daily report entry for that day before reading further, then score it against the rubric. Ten minutes is enough for the first draft; the value comes from the scoring pass, not from length.
- Every entry names the event, the parties, the time, and the action taken — no conclusions inside the entry.
- Observation is separated from hearsay: what you observed versus what the foreman reported.
- RFIs, notices, and safety notifications are referenced by their identifiers and dates.
- Language stays factual; argument belongs in formal correspondence.
| Rubric item | Passing draft shows | Common draft failure |
|---|---|---|
| Event, parties, time, action | Each entry is a self-contained factual sentence | Entries state opinions like the contractor is slow |
| Observed versus reported | Source of each fact is identifiable | Secondhand claims written as direct observations |
| References | RFI and notice identifiers with dates | Mentions of paperwork with no identifiers |
| Tone | Factual language only | Argument or blame embedded in the record |
Case-Style Items: A Three-Read Method for Scenario Questions
Read each scenario in three passes: identify your role and constraints, classify the decision type (time, cost, safety, documentation, or ethics), then choose the action that follows the contract documents and is properly recorded.
First read: establish who you are in the stem and what you are authorized to act on, because that determines whether an option is even available to you. Second read: classify the decision type — time, cost, safety, documentation, or ethics — since each type has a known chain: a float check for time, verification for cost, competent-person escalation for safety. Third read: match every option against that chain and against the record it creates. This turns an open-ended story into a decision type you have already drilled.
Ethics items follow the same method with one addition: when schedule pressure and a reporting obligation collide, the compliant path usually keeps the obligation and manages the schedule consequence openly, rather than treating them as a choice. Watch for options that resolve the tension through silence — fixing something quietly, or delaying a report until a convenient moment. Silence converts a manageable issue into a professional-standards problem, and it is the one pattern that recurs across every decision type in this material.
- Right outcome, wrong process: the option reaches the correct result but skips the required document or approval step.
- Decisive but unverified: the option approves, pays, or extends before the supporting records are checked.
- Silent on the record: the action is correct but leaves no documentation or notice to protect it.
- False either/or: compliance and schedule pressure framed as alternatives when handling them in sequence covers both.
A Preparation Sequence and Readiness Checks Before You Sit the CACM
Sequence preparation by document chains, not chapters: contract documents, then schedule interpretation, then cost, then safety and ethics, then timed scenarios. Track readiness with the checks below rather than with a fixed hour count.
Divide your time proportionally: about a quarter rebuilding the document table from memory with a one-line job for each document; a quarter on schedule drills, taking three mock updates and identifying total float, the critical path, and whether completion moves; a quarter on cost and safety decision drills; and a final quarter on timed scenario sets using the three-read method, mixed with practice questions. If you have more or less time, scale the proportions rather than skipping stages.
Readiness checks: you can classify a document by what it changes in about half a minute; you can explain in one sentence why a delay within float does not move completion; a daily report entry of yours passes the four-point rubric; you can name the next step from an RFI answer to a resolved change; you can distinguish a competent person from a qualified person and say who acts. These are learning milestones, not passing predictions. For eligibility, scheduling, and current requirements, rely on CMCI at cmci.org — study summaries do not establish current versions — and browse the wider library at /study-guides.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.