đź“– What Is the ULC Reference Code Checker?
The ULC Reference Code Checker is an AI-powered quality assurance feature within Inspect Point's Inspection Assistant. It automatically reviews deficiencies created during ULC-certified fire alarm inspections to ensure the correct ULC code clauses are included.
When technicians document deficiencies during ULC-certified fire alarm system inspections (ULC-S536, ULC-S537, etc.), they must reference the specific code clause related to the issue. This tool uses AI to verify those references are present and appropriate, helping ensure your inspection reports meet Canadian compliance requirements.
👉 Feature Overview: AI Inspection Assistant
🎯 Why This Matters
For Field Technicians
- Catch Missing References - No more callbacks for incomplete documentation, catch missing references before reports go out
- Suggested Code References - AI recommendations help you cite the right clauses faster
- Reduce Compliance Risk - Ensure every deficiency meets ULC documentation standards
For Back Office Staff
- Streamlined Review Process - Quickly identify and address documentation gaps before final report delivery
- Batch Corrections - Mark multiple issues at once and send consolidated feedback to technicians
- Quality Consistency - Maintain uniform compliance standards across all inspections
For Company Leadership
- Regulatory Compliance - Meet Canadian fire protection inspection documentation requirements
- Customer Confidence - Deliver professionally documented reports that demonstrate technical expertise
- Reduced Liability - Complete, accurate deficiency documentation supports your work in case of disputes
⚙️ How the ULC Reference Code Checker Works
Automatic Detection - After an inspection is completed, the Inspection Assistant reviews all fire alarm–related deficiencies and looks for:
- Missing Code References – No ULC clause listed
- Incorrect Code References – Clause may not match the deficiency
AI-Powered Suggestions - When an issue is detected, the system suggests relevant ULC clauses based on:
- Specific device type (panel, detector, annunciator, etc.)
- The inspection question that generated the deficiencyÂ
- The technician's answerÂ
- Device details (location, model, manufacturer, zone)
- The applicable ULC standard (such as S536 or S537)
Review and Resolution Workflow - Back office staff review flagged issues via the Inspection Assistant tab on the Inspection Detail screen. From there, they can:
- Accept AI suggestions corrections to technicians
- Dismiss false positives if the AI incorrectly flagged a valid reference
- Add manager notes to provide context or clarification
Technicians receive the suggested corrections in the mobile app and can update deficiency references directly from the field.
Using the ULC Reference Code CheckerÂ
🖥️ For Back Office Users (Overview)
Back office teams review ULC reference code issues directly from the Inspection Assistant tab after an inspection is completed.
Inspection Assistant automatically flags deficiencies with:
- Missing ULC references (Blank Reference Code)
- Potentially incorrect references (Incorrect Reference Code)
For each issue, reviewers can quickly see the device details, the inspection question and answer, any existing reference, and AI-suggested ULC clauses with supporting context.
From the review tab, back office users can:
- Suggest corrections to technicians using AI recommendations
- Dismiss issues that were flagged incorrectly
- Add manager notes for clarification
- Take bulk action on multiple issues at once
Once reviewed, selected corrections are sent to technicians in a single submission, where they can be applied directly from the mobile app.
📱 For Technicians (Overview)
When the back office sends ULC reference code corrections, technicians receive a notification in the mobile app that Inspection Assistant has suggestions available.
Inside the inspection's IA Issues section, technicians can review each flagged deficiency, see the AI-suggested ULC code references, and read any notes from their office team.
Technicians can then select the most accurate ULC clause to update the deficiency, or dismiss the suggestion if their original entry is correct. Once a selection is made, the issue is marked as resolved.
âś… Best Practices
For Getting the Most Value
- Enable for all ULC inspections - Ensure the feature is active for tenants performing Canadian fire alarm inspections
- Review suggestions promptly - Check flagged issues before finalizing reports to customers
- Use manager notes strategically - When AI suggestions need context, add notes to help technicians understand
- Track patterns - If certain deficiency types consistently get flagged, consider additional technician training
For Quality Documentation
- Trust but verify - AI suggestions are highly accurate but always apply human judgment
- Consider device context - The same deficiency type may require different references depending on device specifics
- Document your decisions - Use manager notes when dismissing suggestions to create an audit trail
- Standardize internally - Develop team conventions for common deficiency scenarios
For Technicians
- Reference codes during inspection - Adding ULC clauses as you document deficiencies reduces back-and-forth
- Learn from suggestions - Review AI recommendations to improve your ULC knowledge
- Ask questions - If you're unsure about a suggested reference, reach out to your back office team
- Keep device details accurate - Better device information leads to more accurate AI suggestions
⚙️ Configuration & Settings
Tenant-Level Settings
The ULC Reference Code Checker is controlled by the AI Inspection Manager - Needs Correction feature flag.Â
When enabled, the system will check for:
- Missing Code References (if enabled in advanced settings)
- Incorrect Code References (if enabled in advanced settings)
Your account administrator can adjust these settings to control which types of issues the checker detects.
Advanced Options
- Skip Incorrect Validation - Only check for missing references, not incorrect ones
- Skip Missing Code References - Only check for incorrect references, not missing ones
These settings allow fine-tuning based on your team's workflow and quality standards.
👉 AI Inspection Assistant – General Settings & User Access
👉 AI Inspection Assistant - Advanced Settings
đź§ Understanding the Technology
What the AI Analyzes - The ULC Reference Code Checker processes:
- Deficiency question text and answer
- Device type and specifications
- Current ULC reference (if present)
- Applicable ULC standard (536, 537, etc.)
- Historical context from the inspection
Processing - The system processes deficiencies in batches of up to 15 at a time, ensuring:
- Fast analysis without overloading the system
- Accurate suggestions based on context
- Reliable performance across inspection sizes
Violation Types - The checker identifies three possible outcomes for each deficiency:
- Missing Clause - No ULC reference present
- Incorrect Clause - Existing reference may not be accurate
- No Violation - Reference is appropriate (not flagged)
âť“ Frequently Asked Questions
Why aren't all deficiencies checked?
The checker only reviews fire alarm–related deficiencies that require ULC clause references.
Which ULC standard does it use?
It uses the inspection's configured standard (such as ULC-S536 or ULC-S537). If none is specified, S536 is used by default.
What if multiple clauses are suggested?
More than one clause may apply. Back office staff can send one or more options, and the technician selects the most accurate one.
How accurate is the AI?
Suggestions are highly relevant, but human review is always recommended.
Do technicians see dismissed issues?
No. Only suggested corrections are sent to technicians.
How do I know the feature is active?
After Inspection Assistant runs, flagged ULC reference issues will appear in the IA panel if any are detected.
Need Help?
For training or workflow support, contact your Customer Success Manager.
For technical issues, reach out to Inspect Point Support with inspection details and screenshots.
Comments
0 comments
Article is closed for comments.