Code References link inspection deficiencies to the specific NFPA standard numbers that correspond to a type of failure. When a deficiency is recorded during an inspection, the system automatically pulls the correct code reference based on the standard and year configured for that location and displays it on the generated report.
Setting up code references involves four stages:
- Creating the code reference records
- Uploading reference data via CSV
- Assigning the standard to a custom form
- Assigning specific references to deficiency questions on that form
Before You Begin
- Code references can only be assigned to form questions that are configured to create a deficiency. No other question types will display this option.
- The standard must be assigned to the form template before code reference fields will appear on individual questions.
- You are responsible for sourcing your own NFPA reference numbers and descriptions. Due to NFPA copyright restrictions, we are unable to provide this content. If you need assistance building out the spreadsheet, contact support for a quote.
Part 1: Creating & Uploading Code References
Step 1. From the Configure Page, select Code References.
Step 2. Select Add to create a new record.
Step 3. Complete the following fields:
| Field | Required | Description | Example |
|---|---|---|---|
| Name | Yes |
The grouping name for the standard. Multiple years can share the same name. | NFPA25, NFPA72 |
| Year | Yes |
The edition year of the standard. | 2011, 2014 |
| Source | No |
The origin of the standard. For internal reference only — does not appear on reports. | National Fire Protection Agency |
| Description | No |
A brief summary of what the standard covers. For internal reference only — does not appear on reports. | Alarm and notification systems |
Step 4. Click Save.
💡 Repeat Steps 1–4 for each year you want to support. For example, if you need both the 2011 and 2014 editions, create two separate records — one for each year — using the same Name so they are grouped together.
Step 5. Open the code reference record you just created.
Step 6. Download the blank CSV template provided within the record.
Step 7. Fill in the following two columns using your NFPA standard documentation:
| Column | Description | Example |
|---|---|---|
| Number | The NFPA reference number, typically numeric values separated by periods. | 1.1.1.4 |
| Description | A description of the requirement or reason for failure. | There is rust on this valve. |
Step 8. Upload the completed CSV back into the record.
⚠️ A separate CSV must be uploaded for each code reference year (e.g., one file for 2011, a separate file for 2014).
Part 2: Assigning Code References to a Form
Step 9. Navigate to Configure > Custom Forms.
Step 10. Open the relevant form and select Edit > Template Details. (If the form does not appear in the drop down select transfer to find the form)
Step 11. Scroll down to the Code Reference field.
Step 12. Select the standard name you want this form to use (e.g., NFPA25).
Step 13. Click Save.
💡 Selecting a standard name makes all years under that name available on the form. The correct year will be pulled automatically at report generation based on the location's configured default. A form can only be assigned to one standard name at a time.
Step 14. Open the form template and locate a question that is set to create a deficiency.
Step 15. Select the question you would like to assign a code reference to, then scroll down to the Code References section beneath it.
Note: The question must be configured to create a deficiency. The Code References section will not appear on questions that do not meet this requirement.
Step 16. In the search field, type a year (e.g., 2011) to filter results, then select the appropriate reference number from the list.
Step 17. To support an additional year on the same question, repeat the search for the next year (e.g., 2014) and select the corresponding reference number.
💡 Assigning references for multiple years on each question allows one form to serve locations using different standard editions. The system will automatically apply the correct year based on each location's settings — no form switching needed.
Step 18. Repeat Steps 14–17 for every question on the form that creates a deficiency.
Step 19. Once all questions are configured, select Deploy to make the form active.
What Appears on the Report
When an inspection is processed and a deficiency has been recorded, the deficiency summary section of the report will include:
- The standard name and year used for that location.
- The reference number tied to the question that triggered the deficiency.
- The description from your uploaded CSV for that reference number.
Ongoing Maintenance
No changes are needed for day-to-day inspections after initial setup. You would only need to revisit this guide if:
- You want to add support for a new edition year of the standard.
- New deficiency questions are added to the form that need code references assigned.