Two views of history

A candidate has two views of their history inside Talinty:

• Application History. Every role this candidate has applied to (or been added to) in your workspace. One row per role, with status, dates, and outcome. The wider view: where has this person appeared across our hiring?

  
  

• Timeline. Every action taken on this candidate inside one role, in order. Status moves, notes added, messages sent, assessments completed, scorecards submitted. The narrower view: what happened with this candidate, when, and who did it?

Both views are part of the candidate profile, in separate sections. Use the Application History when a candidate has applied multiple times. Use the Timeline for everything else.

Reading the timeline

Each entry in the timeline shows four things:

• What happened. The action itself: Moved to Online Screening, Note added, Disqualified, Assessment completed.

• Who triggered it. A teammate's name, or System for automated changes.

• When. Date and time, with relative timestamps (2 hours ago) for recent items.

• The reason or detail, if any. For status changes that require a reason, the reason appears in the entry. For notes, a preview of the note text. For messages, the subject line.

Click any entry to expand it. Notes show in full. Status changes show the before and after states. Messages open the full email body. Assessments link to the score and recording.

Status badges and what they mean

Alongside the stage (Application, Online Screening, and so on), every candidate has a status badge that tells you what's happening to them right now. The standard set:

• New. Application received, not yet reviewed.

• In Review. A teammate is actively working the profile.

• Assessment Sent. Skill test or video interview is out, awaiting candidate response.

• Shortlisted. Advanced past initial screening.

• Hired. Offer accepted.

• Disqualified. No longer in consideration, kept in the pool for record and future searches.

Badges change automatically as candidates move through the pipeline. You can also set them manually from the candidate's profile when the situation calls for it.

Filtering the timeline

Long-running candidates can have hundreds of timeline entries. The filter bar at the top of the section lets you narrow it:

• By type. Show only status changes, only notes, only messages, only assessments.

• By person. Show only entries triggered by a specific teammate.

• By date range. Show what happened this week, this month, since the last interview.

Filters stack. Status changes by Sarah in the last 30 days is a valid combination.

What's automatic vs manual

Some timeline entries are triggered by people; others by the system. The entry tells you which.

• Manual entries (a teammate's name on them): notes added, messages composed by a person, manual stage moves, manual disqualifications.

  
  

• Automatic entries (System on them): application received, assessment auto-sent when the candidate hit Online Screening, status auto-updated when the candidate completed an assessment, rejection email auto-fired on disqualification at a configured stage.

Automated actions can be turned off per role from the role's settings if you'd rather handle them manually. Most teams keep the automations on for early-stage moves and turn them off for late-stage ones.

Why the trail matters

Beyond the practical "what's been done with this candidate" question, the timeline serves a real purpose: it's the record behind every decision your team makes. When the hiring manager asks why you advanced this candidate over another, the timeline answers. When a candidate emails three months later asking why they were rejected, the timeline answers.

Keeping the record honest matters more than keeping it polished. If the team has a difficult conversation about a candidate, capture the conclusion in a team-visible note. The note shows up in the timeline. Three months from now, that's the only context anyone will have.