See what the OFM would bounce.
Drop in an EMREP, FIREP, COREP or INJREP file and this reads it against the 2027 specification: field counts, the header row the OFM’s own samples wrongly contain, stray commas and quotes, timestamps, exposure-fire codes, Section C on structure fires, and every code in a column that has a code table.
Your file never leaves your computer.
There is no upload. The page fetches the 2027 code tables and does the checking in your browser; the file is never sent anywhere, and nothing is stored once you close the tab. Incident records carry personal addresses — it is why the OFM’s own SIR database is restricted rather than published as open data — and a tool that posted them somewhere would not deserve to be used.
- No upload
- No account
- Nothing stored
- Nothing sent when you save the report
Drop a .TXT file here
EMREP, FIREP, COREP or INJREP. Read in your browser; nothing is uploaded.
It never says your file is correct
It reports what would bounce. It cannot tell you a file is compliant, correct or accepted, and it does not try: the Fire Marshal’s own validation is the one that decides, and our files have not been through the mandatory test cycle. A clean result here means these rules found nothing, not that the filing will pass.
Unofficial. Built from the OFM’s 2027 developer pack — Technical Requirements dated 2025-11-13. Confirm anything you are about to act on with OFMstatistics@ontario.ca.
Looking up a single code instead? The code explorer takes a 2009 code and tells you what became of it, including the ones deleted with no successor.
Found something you did not expect?
Thirty minutes, and we will go through the report with you. If the answer is that your vendor needs to fix it, we will say so.