Assigned engineers
Visits and report drafts
Capture the work against the correct visit.
What to do
- Open your assigned work order. Confirm the case, equipment, description and previous visit/report context.
- Start the visit using the available action. Open its report draft; the report stays linked to that visit and work order.
- Enter the work performed and save. Wait for confirmation before leaving. Reopening a saved draft should show the server-confirmed content.
- If the system reports a concurrent version change, preserve your unconfirmed information and reload the latest record. Compare changes before editing again.
- Complete the actual labour/parts information and check out when the visit is finished. Follow the report confirmation workflow to finalize the report.
- Open the work order and choose Finish this job. Follow the open points for your role: finish the visit, complete the checklist, review saved time and material, prepare the report and obtain customer confirmation. Refresh after saving. Service closure and billing are reviewed separately.
- In Change history, History author filters all recorded changes, My recorded changes or System actions within this record. The latest-change summary and older/newer pages follow the chosen filter. Changing the filter returns to its first page. My recorded changes uses your current signed-in identity; it does not show changes whose personal attribution was removed. Assignment and the customer signatory remain separate.
- Start the visit when work begins. Save the report text, checklist and actual work separately. End the visit when the work is finished, then review and prepare the saved report for the customer.
- Preparing freezes a version; it does not sign it. Record the customer's acknowledgement or the genuine signature exception. The coordinator closes the service case separately; billing and invoices remain separate.
- If a save or visit end is unconfirmed, confirm that same action again. Do not enter a second action. A real concurrent change requires comparing the saved report; it is never overwritten automatically.
Before you continue
An engineer’s operational scope depends on assignment. Administrative access alone does not make someone the assigned engineer.
No durable offline draft or offline signature is promised. Do not assume typing into a disconnected form saved anything.
Dispatch readiness in the work order shows ready or still to clarify, the saved reason, responsible person and next action. Unknown information stays unresolved. Record site access, customer confirmation, operational authorization and required parts deliberately; this does not approve costs, warranty or safety. On hand minus all reservations is available; required parts must be reserved for this order. Rescheduling requires an explicit choice to release or retain remaining reservations and invalidates prior appointment evidence. Unstarted cancellation releases remaining reservations; return consumed parts first. Started visits and signed records cannot be cancelled here.
Tracked findings are created deliberately from an applicable failed point in an immutable report version. The finding pins the device, report version, template version and measured evidence; the signed original stays unchanged. Record an active owner, next action and review deadline. Deferred requires a reason; repair declined remains unresolved. Resolution needs a successful later reinspection at another visit for the same device/customer and exact template version, plus explicit human confirmation. Link only existing follow-up orders or offer versions; this creates no extra work and approves no costs. Customer updates have a separate title/message, publication and withdrawal; internal notes and offer references never appear automatically. Existing source-report sharing and customer access must remain active.
Unconfirmed report text stays only in this open page when you go back and forward. Reloading or closing the browser loses it. Saved drafts stay on the server. Save or explicitly discard before leaving; discarding never deletes a saved report.
A signature exception is recorded. Billing is still blocked; the billing team must review the exception and the applicable policy.
A current draft blocks case closure, including an amendment draft. Older frozen versions do not block it. A recorded signature exception does not add a new signature requirement for closure; billing remains subject to its existing checks.
The source revision records the original finding. Opening the report may show a newer working version; it does not replace this evidence.
A finding needs a later successful inspection of the same point, device, customer and template version at a different visit. Choose its report revision as evidence. Customer publication is a separate explicit action.
At the top of a report, use Next steps for this report to jump to version and acknowledgement, tracked findings, actual work and, with billing permission, commercial handover. These links keep you in the same report and do not save, publish or approve anything. Review the current version and each section’s prerequisites; coordination handles PDF sharing, the assigned technician handles acknowledgement, and billing handles commercial review.
Use Finish this job in the work order to follow the saved visit, report and case references through completion. Open points are grouped under their source; a report heading shows its saved revision, not a new invoice or authority acceptance. Use your role’s action links; points for another team remain visible for handover. Links open the matching visit, report confirmation, actual work, commercial review or existing billing package; they do not save, sign, send, close the case or create an invoice. A closed case must be reopened with a reason before additional visits or report drafts. Existing reports and billing reviews remain available within access. If the overview cannot be verified, refresh it: no completion is assumed. The displayed check time is a saved-state read, not a live guarantee; each subsequent action checks its own current permissions and versions.
A save or visit-end response is confirmed only when its record, source and revision match the action. If the confirmation is incomplete or belongs elsewhere, the original attempt and report text stay in this open page. Confirm the same action or check the saved record; do not create a second action. A confirmed older save can return a newer report version, which must be reviewed separately.
Questions and troubleshooting
Can two engineers overwrite the same draft?
Version checks reject stale saves. A conflict requires review; it is not a reason to repeatedly press Save.
Can I start another report for the same equipment?
Use the correct new case/order/visit relationship. Do not reuse an old report just because the asset is the same.