Keeping submission status current without a spreadsheet
Chasing the client for feedback on candidates already submitted and keeping the record in one place, given that the record decides fee disputes. Reliability matters more than speed here.
The parser reads the resume, then somebody corrects the employment dates it merged, which is most of the time it was supposed to save.
Resumes arrive in every format that has ever existed, including scans with no text layer and designed templates in two columns that get read in the wrong order. Parsing is nearly always a third-party component, and its characteristic failure is employment history: dates written as ranges with words in them produce merged employers and wrong tenure.
- Bullhorn
- Greenhouse
- Outlook
When this is the wrong thing to build
Pick something else if your clients go silent for reasons a reminder will not fix. Faster chasing changes the relationship rather than the reply.
The constraint that shapes it
This is the sector where the boundary is sharpest, and it is worth stating plainly: rejection is the regulated act, not enrichment. More on how this sector works.
A list of things that are missing, worked until it is empty. Read what this shape is, or start from one of these.
- Chasing a compliance file to complete
- Chasing a referral fee through to a closing you cannot see
- Asking for the replenishment before the retainer runs to zero
- Chasing medical records until the set is complete
- Getting a deposition on the calendar of every party
- Chasing the warranty credit the distributor has not issued
- How do I get feedback from a client on submitted candidates?
- Where should submittal status live if the client works in a portal?
- How long should a candidate sit at submitted before I chase?
- Why do submittals sit in the portal with no status change?
Back to recruiting and staffing, or see how this is priced and scoped.