There are two main types of Jobs in SingleOps: One-Off & Recurring. By default, all Jobs in SingleOps are set as One-Off & will need to be switched to Recurring, as needed.
In this article:
One-Off Job
One-Off Jobs are used when the services requested by the Client will only occur once & generally over a short period of time (one day or a few consecutive days). Examples of a One-Off Job would be removing a tree, pruning work, mulching, or even some landscape installs like a small patio.
On-Off Visit Frequency
| Visit Frequency | Common Services | Common Use Case |
| One Day | General Tree Care | |
| Multi-Day | Design build, Install |
Recurring Job
Recurring Jobs in SingleOps are Jobs with more than one Visit. The work on these Visits can be identical (the same lawn mowing each week) or varied (six different PHC treatments throughout the year.)
Recurring Visit Frequency
| Visit Frequency | Common Services | Common Use Case |
|
Weekly/ |
|
|
| Custom |
|
|
| On-Demand Jobs | With On-Demand Jobs, Proposals can be created with unknown Visit dates, number of Visits, or the exact Line Items for each Visit. |
|
Recurring Invoice Type
| Invoice Type | Detail | Example |
| Per Visit Invoicing | Per Visit invoices will create 1 invoice for each Visit on the Job. The invoice date will match the Visit start date. |
A customer wants their lawn mowed once per week, and asks for the bill to be sent after each mowing for the price of that mowing service only. This type of bill is Per Visit because the Invoice is based on the Work Completed |
|
Fixed Invoicing |
Fixed Invoices are created on a pre-determined schedule for a pre-determined amount, and are billed separately from the work. |
A customer wants their lawn mowed once per week, and asks to be billed the same about each month, regardless of how many services are performed in that month. This type of bill is Fixed because the amount and timing of the Invoice is pre-determined, and is not affected by the work that occurs during that time period. |
Estimation Type
"How is this job estimated?"
| Estimation Type | How it's used | When to use/not use | Example |
| Apply all Items to each Visit |
|
Use when the same work occurs on every Visit. Do not use if one or more services should not be included on every Visit in the Job (Use Specify Items for each Visit estimation instead) |
A client wants her lawn mowed and shrubs pruned every other week. The Line Items "Mowing" and "Pruning" could be included using Apply all Items to each Visit Estimation because those services will occur on every Visit in the Job. |
| Specify Items for each Visit |
|
Use when the work on at least one Visit varies from other Visits on the Job. | A PHC Job requires six different treatments throughout the year. Each treatment is a unique Line Item. This requires Specify Items for each Visit estimation so that each Line Item can be assigned to a different Visit in the Job. |
Comments
Hello, is there any further context for best practices on a Multi-Day / One-Off job that is a Large Scale Design / Build Install?
What is the in house suggestion for this scenario, and whether using PROGRESS BILLING to dictate Invoicing (ie, man hours would be a generic enough method to create a normalized process if cannot determine based off of line items)
OR
Is it better to just create as regular DB One Off, and then have the START / STOP dates set and then adjust the STOP date accordingly in real time pending daily completion of that job?
Thank you!
Check out the 2 articles below for our best practices in managing Design Build in SingleOps:
Create a Design Build Proposal
Design Build Best Practices
Please sign in to leave a comment.