FCICA CIM common mistakes
FCICA CIM · Understand the traps and how to avoid them.
Treating the estimate's labor hours as a fixed budget and reporting job cost against those hours without first re-validating the estimate's stated productivity assumptions and crew mix for the actual site conditions.
Candidates assume the estimate is a cost baseline that transfers unchanged to the field, so they skip the step of reconciling estimated quantities, production rates, and wage rates against the contract scope and the site-specific conditions before setting the installation budget.
What to do instead
Before the job starts, walk the estimate line by line: confirm quantities against the scope documents, confirm the production rate basis and crew composition, separate labor, material, equipment, and subcontract components, and build the field budget from the validated labor hours plus a documented adjustment for known site factors. State explicitly which estimate assumptions the field budget depends on.
Building a schedule from the contract completion date backward without identifying the predecessor activities, inspection hold points, and material lead times that actually drive the sequence.
Candidates equate scheduling with date arithmetic. They produce a bar chart of durations that looks complete but omits the logic ties, submittal and approval cycles, cure or acclimation time, and inspection windows that determine whether the dates are achievable.
What to do instead
Construct the schedule from the work sequence: list activities, tie each to its predecessor, insert submittal approval, material delivery, moisture or temperature conditioning, and inspection hold points as real activities with durations, then calculate the dates forward. Identify the critical path and name the two or three activities most likely to consume float.
Answering contract-obligation questions by describing what is customary in the trade rather than what the specific contract documents require, particularly on notice periods, direction for extra work, and time extensions.
Experienced candidates rely on habit and general practice. They miss that the contract allocates risk through specific clauses, and that a correct-sounding field action can still be a breach if it bypasses the required notice or written-direction procedure.
What to do instead
For any scenario, first identify which contract document governs (agreement, general conditions, supplementary conditions, specifications, drawings, order of precedence) and quote the mechanism it establishes: who directs work, in what form, within what time, and what happens if the step is missed. Practice stating the notice deadline and the consequence of missing it as part of every answer.
Assigning crews by headcount and availability without matching skill level, certification, and crew balance to the task, and without planning for the ramp-up and learning curve on repetitive work.
Candidates treat resource assignment as filling slots on a calendar. They overlook that a crew with the wrong mix of installers and helpers, or with uncertified personnel on a task requiring certification, produces both quality defects and lost productivity that the estimate did not anticipate.
What to do instead
Build a task-to-skill matrix: for each scheduled activity, state the required skill or certification, the crew composition and size, and the supervision ratio. Sequence assignments so the most skill-sensitive work lands on the most capable crews, and account for productivity ramp-up on repetitive tasks rather than assuming full rate from day one.
Describing site-condition management only in terms of housekeeping and safety walks, omitting environmental controls, access and staging constraints, and the documentation that protects the schedule when conditions are not as represented.
Candidates conflate on-site condition management with cleanliness and PPE. They miss that temperature, humidity, substrate condition, dust control, other-trade interference, and access restrictions are schedule and cost drivers that must be monitored and recorded contemporaneously.
What to do instead
For each scenario, name the specific condition, the standard it must meet, the measurement or observation method, the frequency of monitoring, and the record created. Treat deviations as documented events: log them with date, time, reading, and affected activity, and tie them to the notice and schedule-impact process.
Managing materials by reordering when stock looks low rather than by reconciling deliveries against the purchase order, tracking waste and breakage, and controlling storage conditions and security.
Candidates focus on the ordering transaction and neglect the receiving, storage, and consumption cycle. The result is unverified quantities, unclaimed shortages or damage, deteriorated material from improper storage, and waste that never gets charged back to the responsible party.
What to do instead
Establish a receiving routine: verify count and condition against the purchase order at delivery, record shortages and damage immediately with the carrier or supplier, store per the manufacturer's requirements, and track issued versus installed quantities so waste and loss are visible. Reconcile ordered, received, installed, and on-hand quantities at defined intervals.
Treating a change order as a pricing exercise and issuing the price before confirming scope, schedule impact, and the written authorization to proceed.
Candidates want to be responsive and quote a number quickly. They price an unclear scope, omit the time extension and the effect on other trades, and start work on a verbal instruction, which later becomes an unpaid or disputed change.
What to do instead
Process every change through a fixed sequence: identify the change and its cause, document the scope in writing, price labor, material, equipment, and subcontractor plus the appropriate markup, state the schedule impact and any time extension requested, obtain written authorization before proceeding, and record the change in the change log with its budget and schedule effect.
Comparing actual cost to budget only at the total-job level and only at month end, so that overruns in one cost code are masked by underruns in another and are discovered after the money is spent.
Candidates rely on the accounting summary rather than a cost-code-level comparison. Aggregation hides which work packages are drifting, and infrequent review removes the chance to correct course while the work is still in progress.
What to do instead
Compare budget to actual at the cost-code level on a regular cycle, and pair the comparison with earned value: quantities installed against quantities budgeted, labor hours against hours earned, and committed cost against remaining budget. Report variance with its cause and the corrective action, and forecast cost at completion rather than only reporting spend to date.
Responding to a claim by arguing entitlement in general terms without assembling the contemporaneous records that prove notice, causation, and the cost or time incurred.
Candidates believe a meritorious position speaks for itself. They answer with narrative and opinion, but claims are decided on documentation: whether notice was timely, whether records show the delay or cost was caused by the other party, and whether the amount is substantiated.
What to do instead
Build every claim answer around three elements: timely written notice as the contract requires, causation documented by dated records such as daily reports, correspondence, schedules, and photographs, and quantum supported by cost records or a schedule analysis. Where records are missing, say so and describe the mitigation or reconstruction method rather than asserting entitlement.
Treating closeout as a final walkthrough and a punch list, leaving submittals, as-built records, warranties, attic stock, final change order reconciliation, and lien waivers to be assembled after the work is finished.
Candidates see closeout as an administrative afterthought. Because these deliverables were not tracked during construction, they become a scramble at the end, delaying final payment and leaving unresolved change orders and incomplete documentation.
What to do instead
Run closeout as a tracked process from job start: maintain a closeout log for submittals, test reports, warranties, and as-builts as they are produced, update as-built records continuously, resolve and incorporate all change orders before final reconciliation, confirm attic stock and spare material per the specification, and collect final waivers and releases in the sequence the contract requires for final payment.