Cancellations is locked

Enter the team password to continue.

Cancellations

Premium Credit returns, triaged against everything processed before

Step 1

Load today's Premium Credit sheet

Drop the spreadsheet here

Excel (.xlsx, .xls) or CSV. Nothing leaves this machine.

or paste the rows straight from Excel
Keep the header row in the copy so the columns can be matched.

No sheet loaded yet

Load today's file above. Every record is checked against what has already been processed, so you only look at what has actually changed.

Outcome log

Everything the team has recorded: who was cancelled, who paid, who is still being chased.

Record search

Every appearance on every saved run, plus every outcome the team has recorded, for one customer or policy.

Record an outcome

Formatted list

Match the columns

Saved runs

Settings and backups

Stamped against each run and each outcome you record, so the trail shows who did what.

Screen lock

A password screen so the tool doesn't open straight away on a shared screen or a stray link. It is not a substitute for proper access control, anyone comfortable with browser developer tools can get past it.

Backups

Runs and outcomes live in this browser only. Export a backup before changing machine or clearing browser data, and import it on the other side.

Storage used

Danger zone

Wiping clears saved runs and every recorded outcome. Every record looks new again on the next sheet.

How it works

Daily run

  1. Drop in the Premium Credit sheet, or paste the rows from Excel.
  2. Columns are matched automatically. If a header is worded differently you get asked to match it once.
  3. Only rows with an attempt number above 1 are considered. Everything else is set aside.
  4. Each record is keyed on policy reference plus PCL reference, then compared against every run saved before.
  5. Record what you did against each one, then save the run to history.

What the sections mean

  • New - first time this policy and PCL pairing has appeared. This is the cancel list.
  • Changes - seen before, but the name, rejection reason or attempt number has moved.
  • Repeats - seen before with nothing changed.
  • Cleared - was on the last saved run, is not on this one. Either the payment went through or it has already been cancelled.
  • Set aside - attempt number of 1 or lower, so out of scope by the rule.
  • Needs a look - a required field is blank or the attempt number is not a number. Nothing is guessed here.

Recording outcomes

Press Log on any row, or use Record an outcome in the Outcome log tab for a policy that is not on today's sheet. Pick what happened, add a note, and it is stamped with your initials and the date.

Outcomes fall into three states: closed (cancelled, paid, do not cancel), in progress (contacted, awaiting payment) and blocked (query raised, referred to compliance). Anything left in progress or blocked shows up in Open items so it does not get lost.

Reports

  • Copy list - the format the team already uses, grouped by section. Outcomes are appended when recorded, and can be switched off for the plain format.
  • Day report - a handover summary: what was cancelled, what is still open, what has no outcome yet.
  • CSV - every row with its outcome, note, who recorded it and when.
  • Copy full history - one record's complete trail, from the record drawer.

Record search

Search any name or reference to see every run that record has appeared on and every outcome recorded against it, oldest at the bottom. Useful when a customer rings and asks why cover was cancelled.

What actually gets saved

The spreadsheet is never stored. It is read in the browser, classified, and thrown away when you refresh or press Start again.

Saving a run keeps the output only: for each record in New, Changes and Repeats, five fields (name, policy reference, PCL reference, rejection reason, attempt number), plus the date, your initials and the file name. Everything else is dropped, including any other columns in the sheet, rows set aside for a low attempt number, and rows that needed a look.

Tomorrow's sheet is compared against those saved records, never against a stored copy of today's file.

Where the data sits

Everything runs in the browser. No file is uploaded anywhere. Runs and outcomes are saved in this browser's storage on this machine, so use Export backup in Settings if the record needs to move or be shared.