Run multiple jobs under one customer with the job picker, the job scope banner, and per-job stages.
One homeowner, many projects: a roof after the storm, gutters in the spring, siding next year. Revolve Core models this as multiple jobs under a single customer, so the relationship history stays in one place while each project keeps its own scope, schedule, stages, and money.
§Add a job
From any customer, open ⚡ ACTIONS and choose + ADD JOB. Resist the urge to create a second customer record for new work — a duplicate splits the history, the contacts, and the financial picture across two records forever.
§The job picker and scope banner
When a customer has multiple jobs, opening them from the list routes you through a job picker so you land on the job you came for. Inside the workspace, a job picker row and a job scope banner control what you are looking at: ALL JOBS shows everything on the customer, while picking one job narrows most tabs to that job’s items. The banner keeps the active scope visible, so you always know whether you are seeing one project or all of them.
§What can be scoped to a job
- ◆Photos — filter the gallery by job, and assign photos to a job.
- ◆Documents —
⊞assign documents to a job from select mode. - ◆Work orders, tasks, and notes — each can be assigned to a specific job.
- ◆Invoices — assign with the
⊞ JOBaction so billing lines up with the right project.
§Stages are per job
Each job carries its own stage pipeline, seeded from your company’s template for that trade. The Active Job widget on OVERVIEW and the stage tracker on TIMELINE both follow the job you have in scope, and ✎ STAGES customizes that job’s stages without touching the customer’s other jobs. A Days-In-Stage timer widget can keep the current job’s pace on the dashboard.
§Shared or per-job photos and docs
On customers with two or more jobs, the ⚡ ACTIONS menu gains a MULTI-JOB SETTINGS entry. It controls how Photos and Documents behave across the customer’s jobs: SHARED keeps one library that every job draws from, while PER JOB splits them so each job carries its own photos and documents. Pick SHARED when the projects are on the same property and the same pictures matter to both; pick PER JOB when the jobs are genuinely separate and mixing their files would create noise.