The Exception List: set up the Jobber Report Scheduler, then read only what needs a person

This is the guide from the Cortex video on the Exception List. It has the same four steps as the video, in the same order:

1. The schedule. Set up Jobber's Report Scheduler for the reports you already read, so the data arrives without anyone exporting it.
2. The rule. Write one line per problem, such as a finished job with no invoice, and list only what breaks a rule.
3. The connection. If an agent builds the list, a company admin authorizes it through Jobber's API, and the agent renews its access as it goes.
4. The check. For the first few weeks, someone compares the list with the real reports.

You can do steps 1, 2 and 4 this week without any new software. Step 3 is for when you want the list built for you every morning.

Step 1, the schedule

Jobber keeps its reports under Insights, then Reports, on Jobber.com, and you need to be an admin or have the Reports permission to see them, according to Jobber's Reports basics page. The same page says Email CSV sends a .csv of all or selected columns to your signed-in email, and that the Report Scheduler app in the App Marketplace can be set up to export and email reports automatically on a schedule.

Settings we suggest starting with:

Report	How often	Why it feeds the list
Invoices (invoice and payment)	Daily	Unpaid and overdue invoices
Jobs	Daily	Finished jobs, and whether each one has an invoice
Quotes	Daily	Quotes that went out and never came back
Client balance summary	Weekly	Clients whose balance keeps growing
Visits	Daily	Tomorrow's visits with no one assigned

Two limits from the same Jobber page: the Taxation, Waypoints and Job Follow-ups reports cannot be exported. If one of your rules depends on them, someone checks those in Jobber directly.

Send the reports to one shared inbox the office can see, not to the owner's personal email. That way the list does not stop when someone is on holiday.

Step 2, the rule

A report is a pile of rows. A rule picks out the rows that need a person. Write each rule as one plain sentence first, then turn it into a filter.

Rules to copy. The day counts are our starting suggestions; change them to fit how your company works.

Rule	List it when	Who acts
Finished, not billed	A job is completed and has no invoice after 1 working day	Office manager
Quiet quote	A quote was sent more than 7 days ago with no answer	Salesperson
Overdue invoice	An invoice is more than 30 days past due	Office manager
Growing balance	A client's balance went up two weeks running	Owner
Unassigned visit	A visit tomorrow has no one assigned	Dispatcher

Keep the list short. If a morning list runs past ten lines, a rule is too loose; tighten it before you add another one.

What a morning list looks like (the company and numbers are examples):

Arctic Air, Tuesday 6:00 AM Job #5521 Furnace repair, done Oct 20, no invoice (office) Quote #812 Mini-split, sent Oct 9, no reply (sales) Tomorrow: 1 visit with no tech assigned (dispatch)

Step 3, the connection

To have an agent build the list every morning, it reads Jobber through the API. Jobber's developer getting-started page says the API uses OAuth 2.0 rather than API keys, runs on GraphQL with a single endpoint, and is authorized by a company admin. What the builder has to handle:

• Renewals. Jobber's app authorization docs say access tokens expire after 60 minutes, with a refresh token to get a new one. A list that stops arriving is usually a connection that stopped renewing.
• Rate limits. Jobber's rate limit page gives 2500 requests per 5 minutes. A morning list needs a small part of that; pulling years of history at once does not fit, so the first sync runs slowly.
• Webhooks. If the build listens for changes, Jobber's webhook docs say a webhook must be answered within one second and may be disabled if responses are slow or erroring.
• Draft apps. Jobber's custom integrations page says API access is blocked if a Draft app connects to more than 5 paying Jobber accounts. That matters to a builder serving many companies, not to you, but it is a fair question to ask them.

The agent only reads. It writes the list and nothing else. If anything on the list needs action, a person in your office takes it, which is how our daily owner briefing works too.

Step 4, the check

Jobber's own help page on creating a custom report with Jobber AI says the Custom Report Builder is on the Plus plan, that only Admins can create and access those reports, that reports running longer than 5 minutes time out, and that Jobber AI can make mistakes, so you should verify the data. The same caution applies to any list an outside agent builds.

It is a common worry. In the Federal Reserve Banks' 2026 report on employer firms, 46% of small firms using AI named accuracy as an obstacle.

A check that takes ten minutes a day:

1. Pick two lines from the list and find them in the Jobber report. Are they right?
2. Pick one rule and scan the report for a row it should have caught. Did it?
3. Note any miss and the rule it belongs to. Fix the rule, not the list.

After three weeks with no misses, check once a week instead.

How to tell it worked

• The reports arrive in the shared inbox every morning without anyone exporting them.
• The list fits on a phone screen most days.
• Finished jobs get invoiced within a day, because they show up the next morning.
• Your weekly check finds nothing to fix.

For how agents work inside Jobber more broadly, read how an AI agent for Jobber works. If you would like someone to set up the rules with you, your free AI Operations Audit covers it.