Turn fence checks into a repair queue.

A note such as “fix north fence” is hard to assign and impossible to audit. A useful log identifies the exact section, the observed condition, the trigger, the temporary control, the work owner and the closeout evidence.

1. Build the section register once

Use the same section IDs from the site survey and installation records. For each section, record its endpoints, fence role, system family, gates or openings, responsible person, supplier documents and a dated baseline photograph.

2. Record every inspection with the same fields

Print this log template

3. Use observation categories that fit every system

• Posts, ends, corners and braces: leaning, movement, visible damage, decay or disturbed ground—record the observation, not a structural verdict.
• Wire, mesh, rails and attachments: sagging, looseness, breaks, displaced clips, deformation, corrosion or contact with foreign objects.
• Gates, latches and access: alignment, closure, hardware condition, obstruction, surface wear and whether the intended route remains usable.
• Vegetation, trees and debris: contact, fallen limbs, blocked access, concealment or added load.
• Ground, drainage and water gaps: erosion, washout, undermining, sediment, standing water or changing clearance.
• Visibility and controls: missing markers, signs or other project-required safety features.
• Electric system: visible condition plus the actual reading, test point, instrument and date. Compare only with the approved system instructions; this log sets no universal threshold.

4. Route the item by consequence

Priority must follow the site’s approved risk process. The examples above help route observations; they do not declare a fence safe or prescribe a repair.

5. Set routine and event-triggered inspections

Use the operation-and-maintenance plan, manufacturer instructions, livestock pressure, site conditions and local requirements to set the routine interval. Add event-triggered checks after storms, impacts, animal breaches, ground movement, flooding or rapid vegetation change. Avoid copying a universal weekly or monthly interval into every project.

Questions managers ask

What belongs in a fence inspection log?

At minimum: date, location or section, inspector, observed condition, maintenance needed, responsible person, action taken and review or closeout. Add a trigger, priority, temporary control and evidence reference so work can be routed and verified.

How often should farm fencing be inspected?

Use the project’s operation-and-maintenance plan rather than a universal number. Include routine checks and additional checks after storms or other disturbances and after any event that may have changed containment or condition.

Should I record repairs in the same log?

Yes, if the log keeps the original observation visible. Record the separate work action, date, person, materials, evidence and verifier so the issue history is not overwritten.

What should I photograph?

Photograph the exact location and enough surrounding context to find it again. For repaired items, retain before-and-after views with the same section and issue ID.

Can this log diagnose an electric fence?

No. It can preserve readings, test points, instrument, visible condition and the applicable document reference. Diagnosis and thresholds belong to the approved manufacturer instructions and a competent person.

Evidence and limits

Penn State Extension recommends regular monitoring and checks after storms or disturbances and lists posts, wires, vegetation and fallen trees among inspection items. Michigan State University’s Fence Perimeter and Field Inspection Log provides a useful record pattern: date, location, inspector, maintenance needed, service person, remedial action and review. The MSU template is dated March 2010; it informs the fields but does not set current safety or repair criteria.