Reference Check Software Features: A Practical Buying Checklist

Reference check software can look deceptively similar from the outside. Most vendors talk about automation, templates, reminders, reports and integrations. Those features matter, but they are only useful if they make the reference process faster, more consistent, more respectful for referees and easier for the hiring team to review.

For talent acquisition, HR and recruitment buyers, the buying decision should not start with a feature grid. It should start with the risk in your current workflow. Are recruiters losing days to phone tag? Are hiring managers receiving vague notes? Are candidates unclear about when referees will be contacted? Are referee comments scattered across inboxes, spreadsheets and ATS notes? Are you relying on a black-box summary without seeing the underlying evidence?

The best reference check software features solve those practical problems. They capture consent, collect role-related feedback, reduce manual chasing, keep source evidence reviewable, protect sensitive information and help recruiters make a human judgement with better context.

Shortlist reference check tools around evidence quality, not feature volume. Skill Society helps hiring teams collect structured, voice-first reference feedback with reviewable summaries and less recruiter admin: book a demo.

Quick Answer: What Features Should Reference Check Software Have?

Reference check software should include candidate consent capture, referee nomination, role-specific templates, automated invitations and reminders, mobile-friendly completion, relationship verification, source evidence review, summary reports, ATS workflow support, privacy controls, audit history and human escalation.

For most teams, the strongest buying checklist is:

Feature	Why it matters	What to test in a demo
Candidate consent and contact rules	Protects candidates and avoids surprise contact with current employers	Show the candidate consent screen, current-employer restriction and stored consent record
Referee collection and relationship context	Helps recruiters judge whether feedback is relevant	Ask how the platform verifies the referee relationship, work period and role context
Role-specific question templates	Improves consistency and job relevance	Build a template for one live role and compare manager, peer and stakeholder paths
Automated invitations and reminders	Removes manual chasing and late-stage delay	Configure reminder timing, stop rules and stalled-check escalation
Mobile-friendly referee experience	Busy referees often respond outside business hours	Complete a referee check on a phone during the demo
Evidence capture and source review	Keeps summaries grounded in what was actually said	Drill from the report into original answers, transcript or recording
AI summaries with human review	Saves reading time without outsourcing judgement	Ask what the AI does, what it does not do and how users inspect the source
Fraud and authenticity signals	Reduces risk from fake or unsuitable references	Ask which signals are checked and what humans see before acting
ATS integration and status sync	Keeps reference checks inside the hiring workflow	Trigger a check from the ATS and show result writeback
Access controls, retention and audit logs	Protects personal information and creates a reviewable record	Show permissions, exports, deletion settings and event history

That list is more useful than asking whether a platform has "automation". Automation can mean a simple email sequence, a full ATS-triggered workflow or a broader screening suite. Buyers need to understand the detail.

Start With the Workflow, Not the Product Page

Before comparing reference checking tools, map how checks happen today. A simple workshop with recruiters, hiring managers and talent operations usually surfaces the real buying criteria.

Ask:

• When do we trigger a reference check?
• Who asks the candidate for referees?
• How do we record candidate consent?
• How do we handle current-employer restrictions?
• Which questions are standardised across candidates for the same role?
• Which questions change by role, seniority or risk level?
• How do referees respond today: phone, email, form or meeting?
• Where are notes stored?
• Who can see the report?
• What happens when feedback is negative, inconsistent or unclear?
• How long do checks usually take from request to hiring-manager review?

The answer will tell you what features matter. A recruitment agency may care most about speed, client-ready reports and branding. A care provider may care most about audit history, right-to-work adjacency and strict required questions. A scale-up may care most about ATS integration and fast candidate experience. A senior executive search process may need fewer checks, but deeper evidence and more human follow-up.

The Real Job of Reference Check Software

Reference checks should add job-related evidence to the hiring decision. They are not a magic prediction tool and they should not be treated as a late-stage ritual.

The Australian Public Service Commission says referee reports can gather information on work performance, behaviours, experience, technical expertise and other relevant work-related qualities. The Australian Human Rights Commission advises employers to use referees to confirm what they already know about the candidate and enquire about suitability for the job based on selection criteria, while avoiding personal questions that do not directly relate to job requirements.

Those principles are useful for private-sector buyers as well. Reference check software should help a recruiter answer:

• Did the referee actually observe the candidate in a relevant work context?
• What duties, behaviours or outcomes did they observe?
• Does the feedback validate or challenge evidence from interviews and assessments?
• Are comments specific enough to support a decision?
• Is there anything that needs fair follow-up with the candidate?

Software should improve the process. It should not pretend that a referee score is the same thing as a hiring decision.

Feature 1: Candidate Consent and Contact Controls

Candidate consent is the first feature to evaluate because it controls the entire workflow. A good platform should make it clear to the candidate what is being requested, who may be contacted, when contact will happen and how the information will be used.

At minimum, look for:

• a clear candidate invitation or consent step;
• nominated referee collection;
• current-employer contact restrictions;
• the ability to pause contact until a nominated stage;
• candidate-facing instructions in plain language;
• a stored consent event with timestamp and user history;
• configurable copy for different brands, regions or role types.

This is especially important in Australia. The OAIC notes that if a prospective employer wants to seek a referee report from someone other than the applicant's nominated referee, the applicant should be notified before the report is sought. OAIC guidance also treats referee comments about a job applicant's career, performance, attitudes and aptitude as personal information in certain circumstances.

For buyers, the practical demo question is simple: "Show me exactly what the candidate sees before any referee is contacted."

If the vendor cannot show this clearly, keep digging. Consent should not be hidden inside a generic application acknowledgement or left to recruiter memory.

Current-Employer Protection

Current-employer contact is a common failure point. Candidates may not have told their manager they are interviewing. A casual contact can put them at professional risk and damage trust in your process.

Look for features that let the candidate:

• mark a referee as current employer;
• block current-employer contact until a defined stage;
• nominate an alternative referee;
• add notes such as "contact after offer approval";
• receive confirmation before invitations are sent.

The recruiter should see those restrictions clearly. The workflow should make the safe path easy.

Feature 2: Referee Collection and Relationship Verification

Reference evidence is only as useful as the relationship behind it. A glowing comment from someone who barely worked with the candidate should not carry the same weight as a detailed account from a direct manager who observed the role-relevant work.

Strong platforms collect context such as:

• referee name, email, phone and organisation;
• relationship to candidate;
• reporting line;
• period worked together;
• role or project observed;
• whether the referee was a manager, peer, stakeholder, client or direct report;
• confidence that the referee can comment on specific competencies.

Vendor pages increasingly highlight authenticity controls. RefNow markets fraud detection and reference verification features. Crosschq describes fraud alerts and ATS-launched reference workflows. HiPeople's help centre lists relationship verification, job title verification, fraud detection and reference reports among its reference-check product resources.

Treat these as areas to test, not claims to accept at face value. Ask vendors what signals they use, whether those signals are optional, how false positives are handled and whether recruiters can review the reason for a flag.

What Good Relationship Questions Look Like

Relationship questions should be specific and neutral:

• How did you work with the candidate?
• During what period did you observe their work?
• What role did the candidate hold at the time?
• What responsibilities or projects did you directly observe?
• Were you their direct manager, peer, stakeholder, client or direct report?
• How confident are you commenting on this role requirement?

That context helps hiring managers interpret the report. It also stops every response from being flattened into a generic score.

Feature 3: Role-Specific Templates and Question Libraries

Templates are one of the most important reference check software features because they determine evidence quality. Generic templates produce generic feedback. Good templates make the process consistent enough to compare candidates, while flexible enough to reflect the job.

Look for:

• templates by job family, role type or seniority;
• separate pathways for managers, peers and stakeholders;
• question libraries with behavioural prompts;
• required and optional questions;
• rating scales with clear anchors;
• open-response questions that ask for examples;
• conditional logic for regulated roles or missing information;
• version history showing which template was used;
• approval workflows for template changes.

The U.S. Office of Personnel Management says structure can enhance reference checking usefulness and names job-analysis-based questions, consistent question sets and standardised data collection as structuring strategies. AHRI similarly notes that standardised questions can produce more reliable outcomes and provide a stronger basis for comparing candidates, while still warning that referees may disagree.

That nuance matters. Standardisation does not mean asking every candidate in your company the same questions. It means candidates for the same role are assessed against a comparable, job-related structure.

Template Examples by Role Type

For a customer service role, the template might ask about reliability, customer interaction, conflict handling, punctuality and ability to follow procedures.

For a sales role, it might ask about pipeline discipline, resilience, stakeholder management, activity quality and whether results were repeatable.

For a people leader, it might ask about coaching, decision-making, accountability, change leadership and how the person handled difficult performance conversations.

For a safety-sensitive role, it might include role-specific compliance questions, clear required responses and a documented escalation path.

The software should make this variation easy without letting every recruiter invent their own process from scratch.

Feature 4: Automated Invitations, Reminders and Stalled-Check Management

Automation is the feature most buyers expect, but it needs close inspection. A simple reminder sequence is useful. A workflow that removes recruiter admin while keeping candidates and referees informed is more valuable.

Evaluate whether the tool can:

• trigger a request from the right hiring stage;
• invite candidates to nominate referees;
• send referee invitations by email and, where appropriate, SMS;
• stop reminders once a referee completes the check;
• pause reminders when a candidate has asked for delayed contact;
• show recruiter-visible status for each referee;
• escalate stalled checks to a human owner;
• notify the hiring manager when the report is complete.

Zinc describes automated follow-up, question customisation and flags for mismatched dates, job titles or unclear information. RefNow says its automated reference software handles email and SMS reminders, and markets centralised audit trails and PDF reports. Xref describes reference checking software as a way to automate the lengthy manual process of contacting candidates and highlights delay, poor compliance, lack of flexibility and inconsistent approaches as signs the process needs improvement.

The buyer takeaway is not that every vendor's numbers will apply to your team. It is that automation should remove defined steps from your existing process. During the demo, ask the vendor to walk through your real workflow, not a perfect generic one.

Feature 5: Referee Experience on Mobile, Voice and Desktop

Referees are often busy managers, supervisors, clinicians, educators, clients or executives. They may be willing to help, but they are unlikely to prioritise a long, clunky form.

A strong referee experience should be:

• mobile-friendly;
• clear about the candidate and role;
• transparent about how feedback will be used;
• short enough to finish in one sitting;
• accessible without unnecessary account creation;
• easy to pause and resume;
• respectful in reminder language;
• available outside business hours;
• designed for the response format the role needs.

Some tools are form-first. Some are voice-first. Some combine reference checks with broader employment or background verification. The right format depends on your hiring context.

Voice can be valuable when nuance matters: tone, hesitations, examples and natural explanations often carry more meaning than a one-line text box. Forms can be efficient for high-volume, lower-risk checks where questions are narrow and consistent. A hybrid approach can work well when the platform captures structured responses and allows human review of the original source.

Ask to complete a referee check on your own phone during the demo. If the experience is annoying for you, it will be worse for a busy referee who has no commercial reason to finish it.

Feature 6: Evidence Capture and Source Review

The report is not the evidence. The report is the interpretation of evidence.

A good reference check platform should let recruiters and hiring managers inspect the source material behind a summary, score or recommendation. Depending on the workflow, that source may be:

• original text answers;
• rating-scale responses;
• referee comments;
• voice recordings;
• transcripts;
• question-by-question responses;
• timestamped excerpts;
• relationship verification details;
• discrepancy notes;
• recruiter follow-up notes.

This matters most when the reference feedback is mixed. A summary such as "strong stakeholder management with some concerns about pace" is useful only if the hiring manager can see what was asked, who said it and what examples support the conclusion.

Do not buy a tool that turns reference checking into a sealed score. Buyers should ask:

• Can I see the original response behind every summary point?
• Can I export the report and the source evidence separately?
• Can hiring managers see the evidence without seeing information they should not access?
• Can recruiters add a follow-up note when they clarify a concern?
• Can the report separate observed facts, referee opinion and software-generated summary?

Feature 7: AI Summaries, Scoring and Human Review

AI can be useful in reference checking when it reduces reading time and helps organise evidence. It becomes risky when it hides reasoning or implies the software should decide who gets hired.

Useful AI-supported features may include:

• summarising long referee responses;
• grouping feedback by competency;
• highlighting missing or inconsistent answers;
• flagging comments that need human review;
• extracting examples for hiring managers;
• identifying themes across multiple referees;
• turning voice responses into transcripts and summaries.

Features to treat carefully include:

• unexplained pass/fail recommendations;
• black-box candidate scores;
• sentiment analysis that is not linked to source evidence;
• automated adverse decisions;
• claims of bias-free decisions without transparent controls;
• summaries that cannot be challenged or corrected.

The practical rule is simple: AI can help organise reference evidence, but humans should remain responsible for interpretation and decision-making. Recruiters should be able to inspect the source evidence and explain why a concern matters for the role.

Demo questions:

• What exactly does the AI analyse?
• Does it affect candidate ranking or hiring recommendations?
• Can users turn it off or configure it by role?
• Can users review the source evidence for every AI-generated point?
• How are errors corrected?
• Are summaries stored, exported or synced to the ATS?
• Is candidate or referee data used to train models?

If a vendor cannot answer these plainly, involve legal, privacy, procurement or risk teams before proceeding.

Feature 8: Fraud, Authenticity and Discrepancy Signals

Fake or weak references are not the only risk in reference checking, but they are real enough to evaluate. A candidate may nominate a friend as a manager. A referee may use a personal email that cannot be connected to the organisation. Employment dates or job titles may not match the CV. Multiple referees may show unusual patterns.

Useful authenticity features can include:

• relationship verification;
• job title or employment-date checks;
• duplicate email or phone detection;
• domain or organisation checks;
• LinkedIn or identity verification integrations;
• IP, device or behavioural pattern alerts where appropriate;
• discrepancy flags for dates, titles and responsibilities;
• manual review workflows for flagged checks.

These features should support judgement, not create automatic disqualification. A personal email may be legitimate for a small business. A former manager may have changed jobs. A referee may be overseas. The platform should flag the issue and let a human investigate.

Ask vendors to show a flagged report and explain:

• what triggered the alert;
• what the recruiter sees;
• whether the candidate is notified;
• how the concern can be resolved;
• whether the flag is included in ATS notes;
• who can override or clear it.

Feature 9: ATS, CRM and Workflow Integrations

Reference checks are often a late-stage bottleneck because they sit outside the recruiter's system of record. If a recruiter has to copy candidate data into another tool, manually chase progress, download a PDF and re-upload it to the ATS, adoption will suffer.

Evaluate integrations at workflow level, not logo level.

Ask whether the platform can:

• launch a reference check from a defined ATS stage;
• pull candidate, role and recruiter details automatically;
• write status updates back to the candidate profile;
• attach completed reports to the ATS;
• sync notes, summaries or structured fields;
• support agency and client-specific workflows;
• use webhooks or APIs for custom automation;
• respect ATS permissions and candidate consent;
• support audit history across both systems.

Crosschq describes launching from the ATS and producing aggregated reports. Zinc says it integrates with ATS and HRIS platforms and lists Greenhouse, SmartRecruiters and Workable among examples. Skill Society describes ATS-connected reference invitations, voice capture, AI analysis and structured reports in its integration material.

Do not stop at "Do you integrate with our ATS?" Ask the vendor to show the exact trigger, field mapping, user permission model and result writeback.

Feature 10: Reporting for Hiring Managers

Hiring managers do not need a data dump. They need a report that makes the reference evidence easy to use responsibly.

A strong report should show:

• candidate and role details;
• referee relationship and work context;
• completion status and dates;
• questions asked;
• rating scales and comments;
• strengths supported by examples;
• concerns supported by examples;
• gaps or non-responses;
• discrepancies or authenticity flags;
• source evidence links;
• recruiter notes and follow-up outcomes;
• a clear distinction between evidence and interpretation.

For agencies, reports may also need branding, export controls and client-ready summaries. For internal TA teams, reports may need ATS notes, hiring manager comments and approval-friendly summaries.

Be cautious with overly polished reports that hide the messy parts. Hiring teams need to know when evidence is strong, weak, inconsistent or incomplete.

Feature 11: Privacy, Security, Retention and Audit Controls

Reference checks can contain personal information about candidates and referees. They can also include opinions, work history, contact details, voice recordings, transcripts, referee confidence levels and sensitive comments volunteered unexpectedly.

Australian buyers should treat reference checking as a formal personal-information workflow. This is not legal advice, but the operational implications are clear:

• collect only what is needed for the hiring purpose;
• keep questions job-related;
• tell candidates and referees what is happening;
• control who can access reports;
• avoid unnecessary sensitive information;
• keep records accurate enough to review;
• retain data only as long as needed under policy;
• support access, correction and deletion processes where applicable;
• review vendor subprocessors and data locations.

The OAIC's employee records exemption guidance is also a reminder that prospective employee information is not automatically covered by current or former employee-record assumptions. Fair Work's workplace privacy guide recommends creating a policy on employment references, including when references will be given, the form of reference, the request process and a consent form.

When assessing software, ask to see:

• role-based access controls;
• recruiter, hiring manager and admin permissions;
• report-sharing controls;
• audit logs;
• data export settings;
• retention and deletion settings;
• data hosting location;
• subprocessors;
• security certifications or trust centre materials;
• incident response and breach notification process;
• AI data-use settings if AI features are included.

The best vendors will not answer privacy questions with "we are compliant" and move on. They will show the actual settings, workflow and evidence.

Feature 12: Implementation, Analytics and Continuous Improvement

Reference check software should improve over time. Once the workflow is live, you should be able to see where checks are moving quickly, where referees drop off and where templates create poor evidence.

Look for analytics such as:

• average time from request to candidate referee submission;
• average time from referee invitation to completion;
• completion rate by role, team or source;
• reminder effectiveness;
• stalled-check reasons;
• template usage;
• report review rates;
• hiring manager feedback;
• authenticity flags and resolution outcomes;
• candidate or referee experience feedback.

Do not overcomplicate the first rollout. Start with a few metrics that matter to the business: time saved, completion speed, report quality, hiring manager confidence and compliance exceptions.

Must-Have, Should-Have and Nice-to-Have Features

Not every team needs every feature on day one. Use this prioritisation to keep the buying process honest.

Priority	Features	Best for
Must-have	Consent capture, referee nomination, role-specific templates, automated reminders, mobile completion, reviewable source evidence, access controls and audit history	Almost every employer or recruitment agency
Should-have	ATS integration, relationship verification, structured reports, configurable retention, stalled-check escalation, template versioning and human review workflows	Teams running regular reference checks or hiring across multiple roles
Nice-to-have	Advanced fraud analytics, benchmark comparisons, talent-pool features, deep API automation, custom analytics, multilingual workflows and advanced AI analysis	High-volume, enterprise, agency, global or regulated hiring teams

The best buying decision depends on your volume, risk level and operating model. A team running five senior searches per quarter has different needs from an agency placing hundreds of candidates a month.

Practical Examples: Which Features Matter by Hiring Scenario?

High-Volume Retail, Hospitality or Contact Centre Hiring

The biggest risk is delay and inconsistency. Recruiters need fast referee collection, mobile-friendly completion, automated reminders, simple role templates and a dashboard that shows which checks are blocking offers.

Prioritise:

• candidate-led referee nomination;
• SMS and email reminders;
• short mobile forms or voice responses;
• bulk-friendly workflows;
• simple report summaries;
• ATS status writeback;
• exception handling for stalled checks.

Do not overbuild the questionnaire. Ten precise questions will usually beat a long form that referees abandon.

Recruitment Agency Placements

The agency needs speed, credibility and client-ready evidence. Reference checks are part of candidate presentation and client trust.

Prioritise:

• branded candidate and referee communications;
• client-ready PDF or shareable reports;
• source evidence review;
• relationship verification;
• recruiter notes;
• reusable templates by client or role family;
• permissions that separate agency, client and internal views.

The report should help the consultant explain why the candidate is suitable, not just show that references were completed.

Senior Leadership Hiring

The biggest risk is oversimplification. Senior references often require nuance, discretion and follow-up.

Prioritise:

• current-employer protection;
• senior-specific question templates;
• voice or interview-style responses;
• source review;
• human escalation;
• confidential sharing controls;
• clear separation of factual observations and interpretation.

Automation can still help, but it should support a deeper human process rather than replacing it.

Regulated or Safety-Sensitive Roles

The biggest risk is missing required information or keeping weak records.

Prioritise:

• required question sets;
• consent and audit history;
• access controls;
• retention settings;
• discrepancy flags;
• escalation workflow;
• integration with employment verification or background checks where needed;
• reporting that can withstand internal or external review.

In this scenario, "fast" is useful only if the process remains controlled.

Demo Questions to Ask Reference Check Software Vendors

Use these questions in vendor demos and procurement conversations.

Workflow and Setup

• Can you configure a template for one of our current roles during the demo?
• How long does implementation usually take for a team our size?
• Who owns template changes: recruiters, admins, HR operations or vendor support?
• Can we run different workflows for internal hiring, agency placements and executive search?
• Can we pilot with one team before rolling out more broadly?

Candidate and Referee Experience

• What exactly does the candidate see before referees are contacted?
• Can candidates restrict current-employer contact?
• How does the referee know the candidate authorised the request?
• Can referees respond on mobile without creating an account?
• What languages, accessibility options and reminder controls are available?
• Can we preview the full referee journey before launch?

Evidence and Reporting

• Can we inspect the original answers behind the report?
• If voice is used, can we review recordings and transcripts?
• How are strengths, risks and missing information shown?
• Can hiring managers comment, approve or request follow-up?
• Can we export reports, and what information is included?
• Can reports be shared securely with clients or stakeholders outside the system?

AI, Fraud and Human Review

• What AI features are included?
• Does AI produce summaries, scores, recommendations or flags?
• Can users see the evidence behind every AI-generated statement?
• What fraud or authenticity signals are checked?
• What happens when a reference is flagged?
• Can humans override, clear or annotate a flag?

Privacy, Security and Commercials

• Where is data hosted and processed?
• What subprocessors are used?
• Is candidate or referee data used to train AI models?
• What security certifications or assurance documents can you provide?
• Can we configure retention and deletion?
• How are access, correction and deletion requests handled?
• What is included in the base price versus add-ons?
• Are SMS, integrations, implementation, support or extra users charged separately?

Implementation Advice: Rolling Out Reference Check Software

Buying the software is only part of the change. The rollout determines whether recruiters actually use it.

1. Define the Trigger Point

Choose when checks should begin. Common trigger points include finalist stage, post-interview, pre-offer or conditional offer. Avoid vague rules such as "when the recruiter thinks it is time." The workflow should be easy to repeat.

2. Build Three to Five Core Templates First

Start with your highest-volume or highest-risk roles. For example:

• frontline customer or operations roles;
• professional or specialist roles;
• people leader roles;
• agency placement roles;
• regulated or safety-sensitive roles.

Do not try to perfect every template before launch. Build a clean baseline, pilot it and improve based on evidence quality.

3. Write Candidate and Referee Copy Carefully

The best automation still depends on clear communication. Explain:

• why the reference is being requested;
• how long it should take;
• what information will be collected;
• who will review it;
• what to do if the candidate has a current-employer concern;
• how the referee can ask questions.

Plain language improves completion and trust.

4. Train Recruiters on Exceptions

Recruiters need to know what to do when:

• a candidate cannot provide a manager reference;
• a current employer must not be contacted;
• a referee gives adverse feedback;
• a referee volunteers sensitive information;
• a fraud flag appears;
• a hiring manager asks for a backchannel reference;
• the candidate disputes a comment.

Document these scenarios before launch. Software can make the standard path cleaner, but humans still need judgement for exceptions.

5. Review the First 20 Reports

After go-live, review the first batch of completed checks. Look for:

• questions that produce vague answers;
• questions that referees skip;
• reports that are too long or too thin;
• confusing candidate instructions;
• repeated hiring manager questions;
• unnecessary sensitive information;
• slow completion points.

Use those findings to improve templates and comms. A reference check platform should become more useful after the first month.

Common Buying Mistakes

Mistake 1: Buying the Longest Feature List

More features do not always mean better reference evidence. A smaller set of well-designed workflows can outperform a complex platform that recruiters avoid.

Mistake 2: Treating AI as the Decision Maker

AI summaries can save time. AI recommendations can create risk if the reasoning is not visible. Keep humans accountable for the decision.

Mistake 3: Ignoring Referee Experience

The referee is doing your hiring process a favour. If the workflow is long, confusing or hard to complete on mobile, completion will suffer and your employer brand may take the hit.

Mistake 4: Accepting Weak Integrations

An integration logo does not guarantee a useful workflow. Test the exact ATS trigger, data mapping, report writeback and permissions.

Mistake 5: Forgetting Retention and Access

Reference reports can contain sensitive commentary. Decide who can see them, how long they are kept and how exports are controlled before rollout.

How Skill Society Approaches Reference Check Features

Skill Society is built around structured, voice-first reference checks that reduce phone tag while keeping the evidence reviewable. Referees can respond through a guided voice workflow, and hiring teams can review structured summaries, transcripts and source evidence rather than relying on a loose recruiter note.

For buyers comparing reference check software, the important distinction is that Skill Society does not position automation as a replacement for recruiter judgement. The workflow is designed to help teams:

• ask consistent, role-relevant questions;
• collect richer referee feedback asynchronously;
• reduce manual chasing;
• keep reference evidence organised;
• review AI-supported summaries against source material;
• bring reference insights back into the hiring workflow.

This is especially useful for teams that already care about structured screening, AI-assisted hiring workflows and hiring-manager-ready evidence packs.

See the workflow, not just the checklist. If your team wants reference checks that are faster for recruiters and easier for referees to complete, book a Skill Society demo and compare the experience against your current process.

FAQ

Q: What are the most important reference check software features?
A: Start with candidate consent, role-specific templates, automated reminders, mobile referee completion, evidence review, ATS workflow, access controls and audit history. Add advanced fraud, AI and analytics features when your volume or risk level justifies them.

Q: Should reference check software include AI?
A: AI can be useful for transcription, summarisation, theme extraction and exception flags. It should not hide the source evidence or make the hiring decision. Ask vendors to show exactly how humans review and correct AI-generated outputs.

Q: Is voice better than written reference checking?
A: Voice can capture more nuance and reduce scheduling because referees can respond asynchronously. Written forms can work well for simple, high-volume checks. The best choice depends on role complexity, referee availability and how much source evidence the hiring team needs.

Q: Do we need ATS integration for reference checks?
A: If reference checks are frequent, ATS integration usually matters. It reduces duplicate data entry, keeps status visible and helps completed reports sit with the candidate record. For low-volume executive hiring, integration may be less important than confidentiality and evidence depth.

Q: What is the biggest warning sign in a reference check platform demo?
A: Be cautious if the platform cannot show candidate consent, hides original responses behind a score, has vague privacy controls, lacks current-employer safeguards or cannot explain how AI and fraud flags are reviewed by humans.

Q: How many reference check questions should a template include?
A: There is no universal number. Use enough questions to validate role-related requirements, but not so many that referees abandon the check. For many roles, a focused set covering relationship context, duties observed, strengths, development areas and job-specific criteria is more useful than a long generic questionnaire.

Q: How should Australian employers think about reference check privacy?
A: Treat reference checks as formal hiring records containing personal information. Keep questions job-related, notify candidates clearly, control access, manage retention and involve privacy or legal teams for sensitive, regulated or cross-border workflows.

Ready to Compare Reference Check Platforms?

Bring your current workflow problems to the demo: where checks stall, where notes become vague, where hiring managers lack confidence and where privacy or consent feels unclear. Then ask each vendor to show the exact candidate journey, referee journey, recruiter dashboard, report and ATS handoff.

If you want structured, voice-first reference checks that reduce recruiter admin while keeping humans in control of the decision, book a Skill Society demo.

Sources

• Skill Society: Voice-Based Reference Checks
• SkillSociety Lever ATS integration workflow
• Zinc employment reference checks
• Xref guide to choosing reference checking software
• RefNow reference checks
• Crosschq 360 digital reference checks
• HiPeople reference checks help centre
• Australian Public Service Commission factsheet: referee checks
• Australian HR Institute on character references
• U.S. Office of Personnel Management: reference checking
• OAIC agency referee reports
• OAIC: what is personal information?
• OAIC employee records exemption
• Fair Work Ombudsman workplace privacy best practice guide
• Australian Human Rights Commission guide to preventing discrimination in recruitment