The mechanic's notebook
In the workshop there is a notebook, or a spreadsheet on an old laptop, with a page for each machine. The greens mowers get their reels ground and bottom blades changed, the fairway unit needs oil and filters at set hours, the utility vehicles have their own service intervals, and the sprayer has checks your club's procedures require.
When the mechanic is on holiday, nobody quite knows what is due. Hours meters are read when someone remembers. A fault reported on a Saturday by one of the team, a strange noise from the tees mower, is mentioned in passing and forgotten until the machine stops on the eighth tee.
At budget time, the course manager is asked which machines should be replaced. The answer depends on hours, repair history and cost, and that is spread across the notebook, invoices from the dealer and people's recollection.
Why the history stays scattered
Greenkeeping staff record work in the way that is quickest on the day, which is often not at all. Reading an hours meter, finding the notebook, and writing it down is a small job that loses to getting the course ready.
Faults are reported verbally because there is no simple place to put them. Dealer work arrives as invoices at the office, and the office files them without the workshop seeing them.
Service intervals come from manufacturers' manuals and the mechanic's experience. They are rarely written in one place, so they cannot be checked against the hours the machines have actually done.
What that costs the course
| Problem | Effect |
|---|---|
| Services missed or late | Breakdowns on busy mornings |
| Faults reported verbally | Small problems become repairs |
| Dealer invoices not linked to machines | No true cost per machine |
| History in one person's head | Cover is guesswork when they are away |
| Replacement decisions from memory | Weaker case to the committee |
How to maintain a machine is a matter for the mechanic, the dealer and the manufacturer. We give no engineering advice. We give the course team a record they can trust.
How we build a machinery log that gets used
- Each machine gets a record and a QR code sticker. Scanning it on a phone opens that machine's page.
- At the end of a job, staff scan the machine and type in the hours from the meter. It takes seconds and replaces the notebook.
- Faults are reported the same way, with a photo and a short note. The mechanic sees a list of open faults, and whether the machine should be kept off the course until checked.
- Service intervals are set per machine by the mechanic, by hours, by date or both. Services due soon appear on the workshop list, and the course manager sees anything overdue.
- Completed services and repairs are logged with parts used. Dealer invoices can be photographed or forwarded and attached to the machine.
- A fleet view shows hours, service status, open faults and cost to date for every machine, ready for budget meetings.
Where a dealer or fleet system already holds service data, we link to it or import from it rather than asking the team to enter it twice.
A week in the workshop afterwards
On Monday the mechanic opens the list and sees two greens mowers near their service hours and a fault logged on Saturday with a photo of a leaking hose. The fault is fixed before the machine goes out. When the mechanic is off, the relief knows exactly what is due. At the autumn budget meeting, the course manager prints a page per machine with its hours and costs.
- Hours recorded as the machines are used
- Faults reported with photos, not in passing
- Services due shown before they are missed
- A cost and repair history for every machine
Does this describe your sheds?
- Servicing is tracked in a notebook or one person's spreadsheet.
- Hours meters are read occasionally rather than routinely.
- Faults are mentioned verbally and sometimes forgotten.
- Dealer invoices are not linked to the machine they were for.
- Replacement decisions are argued from memory.