Skip to content
English
  • There are no suggestions because the search field is empty.

Managing service requests

This Section Explains The Typical Journey Of A Service Request, From The Point It Is Received Through To Completing The Work, Checking In And Closing The Job.

1. Receiving the service request

A service request is raised by the client and sent through to your contractor portal. You may also receive an email notification to let you know that a new request requires review or action.

2. Reviewing and accepting the request

The contractor admin should review the service request in the portal, checking the job details, site information, priority, attendance requirements and any instructions provided by the client.

Depending on the client setup, the contractor admin may need to accept the request before it becomes an active work order. If the request cannot be completed, the admin should follow the agreed process for rejecting or querying the request with the client.

3. Assigning an engineer

Once the request has been accepted, the contractor admin assigns the work to the appropriate engineer. This should be based on the engineer's skillset, availability, location and any client-specific requirements for the job.

Before attendance, make sure any required documentation, such as RAMS, permits or access information, has been reviewed or uploaded where required.

4. Checking in through the admin portal

If required, the contractor admin can check an engineer in through the admin portal. This may be used when the engineer is unable to check in through the app, has connectivity issues on site, or the client process allows admin-assisted check-in.

Admin check-in should only be used where appropriate, and the job record should still reflect the correct attendance time and engineer details.

5. Checking in through the Engineer App

When the engineer arrives on site, they should check in using the Engineer App. The exact steps may vary depending on the client setup, but the process typically includes selecting the work order, confirming attendance, completing any start work checks, and providing location or access validation where required.

Once check-in is completed, the work order will move into an in-progress state so the client and contractor admin can see that the engineer is on site and work has started.

6. Carrying out the work

While on site, the engineer carries out the required work in line with the job details and any client instructions. During the visit, the engineer should use the app to add updates, notes, photos, documents, hazard information or follow-on requirements where needed.

Keeping the work order updated throughout the visit helps the contractor admin and client understand what is happening in real time and reduces the need for follow-up queries after the job.

7. Checking out and closing the job

When the work has been completed, the engineer should check out through the Engineer App. This usually includes selecting the outcome or resolution, adding completion notes, uploading any required photos or evidence, and confirming that they are leaving site.

Depending on the client setup, the engineer may also need to capture site contact sign-off, complete final checks, provide location confirmation or enter an access code before the job can be closed.

Once checkout is complete, the work order will move into the relevant completed or closed status. The contractor admin should review the job record to make sure all required information has been captured and that the work order is ready for any next steps, such as invoicing, follow-on work or client review.

Tip: The exact workflow can vary by client, so always follow the process and required fields shown on the work order. If a check-in, check-out or closure step is missing or unclear, contact your contractor admin or client contact before progressing.