CAN/ULC-1001 — Integrated Systems Testing

Every interconnection. Every test. One report.

IntegriTest is the first tool purpose-built for Integrated Testing Coordinators. The C4 Integrations Matrix drives test procedures, field results, deficiencies, signatures, and a locked CAN/ULC-1001 report — without copy-pasting last year's Word doc.

Built for ITCs · Aligned to the standard

Integrations Matrix

C4 · Live

Fire alarm

Sprinkler

Elevators

Smoke ctrl

Emerg. light

Voice comm

Fire alarm

Sprinkler

Elevators

Smoke ctrl

Emerg. light

Voice comm

Interconnection Selected row

14 interconnections. Each one generates a test procedure, a field result, a deficiency record (if it fails), a signature, and a section of the final report.

Mandatory · National Building Code Required · Most provincial codes Annual · Periodic re-test in perpetuity Owned by · The building's permanent record

§ 01 · The Standard

The C4 Matrix isn't a checkbox. It's the engine.

CAN/ULC-1001 requires every interconnection between fire-protection and life-safety systems to be tested as an integrated whole. IntegriTest turns that requirement into a working data model. Every matrix row drives a test procedure, a field result, a deficiency, a signature, and a section of the final report.

Step 01 · C3-C4

Enumerate every system, every interconnection.

Pick from a standards-aware catalog or add custom systems. Phased occupancy, multiple instances of the same system type, fully custom integrations — all first-class.

Step 02 · C5

Auto-generate test procedures.

Every matrix row becomes a TP-NNN procedure with normal-mode steps, fire/off-normal steps, and the expected result. Edit, override, or add manual procedures — the numbering stays stable.

Step 03 · C10

Execute in the field. Record what happened.

Pass, fail, or blocked. Timestamps, participants, observed conditions, return to normal. A failed procedure opens a deficiency. A corrected deficiency schedules a re-test. Nothing falls through.

§ 02 · Workflow

From matrix to signed report, one continuous thread.

A report is an envelope. Inside it, revisions move through a defined lifecycle: plan, execute, resolve, sign, lock. The next Annual Periodic Test branches the locked revision — the plan carries forward, the results start fresh.

01 · Plan

Setup wizard

Building, contacts, systems, matrix, procedures, notifications, safety, phasing, pre-docs.
02 · Generate

Procedures (C5)

Every matrix row becomes a TP-NNN procedure with stable IDs. Edit, override, or write manually.
03 · Execute

Field testing (C10)

Pass / fail / blocked. Observed normal & fire conditions. Participants. Return to normal.
04 · Resolve

Deficiencies & re-tests

Open → corrected → verified → closed. Severity, responsible party, re-test tied to the procedure.
05 · Sign

Lock the revision

Annex-C outline assembled from records. Coordinator & owner sign. The revision becomes immutable.
06 · Repeat

Annual Periodic Test

Branch from the locked revision. The plan carries forward. Results & signatures start fresh.

The integrated systems test report shall form part of the building's permanent record and shall be made available to the Authority Having Jurisdiction.

— CAN/ULC-1001, summarized intent

§ 03 · Coverage

Every section the standard asks for. None of the copy-paste.

IntegriTest is structured around the actual clauses of CAN/ULC-1001. Wizard steps map to report sections. Sections validate against record completeness. The exported report mirrors the standard's expected outline.

§ C3 · Building & systems

Building description and systems inventory.

Address, occupancy, phased occupancy flag, height, area. System inventory with type, instance, and clause reference.

§ C4 · Integrations Matrix

Every interconnection, enumerated and editable.

The product engine. Add, edit, remove rows. Each row references the source system, the affected system, and the integration purpose.

§ C5 · Test procedures

Auto-generated, stably numbered, editable.

TP-001, TP-002, … with normal-mode steps, off-normal steps, expected results. Manual procedures supported. Deletion cascades to test results.

§ C6 · Notifications

Participant and occupant notification on record.

Notification methods, distribution list as a structured contact table, lead time, special conditions.

§ C7 · Personnel safety

Hazards, PPE, lockout/tagout, emergency stop.

Special hazards, evacuation route, emergency stop authority. Required acknowledgements before field testing begins.

§ C8 · Phased occupancy

Conditional section, surfaced only when needed.

When the building's phased-occupancy flag is set, the wizard surfaces phase-by-phase planning automatically.

§ C9 · Pre-test docs

Checklist generated from system inventory.

System-type-aware pre-test documentation: commissioning reports, design drawings, manufacturer cut sheets, prior verifications.

§ C10 · Field testing

Pass · Fail · Blocked. Every outcome captured.

Observed conditions, participants, timestamps, return-to-normal confirmation. Failures auto-create deficiencies.

§ C11 · Revisions

Lock, branch, repeat.

Locked revisions are immutable. Branching preserves the plan, clears the results, increments the revision number, and starts the next periodic test.

§ 04 · For Whom

Made for the people who actually write the report.

IntegriTest is designed first for the Integrated Testing Coordinator — the fire-protection engineer or specialty consultant who plans, coordinates, and signs off the integrated test. Owners, contractors, and AHJs sit alongside.

Primary

ITCs

Fire-protection engineers, electrical engineers, specialty consultants. Plan the testing program, coordinate the trades, sign the report.

— Owns the workflow

Stakeholder

Building owners

Receive the locked report as part of the building's permanent record. Persistent access across annual periodic tests, regardless of which ITC is engaged.

— Owns the record

Stakeholder

General contractors

On new construction, arrange the ITC and coordinate the trades involved in field testing. Track readiness against scheduled occupancy.

— Owns the schedule

Reviewer

AHJ & Fire Dept.

Read-only access to locked revisions to verify occupancy compliance. The complete Annex-C report, with no ability to modify the record.

— Verifies compliance

§ 05 · FAQ

Questions worth asking.

Short answers to what professionals ask first when they evaluate the tool.

What is CAN/ULC-1001?

The Canadian national standard for Integrated Systems Testing of Fire Protection and Life Safety Systems. The standard requires every interconnection between fire-protection-related systems to be tested as an integrated whole and documented in a formal report. Referenced by the National Building Code, National Fire Code, and most provincial codes — including the Ontario Building Code's occupancy permit requirements for new construction.

Who needs to produce an integrated systems test report?

Most new commercial construction in Canada requires a CAN/ULC-1001 integrated systems test report for occupancy. Existing buildings with fire-protection or life-safety system modifications also require one. The report is typically commissioned by the building owner or general contractor and produced by an Integrated Testing Coordinator — a fire-protection engineer, electrical engineer, or specialty consultant.

How is this different from a fire alarm verification report?

A fire alarm verification (per CAN/ULC S537) confirms a single system works. A CAN/ULC-1001 integrated systems test confirms that all fire-protection and life-safety systems work together as a coordinated whole — fire alarm triggering elevator recall triggering smoke control triggering voice communication, with every interconnection enumerated, tested, and signed off.

Does IntegriTest produce the final signed PDF?

Yes. IntegriTest assembles the Annex-C-style report from your live records, validates completeness against the standard's required sections, and produces a signed, locked PDF for the building owner, AHJ, and Fire Department.

Does it handle Annual Periodic Tests?

Yes. When a revision is locked, you branch a new revision for the next periodic test. The plan — systems, integrations, procedures — carries forward; test results, deficiencies, and signatures start fresh. Every revision is preserved as part of the building's permanent record, as the standard requires.

Can the AHJ or Fire Department review the report?

Locked revisions can be shared with the Authority Having Jurisdiction and Fire Department as read-only links. Reviewers see the complete Annex-C report — building description, integrations matrix, procedures, test outcomes, deficiencies, signatures — without any ability to edit or change the record.

Is my data isolated from other firms using the platform?

Yes. Every record is scoped to a company tenant and isolated server-side. Cross-tenant access is impossible by design. Read more about our tenant isolation model in the documentation once you sign in.