ARE 5.0: CE common mistakes
ARE 5.0: CE · Understand the traps and how to avoid them.
Builds the schedule of values by copying the cost estimate line-for-line and front-loads mobilization without tying each line to measurable installed work.
Candidates treat the SOV as a budgeting exercise and never reconcile it to the contract sum or to the G703 continuation sheet, so progress payments drift from actual installed quantities.
What to do instead
Build a sample SOV for a small project, reconcile every line to the contract sum, and practice reporting percent complete by installed quantity rather than by cost spent.
Submits a baseline schedule that omits submittal review durations and long-lead procurement activities, so the first shop drawing review consumes unplanned float.
Candidates focus on construction activities and forget that the architect's review time and fabrication lead times are schedule activities with logical ties.
What to do instead
Create a submittal register from the specifications, assign contract review durations to each submittal, and add procurement and fabrication activities with ties to installation.
Describes site visits as 'supervision' or 'inspection' and writes that the work 'complies with the contract documents' in the field report.
Everyday construction language conflates the architect's observation duty with construction means and methods, which the architect does not control.
What to do instead
Memorize the A201 observation standard: the architect visits to observe progress and quality, not to supervise. Rewrite practice reports using 'observed,' 'appeared to be,' and specific exceptions.
Writes field reports as conclusions ('contractor was slow,' 'work looked bad') without date, time, weather, crew counts, equipment, or locations.
Candidates narrate impressions rather than record facts that could support a later rejection, claim, or time extension.
What to do instead
Use a required-field template (date, time, weather, temperature, crew, equipment, area, activity) and practice converting each opinion into an observable fact plus a photo reference.
Certifies a pay application by checking only the G702 total and ignoring the G703 percent-complete, retainage, stored materials, and prior payments.
The G702 is one page and feels like the whole application, while the continuation sheet is where arithmetic and scope errors hide.
What to do instead
Work a full G702/G703 example with retainage, stored materials, and a prior payment; prove the arithmetic ties before signing the certification.
Answers an RFI by telling the contractor to 'proceed' with a changed detail without issuing an ASI, construction change directive, or change order.
Candidates want to keep the job moving and do not connect the answer to the contract mechanism that authorizes cost or time.
What to do instead
Build a decision matrix for RFI, ASI, construction change directive, change order, and field order by initiator, cost authority, time authority, and documentation; practice classifying scenarios.
Returns submittals stamped 'approved' when the item contains a substitution or a deviation from the specifications.
Review is treated as a completeness check rather than a compliance check against the specified product and performance criteria.
What to do instead
Practice with submittal action stamps (approved, approved as noted, revise and resubmit, rejected) and compare each submittal line to the specification section, flagging substitutions for formal action.
Ignores contract time: does not distinguish calendar days from working days, misses notice deadlines for time extensions, and fails to connect schedule updates to liquidated damages.
The schedule is viewed as the contractor's document, so time-related contract provisions are never tracked by the architect.
What to do instead
Practice computing contract time from a sample schedule, apply the notice and extension provisions of the general conditions, and review schedule updates for logic and delay events.
Issues a certificate of substantial completion before the punch list is complete, warranties are assembled, and the owner's occupancy and insurance transition are coordinated.
Substantial completion is treated as 'the job is done' rather than a contractual milestone with specific legal and financial consequences.
What to do instead
Use a substantial completion checklist: punch list issued, cost of completion stated, warranty start date, owner occupancy, insurance and utilities transfer, and certificate language.
Processes final payment before collecting final unconditional lien waivers, consent of surety, record drawings, warranties, and attic stock.
Closeout is treated as paperwork after the fact instead of a gate that must precede release of retainage and final payment.
What to do instead
Sequence a closeout matrix: substantial completion, punch list, record documents, warranties and attic stock, final inspection, final lien waivers and consent of surety, then final payment.