The Morning Exception Report: an AccuLynx daily report for stuck roofing jobs

This is the guide behind the video: the lines in the order the video gives them, the ReportsPlus report each one comes from, the rule to write for each, and the two ways to feed the agent.

The lines, in order

AccuLynx already does half of the work, because ReportsPlus can email reports on a schedule. But eight emails at six in the morning are not a briefing, so an agent reads them together and sends one message:

1. Stuck jobs. Any job sitting at one milestone past your limit.
2. Permits and supplements. Permits that have not come back, and supplements pending over a week.
3. Quiet estimates. The one most owners miss: an estimate with no activity after three days.

The agent only reads and never moves a job, so you decide who makes the call.

Who this is for

Roofing owners and production managers on AccuLynx who check five reports on Monday and are on a roof by Tuesday. If you want the background on how reporting automation fits AccuLynx, read our AccuLynx reporting automation guide; for agents that do more than read, see the AccuLynx AI integration guide.

What AccuLynx gives you to start

The ReportsPlus page describes a pre-built library with reports on job milestones, permits, supplements, accounts receivable, materials, dead leads and estimates, and says reports can be emailed automatically on a schedule, with recipients, file format, frequency and time set by the sender. You can change columns, filters and groupings. The page does not say which plans include ReportsPlus or what it costs, so confirm that with your account rep in writing before you build on it.

Line by line: the report and the rule

The thresholds are starting points for you to change, not benchmarks.

Line	ReportsPlus report	Rule to write	Shows when
1. Stuck jobs	Job milestones	Days at the current milestone, compared with your limit for that milestone	Over the limit, longest first, with the job's salesperson
2a. Permits	Permits	Permit requested and not back	More than 10 business days, or your county's usual time
2b. Supplements	Supplements	Supplement submitted and still pending	More than 7 days, oldest first, with the amount
3. Quiet estimates	Estimates	Estimate sent with no activity logged	More than 3 days, newest first

Set a limit per milestone, not one for all of them. A job can sit at "Contract signed" for a while waiting on materials and be fine; the same days at "Install complete" with no invoice means money waiting.

What the message looks like

An illustration of the layout, not a result from a roofing company:

Morning Exception Report, Mon 6:30 AM	Example line
1. Stuck jobs	Job 2471, Hendricks, at "Install scheduled" 12 days against your 7
2. Permits and supplements	Permit for job 2480 not back after 11 business days; supplement on job 2466, $2,300, pending 9 days
3. Quiet estimates	Estimate for job 2492 sent Wednesday, no activity

Three lines and four calls to make. A good Monday might have one.

Feeding the agent

Route one: the scheduled emails. Point each ReportsPlus schedule at an inbox the agent can read, in a file format it can open (a spreadsheet export works best). This needs no developer access, and the numbers match what your staff see in AccuLynx. Schedule them to land 30 minutes before the message goes out.

Route two: the AccuLynx API. AccuLynx's documentation says you need an active account and an API key, and that its support teams cover the web and mobile apps, not API questions. The API index lists sections for jobs, estimates, leads, reports and financials, including job milestone history. Limits are 30 requests per second per IP and 10 per second per API key, so a careful build slows down rather than hammering your account. Change events can arrive through webhook subscriptions instead of constant checking.

Start with route one. Move to route two when you want the milestone history in more detail than a report gives you.

Setting it up this week

1. Write your limits for each milestone, the permit wait and the supplement wait.
2. Confirm ReportsPlus and scheduled email are on your plan, in writing.
3. Schedule the four reports to the agent's inbox before your first crew leaves.
4. Write one rule per line in the table above, in your own words.
5. Run it next to your Monday routine for two weeks. Check whether the message caught what you found by hand.
6. Cut lines you ignore and add a rule for anything it missed.

What to watch out for

• Write access. The agent reads. Calling a homeowner, nudging an adjuster or moving a milestone is a person's job. Cortex's approval defaults are on our trust and security page.
• One limit for every milestone. It will flag the jobs that are fine and miss the ones that are not.
• A shared API key. If you use the API, give the agent its own key, and keep it read-only where you can.
• Supplements without amounts. A supplement line without a dollar figure gets ignored. Include the amount.

How to tell it worked

After two weeks, the message catches every stuck job, late permit, old supplement and quiet estimate you would have found by hand, it lands before the crews leave, and each line has a named person who acted on it. Building it on your own AccuLynx account is part of the free AI Operations Audit.