It reads the thread you already send.

There is no calendar engine here, on purpose. Coordinating over email works. Copy in an address and the time, the panel and the location or link land in the record.

feedback task due +1 hourpanel-only submissiona round can require feedbackreschedule moves in place
company · interviews NEEDS CONFIRMING
The interviews list, with rounds and their feedback state

Real product screens. Figures shown in them are seed data from a demo workspace, not customer results.

What it takes off a thread

Three things, and a question when it is not sure.

The mail you already send
Re: Backend Engineer, Arjun M.

Hi Arjun, we would like to do the L2 on Thursday 14th at 3pm IST. Panel will be Meera Iyer and Rohit Desai. Link: meet.example.com/bk-l2

cc: interviews@yourcompany.checkedin
What lands in the record
TIMEThu 14, 15:00 IST
PANELMeera Iyer · Rohit Desai
LOCATIONmeet.example.com/bk-l2
THENFeedback task, due 16:00
And when the time is ambiguous, it asks.

“Sometime Thursday afternoon” does not become a guessed date. It raises a Confirm time task and shows in a Needs confirming tile, because a wrong interview time wastes a candidate's day and is impossible to apologise away.

Feedback

Only the panel can file it. And a round can refuse to advance without it.

Every TA team has the “we will write it up later” problem. Naming it in the system is what fixes it: the task appears an hour after the interview, against your scorecard, and the round can hold until it is in.

Structured, not a free-text boxScorecards are built in Form Studio: six answer types, six display widgets, and score bands that turn twelve answers into one readable verdict.
Rescheduling moves the interview in placeSame record, same id. No stale duplicate to hunt down and cancel, and the reminder moves rather than doubling.
An interviewer's world is four itemsThey see their own interviews and nothing else. If an interviewer says they cannot find a candidate, that is the design.
interviewer · my schedule 4 NAV ITEMS
What an interviewer sees: their own interviews and nothing else
Fig 1 The interviewer workspace. Deliberately the narrowest surface in the product.
When you would rather just type it

The thread is the default, not the only way.

You can record an interview directly against an applicant. The email path exists because it matches how coordinators already work, not because we wanted to remove the form.

applicant · record interview DIRECT ENTRY
Recording an interview directly against an applicant rather than from a thread
What this part does not do

Worth knowing before the demo, not after.

No availability finding or free-slot search a stated design decision, not a gap
No calendar invites sent capture only, from your own thread
No video conferencing it records the link you already use
No scorecard carry-forward between rounds read by nothing today
No per-round client-only visibility every panellist on a round sees it
Reminders need the worker process if it stops, nothing fires
Book a demo