For HVAC controls and building automation contractors
Every controller and sensor, checked out and on the record
Controllers, sensors, actuators and terminal units are points with a tag, an install photo and the values from checkout. The crew records them on the phone as they go, and the point-to-point record is in the closeout package the day the job ends.
30 days free · no card required
What changes on the job
Tagged the way the drawings are
The point ID can match the tag on the drawing, and the sheet pin puts it on the plan. The register reads like the points list, because it is one.
Checkout values on the point
Readings at checkout are typed values on the checklist. A required value keeps the point from completing until the crew has taken it.
The checkout sheet, attached
Attach the checkout sheet to the controller's point and it travels with the package, filed where the next person will look for it.
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.
CTR-001, CTR-002, …
Controller
Proof checklist
- Installed photo
- Address (value)
- Checkout sheet (attachment)
SEN-001, SEN-002, …
Sensor
Proof checklist
- Installed photo
- Tag (value)
- Reading at checkout (value)
VAV-001, VAV-002, …
Terminal unit
Proof checklist
- Installed photo
- Tag (value)
- Damper test (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 point register by type, with each device's tag, location and status
- Checkout values on the point they were taken for
- Checkout sheets attached to the controllers they belong to
- Pinned plan overviews, one per sheet
- The daily work record and the change requests 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 a point hold more than one reading?
Yes. A checklist can have as many typed value lines as the type needs, each named by you, each required or optional. The values show on the point, in the register export and in the closeout package.
Put your next controls job on Bana
Define your point types, text your crew their links, and the first daily report lands tonight. 30 days free with no card required.