Skip to main content
The compliance register exports as a CSV file on every plan: one row per active subcontractor, with the coverage on file, the verdict and the reasons behind it. There is no export tier and no exit fee, and the export still works after a trial ends.

Download it

Any of:
  • Overview → Export register
  • Subcontractors → Export
  • Settings → Export & sharing → Download CSV
  • The command palette (Ctrl+K / Cmd+K) → Export compliance register
Subcontractors page in WatchMyCover with the Export button outlined

Export, on Subcontractors.

The file is named watchmycover-compliance-YYYY-MM-DD.csv, dated by your organization’s calendar day. It opens in Excel or Google Sheets. Anyone on the team can export; each export is recorded in the activity log.
Export and sharing settings in WatchMyCover with the Download CSV button outlined

Download CSV, under Settings, Export and sharing.

Every one of these downloads the same file: the whole active register. A search or filter on the Subcontractors page does not narrow it, and archived subcontractors are not in it.
Command palette in WatchMyCover with the Export compliance register action outlined

Export compliance register, in the command palette.

Columns

Rows are in the register’s risk order, riskiest first. A single file holds up to 5,000 subcontractors; a larger register says so in the file. The file ends with a statement of scope: WatchMyCover compares recorded certificate data against your requirements, cannot confirm a policy remains in force, that an endorsement exists, what a policy excludes or that a certificate is authentic, and the file is not a coverage opinion.

One set of columns per coverage

After Reasons, every coverage type has eight columns, in this order: General Liability, Workers’ Compensation, Automobile Liability, Umbrella / Excess Liability, Professional Liability, Pollution Liability, Cyber Liability, Builder’s Risk. Each is headed with the coverage’s name, for example General Liability: policy number: The last column, Exceptions in force, lists each finding the subcontractor has an exception on, with the date it runs to, so a compliant row that rests on an exception does not read as a clean one. It is blank for everyone else. The values are those of the policy in force today, the same one Coverages on file names. A coverage the subcontractor does not carry leaves its eight columns blank. These columns come after the original ones, so a spreadsheet built on the earlier layout still lines up. Any cell beginning with =, +, - or @ is prefixed with a quote so a spreadsheet cannot run it as a formula.

Sending proof without a file

To give someone a live, read-only view instead of a file, create a shareable report.

References

  • CSV Injection. OWASP: why exported cells that start with a formula character are escaped.