How to Document a Job for Someone Who Was Never on Site
Why this matters
A technician writes the record for the next technician. On managed property, the actual reader is a property manager who has never seen the equipment, and behind them an owner or a board member who has never seen the building. They will make a decision from your words and your photographs and nothing else, and if the record does not carry the decision, they will make it by asking you, which costs you a phone call, or by deferring, which costs you the job.
This is a capture problem, not a writing problem. Almost everything that makes a record useful has to be caught during the visit, in a window that closes the moment you take something apart. What you can produce that evening from memory is a summary, and a summary is exactly what fails.
Step 1: Capture before you touch, because that window does not reopen
The first two minutes on site are the only time the fault exists in its found state. Photograph the area and the equipment before you open, move, or test anything.
Skipping this is the most expensive habit in the trade and it feels like nothing at the time, because you already know what you are looking at. You are not the audience. Once the panel is off and the component is in your hand, no photograph you take can establish what the condition was when you arrived, and "what was it like when you got there" is the first question every reader asks.
The same applies to anything you will cover up. A connection that will be behind a wall, a joint that will be insulated, a run that will be buried: photograph it open, with something in frame that establishes where it is.
Step 2: Shoot a fixed sequence of frames, every job, in the same order
Consistency beats volume. A reader who sees the same sequence on every job from your shop learns to read it in seconds. Five frames minimum:
- Context. Wide, from the doorway or the approach, showing where the equipment sits in the space. This is the frame that tells a reader which unit and which room, and it is the one most often missing.
- Identifier. The nameplate, tag, asset label, or unit marking, readable. This is what lets a manager match your work to their asset list a year later.
- The fault, close. Framed so the defect is unmistakable, with enough surround that a reader can tell what part of the equipment they are looking at. A macro shot of a corroded terminal with no surround is a picture of nothing.
- The measurement. The reading and the point of measurement, either in one frame or as a tight pair. See step 3.
- After, from the same position as frame 1. Same spot, same angle. A reader compares two images from the same viewpoint instantly and cannot compare two from different viewpoints at all.
Add frames as the job needs them. Cover-up shots, a second fault found in plain view, the area restored after you moved belongings. Nine or ten frames on a routine job is normal and takes about four minutes across the visit.
Step 3: Photograph the number and where it came from
A meter display floating in a photograph proves you took a reading. It does not prove what you read it on, and on managed property the reading is frequently the whole basis for a replacement recommendation.
Get the leads or the probe and the display in one frame where the geometry allows. Where it does not, shoot a tight pair, one of the connection point and one of the display, taken seconds apart so the sequence is obvious.
Then write the number down as well. Photographs get compressed, forwarded, and printed in grayscale into a board packet, and a display that was legible on your phone is often not legible by the time it reaches the person deciding.
Step 4: Write the finding as condition plus consequence
The single most common defective note in this segment is a conclusion with no condition behind it: "found bad control board, replaced." A manager cannot defend that, an owner cannot evaluate it, and a year later nobody can tell whether it was the right call.
Write two elements every time:
- Condition. What you observed or measured, in words a non-tradesperson can picture, with the value.
- Consequence. What happens if nothing is done, on what timeframe, in terms of the tenant's experience or the asset's condition.
The consequence half is what converts a note into a decision. "Contactor points pitted and welding intermittently; unit fails to start on roughly half of calls and will stop starting entirely" tells a manager what their tenant will experience next week. "Contactor bad" tells them to trust you.
Step 5: Record what you ruled out, not just what you found
An intermittent fault is where this pays. A reader looking at 6.0 hours of labor and one replaced component assumes the time was slack. The same reader looking at 6.0 hours with three causes named and eliminated understands they bought a diagnosis.
Write it as a short list: what you suspected, what you checked, what the check showed. One line each. This is the section that most often converts a challenged invoice into an approved one, and it costs about 90 seconds to write while the sequence is fresh.
It also protects the next technician on that asset from repeating your dead ends, which is the internal reason to do it even on accounts that never ask.
Step 6: Record the facts of the visit, not impressions of the people in it
Times: arrival, start, any interruption started and restored, departure. Occupancy: who was present. Communication: what the tenant or site staff was told and when. Access: the method used and whether it worked.
Write people-facts, never people-opinions. "Occupant declined entry at 10:15 and asked us to return another day" is a fact. Any characterization of attitude is an opinion that will be forwarded to somebody who was not there, and it will outlive the incident. The same rule applies to prior vendors and to the property itself: describe the condition you found, not the competence you infer from it.
Step 7: Close the record on site, before the truck moves
Budget five minutes at the end of the visit. Not that evening, not at the end of the week.
The reason is specific rather than moral. What decays first is exactly what disputes turn on: the order of events, the time something was said, the reading you did not write down, the pre-existing mark you meant to mention. A record written that night reads fine and quietly loses the three details that would have settled a question.
Measure this rather than exhorting it. Over the last 20 completed orders per technician, count the share whose record was timestamped on the day of the visit. Below 8 of 10 for a given technician, treat it as a process problem rather than a personal one, and look for the actual cause, which is nearly always that the last job of the day runs into overtime and the record is the thing that gives.
Step 8: A worked rewrite of one job's record
An intermittent no-cooling call on a rooftop unit serving a managed building's common area. Both versions describe the same 6.0-hour visit by the same technician.
As originally written:
Troubleshoot and repair. Found bad contactor, replaced. Tested OK.
Nine words of substance. It answers nothing a reader needs. A board seeing 6.0 hours against this will hold it, and they will be right to, not because the work was wrong but because there is nothing here to evaluate.
Rewritten, same job, same facts:
Building C rooftop unit serving the lobby and corridors, north end of the roof, asset tag photographed.
Reported: cooling drops out intermittently, mostly afternoons, restores on its own.
Ruled out, in order: thermostat and control wiring, checked continuity end to end and swapped the stat with a known-good, fault repeated. Low refrigerant charge, pressures and superheat read within the expected range for the outdoor conditions on the day. Airflow restriction, filter and coil clean, no temperature split anomaly.
Found: contactor points pitted and sticking. Under load the contactor dropped out and re-made twice during a 40-minute observation, which matches the reported intermittent pattern. Photographed points before removal.
Consequence if left: starts will fail more often, and the compressor sees repeated short-cycling that shortens its life. This is a low-cost part protecting the most expensive component in the unit.
Repaired: contactor replaced with an equivalent rating, connections re-torqued, cabinet closed.
Verified: ran three consecutive start cycles with the unit under load, no drop-out, supply air temperature recorded after 15 minutes of run time. After photo from the same position as the arrival photo.
Labor: access and isolation 2.0 hours, diagnosis 1.5 hours, repair 2.5 hours.
Site: no tenant contact required, roof access via the manager's key, returned same day. No interruption to occupied units.
That is roughly four minutes of writing and it answers every question the reader will ask, in the order they will ask it. The labor segments add to the 6.0 hours claimed, so the duration is now picturable rather than asserted.
Look at what the ruled-out section did specifically. Without it, the reader sees 6.0 hours and one inexpensive part, which is the exact shape of a padded invoice. With it, the reader sees a technician who eliminated three plausible causes before spending money, which is the shape of a vendor worth keeping.
Step 9: Attach it where it survives the trip
A record that lives in your job management system and gets summarized into an email is two documents, and the one the manager forwards upward is the summary. Send the record itself, in the account's expected format, referenced to their work order number.
Confirm once, at account setup, how photographs need to arrive. Some platforms strip attachments, some cap file counts, some require photos embedded rather than attached. Finding this out on the invoice that mattered is a week of delay for a question you could have asked in one email.
How to verify you got this right
Hand a completed record to someone in your shop who was not on the job and who does not work that account. Ask them three questions: what was wrong, why did it take that long, and how do we know it is fixed. If they can answer all three from the document alone, it will survive an owner review.
Then run the harder test on an intermittent job specifically, because that is where records fail. Ask the same reader what the technician ruled out. If they cannot name a single eliminated cause, the record documents an outcome rather than a diagnosis, and every hour beyond the obvious repair time is undefended.
References
- See related: What a Property Manager Needs to Defend a Spend; Who Actually Signs and Who Only Calls
- See related: Documenting Commercial Work to Survive a Payment Dispute; How to Coordinate Work Around a Tenant
- See related: Reading a Commercial Building's Maintenance Log for Clues
- Trade-standard practice for field documentation, photographic evidence, and work-order close-out on managed property