Pipeline

The board

• One column per stage: New, Seen, Shortlisted, On hold, Hired. Not this time sits folded under the board; a card can always come back.
• Drag a card between columns, or open it and use Move to (that is the way on a phone). The stages are the ones findjobs already keeps on the application, so the inbox, the apps and the API all see the same move.
• The reply clock on a New card counts the hours since it arrived with nobody opening it, and turns red at two days. Opening the chat, or any move, stops it.
• Fit is the findjobs match score where the applicant has a profile; a gold mark is a gold applicant from the points race; an interview chip shows the next scheduled interview.

Scorecards

• Open a card and rate four points from 1 to 5: skills, experience, communication, fit for the team, with a note. One card per teammate per applicant; saving again replaces yours.
• The applicant's card shows the team's spread (lowest to highest) and the count, not one opinion. A manager who scored early does not steer the rest.

Where the data comes from

The applications, interviews and team accounts findjobs already has. Nothing is copied: a move here is a move on findjobs.ge, with the same history. A recruiter sees only the vacancies they were given.

In the demo

Three open vacancies and 44 applicants, invented. Every move and every scorecard is saved to your copy alone.

By API

GET /pipeline?job_id=… returns the board; POST /applications/{id}/status moves a card; POST /applications/{id}/scorecard saves a card. Scopes applications:read and applications:write.