Data Model Definitions

Data Model	Description	Available In	Example Questions
Applicant Core	A near-real-time model for most day-to-day hiring and vacancy questions, with applicant, vacancy and activity data in one place. Covers: Applications, offers, interviews, vacancies and related activity, across about 160 ready-to-use fields Candidate progress: applied date, offer and start dates, current stage and milestone, rejection reasons Integrated services: DocuSign, Certn background checks, Interview Scheduler, Referencing, Talent Strength, TrustID, ATR vacancies Custom metrics with built-in formulas, for example total applications or total interviews booked Does not cover: History or time: only each candidate's current stage and milestone at job level, so no time in stage, time between milestones, conversion rates or progression history (use Applicant Journey or Auto Mode) SMS data, HR system data, job posting history (repost dates, credits used) Application form responses, diversity or EEO data ATR drafts or unposted requests, Talos user activity Reports built on it: 50	Standard Reporting Intelligence? Yes	How many applications did we receive last month, by vacancy? Which interviews were cancelled or declined in the last 2 weeks? How many Certn packages were sent this year, and how many are completed? Which vacancies are live, scheduled or archived right now, and who owns each one? How many applicants came from each source this quarter?
Applicant Journey	Job-level history of how candidates move through your recruitment process, including time between stages. Covers: Historical progression by job: milestones (Unassessed, Shortlist, Offered, Hired, Rejected) and stages (CV Review, Interview, Formal Offer) Time between stages and time spent within each stage Counts of candidates entering a stage over a period, and candidate ratios between stages Breakdowns by Vacancy, Vacancy Owner, Team, Region and other job-level attributes Natural-language queries, Auto Mode model selection and Tali's guidance Does not cover: Individual applicants or application-level activity (job-level reporting only) Candidate-level fields such as Candidate Source Reports built on it: 23	Reporting+ Reporting Intelligence? Yes	What is our average time to hire for each team this year? On average, how many days does it take to move candidates from Unassessed to Shortlist, by vacancy owner? How many candidates were moved to Hired each month this year? Which open vacancies have the longest average time from application to Offered? What is the average number of days from vacancy created to hired, by vacancy?
Posting Insights	An hourly-updated model on how vacancies are distributed and advertised across job boards. Covers: Job board postings by vacancy, team and board Repost activity Credit balances and spend, across branded and non-branded postings Posting statuses such as sent, success or deleted About 65 fields: vacancy details, job board metadata, headcount, ATR context, recruitment cost fields Does not cover: Candidate or application data: applications generated per board, pipeline progress, interview or offer activity, time-based hiring metrics Historical credit transaction logs, application form responses, diversity or EEO data, stage or milestone data, SMS data, HR system data For applications by source, candidate journey or time to hire, use Applicant Core, Applicant Journey or Auto Mode; for vacancy and application data in one view, use Applicant Core Reports built on it: 6	Standard Reporting Intelligence? Yes	Which job boards has each live vacancy been posted to? How many credits have we spent per board this quarter, branded versus non-branded? Which postings are due to expire in the next 7 days? How many times has each vacancy been reposted? Which teams are using which job boards?
ATR Reporting	A model refreshed once a day, covering Authority to Recruit (ATR) requests and the vacancies they produce. Covers: An ATR request end to end: who raised it, current approval stage and current approver, overall status Whether it was rejected, withdrawn or overridden, and by whom Recruitment reason, requested headcount, job title, role, region, location, requested salary range and currency The resulting live vacancy: its status, dates, location, salary range, owner and reference details Two ready-to-use measures, Total Number of ATR Requests and Total Number of Vacancies, for volume and trends by month or any period Does not cover: Custom questions added to an ATR form Candidate or applicant-level data Hiring and time-to-hire tracking after a vacancy is posted Watch out: ATR: Current Stage, ATR: Job Region and ATR: Recruitment Reason are free text, so they can return many distinct values unless filtered first ATR: Current Approver Email can hold more than one address when a request has several approvers Salary fields mix currencies and pay frequencies: filter or break down by currency before summing Reports built on it: 4	Standard Reporting Intelligence? Yes	How many ATR requests are currently awaiting approval? Who has the most ATR requests waiting on them? How does ATR volume compare to vacancies actually created, by month this year? What proportion of ATR requests are confidential? How do ATR requests break down by status and recruitment reason?
Fourth Reporting (FourthHR)	A regularly refreshed model on what happens once a new starter is sent to Fourth for onboarding, with the vacancy behind them. Covers: Onboarding end to end: the route (Onboarding API or Employee API), current status (not started, sent to the candidate, in progress, completed or in error), key dates, location, division and job title Pay and contract details, and right to work information The linked vacancy: country, county, reference, job title, location and current status Three ready-to-use measures: Total Number of Fourth Submissions, Total Completed Onboardings, Total Fourth Errors Does not cover: Anything before a new starter form is submitted: applications, stages and offers (Applicant Core), or how long each stage takes (Applicant Journey) Job board or advertising activity (Posting Insights) Diversity and equality data (EDI, EEO and Article 55 models) Client-specific onboarding questions Anything in Fourth after onboarding is complete: it shows what was sent and whether Fourth accepted it Reports built on it: 5	Reporting+ Reporting Intelligence? Yes	How many new starters are currently stuck in onboarding or showing an error? Which locations or divisions have the most onboarding issues right now? How do completed onboardings compare month to month by location and division? How many onboardings came through each route this year? Who is due to start in the next 30 days, and what is their onboarding status?
Equality and Diversity Monitoring (UK EDI)	Applicant-level data for UK Equality, Diversity and Inclusion (EDI) monitoring. Covers: Responses to questions such as gender identity, ethnicity, disability, age range and other protected characteristics Supports compliance with UK equality legislation Does not cover: Personally identifiable applicant information Reports built on it: 32	Standard and Reporting+: the 2 raw data Reports are Standard; the breakdown Reports and the Dashboard are Reporting+ Reporting Intelligence? Yes	What is the ethnicity breakdown of applicants for each team this year? How are gender identity responses spread across each milestone this quarter? What proportion of applicants for each vacancy disclosed a disability? What is the age range breakdown of applicants by vacancy? How do nationality responses break down by team?
Equal Employment Opportunity (EEO) Monitoring (US)	Applicant-level data for US Equal Employment Opportunity (EEO) monitoring. Covers: Responses to questions such as gender, race and veteran status Supports compliance with US equality legislation Does not cover: Personally identifiable applicant information Reports built on it: 2	Standard Reporting Intelligence? Yes	What is the race breakdown of applicants for each vacancy this year? How many applicants of each gender reached the Hired milestone this quarter? How do veteran status responses break down by posting team? How does the gender split of all applicants compare with those who reached Hired?
Article 55 Monitoring (Northern Ireland)	Applicant-level data for community background and gender monitoring under Article 55 of the Fair Employment and Treatment (Northern Ireland) Order 1998. Covers: Community background and gender responses, for Article 55 monitoring Does not cover: Equality questions beyond community background and gender (for UK EDI, use Equality and Diversity Monitoring) Reports built on it: 2	Standard Reporting Intelligence? Yes	What is the community background breakdown of applicants for each vacancy this year? How does the gender split of applicants compare with those who reached the Hired milestone? How many applicants from each community background reached each milestone this quarter? What is the community background breakdown by posting team?
Application Forms, Data Capture & Candidate Fields	Candidate answers to custom questions from the Question Bank, Data Capture forms and Candidate Custom Fields. Covers: Every synced question or custom field as its own reportable column Standard context fields: candidate name, email, applied date, job title, vacancy reference, posting team, current stage Total responses recorded for a question, and how responses are spread across applicants Does not cover: Form names, form completion status, or whether a form was submitted or outstanding (answer data only) Questions or custom fields that look missing may need a resync from the Reporting Settings page Reports built on it: 0	Reporting+ (each Reporting+ client gets their own copy when they run Report Sync on the Report Settings page) Reporting Intelligence? Yes, select this model before you ask, as Auto mode may not find it	What did each candidate for vacancy [reference] answer to [question name]? How are answers to [question name] spread across applicants this month? How many responses have been recorded for [question name], by posting team? Show candidates currently at the Interview stage with their answers to [custom field].
User Adoption	An overview of how people in your organisation use Talos, with one record per user account. Covers: Each user's name, email, job title, account created date, most recent login date and a stored login count A daily login history: how many times each account logged in on each day Finding inactive or dormant users, tracking logins over time, monitoring adoption across user accounts Each user's Interview Scheduler calendar connection status Does not cover: Login trends before 2026: the daily login history starts in 2026 (the most recent login date covers all years) Anything outside user accounts, logins and calendar status, such as SMS, vacancy or candidate data Watch out: The stored login count is one figure per account: read it per user, never add it up; use the daily login history for totals Job titles are free text typed by users, so one role can appear under different spellings Reports built on it: 4: - Users' Last Login - User Activity - Active Users - Interview Scheduler: User Calendar Connection Status	Standard Reporting Intelligence? Yes	Which users have not logged in for the last 90 days? How many logins did we have each week last month? Who were our 10 most active users last month? How many users logged in this month compared with last month? Which users have not connected their calendar to Interview Scheduler?
Agency Portal	Vacancies your organisation has released to recruitment agencies through the Talos Agency Portal, and the candidates those agencies upload against them. Covers: Which agencies received which roles How many applications each agency submitted How far those applications progressed: interviewed, offered, hired or rejected How quickly agency CVs are first opened Does not cover: History or time in stage: milestones and stages show where an application sits now Direct applications, job board activity and diversity data (held in other Reports) Organisations that do not release vacancies through the Agency Portal (they will have no data) Watch out: A vacancy appears on many rows: application counts and rates are reliable, but the current Number Of Vacancies figure overstates vacancies and should not be used until it is corrected Reports built on it: 3: - Agent Submissions, - Agency Vacancies, - Agency Performance: Interview, Offer and Hire Rates (Reporting+)	Standard Reporting Intelligence? Yes	How many applications has each agency submitted this quarter? Which vacancies were sent to which agencies last month? What are the interview, offer and hire rates for each agency? Which agents submitted the most applications this month? How quickly are agency CVs first opened, by agency?
SMS Detail	Text messages sent from Talos, with one row per message. Covers: Each message's created date, delivery status (Delivered, Queued or Failed) and the linked Talos account SMS volumes over time, and how many messages were delivered or failed Messages created from 2018 onwards Does not cover: SMS billing or cost: figures count messages, not the billable segments a long message is split into The message text, template, phone number, vacancy or progression stage a message was sent from Organisations without SMS messaging set up in Talos (they will have no data) Reports built on it: 1: SMS Sent	Standard Reporting Intelligence? Yes	How many SMS messages did we send each month this year? How many messages failed last month? Which users sent the most delivered messages this quarter? What share of messages sent this year were delivered versus failed? How many messages are currently queued?

TalosATS Data Model Definitions

Data Model Definitions