Open with the decisions the owner needs to make
Name the property, reporting period and visit dates before presenting the requests. State the proposed action, why it is being requested, the available options and the reply date. An owner should be able to identify what needs a response without reading the entire visit log. Put routine observations after those requests.
When the cause of a problem is uncertain, ask for the appropriate investigation. A stained roof panel may justify a contractor inspection before a repair scope is known. Do not make the request sound settled by naming a repair the evidence has not established. “Approve an assessment” and “approve replacement” authorize different work.
Explain what happens if the decision waits, using the actual work plan or contractor’s information. Avoid an invented loss estimate or urgency claim. If no consequence has been established, say which person will advise on timing. A useful deadline comes from the proposed work, access arrangement or owner process, rather than a generic demand for a quick reply.
Agree on the report scope and schedule
Set a reporting schedule with the owner and tenant that matches the management assignment. A routine property update, a storm-damage report and a repair-approval request need different detail and timing. Agree on which concerns require immediate contact outside the routine report, and identify the contact method and backup person.
Colorado State University Extension’s Leasing Arrangements for Colorado’s Farms and Ranches discusses the importance of communication and suggests abbreviated reporting for interested owners under a cash lease. It also addresses buildings and maintenance arrangements. Use that context to agree on a report the owner can use; the actual lease and management agreement govern who may authorize work.
Bring forward every unfinished request from the previous update. Give it a stable reference and retain its original date. A new reporting period should not make an unresolved repair disappear. If the owner has already replied, put the actual decision beside the item so the next update starts from the correct status.
Tie each request to a location and dated evidence
Use the field and building names the owner recognizes, with supplied agency identifiers where needed. A reader unfamiliar with the route should still be able to find the problem on the map or in the photo sequence. Name the doorway, crossing, outlet or field corner rather than relying on “the usual spot.”
For each issue, use a view that locates it and another that shows the relevant condition. Keep earlier comparison photos labeled with their original dates. If a close-up no longer makes sense without the broad view, include both. Do not let a circle or arrow replace a written description of what the photograph shows.
Describe what you observed, how you checked it and any access limit. Attribute the tenant’s or contractor’s explanation to that person. A report can carry a useful account without certifying it. For example, a tenant’s statement that the roof was patched belongs beside the manager’s observation of the stain, with performance after rain still untested.
The farm inspection guide explains the underlying visit. Use the detailed farm inspection form for the working record, then select the evidence needed for the owner’s decision. The summary should not bury the requested approval beneath every photo from the day.
Keep costs, quotes and responsibilities distinct
Label an amount by its source: contractor quote, manager’s preliminary estimate, approved budget or actual invoice. Retain the document date and scope. If the quote excludes materials, disposal, permits or another necessary item, carry that limitation into the approval request instead of presenting the number as the full cost.
Do not invent local prices to fill a blank. A missing quote can become the next action: obtain a written scope and price from the named contractor. When comparing alternatives, make clear whether they cover the same work. A lower number for a narrower scope is not necessarily a comparable option.
Purdue Extension’s Crop Share or Crop Share/Cash Rental Arrangements for Your Farm discusses written agreements and includes repair and improvement provisions in a sample lease. Those are discussion points, not instructions to assign every cost to the owner. Refer responsibility questions to the property’s actual lease and the authorized reviewer.
Keep authorization separate from receipt. An owner opening a report or confirming delivery has not necessarily approved the work. Record the approval itself, including the agreed scope, any conditions, the person giving it and the date. If approval must arrive through another system or signed document, preserve that record.
Use practical rules for escalating a finding
Agree in advance which conditions require prompt contact, such as an unsafe access point, active water entry or damage that affects planned work. The management assignment should define the response and authority. Do not introduce a universal dollar threshold or repair tolerance that the owner has never approved.
For an unresolved drainage concern, explain the visible observation and the investigation needed. University of Minnesota Extension’s How agricultural drainage works provides background on surface and subsurface systems. It does not let the manager identify a buried failure from ponding alone. Request the relevant specialist review rather than presenting an unsupported excavation plan.
For routine work, state when the quote is needed, when the owner must respond and who will arrange access. If the next check depends on rain or contractor completion, give that trigger as well as the responsible person. A trigger without an owner can leave the issue open indefinitely.
Worked example: a roof follow-up in PropelMapper
Example account: Prairie Agronomy. Assume a practice update for the machinery shed. The tenant says a contractor patched the roof. On the current dry-day visit, the manager photographs a stain above the north door but does not inspect the roof itself. No rain-performance check has occurred. The report requests the contractor’s written scope and a return inspection after rain when access is safe.
The status is “completion reported; verification pending.” It is not “repair failed,” because the stain does not establish new leakage. It is also not “closed,” because the agreed performance check has not happened. The owner is asked to confirm whether the manager should arrange the contractor’s assessment if the return visit shows active water entry.
In PropelMapper, open the shed’s place and start the visit on the phone. Speak the exact location of the stain, the inspection limits and the tenant’s attributed statement. Take a context photo and a closer view. Add a typed note identifying which earlier photograph should be compared. Keep any measurements with their units and method.
After the captures upload, read the draft against the notes. Add the requested decision and the actual document references. Create an assigned Follow-up task to obtain the contractor’s scope and arrange the return check. Review the finished report, sign it and send it. PDF and DOCX exports provide copies for the owner’s records, while the report activity log retains the capture, version, signature, send and acknowledgment history.
Track the reply through inspected completion
When the owner responds, record the decision with its date and conditions. An approval to obtain a quote should not become approval to start work. A spending limit should remain linked to the authorized scope. If the contractor proposes a change, seek the required decision before treating it as part of the original authorization.
After work, preserve the contractor’s completion statement and any invoice. Then record the manager’s later inspection separately. State what was checked and under what conditions. If the visit verifies only that materials were installed, keep any performance question open. Closing an item should identify which agreed evidence resolved it.
The next report should show the change since the last one: response received, work arranged, completion reported or completion checked. Keep the same item reference so the owner can follow the sequence. Carry unresolved access, missing documents and untested performance into the next action rather than rewriting them as new issues.
Review the report for an owner reading remotely
Read the opening as if you cannot call the manager immediately. It should identify the property, decision, evidence, responsible person and requested response date. Remove directions that depend on being in the truck with the inspector. A precise place name and an understandable photo caption often do more than another paragraph of narrative.
Check that the attachments support the requests actually made. A quote for another building, an undated comparison photo or a tenant statement presented as a manager’s finding can lead to the wrong decision. Correct those mismatches before signing. Keep sensitive or irrelevant material out of the owner’s packet according to the team’s process.
End with the planned next update and any event that will trigger earlier contact. The owner should know what is waiting on them and what the manager will do meanwhile. That makes the report a usable record of decisions and follow-through, while leaving legal, structural and technical judgments with the people responsible for them.
Before sending the owner update
The request
- Property and reporting period
- Approval needed, supporting quote and reply date
The follow-up
- Source visit dates and labeled photos
- Tenant statements attributed
- Owner’s response, person responsible and next check
propelmapper.com