Edmonton · Kelowna-supported claims · 25 August 2026

The Edmonton
night run

Every night a job reads PSA, XactAnalysis, Encircle and the two tracker workbooks, finds where they disagree, fixes what it safely can, and publishes two pages before anyone is at a desk. Here is where to look, and what it has done.

Start here

Two pages, one export

Both are rebuilt at 5:00 AM from the same morning pull, so they never disagree about what day it is. No login.

Where the book stands · 25 August

Five things that should always be true

Each rate is measured only against the jobs it can honestly be asked about, and the page refuses to show one it cannot answer.

Documented in Encircle counts photos. Until 25 August it counted whether the job existed in Encircle at all, which 52 of 208 jobs passed while holding no photo. Same book, stricter question — so the figure fell, and the work it is asking for has not changed.

97.2%Every claim has a job6 of 218 missing
95.8%Every job has an owner9 of 212 blank
94.0%Insured contacted13 of 218 not yet
72.5%Documented in Encircle60 of 218 with no photo
97.2%One job per loss6 of 218 doubled
276jobs in the book — 235 open, 41 closed
235claims cross-referenced this morning; 233 matched to a PSA job, 2 not in PSA yet
0differences the reconciler could not explain

What runs, and when

The order is the point

Each step exists because the one before it produced something the next one needs. A board built before the robot ran would send somebody to redo the robot's work.

  1. 7:00 PMPull everythingFour PSA reports, three XactAnalysis exports, both tracker workbooks, and the Encircle photo record.
  2. 7:40 PMRead the live notesOpens each claim in XactAnalysis and reads the actual conversation, so “an adjuster is waiting on us” means somebody really is.
  3. 7:55 PMWrite to PSA, then read it backFills blank dates, corrects any later than their source, and raises the PSA jobs that were never created — then reopens each one in a fresh session to confirm it stuck.
  4. 8:10 PMReconcile and publishAsks whether the two pages still agree with each other, puts the night's open questions on the board, and deploys both.
  5. 8:45 PMWatchdogA separate job that does not know whether the run happened — which is the point. The outage it was built for was a task stuck silently for four days.
  6. 5:00 AMRebuild both pages, then mailA fresh export, both pages rebuilt on it, and each person's own list sent afterwards.

What it has actually changed

In PSA, not on a report

Counted to 21 August 2026. Unlike the figures above, these are running totals and are not restated every morning.

61PSA jobs created that nobody had raised — Edmonton claims do not auto-sync into PSA the way Kelowna's do
247date fields written or corrected, 238 of them since confirmed by a later export
26CAT jobs closed after they turned out to belong to another franchise

Nothing is written on a guess. Every date is read back out of PSA in a separate browser session before it counts as done, and anything the job cannot prove becomes a question for a person rather than a silent edit.

Waiting on a person

What the machine will not decide

These are on the board under Open questions. The clock on routing them is ours, not yours — three days from the night we notice one.

New this week

Everyone gets their own list

Kyle, Elisa and Dawn now get one short email each morning holding only the items they can personally clear — not a shared list to hunt through. It goes out after the 5:00 AM rebuild, so the numbers in the mail and the numbers on the page are the same numbers. A daily summary for you is built the same way and is ready whenever you want it switched on.

The board now separates work somebody can act on from items that are only informational. That is why the headline count is smaller than it used to be: it counts things a person can actually do something about.