Skip to main content
Every subcontractor has one status, decided by the findings from their latest check. A finding you have recorded an exception on does not count while the exception is in force, and the status is then shown with the exception beside it. There are three verdicts (Compliant, Needs review, Non-compliant) and two further statuses (Expiring soon, No certificate).
Subcontractor page in WatchMyCover with the four summary tiles outlined: status, next expiry, open issues and chasing

The summary tiles on a subcontractor page: status first.

​
How the status is decided

Findings have four severities. The first three are shown as badges on the subcontractor’s page: The worst severity wins, in this order: Critical, then Cannot verify, then Warning. So a subcontractor with one short limit and one unverifiable endorsement is Non-compliant; fix the limit and they become Needs review. Needs review outranks Expiring soon because an open question about cover today is more urgent than a date that has not arrived.

​
What a finding shows

The subcontractor’s page opens with four tiles: Status, Next expiry, Open issues and Chasing. Directly under them, the card Why this subcontractor is not cleared (or What needs renewing for an expiring subcontractor) lists each finding with:
  • a sentence saying what is wrong and why, for example “General Liability aggregate limit of $1,000,000 is below the required $2,000,000.”;
  • Required: the figure or condition the template asks for;
  • On file: what the certificate provided.
Why this subcontractor is not cleared card with one critical finding, its required figure and the figure on file

A finding: the sentence, then Required and On file.

The sentences are written so they can be forwarded to a broker as they stand. The full list, one per finding type, is in Every finding explained. When nothing is outstanding, the card reads Nothing outstanding: “This subcontractor satisfies every requirement on their assigned template. They are cleared to work.”

​
When checks run

A subcontractor is checked again:
  • when a certificate is recorded, the subcontractor is edited, or their template changes;
  • when you choose Re-check on the subcontractor’s page, Re-check all on the dashboard, or Re-check every subcontractor in the command palette (Ctrl+K / Cmd+K);
  • when a template they use is edited, or you change the time zone or warning window;
  • once a day, in the hour the day begins in your organization’s time zone, so an expiry takes effect on the day it happens.
Dates are judged by the calendar day in your organization’s time zone (Settings → Organization or Settings → Renewal chasing). A policy is expired on its expiry date: policies run from 12:01 a.m. to 12:01 a.m., so the expiry date itself has no cover.

​
Changing the warning window

Settings → Renewal chasing → Warn me this many days before expiry sets the window for Expiring soon, from 1 to 180 days. The default is 30. Changing it re-checks every subcontractor. It does not change when chase emails are sent; see How chasing works.
Renewal chasing settings with the Warn me this many days before expiry field outlined

The warning window, under Settings, Renewal chasing.