Purpose Statement

The Configurable Language feature allows administrators to configure Fire Inspection forms in English, French, Spanish, or a combination of two languages within First Due.

This functionality enables departments to generate inspection reports with localized table headers, response values, signature labels, and violation labels. It supports agencies serving multilingual communities and helps meet documentation requirements without creating separate inspection types for each language.

Administrators can configure language-specific response values, select languages within Form Builder, and designate default forms for inspection types.

Background Information

First Due supports configurable language options for Fire Inspection reports through Form Builder and Inspection Setup.

Previously, fixed components of inspection reports displayed in English, even when checklist items, remarks, and violation codes were authored in another language.

With configurable language support, departments can:

• Configure inspection reports in English, French, or Spanish.

• Select up to two languages on a single inspection form.

• Display fixed report labels in both selected languages, separated by a slash (/).

• Create language-specific display values for standard inspection responses.

• Assign a default inspection form to an inspection type.

• Allow inspectors to select an alternate associated form before completing an inspection, when permitted.

• Generate reports using the language configuration of the form active when the inspection was completed.

Important: First Due does not automatically translate checklist items, remarks, or violation codes. Departments must manually author this content in the appropriate language or languages.

The following report components support localized labels:

• Permit table

• Invoice table

• Fire Inspection Results – Checklist table

• Service To table

• Addendum table

• Signature block

• Ad hoc violations label

Standard inspection response values can also be configured for French and Spanish while preserving their underlying system behavior.

Required Permissions

The following permissions are required based on the action being performed.

Note: No additional permissions are introduced specifically for multilingual inspection configuration. Access is controlled through existing First Due permissions.

Video

Step-by-Step Guide

Step 1: Access Standard Inspection Responses

1. Navigate to Inspection Setup.

2. Select Standard Inspection Response.

3. Review the existing English response values.

4. The English configuration serves as the default baseline for inspection response values.

Step 2: Create a Language Set

1. Select French or Spanish.

2. Enter the appropriate Custom and Plural display text for each of the seven standard response values:

• Pass

• Fail

• Citation

• Corrected

• N/A

• Resolved

• Empty

3. Select Save to create the Language Set.

Important: Language Sets modify how response values are displayed. They do not change the underlying system values used for violation tracking, reinspections, or other inspection functionality.

If a translated response field is left blank, the system uses the English value when rendering the report.

Step 3: Access Fire Inspection Form Builder

1. Navigate to Form Builder.

2. Open an existing unpublished Inspection Report template or create a new form.

3. Locate the Language selector beside Template Category.

Step 4: Configure the Form Language

1. Select the Language dropdown.

2. Choose the language or languages that should appear on the inspection report.

Available languages include:

• English

• French

• Spanish

  

3. Select one language for a single-language report or two languages for a bilingual report.

4. First Due automatically populates supported fixed report components with the corresponding localized labels.

5. When two languages are selected, fixed-component labels display both languages separated by a slash (/).

For example, an English/French form displays the English and French versions of supported report labels together.

Important: A maximum of two languages can be selected per form.

Step 5: Publish the Inspection Form

1. Review the selected language configuration.

2. Select Save.

3. The selected language configuration is saved with the published form.

Important: Once a form is published, its language selection cannot be modified. To change the selected language or language combination, create a new form.

Step 6: Associate Forms with an Inspection Type

1. Navigate to the appropriate Inspection Type configuration.

2. Configure Inspection Checklist Content

•  Add or edit the inspection checklist items.

  

• Enter checklist descriptions in the appropriate language or languages.
• Configure applicable code associations and standard remarks.
• Verify that the checklist content matches the intended report language configuration.
• For bilingual forms, manually include both languages wherever bilingual checklist content is required.

Selecting two languages automatically localizes supported fixed report labels only. It does not translate checklist questions, code descriptions, or remarks.

3. Open the Forms tab.

3. Associate the applicable inspection forms with the inspection type.

4. Review the available forms, which may include English, French, Spanish, or bilingual versions.

5. Designate the appropriate form as the Default Form.

6. Select Save.

The default form is automatically used when an inspection begins unless an inspector selects another associated form through the existing manual override functionality.

Step 7: Enable Manual Form Selection (Optional)

1. Open the applicable Inspection Type configuration.

2. Locate the setting Allow Inspectors to manually select a different form in the field when completing the inspection.

3. Enable the setting if inspectors should be able to select between associated inspection forms.

4. Save the inspection type configuration.

When enabled, inspectors can select an alternate associated form before completing the inspection.

This is useful for departments conducting inspections in multiple languages throughout the day.

Step 8: Select the Appropriate Form During an Inspection

1. Navigate to My Inspections.

2. Open the applicable inspection.

3. Complete the inspection checklist using the assigned form.

4. Before completing the inspection, open the Inspection Report tab.

5. Review the currently active inspection form.

6. If manual form selection is enabled, select the appropriate associated form for the desired report language.

7. Complete the inspection.

Important: The form active at the moment of inspection completion is saved to the inspection and determines the language configuration used for report generation.

Once the inspection is completed, the form selection is locked.

Step 9: Email the Inspection Report

1. Select Email using the existing inspection report functionality.

2. First Due renders the report using the language configuration of the form saved at inspection completion.

3. Review the generated report to verify the expected language presentation.

For bilingual forms, supported fixed report labels display both configured languages separated by a slash (/).

Important: There is no separate language or form selection when generating or emailing a completed inspection report. To control the report language, the appropriate form must be selected before completing the inspection.

Best Practices

- Create Language Sets before configuring multilingual forms. Ensure French or Spanish response values are available before publishing forms that use those languages.

- Use descriptive form names. Include the language or language combination in the form name to help administrators and inspectors distinguish between available forms.

- Verify bilingual content before publishing. Confirm that checklist items, remarks, and applicable codes include the required languages.

- Configure the correct default form. Select the language most frequently used by the department as the default inspection form.

- Enable manual form selection when appropriate. Departments serving multiple language populations can allow inspectors to choose the appropriate form before inspection completion.

- Review language selection carefully before publishing. Published forms cannot have their language configuration changed.

- Maintain consistent response terminology. Ensure translated response values accurately reflect their intended meanings without changing the underlying system behavior.

- Test generated reports. Verify localized labels, special characters, and report formatting before using multilingual reports in production workflows.

- Avoid relying on automatic translation. First Due only localizes supported fixed components and configured response values. All other translated content must be authored by the department.

Troubleshooting & FAQs

Why are my inspection report headers still displaying in English?

Verify that the form active when the inspection was completed was configured for French, Spanish, or bilingual output. Reports use the language configuration of the form saved at completion, regardless of the language used in checklist content.

Can I change the language of a published inspection form?

No. Once a form is published, its language configuration is locked. Create a new form to use a different language or language combination.

Can I configure more than two languages on a single form?

No. Each form supports a maximum of two languages. Available languages are English, French, and Spanish.

Does First Due automatically translate checklist questions and remarks?

No. First Due automatically localizes supported fixed report components. Checklist questions, remarks, and violation code content must be manually authored in the appropriate languages.

Can inspectors choose the report language when generating or emailing a completed inspection?

No. The language is determined by the form active when the inspection was completed. Inspectors must select the appropriate associated form before completion when manual form selection is enabled.

Why are some response values displaying in English on a French or Spanish report?

Review the corresponding Language Set under Inspection Setup > Standard Inspection Response. If a translated Custom or Plural field is blank, First Due uses the English value.

Will changing a Language Set update previously generated reports?

No. Changes to a Language Set apply to future report rendering for forms that reference it. Previously generated reports remain unchanged.

Can I use different forms for different languages within the same inspection type?

Yes. An inspection type can have multiple associated forms, including forms configured for different languages. Administrators can designate a default form, and inspectors can select an alternate associated form when the manual override setting is enabled.

Will bilingual report labels automatically make the entire inspection report bilingual?

No. Only supported fixed components and configured response values are localized by the system. Checklist items, codes, and remarks must be authored in both languages for those portions of the report to be bilingual.

What happens if checklist content is in French but the selected form is configured for English?

The generated report displays the fixed components in English while preserving the French checklist content captured during the inspection. This is expected behavior because the fixed-component language is determined by the form saved at completion.

Will multilingual configuration affect existing inspection forms or historical reports?

No. Existing forms default to English, and historical inspections retain their previously saved form versions. No content migration is required.