# Make corrected meeting notes reach the ATS record

When a reviewed meeting note changes, verify whether the correction reaches the ATS and any other destination that used the earlier value.

Canonical source: https://recruitrecap.com/blog/corrected-meeting-notes-ats-update
Author: Recruit Recap editorial team
Published: 2026-10-06T13:45:00+11:00

When a reviewed meeting note changes, verify whether the correction reaches the ATS and any other destination that used the earlier value. A one-time export and an ongoing update workflow are different capabilities.

## Test the correction path

| Step | Fictional test |
| --- | --- |
| Initial source | Candidate's interview availability entered as Monday |
| First handoff | Reviewed note appears on the sample candidate record |
| Correction | Candidate confirms Tuesday instead |
| Destination check | Does the old note change, or is a correction added? |
| Reader check | Can a recruiter identify the current value? |

Use fictional or approved test data. Do not test uncertain update behavior on a live candidate record simply because it is convenient.

## Decide how history should work

Some workflows may edit a note; others may add a dated update. Agree which behavior the agency needs and what the destination supports. The important point is that a later reader can distinguish current information from superseded information.

If an update changes a structured field but leaves an old narrative note, consider how recruiters will interpret the conflict. If only the narrative changes, check whether downstream filters or reports still use the older field value.

## Follow the full chain

Corrections may affect a client write-up, a pending email, an ATS note, and a task. Identify the destinations in the integration scope and assign ownership for those outside it. Do not assume correcting the source reaches every copy automatically.

A generated write-up may also be rebuilt from an older source. Check the version used before regenerating, particularly if a manual correction was made only in the output.

## Define acceptance before rollout

State the expected correction behavior and test it. A vendor demonstration of creating a new note does not establish update semantics. Ask for the exact result your recruiters will see after a changed date, corrected responsibility, or withdrawn statement.

The [retry guide](/blog/ats-integration-duplicate-notes-retries) distinguishes corrections from uncertain transfers. The [submittal correction guide](/blog/correct-candidate-submittal-after-sending) covers client-facing copies. Recruit Recap integrations are scoped on demand; correction propagation must be verified as part of the agreed workflow, not inferred from the availability of custom recruiting write-ups.