ATR Reporting covers the full lifecycle of an Authority to Recruit (ATR) request, from when it's raised, through approval, rejection, withdrawal or override, and on to the vacancy it produces once posted. Applicant Core and Posting Insights only pick up an ATR once it results in a live, posted vacancy, so anything that was rejected, withdrawn, overridden, or is still waiting on approval, isn't visible in those models. ATR Reporting is where that fuller picture lives.
Note: ATR Reporting is available with standard reporting. Every user can see every ATR request in all reports, whether or not they raised it. Once an ATR becomes a posted job though, that job's own details are only visible to users who already have access to that job, following your normal job permissions.
Access and Permissions
Data refreshes once a day, so it isn't built for tracking a single request minute to minute. An ATR raised in the last few hours may not show up yet.
Each row is one ATR. Draft ATRs, started but never submitted, aren't included, so how many requests were started or abandoned before submission can't be answered from this model.
What You Can Report On
Every ATR carries who raised it, the job title, role, region and location it's for, the recruitment reason, requested headcount, and the requested salary range with its currency. You can also see where it currently sits: its approval stage, who it's currently waiting on, and its overall status.
ATR: Status is a live snapshot, not a history. It shows the state an ATR is in right now rather than a timeline of what it passed through, so a status count reflects today rather than a trend of events over time. The values you'll see are Awaiting Selection, Completed, Deleted, In Progress, Posting, Rejected and Withdrawn.
For rejected, withdrawn or overridden requests, the model records who did it and when. There's no separate approval date or approver history field, though, so how long an approval took, or who already approved a request, can't be answered here, only who it's currently waiting on.
Once an ATR is posted, the model also reports on that vacancy's own status, dates, location, salary range, owner and reference, kept in the same place so you don't need a separate report to see whether a request has actually turned into a live role.
Tip: a few fields are worth filtering to a specific value rather than grouping by the whole column.
ATR: Current Stage, ATR: Job Region and ATR: Recruitment Reason are all free text fields, so grouping by the whole field can return a very long list of near-identical values. ATR: Current Approver Email can also hold more than one address in a single field when a request has several approvers waiting on it. Salary figures are recorded in different currencies, so a total across all requests should be filtered or broken down by currency first rather than summed as a raw total.
Confidential ATRs are included in every figure by default. Creating a confidential request is controlled by your TalosATS permissions, but once raised, you'll be able to view it in reports without any restriction.
Standard Reports
Four ready-made reports are available for ATR Reporting:
Report | What it shows |
ATR: Rejected and Withdrawn ATRs | Rejected and withdrawn ATRs raised in the selected period, showing the job title, who raised it, its status, who rejected it (where applicable), and the date it was rejected or withdrawn. |
ATR: Average Days From Request to Posting | Average and median days between an ATR being created and posted, trended by month. |
ATR: Overridden ATRs | Every ATR that's been overridden, showing the role, who overrode it, who originally raised it, and when. |
ATR: Raw Data | The full underlying detail behind every ATR, one row per request: request details, salary and headcount, current status, and vacancy outcome. Useful for exploring the data directly rather than a pre-built summary. |
What This Model Doesn't Cover
It doesn't include any custom questions added to your ATR form, only the standard fields.
No candidate or application data. Applicants, applications, stages, offers and hires live in Applicant Core, and movement over time is in Applicant Journey. Whether an ATR ended in a hire can't be answered here.
No job board or advertising detail, boards used, reposts and credits spent are in Posting Insights.
No diversity data, that lives in the relevant Equality and Diversity, EEO or Article 55 monitoring model, where available on your account.
Also not held here: draft ATRs, an approval audit trail, vacancy status history, or the cost of recruiting.
If a question needs one of these, Tali will say so and point you to the right place.
Questions to Ask Tali
You don't need to open a specific report to get answers, you can ask Tali directly in natural language. A few to try:
“Show me ATRs rejected or withdrawn in the last 30 days, with who raised them and who rejected them.” Tali will filter using the date each request was actually rejected or withdrawn. If you want requests raised in the last 30 days instead, say “raised” explicitly, it's a different question and returns a different set.
“What's the average and median time from an ATR being raised to being posted, by month this year?”
“List every ATR that's been overridden, who overrode it, and who raised it originally.”
“Give me the raw data behind our ATR requests.”
“How many ATRs are currently awaiting approval, and who's got the most waiting on them?”
“How does our ATR volume compare to the number of vacancies actually created?”
“What proportion of our requests are confidential?”