Maintain databases of municipal information

I need to update the municipal database extract and send it to the court administrator and the records clerk for review by Tuesday. Ensure every property record has address, parcel ID, zoning code, and current status populated, and run the dedupe routine so there are no obvious duplicates before I circulate it.

Before I publish the city data snapshot, make it easy for the records team to trust: surface the count of new, changed and removed records at the top, make zoning and status fields searchable on one sheet, flag any records lacking parcel IDs or with conflicting statuses, and attach the source log that shows when each row was last updated.

I sent the municipal extract and the court clerk called out duplicate parcel entries that could affect case scheduling. I don’t know whether the duplicates came from a bad merge, an upstream database export, or manual edits. I’m worried this will hold up filings. What is the most likely source and the fastest triage steps to fix and reassure the clerk?

We keep wasting hours cleaning the municipal extract because duplicates and conflicting status values recur after every import. Across ten monthly cycles the root causes were inconsistent unique IDs, manual edits in the live sheet, and missing validation on status entries. What one process and one spreadsheet control should I adopt so the extract is reliable and I stop firefighting before meetings?