Executive search

Candidate-record corrections: keep the disputed fact and the next action separate

A practical correction-request record for search firms: capture the disputed statement, route it for review and verify approved changes across the working copies that matter.

By LaisyPublished

A candidate says a record describes their role incorrectly. The consultant can fix the sentence in the next draft, but that leaves open questions: where did the statement come from, which other working records repeat it and who is responsible for handling the request?

A candidate-record correction process needs an accountable route from the reported problem to a checked outcome. It should keep three things apart: the statement being challenged, the evidence considered and the action actually taken. Receiving a request, making an edit and verifying the result are different events.

This guide starts from a person's challenge to something the firm holds about them. A firm-initiated review of field quality is covered by the CRM data-quality audit, and combining two records for the same person by the duplicate-record review. It is an operational coordination aid. Legal rights, response deadlines and the treatment of particular information depend on the circumstances; route those decisions through the firm's responsible person and current process.

Copyable correction-request record

Use an identifier that fits the firm's existing process. Keep access proportionate to the request and keep unnecessary personal detail out of general task lists.

FieldUseful record
ReceivedWhen and through which channel the request arrived
Identity and routingThe relevant person or record, with any required verification routed appropriately
Challenged statementExact field or passage and the version or context in which it appears
Requested correctionWhat the requester says is wrong or incomplete
Supporting materialTheir explanation and the permitted sources available for review
Responsible ownerWho accepts handling the request and any specialist question
Interim instructionHow the disputed information should be handled while it is reviewed
DecisionApproved action and reasoning, or the owner of an unresolved determination
PropagationRecords or recipients needing review, each with an action owner
Closure evidenceChecked result, response made and outstanding exceptions

The record should let the next person act. A candidate should not have to explain the problem again because the first conversation was reduced to "update CRM."

Recognize the request at the point of contact

A correction can arrive in an ordinary conversation. Someone may say that a title, employment period or account of responsibility is wrong without using any formal wording.

For organizations covered by UK GDPR, the ICO's right to rectification guidance says a request can be made verbally or in writing, to any part of the organization, not only to a designated contact. The ICO notes that this guidance is under review and may change because of the Data (Use and Access) Act 2025, so check the current version where it applies and follow the responsible person's process. This article is not a legal timetable.

Record the request promptly, including the actual time it was received. Ask a focused clarifying question if the challenged statement is unclear. Do not make the person repeat their whole career history when the issue is one sentence.

Distinguish an internal suggestion to improve wording from an individual's request about information concerning them. Both may need attention, but they follow different routes.

Locate the statement before debating the explanation

Identify the field, note or passage in dispute. Record its version and what it was used for. A sentence in an internal research draft may also have been copied into a client summary or a saved call brief.

The research-note structure separates the underlying source, an attributed account and a consultant's interpretation. That separation can show whether the problem began as a factual error, a dropped qualification or a summary that went beyond its source.

Capture the requested correction in the person's own meaning, with attribution. Do not paraphrase it into a broader claim they did not make. If needed, confirm your understanding through the appropriate channel.

The existence of a source does not answer the challenge. The source may have been misread, may refer to another period or may have been superseded. Review the disputed statement against the evidence relevant to it.

Keep the original account and the challenge visible

A factual statement and an attributed opinion need different examination. "Responsible for the whole division" claims to describe a role. "A referee considered the remit broad" describes an account whose speaker and context matter. Adding an "opinion" label is not a general answer to a challenge.

The ICO's accuracy principle guidance includes recording the source of personal data and, as good practice, keeping a note of any challenges to its accuracy. Keep that UK scope explicit and leave the handling decision to the responsible person.

Record the disagreement and the available evidence without turning the operational note into a verdict on the person's credibility. The question is how the information should be handled, not why the person asked.

While the decision is open, the responsible person should give an explicit interim instruction. A colleague preparing material needs to know what to do with the disputed passage today, not only that someone will look into it.

Use change history to trace the path

Check how the statement entered the record and whether an earlier version carried a qualification that later disappeared.

HubSpot's property-history documentation describes viewing a property's changed values with their dates and sources. That is evidence of what changed inside HubSpot. It does not show whether an earlier or later value was correct.

Tools keep different context. Google Contacts' help notes that older contacts may not have a record of their additions or edits. A missing history entry limits the investigation; it is not proof that the requester or a colleague is mistaken.

If the source path cannot be established, say so. The responsible person may still decide an appropriate correction from other evidence. Do not invent provenance to make the trail look complete.

Map the places where the disputed claim matters

Start from where the statement was actually used. A whole-database export is not needed to investigate one disputed field.

Separate a source record, a derived summary and a sent communication. Changing the source field may not change a saved document, and it cannot change a message already delivered. Each location needs a specific action or a recorded reason why none is appropriate.

For client-facing material, the client-update workflow can help prepare a reviewed explanation. The person handling the request decides whether a communication is needed and who receives it. Preparing the explanation and authorizing its distribution are separate steps; do not send an unreviewed correction notice to every contact on the assignment.

Keep sensitive detail out of the propagation tracker. It can name the document and its owner and link to a restricted explanation. A correction should not spread the disputed information further.

Worked example: one challenged sentence, three working copies

Everything in this example is fictional: the firm, the assignment "Cedar", the documents and Candidate R. It shows how the record and propagation check fit together. It is not a customer incident, an error-rate figure or a legal determination.

On a call on 9 November, Candidate R tells a consultant that research note RN-14 (version 3) wrongly says they "led the European business unit." Their remit covered one region, Iberia, for two years. The consultant opens a correction request the same day.

FieldFictional entry
Received9 November, phone call; consultant's call note made the same day
Challenged statementRN-14 v3, career summary: "led the European business unit"
Requested correctionRemit covered Iberia only, for a stated two-year period
Responsible ownerResearch lead; data-protection questions to the firm's named privacy contact
Interim instructionDo not repeat the sentence in any new material until the decision is recorded
DecisionApproved on 11 November: "led the Iberia region" with its period; the source was a company announcement that named the unit, not the candidate's role in it

The research lead then checks each place the sentence was used.

LocationApproved actionVerification evidenceState
RN-14 research noteCorrect the sentence; keep v3 and the reason for the change in the record historyReviewer reads v4 against the decision and sourceClosed
Cedar client summary, draft 2 (not yet sent)Replace the broader claim before further useSummary owner checks the actual draftClosed
Internal call briefUpdate the derived account and mark the old wording supersededConsultant opens the brief in the view colleagues usePending: brief owner on leave until 14 November; interim instruction stays in force

The request stays open until the third row is checked. The record lists three locations where the sentence was used, not three separate errors or three people notified. If another use of the sentence turns up later, it becomes a new propagation row. The record does not claim the whole firm was searched, because that work was not commissioned.

Verify the change where people read it

Check the working view itself, not only an edit confirmation. A search result, exported summary or prepared client document may still show the old wording.

Compare the result with the approved decision. Has the description changed correctly? Is the date still clear? Can authorized reviewers still reach the source? Did qualifications survive in the new summary?

Record exceptions separately. "Source field corrected; call brief awaiting its owner" is more useful than a single completed checkbox. Give each exception an owner and state what it means for further use.

If responsibility changes while the request is open, include it in the handover. The incoming colleague needs the current decision, the interim instruction and the remaining actions without reopening every conversation about the dispute.

Close the request through the right route

The record should show what was decided, which changes were checked and what response was made where one was required. The responsible person decides how unresolved or refused requests are handled under the applicable process.

Receiving a request does not mean agreeing with every proposed wording. An incomplete investigation is also not closed because the visible CRM field now looks right.

Review recurring causes separately from the individual request: ambiguous field definitions, summaries that lose source context, working copies nobody owns. Process improvement should not delay the response to the person who asked.

If you want to test this alongside existing tools, the pilot success criteria help define one bounded record-review task with selected permitted inputs, a human reviewer and an exit point. No automatic correction, privacy assurance or autonomous response is promised.