Sourcing trace
How a sourcing run went, for the person the search is run for: a line per step, in order, each with its status and its short description, the detail folded under it.
What it shows
How a sourcing run went, a line per step.
Props
| Prop | Type | What it does |
|---|---|---|
steps (required) | readonly SourcingTraceStep[] | The run's steps, in order. With none, nothing is drawn. |
agentName (required) | string | Who did the work, for the run's name ("How Scout searched"). |
live | boolean | The run under way: every step shows, as reported. Any other run (finished, gone quiet or overtaken) folds into one line that opens to its steps, a step it left pending or running shown stopped. |
labels | Partial<SourcingTraceLabels> | |
markdownComponents | MarkdownComponents | Per-element overrides for the steps' Markdown detail, such as a host's heading face. |
Data it needs
The component takes plain values and callbacks and keeps no records of its own. Pass it yours, from the Kith data layer or from a backend you already run.
Copy to your agent
Install RecruiterOS/recruit-ui and add a trace of each sourcing run's steps to my search page.Search progress
Where a search stands, for the person it is run for: its steps in order, each done, in progress or still to come, with the current step's next action under it.
Client search page
A search as the person it is run for sees it, on one page: the conversation that gets the brief ready, then each delivery of people with a Yes or No on each.