Leaving a Device Record the Next Tech Can Use

Why this matters

The tech who installed the water shutoff knows everything about it: which hub it pairs to, which network it joined, whose phone got the alerts, why the third sensor sits on a shelf instead of the floor. Eighteen months later a different tech arrives at 7 a.m. because the valve closed overnight and the customer cannot open it, and none of that knowledge came along. They spend the first 40 minutes rediscovering what someone already knew, on the customer's clock.

A device record is a short card attached to the customer's equipment history that answers the questions the next visit will ask. It takes about 5 minutes at the end of an install, and it is the difference between a diagnosis that starts at the fault and one that starts at "what is this thing?"

What the card is, and what it is not

The record is a set of facts about one installed device, written for a stranger. It is not the job notes (which describe what you did that day) and it is not the commissioning checklist (which proves the install works). Commissioning is owned elsewhere; see related: The Connected-Device Commissioning SOP. The card is what survives after both are filed.

It never contains a password. Not the Wi-Fi password, not the app account password, not an admin PIN. A customer record is read by office staff, techs, sometimes subcontractors, and it lives in software you do not fully control. A password written there is a password shared with everyone who will ever open that record. Write where the secret lives ("customer has it", "printed on router label"), never the secret.

Step 1: Identify the device so it can be ordered

Write the device type in plain words, then the model exactly as printed on the label, then photograph the label and attach the photo.

Why the photo, not just the typed model: model strings get mistyped, and the label often carries a hardware revision or a manufacture date that a typed field drops. Two units with the same model name can take different replacement parts or different firmware. What breaks if you skip it: the next tech orders the wrong replacement actuator, or a recall notice arrives and nobody can tell whether this unit is affected.

Record the serial number too if the label has one. Warranty claims and recalls run on serial numbers.

Step 2: Record where it is, in words a stranger can follow

"Basement" is not a location. "Basement, mechanical room, on the main 18 in after the meter, valve body faces the water heater" is. For sensors, list every one with its spot: "laundry, floor behind washer, left side."

Why: a battery sensor is the size of a cookie and lives behind or under something. A tech who cannot find sensor 3 cannot test it, cannot change its battery, and cannot tell the customer which alert means which room. What breaks if you skip it: a "sensor offline" alert six months later is unanswerable without a house search.

Step 3: Record the firmware version and the date you read it

Open the device's app or its local status page, find the firmware version, and write it with the date: "firmware 2.4.11, read in app 2026-03-14."

Why the date matters as much as the number: firmware changes silently, often overnight, with no one present. A recorded version with a date is the only way the next tech can tell whether the device changed since install. If the version now reads 2.6.0 and the misbehavior started last week, that is a lead. See related: Firmware Updates: The Silent Change to Installed Equipment. What breaks if you skip it: the "it worked until last Tuesday" call has no baseline.

Step 4: Record how it reaches the network

Write the network name (the SSID, the name the router broadcasts) exactly, including capitals, and the band if the device is band-limited: "joined HOME-NET, 2.4 GHz only." If it connects through a hub instead of directly, name the hub and its protocol: "sensors pair to valve hub over its own radio; hub joins HOME-NET by Wi-Fi."

Record the signal reading at the device location if the app shows one, with what the reading means in that app (bars, a percentage, or a dBm figure). See related: Measuring Wi-Fi Signal Where the Equipment Lives.

Why the network name and not the password: the name tells the next tech whether the customer has changed routers since. If the card says HOME-NET and the phone in the house now sees only a new name, half the diagnosis is done. What breaks if you skip it: a router swap looks like a device failure. See related: The Whole House Went Offline After a New Router.

Step 5: Record who owns the account

Write whose account the device is registered under, by role and name: "homeowner, A. Reyes, account created on her phone at install." If a second household member was invited, record that too. Note who receives alerts: "alerts go to A. Reyes and D. Reyes phones; shop does not receive alerts."

Who should own the account is a decision with its own sibling; see related: Who Owns the App Account on a Connected Device. The card only records the decision that was made.

Why: a device that "stopped alerting" has very often alerted perfectly to someone who no longer reads it: a former tenant, a seller, a shop employee who left. What breaks if you skip it: the next tech replaces a working device. See related: The Alert Went to an Employee Who Left.

Step 6: Record dealer access status

Many connected platforms let an installer or dealer account see or manage the device. Record which of three states it is in, with a date: none (shop has no access), granted (shop has access, for what purpose, consented by whom, on what date), or revoked (access existed and was removed, on what date, by whom).

Why all three states, not just "yes or no": "revoked" is information. It tells the next tech that remote checking is not available and why, so they do not spend 15 minutes trying to log in. It also proves the shop removed access when it said it would, which matters if the house sells. What breaks if you skip it: a shop holding silent access to a camera or an occupancy log it no longer needs, which is a privacy problem waiting to surface.

Step 7: Write the one thing that is not obvious

Every install has one fact the next tech would not guess. The sensor on the shelf because the floor floods with condensate from the dehumidifier and would false-alarm. The valve set to a 30-second delay because the irrigation system's start surge tripped it. The thermostat's C wire landed on a spare conductor because the original was broken in the wall.

Write it in one sentence under "Note." Why: this is the field that saves the most time and gets skipped most often, because the installing tech thinks it is obvious. It is obvious to them. What breaks if you skip it: the next tech "corrects" a deliberate choice and creates a callback.

The finished card

Steps 1 through 7 produce a record like this one, attached to the customer's equipment history:

DEVICE: Automatic water shutoff + 3 leak sensors
MODEL: per label photo 01 (valve), 02 (sensor)
SERIAL: valve label photo 01
LOCATION: bsmt mech room, main, 18 in past meter
 S1 laundry, floor behind washer, left
 S2 water heater pan, front edge
 S3 utility sink, SHELF 8 in up (see note)
FIRMWARE: hub 2.4.11, read in app 2026-03-14
NETWORK: hub on HOME-NET, 2.4 GHz only
 sensors -> hub on hub's own radio
 hub signal at install: 3 of 4 bars
ACCOUNT: homeowner A. Reyes, her phone
 alerts: A. Reyes, D. Reyes. Shop: none
DEALER ACCESS: none (declined 2026-03-14)
WIFI PASSWORD: customer has it. NOT RECORDED.
NOTE: S3 on shelf, dehumidifier drains to
 floor there and false-alarms a floor sensor.
INSTALLED: 2026-03-14, tech R. Okafor

Worked example: the 7 a.m. call, eighteen months later

The Reyes household calls at 7:05 a.m.: the water is off, the app says "valve closed - leak detected," and nobody can find a leak. A different tech, who has never been to the house, pulls the card in the truck.

Before arriving, the card answers four questions in about 2 minutes of reading. There are three sensors, so the alert came from one of three known spots. Alerts go to two family phones, so the customer can read the app's alert history and tell the tech which sensor tripped. Dealer access is "none", so the tech does not try a remote login. The network was HOME-NET on 2.4 GHz.

On the phone, the tech asks Mrs. Reyes to open the alert. It names S2, the water heater pan.

On arrival, the tech goes straight to the water heater (the card says front edge of the pan) and finds about a quarter inch of water in the pan from a weeping relief valve discharge. The leak is real; the sensor did its job. Before touching anything at the heater, the tech treats it as a pressure and scald hazard: the relief valve was discharging, which means either the valve itself is weeping or the tank pressure or temperature is high, and the tech checks the heater's temperature setting and does not lift the relief valve lever or stand in front of the discharge tube while it is warm. The heater repair becomes its own ticket.

Then the tech dries the sensor, re-opens the valve from the app with Mrs. Reyes watching, and confirms water at a faucet.

One more check the card makes possible: the firmware line. The tech reads the hub now: 2.7.3. The card says 2.4.11 at install. So the hub updated at least once since install, which matters for one reason only: the valve's auto-reopen behavior changed in some updates on some platforms, and Mrs. Reyes says the valve used to reopen itself after a sensor dried. The tech checks the current setting, finds auto-reopen disabled, and leaves it disabled because the leak was real and the family should decide that knowingly. The tech updates the card's firmware line with today's reading and date.

Time from arrival to the cause: about 6 minutes, because the card pointed at the sensor and the sensor pointed at the heater.

Without the card, the same call goes like this: the tech searches the house for sensors, finds two, misses S3 on its shelf (and might "fix" it by moving it to the floor), cannot tell which sensor tripped because they do not know whose phone has the alert history, and spends 30 to 40 minutes before reaching the water heater. The diagnosis is the same; the bill and the customer's morning are not.

Keeping the card true

A record is only as good as its last update. Three rules keep it honest:

• Every visit that touches the device updates the firmware line, with the date, even if nothing else changed.
• A changed field is replaced, not appended. Old values go to the job history; the card shows current state. A card listing three network names is a puzzle.
• A field you could not fill says so. "Firmware: not readable, app would not load, 2026-09-02" is better than a blank, because a blank looks like the installer forgot, and a stated gap tells the next tech exactly what to check first.

When the house sells, the card is what makes a clean handoff possible: it lists every device, every account and every access the new owner needs to take over or remove. See related: The Connected-Device Handoff at Home Sale SOP.

References

• See related: The Connected-Device Commissioning SOP
• See related: Who Owns the App Account on a Connected Device
• See related: Firmware Updates: The Silent Change to Installed Equipment
• See related: The Connected-Device Handoff at Home Sale SOP
• See related: The Alert Went to an Employee Who Left