Fire marshal handoff

Give the fire marshal a report that is easy to review.

The goal is not to predict every local request. It is to issue a factual, complete record that helps the customer or authority find the service identity, evidence, exceptions, and follow-up items quickly.

Create my first report Review a sample PDF

Direct answer

Which workflow fits?

A fire marshal handoff should identify the serviced system, work date, scope, before-and-after evidence, inaccessible areas, deficiencies, technician information, and customer acknowledgement required by the job or local process.

01

Make review paths obvious

Put identity and scope first, evidence next, and unresolved items in their own section. Do not force a reviewer to infer an exception from a missing image.

  • List each hood system and the components in scope
  • Label photos by component and before-or-after state
  • State inaccessible or excluded areas directly
  • Keep credentials and service tags aligned with local requirements

02

Use bounded compliance language

The report documents contractor work. It should not state that software certifies compliance or guarantees AHJ acceptance.

  • Reference only the standard edition actually used
  • Distinguish cleaning from inspection or suppression work
  • Tell the customer when local verification is still needed
  • Retain the exact PDF that was issued

Decision

Use this workflow when a customer needs a reliable inspection record and the contractor needs a defensible account of scope and exceptions.