Job Life Cycle and Stages

Jobs are a core part of the SingleOps application. Here the stages of the Job are explained in greater detail.

The life cycle of a Job is composed of the following five stages:  

Lead  >>  Proposal  >>  Active Job  >>  Completed  >>  Approved

Even though a Lead represents the earliest possible stage of a Job, a Job may also begin in the Proposal or Active Job stage.  The final two stages of the Job represent a level of 'completeness', but have been separated in order to create and show a system of checks and balances between the field and the back office.  Below is a more detailed description of each stage.

•  Lead  -  A Lead is useful if there is potential work desired by the customer - but you're yet uncertain as to the nature or extent of the work to be done (e.g., you don't yet know what line items would be included) - or if the customer has not yet expressed any interest in having work done (it might be speculative in nature in that your crew lead noticed work that needed to be done to remedy some situation).  NOTE:  the term 'client' is used throughout SingleOps (as there must be a 'client' in SingleOps to associate with the lead) - but that doesn't necessarily mean that you have done work for them in the past.

•  Proposal  -  Jobs in the Proposal stage indicate that the client has yet to agree to having the work done. The Proposal must be accepted by the client before it is converted to an Active Job.  Typically this stage entails a sales rep going on site to look at the scope of the work, adding services to the Proposal, and sending the Proposal to the client. The Job will remain a Proposal until the client accepts or rejects the Proposal.

•  Active Job  -  Jobs in the active stage have been accepted by the client and are awaiting scheduling and completion by your crew(s).  The start and stop dates may not be known at the time the proposal is accepted by the client, but should be updated as soon as the Job is scheduled.

•  Completed  -  Upon completion of work, the SingleOps user can select the 'Complete' button to show the work as having been completed and to be taken to the Job completion page.  The Job completion page will serve as a checklist to have the user review and verify materials and equipment used, as well as ensure accuracy of quantity of materials and the number of labor hours dedicated to the Job.  It may be necessary at this point to modify quantity or pricing which can easily be done within the application.  Once completeness has been verified, the user should click the 'Complete' button once more to mark the Job as being completed. 


This page can also be used to update material and labor quantities without marking the Job complete (for example if the crew needs to come back the following day). In this case, the user should instead click 'Update Visit' which will save the visit with the updated values, but the Job will revert to an active state.

•  Approved  -  The Job approval process is often done by an administrator-level user who is responsible for signing off on the Job's completeness so that the Job data can be synced to QuickBooks.  Once the Job has been marked as approved, the invoice and any associated bills are synced, triggering the invoicing process to the customer.  Job approval is usually best done from the Completed Jobs page.

Was this article helpful?
6 out of 9 found this helpful



Please sign in to leave a comment.