Site records: the half of a trade CRM people skip

Most trade businesses record the customer carefully and the address as a line of text on the job. That works for a single visit. It breaks on the third, because everything learned on the first two went home with whoever attended. The gate code, the switchboard location and the awkward parking all live in one person's memory.

A site record fixes that by giving the place its own existence. The customer pays, the site holds the knowledge, and the job links them. None of it takes much effort, and very few small businesses bother.

What a site knows that a customer does not

• Access. The gate code, the key safe, who to ring, where to park.
• Where things are. The switchboard, the isolation valve, the meter, the roof access.
• The equipment there. The unit, its model, its age, its warranty.
• The earlier faults. The repair last winter, and the part that failed twice.
• The hazards. Asbestos, a dog, a steep roof, live equipment.

Every one of those is knowable once and useful indefinitely. None of it belongs to the person who happens to pay the invoice, and all of it is what a technician needs before they arrive.

The second visit is where it pays

A technician arriving at a site with notes starts working. One arriving without them rings the office, waits, and occasionally drives away again. Across forty maintenance visits that difference is most of a day. The record that produces it took somebody three minutes to build during an earlier visit.

The saving compounds where staff change. A business that loses a technician loses their site knowledge the same afternoon. The written record is the only thing that survives them. Our guide to why a CRM gets abandoned covers the same principle from the other direction.

One customer, several sites

A property manager, a school, a strata committee and a franchise all pay for work at addresses they do not occupy. A single address field cannot express that. Diract CRM links many sites to one customer, so a job names both and every report still reads correctly.

The occupant needs recording too. A tenant lets the technician in and knows what is broken, and the property manager approves the spend. Recording both against the site, with their roles, stops the wrong person receiving an invoice or an approval request.

The address has to be real enough to route

A site recorded as the shop near the roundabout defeats the map, the route and the check in measurement. A proper street address takes the same time to type. What it buys is every later feature. A day ordered by driving time, a check in measured against the site, and a suburb anybody can filter.

Our guide to planning the day's runs depends entirely on that. A business whose sites carry vague addresses cannot use any of it, and usually blames the routing rather than the records.

Hazards, equipment and photographs

A hazard note in the office file protects nobody. On the site record, in front of tomorrow's technician, it does its job. The same applies to a difficult occupant, recorded factually rather than as an opinion anybody would mind reading.

Equipment makes the replacement conversation possible. A unit with a known age and a documented service history gives you standing to raise replacement before it fails. Photographs answer the questions no note anticipated: the switchboard, the roof access, the meter position. Two pictures on the first visit save a phone call on every visit afterwards. Diract CRM attaches them to the site rather than to one job, so the next technician finds them without knowing which visit took them.

Build it in a cycle, not as a project

A business that decides to document three hundred sites documents none of them. The task never becomes anybody's afternoon, and it never will. Three fields completed on each visit builds the whole record inside one maintenance cycle, and nobody notices the effort. Diract CRM asks for those three on the phone, at the site, rather than on a form back at the office.

The record then outlives almost everything around it. Property managers change, tenants move, and the building stays where it is with the same switchboard in the same cupboard. That permanence is the argument for keeping the site separate rather than inside whoever currently pays.

What to change first

• Every job names a site record, not a typed address
• The site holds access, hazards, locations and equipment
• One customer links to every site they pay you to attend
• Each address is real enough to map and to route
• Hazard notes sit where the next technician will read them
• Photographs of access and services go on the first visit
• Three fields go in per visit, rather than one big recording exercise