What the Overview pages are for
The state of all the work at once: what is active, what is due, what is late, and every job in one grid.

Jobs is the operational core of InspectSync. A job is either an Inspection or a Service, and this module is where jobs are created, scheduled onto technicians, tracked through the field, reviewed when they come back, and turned into service quotes for the deficiencies they find.

The Overview group is where a day in the office starts: a dashboard that says whether the workload needs attention, and the master grid that holds every job of both types.

Dashboard

Open Dashboard
Who it is for
The office manager and the dispatcher, first thing in the morning.
Without it
"How much is on the board this week and how much of it is late?" means scrolling a grid and counting. Nobody counts every day, so late work is found when a customer asks about it.
What it shows
Four cards: Active Jobs, Due This Week, Overdue and Completed This Month, each drilling into All Jobs at that bucket. Two charts beneath them: Job Activity over the last six months, and the Job Status Distribution.
What it is worth
  • The workload in four numbers. Active, due, late and done. Enough to know whether today needs a plan.
  • Overdue is a list, not a statistic. Click it and the grid arrives already filtered to exactly those jobs, with the same count.
  • Six months of shape. Job Activity shows whether volume is climbing toward a peak the team is not staffed for.
Pays for itself the first morning Overdue reads higher than yesterday and the dispatcher acts on it before the phone rings.

All Jobs

Open All Jobs
Who it is for
Anyone looking for a job. The office, dispatch, billing, the account manager taking a call.
Without it
Inspections and services live in two lists, and a customer asking "what do you have open for us?" needs both checked. Finding a job by its PO or reference number means asking whoever created it.
What it shows
The master grid of both job types. Search by customer, building, address or reference number. Multi-select filters for Status, Priority, Type, Office, Tech, Attribute and Metro, each rendering as a chip once applied and remembered between visits. Every row shows its assignees, and the Actions column opens the job's dashboard, its edit page, or deletes it. The grid exports to a spreadsheet.
What it is worth
  • One grid, both job types. Inspections and Services are this same grid pre-narrowed, so a search here is the whole answer.
  • Filters that stay put. A dispatcher who works one office and one metro sets it once and finds it set tomorrow.
  • Every dashboard and every analytics card lands here. The Jobs grid is the drill target for the module dashboard, the Analytics cards and the Forecast pages, so a number anywhere in the app can be traced to rows here.
Pays for itself the first customer call answered from one search instead of two lists and a follow-up call.

Where to go next

  • To put a pending job on a technician's day, use Scheduling. All four scheduling views draw from the same unscheduled jobs.
  • To see only one job type, open Inspections or Services. They are this grid, pre-narrowed.
  • For the company-wide picture across quoting, service and inspections, see the Analytics Overview.

Good to know

  • A job is one of two types. Inspection or Service. The type decides its form, its dashboard and which grid it appears in besides this one.
  • Every job has a dashboard. Open one and the Lineage rail shows where it came from (national account, customer, building, contract) and what it produced (service quotes, services, reports).
  • Every change is recorded. The History button on a job's dashboard opens its audit trail: the job and everything that hangs directly off it (assignees, scheduled days, items).
  • Deleting is a confirm, not a click. Delete asks first, and the dashboard's Cancel and Completed actions change status rather than removing the record.