Why Your O&M Manual Submittal Got Rejected — And How to Avoid a Second Rejection

If a consultant just kicked back your closeout submittal, you're not alone — and you're probably on a deadline. This page covers the most common, avoidable reasons Alberta O&M manual submittals get rejected on first pass, so the resubmission actually clears.

The Most Common Rejection Reasons

1. Unstamped or Preliminary Shop Drawings

The single most common rejection cause. Shop drawings and manufacturer documentation need the Consulting Engineer of Record's official "Approved" or "Reviewed as Noted" stamp clearly visible on the cover page. A preliminary revision (marked "Revision 0") or an unstamped package gets rejected outright, regardless of trade. Draft stamps don't count — confirm the engineer of record has issued final approval stamps before you submit, not just preliminary ones.

2. Missing ABSA Registration

Every pressure vessel, boiler, and commercial water heater requires ABSA registration on file. This is checked on every closeout audit — if it's missing, the submission stalls at that item until it's produced.

3. TAB Reports Without a Professional Wet Stamp

A Testing, Adjusting, and Balancing (TAB) report needs the Professional Engineer's wet stamp or an authenticated digital seal. Preliminary balance sheets without that seal are rejected, not just flagged.

4. Hand-Written or Modified Schedules

Panel schedules and other as-built documentation must be typed to accurately reflect final installations. Hand-written modifications on an otherwise-typed schedule are not accepted during municipal audits, even if the underlying data is correct.

5. Warranty Documentation on the Wrong Letterhead

Warranty certificates need to be on corporate letterhead, with a minimum one-year duration clearly stated. A warranty buried in an email thread or without letterhead is treated as incomplete.

6. Fire Alarm Verification Without Pass/Fail Detail

Fire alarm verification reports need individual device addresses and explicit pass/fail statuses per device — a summary "system passed" statement isn't sufficient documentation on its own.

7. Wrong Acceptance-Milestone Terminology

On Alberta Infrastructure–owned projects, using "Substantial Completion" language when the contract actually specifies Interim Acceptance / Practical Completion / Final Acceptance reads as not knowing the project's own contract structure — and can trigger a closer, more skeptical review of everything else in the package.

See our full breakdown of Section 01 78 23 requirements on the Alberta O&M Manual Requirements page.

The Pattern Behind Most Rejections

Almost every item above comes down to the same root cause: the paperwork exists, but it's in the wrong state — draft instead of final, hand-written instead of typed, unstamped instead of stamped. It's rarely that the underlying work wasn't done. It's that closeout documentation has its own, very specific compliance bar, separate from the construction work itself, and it's easy for a busy PM juggling a dozen trades to miss one item.

How to Avoid a Second Rejection

1. Audit every document against the compliance bar above before submission, not after a rejection.

2. Confirm final (not preliminary) stamps and wet seals are actually in hand before compiling.

3. Confirm which acceptance-milestone vocabulary the contract uses — don't assume.

4. Build a single tracking log of what's required vs. what's actually been received, so nothing is missing at the last minute.

That audit step is exactly what a dedicated closeout documentation partner exists to do — catching the gaps before a consultant does.

FAQ

What's the single most common reason for rejection?

Unstamped or preliminary shop drawings — missing the Consulting Engineer of Record's final "Approved" or "Reviewed as Noted" stamp.

Can I resubmit with the same errors fixed individually, or does the whole manual need re-review?

This depends on the consultant and the project, but a second rejection on the same category of error (e.g., another unstamped drawing) tends to trigger a more thorough, slower re-review of the entire package — worth getting it right the first time.

Does a typed schedule need to be regenerated from scratch if one entry was handwritten?

The specific schedule needs to be typed and reissued; it doesn't necessarily require touching unrelated sections of the manual, but check with your reviewing consultant on scope.

Who is actually responsible for catching these issues before submission — the contractor or the manual compiler?

Ultimately the Contractor is accountable for the submission, but a compiler who audits against this exact checklist before the package goes out is how first-pass approval actually gets protected.

Don't risk a second rejection.

ProSpec Manuals audits every closeout submittal against the exact compliance bar Alberta consultants check for — before it goes out, not after it comes back.