A recruiting pipeline can look busy and still be in trouble. The strongest candidates are waiting on feedback, everyone active came from the same narrow source, or nobody knows whether this funnel can produce a hire in time.
Strawberry can review the ATS alongside applications, sourcing, interviews, email, and calendars, so you can see what actually happened and where the pipeline needs new coverage rather than another status meeting.
Start with one role. The review stays read-only until you approve an update.
Start with the hiring goal
A useful review needs to know what the team is trying to hire, by when, and what the accepted bar and stages look like. It can work from a connected ATS view, export, spreadsheet, pasted list, or smaller candidate set.
If the target, timing, qualification bar, or conversion context is missing, say so. A universal pipeline score or coverage ratio creates certainty the team has not earned.
Ask your Strawberry companion: “Review our recruiting pipeline against our hiring goals, show the coverage conclusion and evidence, and recommend the best handoff without starting it.”
Review our recruiting pipeline
Review one role or pipeline slice against its real hiring goal.
Reconcile the ATS with what actually happened
An ATS stage is useful, but it may not show that an interview happened yesterday, a candidate is waiting on an answer, an interviewer never submitted feedback, or a scheduling thread has stalled. Strawberry can bring those signals together while keeping recorded state separate from interpretation.
- Candidates who need attention now, with the reason and owner.
- Missing feedback, evidence, next steps, or decisions.
- Delays and communication gaps that could damage candidate experience.
- Duplicate, stale, or conflicting records that may need correction.
Ask whether the pipeline can support the goal
Look at volume, job-related quality, stage balance, concentration, timing, momentum, likely attrition, and missing evidence in the context of the team's targets and known conversion patterns. A long list of weak or stalled candidates is not strong coverage.
The review should conclude that coverage is sufficient, potentially insufficient, insufficient, or not assessable, then explain the evidence and uncertainty behind that conclusion.
Choose the right way to rebuild coverage
Sometimes the fastest answer is already in the application queue. Sometimes the market is understood and the team simply needs more qualified candidates. And sometimes the thin pipeline is telling you that the titles, geography, compensation, employer set, or search strategy still need work.
A review-only request recommends the best handoff without starting broad research. If the request is to diagnose and rebuild the pipeline, agree on the definition, scope, sources, scale, and first review point before continuing.
Keep ATS corrections separate from the review
List proposed stage, owner, date, note, and duplicate corrections with the source and reason behind each one. Reviewing the analysis does not authorize a record change, candidate message, rejection, advancement, or new search.
When updates are approved, report what changed, what was skipped, and what still needs attention. That audit trail makes the next review easier to trust.
Turn the review into a useful team rhythm
Share the approved review through an access-controlled team destination, keeping sensitive candidate notes and proposed changes limited to the people who need them. Once the format works, save the method as a team skill.
A Routine can prepare the same role or pipeline view before a recurring review, bring in recent movement, and draft the priority list. Begin read-only or draft-first, with agreed sources, timing, audience, and review point.