A facilities manager reviewing a maintenance visit needs to understand what happened without reconstructing the job through emails and phone calls. Which asset was inspected? What was completed? Is anything still outstanding, and who needs to act?
Your report should answer those questions. It also gives the client information they can use in budget discussions, contractor reviews and requests for maintenance evidence from building owners or other stakeholders.
For contractors, the challenge is capturing enough detail to support those decisions without creating unnecessary administration. Start with the client's reporting requirements, then build a consistent process from the engineer's visit through to delivery and follow-up.
Agree reporting requirements with your client, including asset references, evidence, delivery deadlines and the people authorised to receive information.
Record completed work and outstanding findings separately, so a finished visit does not conceal an unresolved repair or approval.
Measure SLA performance using agreed definitions, clock rules and timestamps rather than assuming every contract measures response in the same way.
Give each follow-up action an owner, a justified deadline and a record of the evidence needed before closure.
Fieldmotion supports mobile forms, photographs and asset records, while your team remains responsible for accurate capture, review and client communication.
FM clients need reports that support maintenance decisions, show outstanding work and explain performance against the contract. A document confirming attendance provides only part of that picture.
For a multi-site client, a useful report connects the visit to the correct building and asset. It explains the condition found, what changed during the visit and what remains unresolved. Those details help the client distinguish routine servicing from an issue requiring approval, investigation or further work.
Clients also need evidence they can retrieve later. Someone asking about one asset should not have to search an entire portfolio of PDF attachments. Agree a naming convention and references that work with the client's records as well as your own.
Set out the reporting standard at mobilisation: mandatory fields, attachments, delivery method, recipients and deadlines. Ask for an example of a report the client can use, then check whether your forms capture the necessary information.
Separate individual job reports from periodic summaries. The job report explains one visit; a monthly summary might cover planned maintenance, reactive work, open defects and exceptions. Agree who prepares each document and who checks it before issue.
An FM maintenance report should identify the visit, describe the work, record findings and evidence, and make the next action clear. Adjust the detail to the job type and contract rather than applying an identical form to every task.
Include the client, site address, building or area, job reference and asset identifier. Where several similar units exist, record enough location detail to distinguish them. Check the reference on site rather than selecting the first matching description.
State why you attended and what the visit covered. A planned inspection, a reactive diagnosis and an authorised repair have different scopes. Record exclusions and access limitations so the reader understands what was not inspected or completed.
Explain the checks, adjustments, repairs or replacements carried out, using terminology appropriate to the reader. Include parts and relevant results where they support the maintenance record. Avoid a lengthy narrative that obscures the outcome.
Separate the customer's reported symptoms from your findings. If the client reported intermittent noise but it was not reproduced during the visit, say so. An unconfirmed symptom should not become a diagnosed fault simply because it appears in a report.
Describe the condition found and attach relevant photographs, readings or completed checklists. Label evidence so a reviewer can identify the asset, the issue and what the image demonstrates. A photograph with no location or explanation can create another query.
Record any limitations. An image may show visible damage without establishing its cause. A completed checklist records the checks reported; it does not independently establish that every contractual or technical requirement has been met.
Identify anything left unresolved, including further investigation, parts, access, authorisation and remedial work. State the proposed next step and who owns it. Keep these actions visible even when the engineer has finished the booked visit.
Findings outside scope need their own review route. The process for reporting additional work should distinguish the observation, technical assessment and customer approval. Permission to prepare a quotation is not permission to carry out chargeable work.
Use the following as an operational starting point, not a universal statutory form. Add the trade-specific evidence and contractual fields required for the work.
Identification: Client, site, area, job reference and asset reference.
Visit details: Engineer, date, attendance and relevant job times.
Scope: Reason for attendance, authorised work and limitations.
Work: Checks, repairs, adjustments, materials and relevant results.
Findings: Observed condition, unresolved symptoms and recommendations.
Evidence: Labelled photographs, checklists, readings and applicable documents.
Next actions: Owner, approval requirements, target date and update commitment.
Handover: What was communicated, to whom, and what any signature acknowledges.
Report SLA performance against the definitions and measurement rules in your contract. The word response can mean acknowledgement in one agreement and attendance in another. Confirm the meaning before building a dashboard or promising a target.
Keep acknowledgement, attendance, restoration, permanent repair and documentation separate where the agreement distinguishes them. A technician can attend within target while the repair remains incomplete. A restored service may still need permanent remedial work.
Record the relevant milestones alongside the priority assigned to the job. If that priority changes, retain the original classification, the reason for the change and who authorised it. Otherwise, a performance summary can conceal how the work was managed.
Confirm the trigger for each measure: job logged by the client, notification received, instruction accepted or another agreed event. Specify whether the calculation uses working hours or elapsed time, including out-of-hours arrangements.
Do not silently substitute the time dispatch entered a job for the time the client raised it. If both exist, preserve both and use the contracted trigger. Record the source of each timestamp and correct errors transparently rather than overwriting the history.
Apply clock pauses only where the contract allows them and the required approval has been obtained. Waiting for parts or access does not automatically suspend the SLA. Report the dependency even when it does not qualify for an exclusion.
Where a pause is permitted, retain the reason, start and end times, authorisation and supporting correspondence. Show the original elapsed time alongside the adjusted measure where useful, so the client can understand both service interruption and contractual performance.
State which jobs the summary covers and how the percentage is calculated. Distinguish jobs raised during the period from jobs completed during it. Those groups can differ, particularly when older outstanding repairs are closed.
If you show attendance compliance, name the eligible job group and display compliant jobs, total eligible jobs and exceptions. Report missing timestamps separately. Excluding records with incomplete data without explanation can make performance appear better than the evidence supports.
For PPM, compare visits due with visits completed within the agreed window. Show overdue, deferred and cancelled work separately, with reasons. A rescheduled visit should retain enough history to explain the original commitment.
Include the age and next action of unresolved reactive jobs. A report containing only completed jobs leaves the client unable to see the work still waiting. Agree how partially completed visits and multiple assets on one job are counted.
Document each defect as an action that can be tracked from discovery to an appropriate closure decision. Sending the visit report is one handover; it does not establish that somebody has accepted responsibility for the work.
Record a unique finding reference, asset or location, description, evidence and proposed next step. Assign a named person to coordinate that next step, even when several organisations are involved.
Separate responsibility for approval, access, repair and verification. The person receiving your report may have no purchasing authority. Confirm the approval route rather than assuming a site contact can commission work on behalf of the building owner.
Set timescales using the actual finding, applicable requirements and competent assessment. Avoid arbitrary replacement dates or unsupported promises that equipment will remain operational until the next service.
Keep urgent technical or safety notifications on the appropriate direct escalation route. A report uploaded to a portal is not proof that the responsible person has received an urgent warning. Record the communication and confirmation required by your procedures.
Keep approval requests, deferrals, revised dates and completed work connected to the original finding. Where work requires verification, record the reviewer, evidence and result. Distinguish work reported complete from an outcome that has been checked.
The process for closing pest recommendations illustrates this handover clearly. Apply the same discipline to appropriate FM actions: preserve ownership, progress and the basis for closure rather than allowing the item to disappear between reports.
A useful report gives another person enough information to identify the work and take the next decision. The following hypothetical example concerns an ordinary office storage cupboard, not fire safety equipment or a regulated inspection.
“Attended site. Fixed handle. Other cupboard needs attention.”
The note leaves several questions unanswered. Which cupboard was repaired? What work was completed? What was found on the other cupboard, and is anyone arranging follow-up? A client cannot reliably connect the note to a location or approval request.
Site and scope: Maple House, first-floor stationery store. Job J-0142: repair the loose handle on cupboard C-03. Routine furniture maintenance only.
Work completed: Replaced the damaged handle and its fixings on C-03. Checked operation after fitting. Attached photographs identify the cupboard and show the replacement.
Separate finding: The handle on adjacent cupboard C-04 is visibly cracked. No repair was authorised or completed on C-04 during this visit. Photograph attached under finding F-0087.
Next action: Office coordinator to send a separate repair proposal to the client's authorised contact. Client approval remains outstanding. The job record contains the agreed date for that update.
The clearer report identifies the completed repair and keeps the additional finding separate. The office can review the proposal without asking the engineer to reconstruct the visit. The client can see what they are being asked to approve.
It also avoids implying that all work at the location is complete. A finished visit, an outstanding recommendation and an authorised future job are different states. Your reporting should preserve that distinction.
Keep reporting consistent through job-specific forms, clear evidence requirements and proportionate review. Give engineers examples of the required detail rather than relying on an instruction to write better notes.
Use different prompts for a routine inspection, a diagnosis and a completed repair. Require information that somebody needs for an operational, contractual or technical decision. Remove duplicate fields and questions that have no clear purpose.
Test the form with engineers and office reviewers. Check whether asset references are easy to select, photographs are identifiable and follow-up actions have somewhere to go. A mandatory field can prevent a blank entry; it cannot establish that the answer is accurate.
Record findings while the asset, location and evidence are available. Allow time in the job for photographs, results and the handover. Treat retrospective additions as additions, with an accurate preparation date and an explanation where necessary.
On-site reporting should support the engineer's customer handover. Explain completed work, limitations and next steps, then record the same commitments for the office. Do not promise an update without checking who will provide it.
Give a reviewer responsibility for checking the correct asset, required evidence, unresolved actions and report recipients. Use more detailed technical review where the work requires it. Avoid creating a queue that delays urgent communication or contracted delivery.
If the client challenges a report, review the evidence rather than treating a completed form as conclusive. A clear complaint investigation process helps distinguish missing documentation, missed work and a disagreement about the original scope.
Set an agreed delivery deadline and identify who checks that the report is available to the intended recipient. Sending a document and confirming access are different steps. Keep delivery failures and rejected reports visible until addressed.
Organise records by client, site, asset and visit date. Agree access and retention arrangements appropriate to the contract, applicable requirements and your organisation's policies. Trade-specific records, such as waste duty-of-care documentation, may have their own requirements beyond your general maintenance report.
Digital records support client reporting by connecting forms, evidence and job history in a retrievable record. Your business still needs an agreed reporting standard and people responsible for checking and acting on the information.
Fieldmotion supports mobile forms, photographs and signatures, including offline capture. Engineers can record the visit without waiting to return to the office. Newly captured offline information synchronises when connectivity returns.
Use a direct contact route for urgent findings rather than assuming an unsynchronised record has reached dispatch. Check what any signature acknowledges on the form; a signed visit record should not be treated as proof of satisfaction or unrestricted approval for extra work.
Fieldmotion's facilities maintenance software supports asset registers, service history and records associated with sites or assets. That context helps your team review previous work rather than searching disconnected folders.
Maintain the references and review duplicates. Digitising a wrong asset selection preserves the error more neatly; it does not correct it. Check record quality before relying on a portfolio report or exporting history for a client.
Fieldmotion's customer portal supports access to job information and shared documents. Agree what the client needs to see, which contacts should receive access and how your team checks that required reports are complete.
The wider Fieldmotion platform connects job management and reporting. Use that connection to preserve the visit context, while keeping technical assessment, authorisation and closure decisions with the people responsible for them.
A record of maintenance supports an account of what happened. It does not by itself establish legal compliance, settle liability or guarantee an insurance outcome. Keep the original findings, limitations and supporting documents available for review.
For example, HSE's work equipment inspection guidance explains inspection records in its Great Britain context. Check the specific requirements for the equipment, activity and jurisdiction; do not apply one general reporting checklist as a universal compliance standard.
Likewise, records can help explain a potential claim, but policy terms and circumstances still matter. Your business insurance arrangements should be reviewed separately from the design of your job report.
Test your reporting process by selecting a completed job with an outstanding finding. Ask someone who did not attend the visit to identify the asset, explain the work, locate the evidence and name the person responsible for the next step.
Where they need to search an inbox or phone the engineer, improve that part of the handover. Then review subsequent jobs to see whether the gap has been resolved. This gives you a defined reporting improvement to make before expanding the form or adding another performance measure.
Include enough detail for the client to identify the asset, understand the work and decide what happens next. Match the depth to the visit, contractual requirements and technical evidence needed. A focused report with clear findings is more useful than a long narrative without an outcome.
No. A visit can finish while a defect remains awaiting approval, parts, further work or verification. Keep the defect's status separate from the visit status, with a named owner and next action. Record the evidence and decision supporting closure.
Record the attempted attendance, access restriction, contact made and agreed next step. Check the contract before excluding that time from SLA calculations or counting the visit as completed. Preserve the original commitment and the reason for any rescheduling.
No. A general maintenance report does not replace the inspection record, test result, certificate or other documentation required for a particular activity. Identify the documents applicable to the work and jurisdiction, then file them with the relevant visit and asset record.
First establish whether the work occurred and what authentic evidence exists. Distinguish a report not delivered from a visit not completed. Identify retrospective notes accurately, disclose evidence gaps and agree the appropriate action. Never invent findings or backdate documentation to complete a record.