Luminid's pipeline is a board. Applicants move through the stages you configured for the role, from application received to decision, by drag and drop. What makes it different from other trackers is the commitment attached. Applicants see a visible timeline of their stage, so each one can see where they stand.
Reading the board
Each column headline shows how many people are in that stage, how many have moved on from it and how many dropped out there, and the median time people spend in it. A card turns gold at the edge when someone has waited 5 days in one stage, so the people who need an answer stand out. Click a stage name to open that stage on its own page: everyone in it now, everyone who ever went through it, with search, filters and sorting, and each person's full path through the pipeline with the dates and who moved them. Every move is logged with the time it happened and who made it, so you can always reconstruct where someone was and when.
Your decision policy
Your organization can set a decision window, between 7 and 45 days, counted from the last time an application moved, or from the end of a wait your team set for the applicant, whichever is later. Once you save one in Settings, applicants see it on their application page, your job posts and your trust page. Until then Luminid's default of 14 days runs, and applicants are told it is Luminid's, never your promise. It is the operational core of the no ghosting commitment, so pick a number your team can actually keep.
Nudges, then auto-close
When an application sits without activity, the assigned team gets a reminder 3 days before the window ends. If there is still no action 7 days past it, the application closes automatically and the applicant is told whose rule closed it, your window or Luminid's default. An auto-close is never a silent archive, and it is the outcome to avoid. It tells the applicant your process failed them, and if you publish an employer trust page, every automatic close lowers the decision rate it shows. That rate counts only the decisions your team records, so neither an automatic close nor a withdrawal ever counts as one. The nudges exist so it never gets that far.
Decisions and dispositions
Closing an applicant means recording an outcome. Hired, offer extended, or reserved for future roles on the positive side. Not moving forward, overqualified, underqualified, position filled, withdrew, or no show on the negative side. Applicants receive respectful feedback, never the Role Match number, and when they lacked skills your role wanted, the decision points them to where those skills can be practiced and verified.
Holding a message, with a reason
When you move someone into a stage that messages them, Luminid asks first. Notify is the default, and Enter confirms it. Choose Hold the notification when the Job Seeker should not be told yet, and say why: imported from another system, told in person, decision pending, or other with a short note. The last step of a decision has the same choice, so you can record a decision now and tell the Job Seeker later. Your own automations still run on a held move.
A held card shows a chip on the board, gold with the date for a pending decision and grey otherwise. Open the card to see the held message, then Send it now, which sends exactly what was held, or Push a week.
Decision pending needs a decide by date. On that date the person who held it and your company admins get a reminder in Luminid and by email, once a day until it is sent or pushed. Meanwhile the Job Seeker's application page keeps showing the stage they last saw, tells them when a decision is expected, and lets them ask for an update once a week, which notifies the people on the role and your admins. If your decision policy deadline passes with nothing sent, the page tells them plainly that no decision has been made yet. Imported and told in person holds show the Job Seeker nothing.
Holding goes against what Luminid promises Job Seekers, which is why every hold carries a reason and a date. A later move or decision replaces an earlier held message.
Bulk decisions
Two tools keep high-volume roles honest without one-by-one clicking. Select mode lets you check multiple applicants in a stage and act on them together. And when your hired count reaches the role's openings, Luminid offers to disposition all remaining applicants as position filled with feedback, immediately or after a delay you choose. Bulk closing is always opt-in, and every affected applicant still gets a real notification.