Keep policy rows separate
The required columns are Vendor, Coverage, Effective date and Expiration date. A contact email and policy number are useful additional fields. One vendor can have several policy rows, so the validator does not flag a repeated vendor name as a duplicate. An exact repeated combination of vendor, coverage, policy number and policy period is flagged for review.
What gets checked
The tool checks row width, required fields, recognized date columns, expiration after effective date, basic email formatting and policy-period duplicates. Dates must be unambiguous ISO calendar dates in YYYY-MM-DD format. Unknown columns are retained, and the tool does not guess whether 03/04 means March 4 or April 3.
What the trimmed export changes
The export trims whitespace around cell values and standardizes recognized column names. It preserves rows and does not delete duplicates, fill missing dates or change review decisions. Text beginning like a spreadsheet formula is escaped. The download remains available with unresolved issues so you can inspect it, but those issues are not automatically repaired.
A formatting check is not an insurance review
A perfectly formatted row can still contain an incorrect insured, inadequate limit, missing endorsement or cancelled policy. Compare cleaned data with source documents and your current requirements before treating it as reliable. Use a secure process for storing the original tracker and avoid placing sensitive claims or personal information in an unrestricted shared sheet.