DocsRecruitment

Interviews

Interview plans, the numbered participant queue, running a session live with the elapsed timer, and how a Passed result feeds the pipeline gate.

4 min readLast updated September 3, 2026

An interview in HRTEQ is a session, not a calendar entry. You build a plan with a numbered queue of applicants, then run it: one applicant at a time, with an elapsed timer, a result, and automatic progression to the next person in the queue. The results feed straight back into the pipeline gate.

Creating a plan#

A plan needs a title, a type, a mode, a scheduled time, a duration, and the applications taking part. Everything else is optional.

Field	Notes
`type`	`AGENCY` for your own screening, `PRINCIPAL` for the employer’s interview.
`mode`	`ONSITE`, `VIDEO` or `PHONE`.
`scheduledAt`	When the session starts.
`durationMin`	Per participant, not for the whole session.
`location`	For onsite sessions.
`meetingUrl`	Normalised on save for video sessions.
`interviewerName`	Recorded on the plan and copied onto each participant’s panel.
`applicationIds`	The queue. Duplicates are collapsed.

Only applications with status IN_PROGRESS can be added. If any one of the submitted IDs is unavailable, the whole request is refused with 409 rather than silently creating a partial plan.

Queue numbers are assigned from the order you submit, starting at 1. That number is what the applicants waiting outside are called by.

Creating a plan completes a checklist item. Adding an application to a plan marks EMPLOYER_INTERVIEW_SCHEDULED done. That is the entry requirement for the Employer Interview stage, so scheduling is what unlocks the move rather than a separate tick.

Running the session#

Starting a plan moves it to IN_PROGRESS and stamps startedAt on the first uncompleted participant. From then on exactly one participant is current — the one that has started and not finished.

Start
The plan status becomes IN_PROGRESS. If the plan has no participants the request is refused. Starting an already-completed or cancelled plan returns 409.
Interview the current participant
The screen shows who they are, the position and principal they are up for, their current stage and their location. A one-second timer ticks the elapsed time against the allotted duration.
Add time if needed
Time can be added to the current participant in increments of 5, 10 or 15 minutes, capped at 480 minutes total. Only the current participant can receive more time, and every addition is audited.
Record the result and finish
Finishing takes a result of PASSED, REJECTED, RESERVED or NO_SHOW, plus optional employer remarks. The participant is stamped complete, and the next in the queue starts automatically in the same transaction.
The plan closes itself
When the last participant finishes there is no next one, so the plan moves to COMPLETED with a completedAt timestamp. Once completed, the screen renders a printable result sheet.

The queue advances in one transaction. Completing the current participant and starting the next happen together. There is no window where nobody is current and no way for two participants to be current at once.

Results#

Result	Meaning
`PENDING`	Not yet interviewed. The default.
`PASSED`	The interviewer accepted them. This is the result that moves the pipeline.
`FAILED`	Did not meet the standard.
`REJECTED`	Declined by the interviewer.
`RESERVED`	Held as a backup — acceptable, but not selected now.
`NO_SHOW`	Did not attend.
`RESCHEDULED`	Moved to another session.

A result can also be set outside the live runner, which is how a correction is made after the fact.

How a result feeds the gate#

Recording PASSED on a completed participant marks the EMPLOYER_INTERVIEW_PASSED checklist item done on that application. That item is the entry requirement for the SELECTED stage, so the application becomes eligible to move the moment the interviewer finishes — and, if it was the last outstanding requirement, it moves by itself.

Changing a result away from PASSED reopens the checklist item, which correspondingly takes the eligibility away. See Stage gates.

Plan status#

Status	When
`DRAFT`	Being prepared.
`SCHEDULED`	Created and waiting for its start time.
`IN_PROGRESS`	Started; one participant is current.
`COMPLETED`	Every participant finished. The result sheet is available.
`CANCELLED`	Called off. Cannot be started.

What gets recorded#

Interviews are one of the more heavily audited areas, because a principal’s selection decision is exactly the sort of thing that gets questioned later.

interview.plan_created — with the title and participant count.
interview.plan_updated — plan-level edits.
interview.started — with the participant that became current.
interview.time_added — the increment and the resulting duration.
interview.participant_updated — a result set outside the live runner.
interview.completed — the result and which participant became current next.

The list endpoint returns the 100 most recent plans, newest scheduled first. Evaluations recorded against an interview live on a separate Evaluation record for structured scoring.

Was this page helpful?