CAN/ULC 1001 FocusedField + Report WorkflowWorking Browser MVP

The S1001 operating system generic Cx software cannot be.

Model the interconnections. Generate the procedures. Run integrated tests. Capture photos and video. Create deficiencies directly from failed responses. Retest without losing history. Generate the final technical report. Then keep the building record alive for periodic testing and modifications.

InitialPeriodicRetro-integratedModificationsCause & effectReports
INITIAL INTEGRATED SYSTEMS TESTING181 Queen Street — Life Safety Integration
INTEGRATIONS84
PROCEDURES61
OPEN ISSUES7
EVIDENCE238
Cause & Effect
Detector
→
FACP
→
BAS
→
AHU-4
Readiness
Test Completion by System
GUIDED TEST • TP-041 • STEP 4/8
Level 4 East Corridor

Verify AHU-4 shutdown

Activate SD-401. Confirm FACP annunciation, BAS alarm state, AHU-4 OFF and SD-4A CLOSED.
PASS
FAIL
EVIDENCE
N/A
Technical foundation

Treat every interconnection as a first-class engineering object.

The active CAN/ULC-1001-2026A Edition 2 scope covers integrated-testing qualifications, process, requirements, documentation, periodic integrated testing, retro-integrated testing and testing for modifications. SafeVerify’s data model is built around that lifecycle rather than around generic checklists.

Core data model

Integration-first architecture

BUILDING
 ├─ SYSTEMS
 │   ├─ Fire Alarm
 │   ├─ BAS / Controls
 │   ├─ HVAC
 │   ├─ Smoke Control
 │   ├─ Elevator
 │   └─ Emergency Power
 │
 └─ INTEGRATION INT-041
     ├─ Initiating event
     ├─ Originating system
     ├─ Interface path
     ├─ Receiving system(s)
     ├─ Expected response(s)
     ├─ Acceptance criteria
     ├─ Source drawing / sequence
     ├─ Test procedure
     ├─ Evidence set
     ├─ Failed-response deficiencies
     ├─ Retest lineage
     └─ Final report record
Lifecycle

Initial → periodic → modifications

Initial Integrated TestingBuild the first digital integration record and verify project-specific interconnections.
Periodic Integrated TestingReuse the building record, preserve history and execute the next cycle.
Retro-Integrated TestingCreate the structured record for an existing building with incomplete legacy documentation.
Modification TestingIdentify integrations and procedures potentially affected by system changes.
⌁Cause-and-effect graph across systems and devices.
↻Original failures stay immutable while retests accumulate.
🏢The project becomes part of a permanent building history.
Product depth

Everything an ITC needs. Nothing generic for the sake of being generic.

▦

Integration Matrix

Trigger → interface → receiving system → expected response → acceptance criteria.

  • Multi-response integrations
  • Source drawings / sequence references
  • Status and coverage filters
⌁

Animated Cause & Effect

Visualize live system relationships across fire alarm, BAS, HVAC, smoke control, elevators and doors.

  • Interactive SVG graph
  • System-state coloring
  • Click through to tests/issues
◫

Template Library

Start with original editable S1001 workflows instead of a blank spreadsheet.

  • AHU shutdown
  • Elevator recall
  • Waterflow / door release / smoke control
◉

Guided Test Runner

A field interface simple enough for trades and detailed enough for the ITC.

  • PASS / FAIL / BLOCKED / N/A
  • Photo / video evidence
  • Restoration verification
⚠

Deficiency + Retest Lineage

One click from failed response to issue, correction and retest history.

  • Responsibility
  • Corrective action
  • Immutable first failure
▱

Interactive Drawings

Upload a floor plan, place test/device pins and preserve spatial context.

  • Clickable pin board
  • Location labels
  • Drawing-linked testing
📷

Evidence Vault

Keep photos and videos tied to the exact project, test and step.

  • IndexedDB browser storage
  • Image/video preview
  • Evidence metadata
◎

Readiness Center

Know which disciplines are ready before test day and what may block the plan.

  • Trade readiness
  • Blocker flags
  • Readiness score
▤

Report Studio

Generate the closeout document from live project data instead of rebuilding it.

  • Matrix + procedures
  • Results + deficiencies + retests
  • Print / Save PDF
✦

Modification Impact

Search a changed asset/system and identify stored integrations and tests that may be affected.

  • Keyword matching
  • Linked test list
  • Review workflow
🏢

Building Record

Carry project history into future periodic testing and modification work.

  • Cycle timeline
  • Clone as periodic test
  • Historical integration record
🔒

Enterprise Roadmap

Structure the product so firm-wide templates, SSO, audit logs and Canadian hosting remain possible.

  • Multi-tenant architecture
  • Role permissions
  • Immutable report revisions
Competitive benchmark

Match modern Cx fundamentals. Go much deeper on S1001.

CxAlloy currently offers asset tracking, dynamic checklists, customizable test sheets/templates, issue tracking, automated reports, file storage, offline mobile and photos. SafeVerify should meet that usability bar while making integrated-system relationships the center of the product.

CapabilityModern Cx benchmarkSafeVerify 1001 target
Assets / equipmentCore capabilitySystems + devices directly linked to integrations
Tests / templatesCore capabilityProcedures generated from integration objects
Issue trackingCore capabilityFailed-response deficiencies with retest lineage
Offline field workCxAlloy supports offline mobileOffline-first guided integrated testing target
Photos / filesCore capabilityEvidence tied to exact test step / integration
Automated reportsCore capabilityPurpose-built integrated testing report assembly
Cause-and-effectTypically indirectFirst-class data model + visual graph
Periodic / retro / modification lifecycleGeneric project workflowsDedicated building-history workflows
One connected workflow

The report is not the product. The entire testing record is the product.

01Create Building

Owner, project type, ITC, dates and building identity.

02Register Systems

Systems, devices, equipment, trades and locations.

03Build Integrations

Triggers, interfaces, responses, sources and criteria.

04Generate Tests

Turn accepted integrations into executable procedures.

05Run Test Day

Field execution, evidence and live outcome capture.

06Correct / Retest

Preserve failure lineage and record each retest.

07Issue Report

Generate closeout and keep the building record alive.

Free browser MVP

Create an account and actually use the workflow.

The prototype below is not a dead landing page. Accounts, projects, integrations, test results, deficiencies, readiness and report data are saved locally in your browser. Evidence files use IndexedDB so small photos/videos can persist locally as well.

Account + loginProjectsTestsEvidenceReports

New S1001 Project

Add System / Asset

Add Integration

New Test Procedure

New Deficiency

Saved