Optional module · Compliance Engine

From the inspection report to the next clear action.

Give your authority a connected place to receive reports, review evidence and follow unresolved issues. Providers prepare their submissions. Property owners see the records and actions assigned to them.

Private records. Defined roles. A traceable review process.

Compliance Engine

Keep the next step visible.

  1. Identify the premises & system

    Department scope · provider · recorded requirements

  2. Review the submitted evidence

    Assignment · review decision · retained revision

  3. Follow through on the finding

    Responsible person · repair evidence · case history

Evidence stays connected.Decisions stay with people.
Workflow illustration · review decisions and reported outcomes stay distinct

Know where the work stands

The report is the beginning of the follow-through.

Move between a premises, its protected systems, submitted reports and the findings that need attention. Give each review decision and repair response its own record.

Organize the jurisdiction

Maintain premises, systems, exact locations and department scopes. Review imported records before promotion.

Review the evidence

Accept, return or reject a submitted report without confusing that decision with its inspection outcome.

Track the unresolved work

Assign deficiencies, record repair evidence and retain the history when a case closes or reopens.

Systems and equipment

A reporting structure that fits the system.

Keep sprinkler, alarm, pump, suppression and extinguisher records organized alongside other configured fire and life-safety categories. Separate catalogs support backflow, elevators and mobile-unit records.

  • Authority-adopted question banks for inspection, testing and maintenance.
  • Yes / No / N/A choices where defined, plus measurements, dates and evidence notes.
  • The selected question-bank version stays with the submitted report.

Starter banks require professional review and local adoption. They are original record prompts, not licensed code text, a complete inspection procedure or an automatic pass/fail decision.

More than a report inbox

Keep the surrounding responsibilities visible.

Bring impairment records, daily fire-watch logs, notices and responder pre-plans into the same scoped workspace. Each workflow preserves the responsible person and the evidence behind a change.

  • Fire-watch logs retain reviewed revisions and missing-day visibility.
  • Notices have draft, approval and recorded-delivery stages; approval alone does not send.
  • Published pre-plans retain their reviewed source-report references.
  • Mobile units retain identity and location history while earlier reports keep their access boundaries.

Assisted intake, with accountable handoffs

Keep the source. Review the entry. Let the provider submit.

Retain the source PDF, assign an authorized team member to enter structured data and work through a requirements checklist. The named provider reviews the current version before the billable filing step.

  • Source files, assignments and the intake timeline remain traceable.
  • Preview groups of records, invitations and notice approvals before choosing what to approve.
  • Your authorized team performs the intake; review ownership stays visible.

Clear program ownership

Your authority defines the program.

Adopt question-bank versions, record applicable code references and set reporting policies for your jurisdiction. Keep authority inspections and specifically eligible owner reports distinct from provider submissions.

Explore the authority workflow

Good questions

A few things worth knowing.

What happens when I sign up?

Create your account, confirm your email and request the modules that fit your role. Your request is reviewed before workspace access is granted. Signing up does not unlock an existing department, customer, provider or property record.

Can providers keep drafts private?

Yes. Provider working drafts stay in the provider’s permitted scope. An explicitly assigned intake reviewer can help with that working copy. Jurisdictional review follows the submission and configured payment requirements.

Does an accepted report mean the system passed?

No. Review status and reported inspection outcome are separate. Acceptance records an authority review decision; it is not an automatic certification of the system.

Are report files included in report billing?

Where a provider-report charge is configured, it includes the report’s uploaded files. The filing workflow presents the configured charge. No universal price is advertised here.

Does FD Maintain replace the responsible inspector?

No. Qualified people perform the work, assess the findings and determine applicable requirements. The module organizes evidence, review and follow-through.

Let’s make the work easier

Give every report a useful next step.

Request Compliance Engine access for your authority, provider company or property-owner role.