·
Boreal
Loading…
Inspector context
Loading…
Auth
Triage queue
—
Loading queue…
Establishment profile
Select an establishment from the queue.
Inspector decision
Select an establishment to take action.
Active inspectors
—
—
Open critical findings
—
—
Sites overdue
—
—
Surge events · 7d
—
—
Capacity grid · areas × weeks
Completed (past) and on cadence (current). Forward scheduling becomes precise when assignment workflow lands.
Loading…
Priority queue · next 30 days
Sites ranked by cadence status and risk score. Click a row to open the site profile.
Site Area Risk Last inspection Cadence Open
Loading…
Trajectory · v2
Inspection volume vs target, critical findings trend, inspector workload distribution. Wires up after the assignment substrate lands.
Inspection details
—
ISO: —
Loading inspection items from database…
Submit inspection
All findings will be recorded with regulator provenance.
0 of 0 items checked
✓
Inspection recorded
—
Establishment
—
Site
—
Inspector
—
Inspection ID
—
Findings recorded
0
Critical
0
Major
0
Minor
0
Compliant
Risk score impact
—
→
—
Risk score recomputed from new evidence.
·
—
—
Loading mandate snapshot…
Program overview
Inspections (12 mo)
—
Submitted, all establishments
Avg compliance rate
—
Across all programs
Open critical findings
—
Requiring enforcement action
Active recalls (90 days)
—
Class I–III combined
Elevated risk · top regulatees
Loading…
Enforcement pipeline
Open cases
—
all stages
CAP overdue
—
past due date
Awaiting verification
—
CAP received
Closed (90 days)
—
all closure types
Recent enforcement actions
Loading…
Departmental performance — TBS reporting
Lineage
CFIA · Safe Food for Canadians

Program performance

Last 12 months

Average compliance
—%
Open critical findings
— unresolved
Severity mix · last 12 months
Site coverage
— % of sites inspected · 12mo
Compliance trend
18 months
Inspection volume
18 months
Compliance trend · 18 months
Finding distribution · 12 months
Recall events · severity × scale
Compliance composition by inspection domain
Establishment compliance heatmap
Audit timeline
Loading…
Triage decisions
Apply filters to load.
Evidence by source
Pick an entity to compare what each source recorded over the date range.
Pick an entity above.
—
Loading cases…
Select a case to view detail.
Regulated Entity Portal
—
—
Regulated entity view
—
Actions required
—
Open cases
—
Overdue
Your compliance posture as the regulator sees it
—
Risk score
Regulator-derived
—
Last inspection
By regulator
—
Open critical findings
Regulator-collected, last 180 days
—
My self-reports
Submitted, last 12 months
Recent regulator findings about your operations
Loading…
Submit self-inspection
Routine self-monitoring is a regulatory obligation. Submissions are validated and accepted on entry; a subset is routed for inspector verification (audit sample or risk-bearing content).
Pick a domain to attest.
No items attested yet
Compliance documents
—
Upload evidentiary artifacts. Each document is auto-assessed against the regulatory framework; results are visible to the regulator alongside their own observations.
Loading…
System-to-system integration (API)
Active
For larger entities, self-reporting via UI doesn't scale. Boreal exposes the same submission surface as a REST API. Your internal compliance system POSTs structured findings; Boreal validates against the regulatory vocabulary and returns confirmation. No spreadsheets. No PDFs. No reconciliation.
Endpoint
POST https://api.boreal.gc.ca/v1/observations
Sandbox (live):
API key
—
—
Treat this key like a password. Rotate quarterly or after any suspected exposure.
Same submission, automated
—
Recent API calls
No API submissions yet.
Architectural commitment: Submissions are validated and accepted on entry — no human-review gate. A small subset is routed for inspector verification (random audit sample, content carrying critical or major non-compliance, or statistical anomaly). Verification continues during on-site inspections; disputes are first-class. Self-reported observations carry data_source = 'self_report' in the unified observations substrate; they appear alongside regulator findings in analytics but never override regulator-collected data in risk computations. Every submission carries structured attestation with named accountability under the applicable Act. The same surface serves UI today and API tomorrow.
Past submissions
Loading…
What you need to do
Loading…
Your open cases
Loading…
Inspection history
Loading…