Evaluating and Applying Client Written Expectations

Client Expectations and Cost Justification of Inspection

Quick Answer: CIP Level 2 inspectors work from the client’s written expectations—the scope of work, inspection and test plan (ITP) references, hold points, reporting frequency, and acceptance criteria. Cost justification of inspection means showing that the cost of inspection labor and testing is small next to the cost of coating failure, rework, and downtime. Reducing inspection without a documented risk basis shifts failure risk back to the owner.

Why Client Written Expectations Come First

At CIP Level 2 you are expected to evaluate and apply the client’s written expectations, not improvise quality criteria from personal habit. Written expectations typically appear in one or more of these documents:

• The contract or purchase order (who inspects, who pays, liability language)
• The project coating specification (systems, standards, DFT ranges, surface-prep grades)
• The inspection and test plan (ITP) or quality plan (activity sequence, hold/witness/review points)
• Owner quality procedures or bid exhibits (report forms, submittal timing, photo requirements)
• Pre-job conference minutes that amend expectations in writing

Verbal instructions from a site engineer are useful only when confirmed in writing. If a superintendent says “skip the salt test today,” you document the request, check whether the ITP or specification allows it, and escalate if it conflicts with client written expectations. Level 2 competence is knowing which document controls and when to stop and ask.

Elements You Must Extract From Written Expectations

Treat every project kickoff as a document-mining exercise. Pull and reconcile at least these items:

If two documents disagree—for example the ITP still shows NACE No. 2 / SSPC-SP 10 but the latest addendum upgraded immersion surfaces to white metal—you flag the conflict before production coating starts. Applying the wrong cleanliness grade is not “being flexible”; it is failing to apply client written expectations.

Scope of Work Nuances

Scope language is often where disputes hide. Watch for:

• Partial systems (stripe coat only; repair only above a weld; interior shell only)
• Access exclusions (undersides, bolts, crevices) that still need coating or testing
• Shop vs field split (blast and prime in shop; intermediate and finish in field)
• Third-party vs owner inspector roles and who holds stop-work authority

Your daily decisions must stay inside that scope. Expanding inspection beyond scope without owner direction burns budget; shrinking inspection below scope without written change creates liability.

Hold Points, Reporting Frequency, and Acceptance Criteria

Hold points convert expectations into hard gates: surface prep verification before primer, ambient checks before spray, DFT before next coat, holiday testing before immersion service. Reporting frequency converts expectations into a paper trail: if the owner requires a DIR by 09:00 the next calendar day, late reports are themselves a non-conformance to the inspection contract. Acceptance criteria convert expectations into numbers and visual grades you can measure—SSPC-SP grades, profile mils or microns, DFT sampling frequency, holiday detector settings, and cure checks tied to the product data sheet (PDS).

CIP Level 2 goes beyond “execute the hold points.” You evaluate whether the package of expectations is complete enough to protect the asset. Missing acceptance criteria for a critical immersion lining is a planning defect you raise at the pre-job conference, not something you invent on day three of spray.

The Live-Revision Problem

The most common way a competent inspector applies the wrong criterion is not misreading the specification — it is reading the wrong revision of it. Coating documents change during a project through addenda, approved ITP revisions, and RFI responses, and field copies drift out of date almost immediately.

A practical habit: write the revision number and date of the controlling document into the daily report header. When a dispute arises two years later, that single line establishes which criteria you were applying and why.

Extracting expectations without over-reading them

Two failure modes bracket this task. Under-reading means executing a boiled-down checklist and missing a requirement the specification actually contains. Over-reading means importing requirements from a standard the project never invoked, or from a previous job with the same owner.

Both are corrected by the same discipline: for every check you perform, be able to name the document and clause that requires it. If you cannot, either you have found a gap the project needs to close, or you have found a habit you brought from somewhere else. Raise the first; drop the second.

When the package itself is incomplete

CIP Level 2 goes beyond executing hold points to evaluating whether the expectations are complete enough to protect the asset. Missing acceptance criteria for a critical immersion lining, no defined holiday method, or a specification that says "good commercial practice" instead of a measurable limit are planning defects. Raise them at the pre-job conference, where a written clarification costs nothing — not on day three of spray, when it costs a shutdown.