Prepare for the Associate Constructor (AC) credential by practicing scenario judgment, not definition recall. The exam's case-style domains reward candidates who can identify which named concept a scenario is testing - float, document type, quality role, or safety observation - and apply it step by step. Work through the two scenarios below, complete the paper-based exercise, and use the readiness checks before test day. Administrative details such as eligibility and scheduling belong to the American Institute of Constructors, the credential's issuer.
Why Definition Memorization Collapses in Case-Based Questions
Scenario questions describe situations, not terms. Knowing the definition of float does not help unless you can recognize float inside a story about a late window delivery. Preparation should therefore center on application drills tied to the credential's applied-practice and decision-making domains.
A definition-based question gives you the term and asks for its meaning, so recognition is enough. A case-based question inverts the task: you receive a construction situation and must first decide which concept governs it. This inversion is the core difficulty of the AC's scenario material, and it cannot be solved by rereading a glossary. The fix is deliberate transfer practice - after learning each term, immediately answer three or four short cases that never name the term directly.
Build this transfer habit with a two-column drill. In the left column, write the term with its definition and one distinguishing feature. In the right column, write the one-sentence cue that signals that term in a story, such as 'a delivery slips but completion dates are unchanged' for float. Then quiz yourself from the right column only: read the cue, name the term, state what decision it forces. When a cue produces the wrong term, you have found a real gap that flashcards alone would have hidden.
- Study cue-first: write the scenario signal next to every definition you learn.
- After each topic, answer at least three unlabeled mini-cases before moving on.
- When two cues feel identical, write one sentence explaining how a decision would differ under each term.
Turning a Case Narrative into Facts, Rules, and a Decision
Assessment and interpretation questions bury the relevant facts inside project detail. Before choosing an answer, separate the narrative into observed facts, stated assumptions, and the decision being requested, then match the facts to the governing rule.
Case narratives in the constructor assessment domain typically include irrelevant texture: subcontractor names, weather mentions, or background on the project's history. Train yourself to extract only three categories. Observed facts are things documented in the scenario - a delivery date, an inspection result, a written instruction. Assumptions are things a party believes or hopes without evidence. The requested decision is the specific question at the end.
Practice with any scenario you can write or find, using this three-line format. Line one: list every fact in the passage, quoting it briefly. Line two: list every assumption and mark who holds it. Line three: state the decision in one sentence, for example, 'Should the schedule be revised?' Then test each answer choice against line one only, and flag any choice that depends on an assumption rather than a fact as weaker. Repeating this on a dozen short cases builds the filtering speed the case-analysis domain rewards.
Float vs. Delay: The Scheduling Trap in Scenario Questions
A scenario may report that an activity is running late without any effect on project completion. Candidates who conflate activity delay with project delay choose unnecessary responses. Always ask whether the delayed activity sits on the critical path before deciding.
The critical path is the longest chain of dependent activities; it fixes the shortest possible project duration. Float is the amount of time a non-critical activity can slip without pushing completion. A delay inside available float is a schedule-management matter, not a project delay. Scenario questions exploit the gap between these ideas by describing a late activity in alarming terms and offering answers that treat the project end date as automatically at risk.
Worked scenario: a case states that window delivery slips three weeks, and the question asks what the constructor should do first. The tempting choice is to expedite or add crews to recover the three weeks. The better choice, if the scenario's schedule data shows four weeks of float on the window installation path, is to update the schedule and confirm the completion date is unchanged, then re-sequence to protect the remaining float. The mistake matters because expediting consumes management attention and budget to fix a problem that the schedule shows does not exist - and float, once consumed, is no longer available for a genuine critical-path problem later. In practice this depends on the actual schedule logic; the principle to carry into the exam is to check path criticality before reacting to any delay.
RFI, Change Order, or Change Directive: Picking the Right Document
Change-management scenarios test whether you select the document that matches the situation's timing and authority. An RFI asks a question, a change order agrees on scope and price, and a directive orders work before agreement. Match the document to who is acting and when.
These three instruments differ in purpose and sequence. A request for information (RFI) seeks clarification of drawings or conditions; it changes nothing by itself. A change order is the mutually agreed record that modifies scope, price, or time. A construction change directive orders work to proceed when the parties have not yet agreed on cost - appropriate when delay would be worse than proceeding on an unagreed basis. A useful way to keep these straight is to write a one-line decision rule for each document and test it against short verbal-instruction cases you write yourself, so the choice between instruments becomes a habit rather than a guess. In every case, the decision turns on two facts: has the condition been clarified, and have the parties agreed?
Worked scenario: during excavation the crew uncovers buried debris. The owner's representative says on site, 'Remove it and we will sort out the cost later.' A tempting answer is to proceed and invoice afterward, or alternatively to stop work until a price is fixed. The better decision is to document the condition with photographs and a written record, submit a written request for direction clarifying the new condition, and - if the work is time-critical - proceed only under a written directive that establishes entitlement, with a change order to follow for cost. The mistake matters because oral direction plus later invoicing leaves both scope and price undocumented, which is exactly the ambiguity the documentation chain in the methods-and-procedures domain exists to prevent.
| Document | Purpose | When It Is Used | What It Changes |
|---|---|---|---|
| RFI | Ask for clarification of drawings, specifications, or conditions | When meaning is unclear before or during work | Nothing directly; it may lead to other documents |
| Change order | Record an agreed modification | When scope, price, or time changes and both parties agree | Contract scope, cost, or schedule |
| Change directive | Order work to proceed | When work cannot wait for agreement on cost | Scope now; price settled afterward |
| Daily report | Record site conditions and progress | Every working day as routine documentation | Nothing; it provides the evidence trail |
Quality Assurance vs. Quality Control: Who Observes, Who Records
Quality assurance is the planned system that prevents defects; quality control is the inspection and testing that finds them. Scenario questions distinguish the two by asking whether an action is systemic and preventive or activity-specific and verification-based.
The distinction is easier to apply with role-based cues. Assurance answers the question 'are we set up to do this right?' - procedures, qualified personnel, approved submittals, defined inspection hold points before work proceeds. Control answers 'did this particular work come out right?' - a concrete pour checked for specified strength, an installed conduit run measured against drawings, a torque value verified. In a case question, an action taken before or during planning of the work signals assurance; an action measuring or testing completed work signals control.
This distinction connects directly to the documentation chain. A submittal approval is an assurance act: it verifies the proposed material before installation. An inspection report on that installed material is a control act. A scenario may show both and ask which step was omitted - the classic omission being control performed without the prior assurance step, such as testing material that was never approved through the submittal process. Practice by labeling every quality-related action in a case as A or C, then check whether the sequence runs assurance first and control second; when it does not, you have located the flaw the question is testing.
Safety and Ethics Scenarios: Reasoning on Paper, Not on Site
Safety and professional-standards questions describe observed conditions and ask for the constructor's response. Treat them as documentation-and-escalation problems: record the observation factually, connect it to a standard, and identify who must act next.
A hazard scenario on paper gives you observations - an unprotected edge, a blocked exit, a worker operating equipment without training noted - and answer choices ranging from ignore, to fix it yourself, to document and escalate. The reasoning pattern to build for these cases has three steps: state the observation in factual language, name the standard or duty it implicates in general terms, and identify the responsible party for correction. A useful exercise is to draft your own answer choices for a scenario and then discard any that depend on guessing about people's motives or on personal improvisation in place of the established reporting path.
Practical exercise with a self-check rubric: write a one-paragraph site scenario containing two hazards and one verbal instruction from a supervisor that conflicts with a safety rule. Then produce two deliverables - a daily report entry and a short note describing the constructor's response. Check your work against this rubric: (1) Does the report contain only observed facts, with no opinions or assumptions about why conditions arose? (2) Is each hazard paired with a specific observation rather than a vague phrase like 'unsafe area'? (3) Does the response identify who was notified and what follow-up is expected, rather than assuming the problem is resolved? (4) Is the conflicting instruction documented rather than silently obeyed or silently ignored? Aim to meet all four checks on a redrafted second attempt; if you repeatedly fail check one, your extraction habit from the case-interpretation drill needs more reps.
A Preparation Sequence You Can Adapt, Plus Readiness Checks
Sequence your study in four passes: concept coverage, scenario conversion drills, mixed case practice, and timed review of your error log. Treat self-check scores as learning milestones, not predictions, and confirm all administrative requirements directly with the issuer.
Pass one covers the core domain concepts - scheduling terms, change documents, quality roles, safety duties - using the cue-first notes described earlier. Pass two applies each concept cluster to short cases using the facts-assumptions-decision format. Pass three mixes domains in single cases, because real scenarios combine them: an unforeseen condition touches documentation, quality, safety, and schedule at once. Pass four is a timed review of your error log only, re-solving every case you answered wrong and writing one sentence on which distinction you missed. Adapt the number of days per pass to your available study window; the order, not the calendar, is what carries the learning.
Readiness checks before you sit the exam: you can name the governing concept for an unlabeled case in under a minute; you can explain the difference between float and delay with an example of your own; you can select the correct change document for three different verbal-instruction scenarios; you can draft a factual daily report entry that passes all four rubric checks. When any check fails, return to the matching section rather than re-reading the whole guide. Note that eligibility criteria, exam format, and scheduling are administrative matters published by the American Institute of Constructors at aic-builds.org, which you should consult directly for those details.
- Pass 1: concept coverage with cue-first notes for every named term.
- Pass 2: facts-assumptions-decision drills, three mini-cases per concept.
- Pass 3: mixed-domain cases, including the two worked scenarios re-solved from scratch.
- Pass 4: timed error-log review with one-sentence diagnosis per miss.
- Final: verify eligibility, format, and logistics with the issuer, not secondary sources.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.