Skip to content

For fire alarm and life safety contractors

Every device, by address, with its proof

Detectors, pull stations, notification appliances, and modules are points with an address, an install photo, and a test result. The office sees what is tested, the customer sees what is done, and the record of what went in is ready for the inspection.

30 days free · no card required

A fire alarm points register: smoke detectors, pull stations and notification appliances with their counts, the latest install photos, and two register rows with their status.

What changes on the job

  • Addressed, not just counted

    The SLC address is a typed value on the device's checklist. The register shows every device with its address, so the loop on paper matches the loop on the wall.

  • Tested before it is complete

    Make the test result a required line and a device cannot be marked complete until the crew types it. Nobody declares a loop done; the proof does.

  • Readable by the people who sign

    Invite the GC or the owner to the read-only portal. They see devices, status and the released package. Late and off-site flags stay with your office.

Your point types, your IDs

These are examples. Point types belong to your organization: set yours up in minutes, in English and Spanish, with the checklist each must satisfy.

  • SMK-001, SMK-002, …

    Smoke detector

    Proof checklist

    • Installed photo
    • SLC address (value)
    • Sensitivity or test result (value)
  • PUL-001, PUL-002, …

    Pull station

    Proof checklist

    • Installed photo
    • Label photo
    • Address (value)
  • NAC-001, NAC-002, …

    Notification appliance

    Proof checklist

    • Installed photo
    • Circuit and candela (value)

What the package hands over

The turnover package assembles itself from proof that already exists: a formal PDF register plus supporting files organized by point and by date. It is the package the GC’s closeout software is waiting for, built on your side of the handover.

  • The device register by type, with each device's address, location and status
  • Test values on the device they were taken for
  • Your completion and test forms, attached to the project and carried in the package
  • The replacement schedule for every swapped device, with serials
  • The daily work record and the change requests you marked for closeout

The same product for every trade

  • 6

    kinds of need a tech can raise from the phone: material, tool, information, access, decision, or scope.

  • 1

    GPS reading per daily report, taken on the form and checked against the site geofence. No tracking.

  • 2

    languages on the field surface, English and Spanish, chosen once by the tech and remembered.

Questions from the trade

Do my techs need to install an app?

No. Each tech gets a text with a link, and the report opens in the phone’s browser. There is nothing to install and no password to remember. The field surface works in English and Spanish.

What if a tech has no signal on site?

The written report saves as a draft on the phone, and a photo that fails to upload stays on the form with a retry button, so the tech can send it when signal returns without redoing anything. A missing or denied GPS reading is recorded as such and never blocks a report.

Is Bana tracking my crew’s phones?

No. Bana takes one GPS reading when a tech opens the report form, shows it to the tech, and sends it with the submitted report, checked against the jobsite geofence. There is no background location and no location history, and off-site flags are visible to your office only.

What happens if a tech replies STOP to a text?

That number is opted out of texts across Bana until it replies START. Nothing is blocked: the tech’s daily link falls back to email when there is an address on file, and the office sees each tech’s reachability as text, email only, or unreachable.

How does a point get marked complete?

Nobody declares it. Each point type carries a proof checklist, and a point becomes complete when the required lines are satisfied by photos, videos, values, or attachments. The office can mark a point Needs attention or Not required; everything else is computed from proof.

How are device swaps recorded?

A replacement is a flag on the point, not a new point. The tech records the removed device with a before photo, description, make and model, serial, condition, and where it went, and the replacement schedule carries into the customer portal and the turnover package.

Does Bana work for my trade?

Yes, if your crew installs, labels, and tests things one at a time. Point types belong to your organization and you define them: the ID prefix, the name in English and Spanish, and the proof checklist, from photos and typed values to attachments and port maps. The defaults are low-voltage types; replacing them with your own takes minutes in Settings.

Can I get my data out?

Yes. Turnover packages download as a PDF register plus organized supporting files, and a data export packs any project, or your whole organization, as CSV tables with the same file structure. Export links stay live for 7 days. If you cancel, your records stay readable for at least 12 months.

Can the inspector see the records?

Anyone you invite gets a read-only view of the job: points with their status and proof, plans, the daily records and the released turnover package. Internal flags such as late, missed or off-site never appear there.

Put your next fire alarm job on Bana

Define your device types, text your crew their links, and the first daily report lands tonight. 30 days free with no card required.