Job search
Crosschq References: Add, Replace, or Reinvite the Right Person
Choose the right Crosschq action for contact corrections, replacement references and new invitations, and check when previous responses can be reused.
Use Crosschq’s reference actions according to what is changing: correct the same person’s contact details, replace that person, invite an earlier reference to answer again, or reuse eligible previous responses. A contact correction changes identifying information; a replacement changes the person. A new invitation and reuse of earlier responses also have different effects. A familiar name in your Candidate Locker does not mean an old questionnaire has been carried into the new employer’s request.
Begin with the current employer’s instructions and the intended person. Resolve any identity, relationship or permission question before submitting. Keep your broader search organized through LandOffer.ai, while the recruiting team clarifies the reference requirements for this application.
This guide reviews official public Crosschq help checked October 22, 2026. It does not test a private Candidate Locker or send an invitation. Both worked examples are fictional planning records; they contain no reference answers or hiring evaluations.

Decide whether the person or the information is changing
Crosschq’s Adding/Editing References guide documents these routes: Edit Reference for the same person’s contact information; Cancel Reference, then a new reference, for someone different. New entries include shared work history and send a survey link at the final Continue step. The employer controls the requested number; additional references require the employer to request them.
Before using a control, write a plain sentence describing the intended change. “Correct the address for the manager I already nominated” concerns one person. “Ask my former technical lead instead of that manager” changes the person. That sentence helps prevent a convenient-looking edit from attaching a different individual to the original relationship record.
Check the surrounding work history as carefully as the name so the employer receives an accurate account of how you know this person. A current job title may differ from the title someone held when you worked together. Explain the actual relationship and period rather than upgrading a coworker to manager because the employer requested a supervisor. If the requested category does not fit anyone you can appropriately provide, ask the recruiter about alternatives.
If the expected control is missing, ask about the current request instead of creating a duplicate request or another account. The public instructions describe a workflow; they do not establish the permissions or state of your particular request. Identify the employer request, affected entry and exact missing control or error in a support question; omit private contact details from public forums.
Separate a new invitation from previous-response reuse
The guide labels two ways to use an earlier reference: Add as a Reference sends a new questionnaire link; Reuse Previous Responses assigns earlier responses to the new request when allowed. Choosing the first route does not establish that the second happened.
The employer-facing Managing Crosschq 360 Settings guide adds the controlling conditions. Administrators can enable or disable reuse. When enabled, Crosschq checks survey compatibility; below 70% matching questions, previous responses cannot be reused. When disabled, new surveys are required. Candidate self-assessment reuse is also subject to settings and requires confirmation before submission.
Read that percentage as a survey-alignment rule. It is not a reference’s rating, a pass mark or a measurement of how positive their feedback was. Candidates should not calculate a match from remembered answers and decide reuse is authorized. The documented compatibility check belongs to the platform.
There is a wording issue worth recognizing. The candidate article retains an older passage referring to matching “answers,” while a later section on the same page and the settings guide describe matching survey questions. The later candidate section and the settings guide agree on matching questions. Neither establishes that a candidate can choose favorable old answers for transfer.
Availability can differ between employer requests. A previous reference record provides context, but it does not establish that every future survey, relationship requirement or reuse option will be the same. If an option is unavailable, ask what the current request requires; do not paste remembered feedback into a replacement form.
Worked example: a correction that must preserve identity
Fictional case: Briar Voss is preparing references for a data engineering role at Alder Bridge Analytics. Its invented request asks for two references, including one former manager. Briar notices that the manager entry contains an outdated contact address. No actual address, account or invitation is used here.
| Field | Completed planning record |
|---|---|
| Current request | Alder Bridge Analytics, Data Engineer; two requested references |
| Affected person | Former engineering manager, nominated in the manager slot |
| Shared work history | Briar was Data Engineer; the person was Engineering Manager; April 2022–December 2023 |
| Problem identified | Contact address is outdated; the person and relationship are unchanged |
| Correct information source | In this fiction, the same person has confirmed a preferred address; the address itself is omitted |
| Intended route | Same-person contact correction; retain the original relationship history |
| Unrelated entry | Former coworker entry has no identified error and should remain separate |
| Unresolved effect | Whether saving the correction triggers another notification or requires a further action is not established here |
Briar’s completed change note reads: “Correct only the former manager’s contact field. Keep the person, shared company, historical titles and dates unchanged. Do not substitute the coworker’s details in the manager entry. After any authorized correction, check the displayed record and request state before describing what happened.”
The useful output is a precise correction scope. Briar can distinguish the intended edit from an unverified delivery result. A saved address would not itself prove that a message arrived, the person opened it or a survey was completed.
Now change one fact: suppose that manager is unavailable and Briar wants a different former supervisor. The correction note no longer fits. That is a replacement problem, requiring the new person’s own relationship details and confirmation that the replacement meets the employer’s request. The candidate should not preserve the old person’s identity while silently changing the destination.
This contrast makes the first question practical: can the existing work-history record remain truthful after the intended change? If the answer is no, pause and identify the correct replacement route rather than stretching the meaning of Edit.
Build the replacement record before the send step
Prepare a short factual description of the new person: where you worked together, the respective roles at that time, the period and why that person can speak to your work. Keep the explanation about direct professional knowledge. Do not draft praise or predict the answers the person will give.
A role-specific reason could be that a former lead reviewed your pipeline changes and coordinated incident follow-up. That explains the source of their knowledge without claiming they managed you or promising a positive assessment. If the employer needs a manager, identify that distinction before proceeding.
Confirm that the person expects the request and which contact channel they agreed to use. Before an automated invitation, confirm that the earlier contact information is still appropriate for this request. Avoid entering extra personal information merely because a field permits it, and keep private contact information out of shared application notes.
The documented send step matters. Reviewing a draft list and submitting a reference request are different actions. Before submission, check the person, employer, relationship and intended consequence together. Afterward, describe only an observed confirmation; do not turn a planned replacement into a completed reference in your own tracker.
Worked example: an old reference for a new employer
Fictional case: Lucien Hart previously completed a reference process for an infrastructure role. A new employer, Birch Lantern Systems, now requests a former manager and a peer for a platform engineering application. The earlier manager appears in Lucien’s planning records, but this example does not access a Locker or reproduce any past responses.
| Decision field | Completed record for the new request |
|---|---|
| Earlier person | Former Platform Manager, with direct knowledge of Lucien’s deployment work |
| Earlier relationship | Lucien was Platform Engineer; shared work ran February 2021–September 2022 |
| Current requested category | Former manager; the historical relationship fits the stated category in this fiction |
| Contact freshness | Not yet reconfirmed for this new request |
| Intended information | Current employer needs its reference requirement fulfilled, not a candidate-written summary of old feedback |
| Employer reuse setting | Unknown; no assumption that reuse is enabled |
| Survey compatibility | Unknown; no questionnaire comparison or percentage calculation performed |
| Present decision | Clarify the allowed route and contact availability before any invitation or reuse action |
Lucien prepares this full UNSENT question to the recruiting contact:
Subject: Reference route for the Platform Engineer request
Hello Recruiting Team,
I have previously nominated a former manager through Crosschq. For the current Platform Engineer request, should I invite that person to complete a new survey, or is reuse of previous responses available under your process?
I have not assumed that an earlier response transfers to this request. If a new response is required, I will confirm the person’s current availability and contact details before proceeding. Please also confirm whether the requested former-manager relationship needs to cover a particular period of my work.
Thank you, Lucien
This produces a bounded next step, not a claim that old feedback was reused. If the employer requires a new response, Lucien’s preparation shifts to availability and a fresh invitation. If reuse is permitted, the actual supported option and compatibility outcome still need to be established. Neither branch supplies a reference answer on the person’s behalf.
The example also separates two questions that are easy to combine: “Is this the appropriate person?” and “Which response route is available?” A suitable former manager may still need a new survey. A visible old response option cannot make an unsuitable relationship meet the employer’s requirements.

When a reminder fits the problem
For an existing reference that has not responded, Crosschq’s reminder guide describes a Send Reminder control after a 24-hour delay and automatic reminders with a default 24-hour frequency. These are published instructions, not a tested schedule for your account or a deadline for receiving an answer.
A reminder addresses an outstanding response from the intended person. It does not resolve a wrong identity, establish that an address is correct or transfer old answers into a new survey. Check what is actually missing before adding another communication.
Keep any personal follow-up neutral and limited to logistics. Ask about availability or an access problem rather than telling someone what to say. If the person cannot participate, clarify timing and the acceptable alternative with the recruiter. Silence alone does not establish refusal or negative feedback.
Close the loop without inventing completion
Crosschq’s getting-started guide describes an employer-initiated email route into the candidate portal, with SMS depending on the organization. Use the request associated with the correct employer and role; do not forward a reference provider’s link as a workaround for your own access problem.
Its completion guide describes a completion email after all references and the candidate’s self-reference are complete. That is a process milestone. It does not state an offer, start-date approval or hiring outcome.
Keep your own notes equally specific: correction planned, replacement clarified, new request confirmed, or completion notification received. Date each confirmed change and identify the supporting notification; keep planned actions separate until the platform or recruiter confirms them. Leave the employer’s decision separate, and use LandOffer.ai’s recent roles to keep reviewing opportunities while this application proceeds.
Sources and Further Reading
- Crosschq: Adding/Editing References — same-person edits, replacements, old-reference routes and employer count limits.
- Crosschq: Managing Crosschq 360 Settings — employer reuse controls and survey compatibility.
- Crosschq: Sending a Reminder to a Reference — documented reminder behavior.
- Crosschq: Getting Started with a Crosschq Request — candidate entry route.
- Crosschq: Completion of Reference Requests — stated completion milestone. Public documentation checked October 22, 2026; these pages do not display a clear article update date.


