Work Reports
Digital work reports with forms you configure yourself: each service type has its own questions, with the mandatory ones flagged so a report cannot be closed half done.
A generic report is useless. What has to be checked on an air conditioning service looks nothing like what has to be recorded on a pest control treatment, an electrical installation or a fire extinguisher inspection. That is why forms are defined per service type, with the right format for each question (text, number, date, yes/no, option list, photo or signature) and with answers able to trigger an action, such as opening an issue or requiring a photograph.
Questions drill down to whatever level of detail is needed: the whole job, each area of the site, or each machine being worked on. That is what lets you document a contract zone by zone and unit by unit, with evidence from every visit.
The result is a document with real value: it supports invoicing without argument, evidences compliance with the work plan for the customer or an audit, and lets the next visit know what the previous one found.
Forms that fit
A generic report documents nothing
What has to be checked on an air conditioning service looks nothing like what has to be recorded on a pest control treatment, an electrical installation or a fire extinguisher inspection. When the report is the same for everything, it ends up as a free-text box where each technician writes whatever they see fit.
Here the form is defined per service type, with the questions that job requires and the right format for each one:
- Text, number or date for readings, measurements and references.
- Yes or no for checks that only admit two answers.
- Option lists when answers need to be comparable between visits.
- Photo or signature when the evidence is the record itself.
Mandatory ones are flagged, so the report cannot be closed half done. And a specific answer can trigger an action: opening an issue, alerting the office or requiring a photograph before continuing.
How far it drills down
Questions per zone and per machine, not just per visit
A cleaning contract is not fulfilled "in the building": it is fulfilled on each floor, in each washroom and in each common area, and the customer reviewing it wants to know what was done in every one. The same goes for landscaping with each green space, or maintenance with each unit in a plant room.
That is why questions can drill down to three levels:
- The whole job, for what is checked once.
- Each area of the site: a floor, a washroom, a route, a park, an estate.
- Each machine being worked on, with its readings and its condition.
That detail is what turns the report into proof of compliance with the work plan, both for the customer and for a quality or food safety audit.
What it is for afterwards
A properly made report serves three purposes
Invoicing without argument. Billable items (hours by technician grade, travel, materials) come from the report itself, signed by the customer. When an invoice is questioned, the document is there.
Proving compliance. In sectors with a documented work plan (food, healthcare, industry) the history of reports by area and date is exactly what an auditor asks for, and it needs no preparing.
Letting the next visit know what the last one found. The technician going back in three months reads what condition the equipment was in, what was replaced and what was left pending, even if it is somebody else. Without that, every visit starts from scratch and diagnoses get repeated.
Clearing things up
Frequently asked questions
Answers to what we get asked most.
Can I define my own forms?
Yes, per service type, with the right format for each question: text, number, date, yes/no, option list, photo or signature. Mandatory ones are flagged, so a report cannot be closed half done.
Can checks be done per zone?
Yes. Questions drill down to the whole job, to each area of the site (a floor, a washroom, a route, a green space) or to each machine being worked on. That is what lets you document a cleaning or maintenance contract room by room.
Can an answer trigger an action?
Yes: opening an issue with its follow-up, alerting the office, or requiring a photograph before continuing. It is how what the technician spots stops depending on them remembering to mention it when they get back.
Does the report stand as evidence in an audit?
Yes, and it is one of its main uses. The history of reports by area and date, with their photos and the customer's signature, is exactly what an auditor asks for to verify compliance with the work plan, and it needs no separate preparation.
Field service and after-sales
Digital work reports with forms built to your needs, a mobile app for technicians, on-screen customer signature and invoicing with no waiting.
Field Workers Mobile App
Technicians carry their working day on their phone: the day's jobs on a map, the customer and machine information before ringing the bell, and the work report closed on the spot.
View moduleEvents
Visual scheduling of jobs on a calendar, with technician and vehicle assignment and each person's workload in view.
Issues
Issues the technician spots during a job are logged and followed through until they are fixed.
Work Areas
Split the customer's site into areas with their own questions and checks: a floor, a washroom, a green space, a route, a building or a playground.
Workshop Services
Complete management of workshop repairs: equipment intake, diagnosis, quote to the customer, repair and handover, with time logged and spare parts recorded.
View moduleMachinery
An inventory of machines and equipment, yours or your customers', with location, serial number, warranty, running hours and full service history.
View module