Stable-key check
Confirm a listing ID or another agreed key that does not change when the days-on-market field advances.
Weekly property spreadsheet merge
A changing days-on-market value should not decide whether two rows are the same. This merge uses a stable listing key, carries prior notes forward and isolates uncertain keys for review.
The delivery
Confirm a listing ID or another agreed key that does not change when the days-on-market field advances.
Bring the previous visit note onto the current row when the current export has no new note.
Use the new note when staff add an update, while keeping the prior note visible for audit.
Hold missing and duplicate IDs for review instead of guessing, dropping a row or attaching a note to the wrong property.
Return the merged workbook, change log and short instructions for the next weekly update.
Owned synthetic proof
The downloadable workbook uses fictional properties and staff notes. It contains no customer project, personal data, private account or production export.
Download the synthetic Excel proof ยท Read the stable-key merge control note
Included
Excluded
Start with metadata
The public form asks only for format, row-count band, stable-key availability and note behavior. Do not attach a workbook, paste addresses or reveal staff notes in the public issue.