Supporting Job Specifications

Supporting Job Specifications

Quick Answer: Supporting job specifications means interpreting the coating specification and related documents accurately, applying the spec hierarchy, and resolving conflicts with a formal RFI (or equivalent). CIP Level 2 inspectors do not rewrite the owner’s specification in the field. When the project spec and the PDS disagree, stop and get written direction—do not “average” the numbers.

What “Support Job Specifications” Means at Level 2

Blueprint task language—“support job specifications”—is broader than “read the DFT table.” It includes:

• Locating the controlling clauses for surface prep, application, inspection, and repair
• Translating those clauses into field checks that fit the ITP
• Recognizing conflicts between documents before they become coating defects
• Communicating gaps to the people who do have authority to change the spec
• Documenting work against the actual acceptance criteria, not tribal knowledge

Level 1 often receives a boiled-down checklist. Level 2 is expected to go back to the source specification when the checklist is incomplete, ambiguous, or outdated after an addendum.

The Specification Hierarchy

Projects stack documents. Unless the contract reorders them, use this working hierarchy:

How to Apply the Hierarchy

• If the project specification requires SSPC-SP 10 and 8–12 mils DFT for a system, that governs even if a salesperson prefers a different prep.
• If the project specification says “apply per manufacturer’s PDS,” then the PDS supplies the detailed application limits—but still inside any hard limits the project specification set.
• If the project specification is silent on test method and simply names “adhesion testing,” the referenced standard (for example ASTM D4541) supplies the method once identified in the ITP or by RFI.
• The SDS never authorizes thinner coating thickness “because the product is hazardous” or waives holiday testing. SDS supports safe work practices under OSHA or local rules; it is not a performance specification.

Always check the contract’s order-of-precedence clause. Some owners place “drawings over specs” or list addenda as controlling over base specifications. Level 2 competence includes reading that clause before arguing hierarchy from memory.

Interpreting Coating Specifications

When you open a coating specification, extract a structured briefing:

1. Systems schedule — primer/intermediate/finish identities, generic types, DFT per coat and total
2. Surface preparation — cleanliness standard, profile, salt limits, concrete ICRI CSP or equivalent
3. Application constraints — ambient limits, stripe coats, spray methods allowed/forbidden
4. Inspection and testing — PA 2 or other DFT rules, holiday method/voltage, adhesion, cure tests
5. Repair — how to treat defects, overlapping, feathering, reblast thresholds
6. Documentation — reports, hold points, submittals (ITP, product data, applicator quals)

Mark every “shall,” numeric limit, and referenced standard. Vague phrases such as “good commercial practice” are red flags: either the ITP will need owner-agreed criteria, or you will need an RFI to make the requirement testable.

Shop vs Field Language

Specifications often split requirements by location. A beam may be blasted and primed in the shop to one DFT, then field-coated after erection. Supporting the job specification means applying the correct section to the correct location and not using shop criteria for field touch-up (or the reverse). Track batch numbers and surface condition of shop primer at arrival—many specs require assessment of damaged shop primer before field coats.

Conflicts Between Specification and PDS

Common conflict patterns:

Wrong approaches:

• Silently following the PDS because “the manufacturer knows the product”
• Silently following the looser document to help the contractor’s schedule
• Averaging the two DFT ranges
• Writing a new DFT range on the daily report as if you were the engineer of record

Correct approach: treat the conflict as a stop-and-clarify item before the affected work proceeds past a hold point.

The RFI Process

A request for information (RFI) (names vary: technical query, clarification request, CQ) is the formal written path to resolve ambiguity. A good coatings RFI includes:

• Project identifiers and specification section/clause numbers
• Exact quote of the conflicting PDS statement (with revision/date)
• Why the conflict matters now (upcoming hold point, area ID)
• Clear question options when helpful (“Confirm whether DFT shall be 10–14 mils per Spec §5.2 or 6–8 mils per PDS Rev C”)
• Your recommended option only if invited—and labeled as a recommendation, not a decision

Route the RFI through the contract chain (typically contractor → engineer/owner). The inspector may draft technical content for the contractor or owner’s representative but should not bypass the chain unless the contract assigns that path. Keep RFI numbers on the DIR when work is waiting. When the answer returns, update the ITP or field briefing so Level 1 inspectors apply the clarified criteria consistently.

When Work Is in Progress

If conflict appears mid-coat, protect the asset:

1. Do not approve the next hold point if acceptance criteria are undefined or dual.
2. Document actual measurements taken so far.
3. Escalate promptly—delay costs less than a full rework of an immersion lining.
4. Apply only the written RFI response going forward; attach it to the quality file.

Authority Limits: Do Not Rewrite Owner Specs

CIP Level 2 inspectors support specifications; they do not own them. You lack authority to:

• Delete holiday testing to recover schedule
• Downgrade SP 5 to SP 6 because blast media is scarce
• Accept DFT outside the specified range “as a variance” without owner disposition
• Substitute a different product system because the specified product is on backorder

You do have professional responsibility to:

• Report that the specified product is unavailable or the specified test is impossible under current access
• Propose practical options (alternate product, temporary protection, phased testing) as recommendations
• Record non-conformances against the correct clause when work proceeds out of compliance
• Refuse to falsify records that claim compliance with a criterion that was not met

Owner or engineer disposition (use-as-is, repair, rework, reject) is a design/commercial decision. Your job is accurate evidence and clear reference to the job specification.

Standards Invoked by the Specification

Project specs incorporate standards by reference. Supporting the job specification includes opening those standards for the clauses that matter:

• Cleanliness and visual standards for the specified SP/ISO grade
• SSPC-PA 2 (or stated alternative) for DFT frequency and conformity
• Holiday detection practices named by the spec (method and voltage basis)
• Concrete surface prep standards when concrete is in scope

If the specification cites a withdrawn or superseded standard number, raise an RFI rather than silently substituting the newest AMPP designation—even when you know the technical equivalent. Document control is part of supporting the specification.

Field Communication Pattern

Effective Level 2 support sounds like this:

• “Spec Section 5.2 requires 10–14 mils total DFT and invokes SSPC-PA 2. Today’s area average is 8.1 mils with two gauge readings below the absolute minimum. This is an NCR to §5.2; recommended disposition is recoat after surface prep per §7.”
• Not: “I think we should put more paint on it.”

Cite the document hierarchy, measure against it, and leave authority where the contract placed it. That is how CIP Level 2 supports job specifications without overstepping into engineering of record.