A farm inspection checklist for farm managers

Set the inspection scope and timing

Begin with the last inspection report, open repair list, owner questions and lease. Identify which fields, structures, access points and drainage features the visit will cover. Ask the tenant about work in progress and access restrictions. A manager visiting for a drainage complaint may need a different route from someone preparing a broad property update.

Choose timing to match the question. A dry-weather outlet inspection can reveal visible damage but may leave drainage performance unresolved. A return visit after a suitable rain can answer a different question, provided access is safe. Record the conditions under which an item was checked rather than calling it satisfactory for every season.

Use an agreed seasonal inspection plan, with additional visits after reported damage or completion of an important repair. This is a management schedule to settle with the owner and tenant, not a universal inspection interval. Put a specific return date or trigger beside each open item. “Inspect after the contractor finishes and access is safe” needs an assigned person who will arrange that inspection.

Colorado State University Extension’s Leasing Arrangements for Colorado’s Farms and Ranches discusses written arrangements, building use, maintenance and communication. Use it to frame questions, then read the actual lease. The person who reports a defect is not automatically the person obligated to pay for it.

Prepare the property map and repair list

Match local names to supplied farm, tract and field identifiers. USDA FSA’s acreage-reporting notice describes farm maps and boundary exports available through farmers.gov. Keep the supplied map’s date and source. A current field outline helps organize a walk but does not resolve a property-line disagreement.

For each open item, bring its previous photograph, last status, requested action and responsible person. Mark the stops that need a repeat view. If a repair was reported complete, list the physical check needed to verify that statement. Retain the original problem description so the follow-up does not become a vague “looks better.”

Separate a routine inspection from work requiring a specialist. Structural assessment, electrical work, buried-line diagnosis and legal interpretation need the appropriate person. The manager can locate and describe a concern without assigning an unsupported cause. Say which question will go to the contractor, engineer, drainage specialist or legal reviewer.

Walk access points, crossings and field edges

At each entrance, check the visible approach, gate, crossing surface and any reported obstruction. Record whether access was used or merely viewed. A photograph of an open gate does not show whether it closes and latches. If a safe functional check is within scope, record what you did and what happened.

At a washed crossing, take views from both approaches and locate the damaged section. Measure dimensions only where safe and useful for the next decision. Keep units and measurement method with the dimensions. A rough estimate can support a request for a contractor visit, but should not be passed along as a measured repair quantity.

Along field edges, record visible encroachment, erosion, damaged fencing or debris without deciding ownership from appearance. Pair the location with the source map and any supplied boundary reference. If the tenant describes when the change occurred, attribute the statement. A condition first seen today may have existed before today’s visit.

Inspect drainage observations without diagnosing buried lines

University of Minnesota Extension’s How agricultural drainage works explains surface and subsurface drainage and the role of an outlet. It provides context for inspecting visible features. It does not let a photograph establish the condition of an unseen pipe or authorize a drainage change.

At an accessible outlet, record its location, visible blockage or damage, surrounding erosion and whether water is flowing at that time. Say if vegetation, high water or lack of access prevents a clear view. Pair a field-ponding observation with its own location and date. Keep the outlet and wet area distinct unless a documented system map connects them.

Compare conditions with the prior record and available tile maps. An outlet with no flow during dry weather is a different observation from no flow while water stands above a known connected system. Retain the weather context and the limits of the check. Ask the specialist what further inspection or testing is needed before recommending excavation.

Use an operational decision rule: visible washout, a reported loss of access, or unresolved standing water affecting the planned work warrants prompt review by the responsible person. The required response depends on access, risk, the lease and the work plan. Do not invent a universal water-depth or repair-cost threshold for every farm.

Check buildings and reported repairs

For each structure in scope, record the building name, area inspected and access limitations. Photograph a defect in context and at closer range. At a reported roof repair, identify the location of the earlier leak and whether the current visit occurred after rain. A remaining stain alone does not prove continued leakage; a contractor’s statement alone does not verify performance.

Keep safety concerns separate from routine maintenance requests so the owner can see which needs immediate contact. Do not enter a damaged building or climb onto a roof to complete a checklist. Record the limitation and arrange the appropriate inspection. A missing observation is preferable to an unsupported assurance about structural condition.

For gates, doors and other simple items, describe a safe functional check when it is part of the assignment. Record the result and any unresolved defect. “Tenant reports repaired; manager opened and latched the gate during this visit” distinguishes the source statement from your verification. Use the same distinction for contractor-reported completion.

Worked example: a crossing repair in PropelMapper

Start the phone visit at the correct place in PropelMapper. Speak the crossing name, observed condition, measurement method and alternate access. Take photographs from both approaches. If you record the tenant’s explanation, identify it as their account. Use a typed note to retain the question that needs the contractor’s answer.

After upload, check the draft’s dimensions and units against the voice note. Add the requested next step without inventing a repair method or price. Create a Follow-up task with the tenant or manager as assignee, stating who will arrange the assessment. Review, sign and send the report. Recipient acknowledgment confirms that it arrived, not that the owner authorized the work.

Send requests the owner and tenant can act on

Open the final report with the decisions required, then attach the detail behind them. Each item should identify the location, observation date, supporting photos, next action, owner and response date. Keep a quote, an approval and an invoice as different records. An estimated cost should say who estimated it and when.

Identify uninspected ground and unresolved questions near the findings they affect. If the visit covered the yard and crossing but not the wet interior field, do not describe it as a complete property inspection. Carry that limitation into the next visit plan. The farm inspection form holds the detailed record, while the landowner report guide explains the shorter decision summary.

At the next update, show what changed: approval received, work arranged, completion reported or completion inspected. Keep the relevant dates and sources. A reliable repair history lets the next manager understand which condition was observed and which question still needs an answer, without turning every earlier statement into a verified fact.