1. LandOffer
  2. Blog
  3. All articles
  4. SkillSurvey Reference Requests: Send Invitations, Fix Contact Details, and Track Responses

Job search

SkillSurvey Reference Requests: Send Invitations, Fix Contact Details, and Track Responses

Check the requested reference count and relationships, distinguish delivery states from received responses, and keep contact corrections separate from resending.

10 min readLandOffer team

Adding a reference to SkillSurvey is not always the same as sending that person an invitation, and a completed response is not a hiring result. Follow the number and relationship types requested by your prospective employer, then verify the actual state of each request. If an address is wrong or an invitation bounces, keep contact correction, sending and response completion as separate events.

This LandOffer.ai guide reviews public HiringThing, UW–Madison and iCIMS materials inspected October 22, 2026. We did not access a candidate account, upload contact information, send an invitation or reminder, or view reference answers. The two worked records are fictional and omit names, addresses and survey content. You can browse recent roles on LandOffer.ai, while treating each employer’s reference instructions as a separate process to verify.

A coordinator examines separate closed envelopes and a blank dispatch ledger in a postal sorting room

Start with the employer’s requested number and types

Read the actual invitation before assembling the list. Write down the employer, role, deadline, requested count and relationship categories before deciding that the list meets the invitation’s instructions. Do not substitute a generic platform article’s typical number for the employer’s stated requirements, and do not relabel a relationship simply to make the count appear complete.

HiringThing’s applicant guide, modified September 16, 2025, says the invitation identifies the required number. It describes collecting professional-reference details and keeping responses confidential from the candidate. Its discussion is documentation for that integration, not evidence that we tested a private SkillSurvey account.

If a required relationship is unavailable, ask the employer whether an alternative is acceptable. Keep “alternative proposed” distinct from “alternative approved.” Likewise, if a reference cannot use the requested communication method, obtain the employer’s supported route rather than inventing an address or completing the reference’s survey yourself.

Before sharing another person’s details, confirm their willingness and the appropriate contact information. This article does not supply real contacts, reach out on your behalf or recommend coaching a reference’s responses. The administrative goal is an accurate, authorized request list, not a manufactured rating.

Check which workflow your employer actually uses

HiringThing’s manual workflow uses Send Email to Reference(s) for an unsent entry; after reviewing the details and using the applicable send control, verify the resulting waiting status rather than assuming entry alone dispatched it. In contrast, UW–Madison’s Workday integration guide describes an employer workflow requesting three references and automatically emailing them after the required information is entered. These examples explain why a universal button-by-button recipe would be misleading.

Use the invitation, the controls actually presented and the resulting status in your own employer’s process. A saved row does not prove dispatch unless the relevant workflow or event record establishes it. Conversely, do not keep looking for a manual send button when the employer’s integration uses an automatic step.

The public HiringThing article also retains an Internet Explorer troubleshooting note. That is a reason to read the page as dated documentation, not a current recommendation to switch to an obsolete browser. If a control differs or is unavailable, describe the specific discrepancy to the employer rather than repeatedly trying unrelated fixes.

We could reach only a login page at the iCIMS SkillSurvey community destination. Its private help contents were not inspected. Account-specific controls, permissions and delivery history therefore remain outside this review.

Read delivery states without inferring feedback

HiringThing’s documented labels distinguish entries awaiting dispatch, invitations awaiting a response, delivery failures and received responses. In that guide, Entered But Not Sent means no request email has been sent; Waiting for Reference means sent and awaiting response; Bounced means an email delivery error; Completed means a response was received. The guide also uses Pending for an already-sent request in its email-editing discussion.

Keep the exact displayed wording, observation time and employer workflow in your record, rather than replacing several different states with “pending.” Do not automatically translate every employer’s “Pending” into the same meaning or assume that a vendor’s administrative dashboard matches a candidate view. A timestamp and status label let you distinguish a later delivery change from the earlier contact entry; remembering a button click alone does not establish its result.

These are process states. Waiting does not prove someone refused, Bounced does not establish why an email failed, and Completed does not disclose whether feedback was favorable. None establishes that the employer has reviewed a report, approved the candidate or issued an offer. A reference’s private answer belongs to the reference, not to an applicant trying to clear a task.

A completed seven-row request ledger

Morgan’s fictional employer instruction asks for three professional references, including two supervisors and one colleague. That mix is invented for this example; it is not a SkillSurvey-wide rule. The ledger uses reference labels only, and no invitation or reminder is actually sent.

Ledger item Supplied fictional observation Completed reading and next administrative step
Employer instruction Three references: two supervisors, one colleague Preserve the actual requested mix; do not replace it with a generic count
Reference A Supervisor; Completed One response recorded; content and employer review unknown
Reference B Supervisor; Waiting for Reference A sent request awaits response; no refusal inferred
Reference C Colleague; Entered But Not Sent Contact entry exists but dispatch is not established in this assumed manual workflow
Count of entered references Three labels recorded Entry count matches the requested total; response count does not
Count of completed responses One of three Two requests remain unfinished for different reasons
Employer review No review update supplied No hiring decision or report approval established

Morgan’s finished status memo reads: “Three references are entered, but only A has a recorded response. B is already waiting; C has not been dispatched in the supplied workflow. The two unfinished requests need different handling. No rating, refusal, employer review or hiring outcome can be read from these labels.”

The complete unsent process question is: “Subject: Reference-request workflow clarification. My record shows one completed response, one invitation waiting for a response and one entry labelled Entered But Not Sent. The invitation asks for three references with two supervisor relationships and one colleague. Please confirm the appropriate next step for the unsent entry in this employer’s workflow and the deadline that applies. If a reference becomes unavailable, what is the process for requesting an approved alternative? I am asking about administration only and am not requesting survey answers.”

The completed arithmetic note is: “Three entered references minus A’s one recorded completed response leaves B and C unfinished: two requests with different next steps. That subtraction does not identify a response target sufficient for finalization, and it does not tell me whether the employer will accept a substitute. Those requirements remain with the employer.”

This is a finished worked record even though the process is unfinished. It replaces an imprecise “references done” statement with three distinct observations and one bounded question. Morgan does not assume that sending another message to B would solve C’s unsent state or that one completed response satisfies the employer’s requirements.

A conservator compares separate paper packets and a closed route folio in a cartography studio

Correct contact details without losing the delivery history

HiringThing documents editing reference email details, but the action and the resulting delivery state still need separate verification. Do not assume that saving a corrected address necessarily sends an invitation, resends an earlier one or produces a response. The supported controls may differ by integration and by whether the request is already complete.

Record that a delivery error was observed, which contact field needs checking and whether the corrected information has been confirmed through an appropriate channel. Keep actual contact values out of a general troubleshooting log when labels suffice. Ask the employer what to do if editing is unavailable or the reference cannot participate; do not invent a new identity or duplicate entry as a workaround.

Ari’s separate fictional audit concerns Reference D. The example assumes the contact has confirmed a correction outside this article, with both address values omitted. It demonstrates what evidence would distinguish correction from redelivery. No real contact verification, edit, resend or survey completion is performed here.

Audit checkpoint Supplied fictional evidence Finished audit entry
Original request October 21 record shows invitation attempt Preserve the original event; it does not prove successful delivery
Delivery error Bounced shown at 2:05 p.m. PDT Delivery failure observed; cause not established solely by the label
Contact verification Corrected email value confirmed in the fictional scenario Value omitted from this record; confirmation is not an edit event
Saved correction October 22 save recorded at 10:10 a.m. PDT Contact field updated in the scenario; dispatch still separate
Later delivery state At 10:20 a.m. PDT, still Bounced No verified transition to waiting or completed
Duplicate entry None created Do not hide the original failure behind a second label
Employer instruction No instruction about the next supported action supplied Ask for the applicable resend or support route

Ari’s finished finding reads: “The correction-save event occurred ten minutes before the later observation, but the supplied status still shows Bounced. Ten elapsed minutes do not prove a delivery attempt, a processing deadline or successful receipt. The record supports a correction followed by an unresolved delivery state, not a completed reference request.”

The full unsent clarification is: “Subject: Corrected reference contact with unresolved delivery status. My record shows a delivery failure for Reference D, followed by a saved contact correction on October 22. The later status observation still shows Bounced. Please confirm whether this workflow requires a separate resend action, whether an authorized administrator must assist, and what event or status should confirm the next attempt. I have not created a duplicate entry or treated the reference as completed. Contact values and survey content are omitted from this message.”

The completed audit memo adds: “Retain the original failure, confirmed correction, save time and later observation separately. Do not change the relationship category or supply feedback on the reference’s behalf. The unresolved item is the supported delivery action and its evidence.”

Let the employer resolve unavailable references and review status

UW–Madison’s guide illustrates an employer-controlled process for additional references and finalizing a report. Those controls are for its staff, not candidate permissions or a universal rule about how many responses suffice. Even a completed response and a finalized report are distinct administrative events in that employer’s workflow.

For application updates, iCIMS’s public contact page directs candidates to the employer using its software. Start with the named recruiter or contact in your invitation for requirements, substitutions and hiring status. A vendor support route does not replace the employer’s authority to decide which relationships or alternatives it accepts.

Keep follow-up neutral and consistent with the employer’s instructions and the reference’s willingness. Do not request ratings, dictate answers, use someone else’s link or turn a reminder into pressure to provide favorable feedback. If a person cannot participate, state the administrative issue and ask about the approved alternative rather than implying a response exists.

A status log can identify the unresolved item; it cannot guarantee a reference’s response, faster processing or a favorable employer review. Neither this guide nor the public documentation establishes a response-time guarantee for your employer or predicts how the employer will interpret the eventual feedback.

Close each request with the right evidence

Maintain separate fields for contact entered, invitation dispatched, delivery issue, response received and employer review. Update only the field supported by a new event. A corrected contact value is not a response, and a response is not a job offer.

Before calling the process complete, compare the actual requested count and relationship mix with the recorded states, then ask the employer about any remaining requirement. Preserve the original invitation and subsequent clarification rather than replacing them with a generic assumption about SkillSurvey.

When reviewing recent roles on LandOffer.ai, keep the reference-request record alongside the role’s other hiring steps. Record the next supported administrative action and the evidence needed to confirm it, leave confidential feedback to the reference, and let the employer confirm review and hiring outcomes.

Sources and Further Reading

Public materials inspected October 22, 2026. HiringThing’s guide is dated September 16, 2025; UW–Madison documents its own integration. Private iCIMS community help was not accessible without login.