Visit Thresholds

Visit Thresholds are price bands that tell the system how many project manager (PM) site visits a job of a given value should receive and how long the job is expected to run. Operations and management use them to keep supervision consistent across small and large jobs. Found under Settings > Entities > Visit Thresholds.

What you see

The list shows every active band, 25 per page, oldest first:

Column	Meaning
Low Threshold	The bottom of the job price band, shown in dollars.
High Threshold	The top of the job price band, shown in dollars.
Visits Required	How many PM visits are recommended for a job whose price falls in this band.
Expected Duration (weeks)	How many weeks a job of this size is expected to take. The visits are spread across this period.
Actions	Edit (pencil) and Delete (bin).

A count of the total bands sits under the table. Deleted bands are kept in a separate Deleted list where they can be Restored or Deleted permanently.

Who can open this page

The Entities menu, including Visit Thresholds, is visible to anyone with the quote templates permission (management, operations and accounts by default). See Roles and Permissions.

What you can do

Create a band

1. Click the green + button at the top right of the list.
2. Enter Visits Required (whole number, at least 3).
3. Enter Expected Duration in Weeks (whole number, at least 3).
4. Enter Low Threshold and High Threshold in whole dollars, for example 150000 and 500000.
5. Click Create.

The system refuses to save if either threshold falls inside a band that already exists, with the message “There is a threshold already created within this range.” Bands must not overlap.

Edit or delete a band

Click Edit to change any of the four values (the same overlap rule applies) or Delete to soft-delete the band. A deleted band no longer affects visit suggestions, but you can restore it from the Deleted list.

How it works behind the scenes

The bands are read wherever a sub job is being scheduled:

• Jobs Board and Planning Board sub job window. When you open a painter sub job to set its start date, the window shows “Based on a Job Price of $X a recommended total of N visit(s) are suggested for this job over W week period”, using the band whose low and high thresholds bracket the master job’s price. If the job already has a PM, a Suggest Dates button appears (only while the sub job has no visits yet) alongside Add Date. Suggest Dates books the start date as the first visit and then checks the PM’s calendar for those days, clearing any date that is already full so you can choose another. See Planning Board and Jobs Board.
• Project Manager Visits calendar. The same bands are loaded so visits created from the calendar follow the recommended count. See Project Manager Visits.
• Tradesperson job card (ring and book). When a tradesperson confirms the start date from their job card, the system creates the full set of visits automatically: one on the start date, one at the end of the expected duration, and the remaining visits spread evenly between them. Any visit that lands on a weekend is pushed to the following Monday. See Tradesperson App.

The job’s suggested number of visits is saved on the sub job the first time it is calculated, so changing a band later does not alter visits already planned.

Tips and gotchas

• A job price must sit strictly between a band’s low and high values to match. Leave no gaps between bands, otherwise a job priced in the gap will have no suggestion and the sub job window cannot load its visit recommendation.
• Keep a top band with a very high upper limit so large commercial jobs always match.
• The business rule agreed in the ROCH Jira project is that active jobs should be visited roughly every three days. If PMs report long gaps between visits, review the visits and weeks in each band rather than adding visits one job at a time.
• Do not confuse this page with Thresholds, which controls how a job’s price is split into progress invoices.