WorkOrderPro product guide · Updated 12 September 2026.
Generator service software starts with a reliable equipment record
A generator maintenance business needs to connect each request with the correct site and machine before it can prepare a useful appointment. A customer may report that backup power is unavailable, while the office still needs to establish which unit is involved, what the customer observed and who can provide access. A useful work order preserves those facts without turning the initial report into an unverified diagnosis.
WorkOrderPro brings customer, job-site, equipment and work-order records together with scheduling and maintenance-contract workflows. For a generator service team, the practical test is whether those records support planned maintenance, an unexpected breakdown and a later return visit. Each scenario needs a clear brief and outcome, but the next action can differ considerably. The office should not have to reconstruct the difference from private messages after the technician leaves.
This guide covers administration for South African generator maintenance and backup-power service businesses. It does not prescribe service intervals, electrical procedures, operating limits or emergency actions. Those decisions belong to the applicable manufacturer guidance, responsible specialists and site procedures. The software evaluation should establish how their decisions are recorded and handed over, rather than implying that a job-management application controls the equipment.
Identify the account, physical site and generator
The customer paying for service may manage several premises, each with more than one unit. A site contact may arrange access while another person approves additional expenditure. Record these responsibilities distinctly. The customer record identifies the commercial relationship; the job site identifies the location where work happens. A contact name alone is not a reliable substitute for the specific site and machine.
WorkOrderPro equipment records include type, make, model, serial number, installation date and warranty expiry. Demonstrate how the equipment is linked to its job site and how your team will use the available history. Confirm the intended plan includes the workflow you need. If your register requires additional structured fields such as rating or fuel type, demonstrate how those requirements will be represented rather than assuming they already exist.
Use two generators at one site in the trial. Give them recognisable labels and check that an employee unfamiliar with the customer can distinguish them. Where a serial number is missing or unreadable, record the information as outstanding. Do not invent identifiers to complete an import. The goal is a record that refers reliably to the physical unit your team is attending.
Separate planned maintenance from a breakdown request
A planned service and a breakdown callout have different starting information. The planned visit can refer to an agreed scope and prepared schedule. The breakdown request begins with an observed problem that still needs assessment. Preserve that distinction in the work order so the attending person understands the purpose of the appointment and the customer understands what has actually been promised.
For a breakdown request, record the customer's description, location and relevant contact information without supplying a technical conclusion. Identify the person who will review urgency and decide the next operational step under your established procedures. A priority label helps communicate the request within the system; it does not establish a guaranteed response time or replace the site's own emergency process.
During evaluation, create one planned service and one unexpected request for the same customer. Ask the dispatcher to explain the difference from the saved records. The workflow should make the intended attendance, known facts and outstanding questions clear. If both jobs look identical except for a title, improve the brief before using the system for a larger service portfolio.
Configure service schedules from verified requirements
Determine the maintenance schedule through the relevant equipment guidance, agreement and responsible specialist. Some businesses need to consider calendar dates alongside recorded usage. The administrative system should reflect the process you have established, but a recurring date alone does not prove that a particular unit is due or that every condition affecting service has been considered.
WorkOrderPro includes maintenance contracts for repeated work. Demonstrate how a due contract generates a work order and which details the office must review. Do not assume that the application automatically reads runtime meters, receives telemetry or creates jobs when a machine crosses a usage threshold. If those capabilities are essential, ask for a demonstration of the exact integration and resulting workflow.
Test the schedule with a representative agreement and a change in the information used by your service planner. Confirm who reviews the new information and updates the next action. A useful process makes that responsibility explicit, especially when the timing of a visit depends on a value reported by the customer rather than a fixed date alone.
Record runtime observations without implying live monitoring
If your operating process uses runtime readings, identify how the value was obtained and which unit it belongs to. A customer-reported value, an observation during attendance and a value received through another system have different contexts. Preserve the relevant date, source and unit of measure in the demonstrated workflow. An isolated number is difficult for the office to interpret later.
Verify any need for structured meter fields, history charts, threshold alerts or imports separately. General job notes can preserve an observation, but they should not be described as an automated condition-monitoring system. The responsible person still needs to decide what the information means for service planning. Software should not silently convert an incomplete or uncertain reading into a technical conclusion.
Use a trial where the office receives an updated reading after the initial appointment has been proposed. Ask the planner to locate the earlier context and record the agreed next step. This tests whether the information remains attached to the correct equipment and whether the team can explain why the plan changed without relying on the memory of the person who answered the call.
When preparing a historical import, distinguish recorded readings from dates on old service documents. A visit date does not establish the meter value at that visit, and a later reading should not be copied backwards to fill a gap. Keep the available source reference and identify incomplete history. Ask the planner to review one imported unit before processing the rest, especially where the customer has changed the equipment or the identifying label differs from an older document. This protects the usefulness of future comparisons without manufacturing a complete history.
Prepare the service brief and materials together
A useful planned-service brief identifies the unit, agreed work, appointment and relevant access arrangements. The attending technician should be able to distinguish confirmed information from an item that still needs checking. Include the operational references your team needs, while keeping sensitive site details visible only where appropriate. A copied historic note should not be assumed to describe current access conditions.
Review material readiness before confirming the visit. A quoted service item does not prove that the intended consumables or replacement parts are available. Agree who checks the required materials and how an exception will be communicated. The responsible person must confirm suitability from reliable equipment information; a searchable catalogue is not a manufacturer compatibility engine.
Evaluate a planned visit with one missing preparation item. Ask the office to identify whether the job remains ready, who owns the outstanding action and what the customer has been told. This is a more useful test than an ideal example in which the equipment details, stock and access arrangements are all assumed to be correct without review.
Schedule the attending team and manage changes clearly
WorkOrderPro includes dispatch and scheduling workflows for assignments and appointments. Test the roles your business uses, including an administrator who receives requests and a dispatcher who moves work. If a lead and supporting crew attend together, include them in the example. Assignment in the software does not establish qualifications or decide which people are appropriate for a particular technical task.
Use realistic appointment durations and review travel, access and preparation as part of your own planning. A calendar does not remove those constraints. For multi-site customers, check that the attending user can distinguish the location and current purpose of each visit. An appointment title should not be the only place where the relevant unit or site is identifiable.
Include a reschedule caused by changed customer availability or an unresolved preparation item. Inspect what the office and field users can see after the update, then identify who informs the customer. The saved record should show the current commitment clearly enough that the attending team does not need to compare an old document with a separate message thread.
Make breakdown findings useful to the next person
After attendance, separate the reported symptom, the technician's observations and the proposed next action. A completed assessment can still leave the repair awaiting a quotation or part. The record should explain why the work remains open and which decision is needed. A generic status cannot carry all of that meaning on its own.
Use job photos where they help identify the equipment or explain a recorded observation. Add a description that tells the reviewer what matters in the image. Verify any requirement for specific technical forms or structured test results rather than assuming general notes and photographs provide them. This guide does not supply testing procedures or values; the responsible specialist determines the appropriate work and interpretation.
Ask an office colleague who did not attend to explain the saved outcome. They should be able to identify the affected unit, work performed and next action without inventing a diagnosis. If another technician must return, prepare a brief that preserves the earlier context and explains what is now ready. A good handover reduces reliance on the original attending person's availability.
Keep quotations and customer decisions traceable
Additional work needs a clear proposal that distinguishes labour, materials and the agreed scope. Use the service catalogue as a starting point for consistent descriptions, then explain the actual job. A broad line such as “generator repair” can be insufficient when the customer needs to know which unit and work are included. The office reviewer should understand the proposal without the original phone conversation.
Identify who can approve the work. A facilities contact may need to refer expenditure to another person, and a site escort may have no commercial authority. Keep an outstanding decision visible and assign responsibility for follow-up. Sending a quotation or completing the assessment should not be treated as proof that additional repair work has been authorised.
| Situation after assessment | Record to preserve | Next action to assign |
|---|---|---|
| Information incomplete | Equipment identifier or unresolved question | Obtain reliable information before finalising the proposal |
| Repair proposed | Findings and clear proposed scope | Request the relevant customer decision |
| Part unavailable | Required item and current preparation status | Confirm availability before committing a return date |
| Further specialist review needed | Purpose and relevant observations | Arrange the review through the responsible person |
| Agreed work completed | Work performed and outcome | Review the customer handover and billing details |
Review stock movements and work outcomes separately
A stock movement explains a quantity change, while the service record explains what happened to the customer's equipment. An item issued to a technician might be used, returned or found unsuitable. The office needs the relevant explanation before preparing a charge or arranging another purchase. Do not assume every quantity leaving stock became a completed repair on the associated visit.
If inventory is important, demonstrate WorkOrderPro's parts and van-stock workflows in the intended plan. Start with a small set of actual item types and test a receipt, correction and return. Agree descriptions and units before importing a large catalogue. If you require supplier ordering, batch traceability or a specialist purchasing process, verify those requirements separately.
Include a material exception in the trial handover. Ask the billing reviewer to distinguish the planned item from what was actually used. The result should explain the customer impact and the inventory correction without hiding either. This makes the evaluation relevant to ordinary service administration, where preparation and attendance do not always follow the first plan exactly.
Prepare a completion record that the customer can understand
The outcome should state what was performed and what remains open. If the attending person recorded further recommendations, keep them distinguishable from completed work. The office should know who owns any follow-up and what the customer was told. A completed status should not silently imply that every possible issue at the site has been resolved.
Inspect the customer-facing documents during evaluation. Check the site and equipment references, work description, relevant line items and total. If a commercial account requires a purchase order reference or a particular report format, demonstrate how the office produces it. Multiple sites under one customer do not automatically provide every consolidated reporting or procurement feature a larger account might require.
Then test a question about an earlier visit. Ask someone who did not attend to find the right unit and explain the recorded work. A later reported problem needs its own assessment and commercial decision; preserve the new report without rewriting the earlier outcome. This keeps the service history useful without assuming that every later issue has the same cause or treatment.
Trial the field workflow on real devices
The field experience should be evaluated on the devices and connections your team uses. Test the brief, outcome record and photographs under realistic conditions. If an action is essential during weak connectivity, demonstrate that action and verify what reaches the office after reconnection. Do not assume every approval, attachment or edit works offline because a page can remain open.
Train one office reviewer and one attending user on the same planned-service example. Then add a breakdown and return visit. Ask both people which information was useful and where the next action was unclear. Their feedback can improve the record format before the entire team adopts different conventions or imports a large volume of inconsistent history.
Begin with a limited customer and equipment sample. Assign responsibility for checking identifiers, service descriptions and current contacts. Expand the data only when the team can repeat the workflow and recognise an incomplete handover. Account creation is not the same as activation; the useful milestone is a real job that another employee can understand and review.
Review the full active-team price and remaining requirements
WorkOrderPro's active-user count includes administrators, dispatchers and field users. Disabled accounts are excluded. Two field technicians, one service planner and one active office administrator therefore mean four active users. Review the current base fee, per-active-user charge, billing cycle and VAT on the pricing page. Confirm each essential workflow is available in the plan being considered.
Assess the purchase using your own service examples. Note missing equipment references, unclear return-visit actions and time spent reconstructing outcomes before and during the trial. These observations can show where administration becomes clearer, but they are not guaranteed savings. Avoid treating an expected improvement in service coordination as a promise of equipment uptime.
| Evaluation item | Evidence to collect |
|---|---|
| Equipment identity | Two units at one site remain distinguishable |
| Maintenance planning | A due job is generated and checked by the office |
| Usage information | The source and context of a reported reading remain clear |
| Breakdown handover | Another employee can identify the next action |
| Customer output | The unit, agreed work and outcome are understandable |
| Subscription decision | All active users and required features are included |
Before rollout, list requirements that remain unproven, especially telemetry, usage-triggered scheduling or specialist reports. Decide who owns those processes and whether a separate system is needed. Move forward when the demonstrated workflow fits your operation and the team understands both its benefit and its limits, with a clear owner for the first review of completed jobs.