A guide for pilot recruiters

Scout is the screening step.
Nothing more, nothing less.

You already have an ATS. You already have LinkedIn Recruiter. You already have a way to send a calendar invite. Scout slots into the one part of your day that nothing else has cracked: the intake call, the notes you scribble during it, and the hour afterwards turning a 35-minute conversation into something a hiring manager can actually read.

Start a screening 5 free trial screenings · no card required
Where Scout fits

One slot in the funnel.
The one nobody's nailed.

Scout doesn't replace anything you use today. It plugs into the one workflow step where your existing tools leave you to take notes by hand.

Source
LinkedIn, Indeed
Outreach
InMail, email
Screen with Scout
Intake call
Submit to ATS
Bullhorn, Greenhouse
Hand off & hire
Hiring manager

We don't try to be your CRM.

No pipeline stages. No candidate database. No outreach automation. No ATS integrations. Scout finishes when you click Export PDF or Copy. Whatever you use after the screening — keep using it. Scout is not trying to replace it.

How a screening works

Five steps. About 90 seconds of overhead before the call.

The whole point is to disappear into your existing flow. You set Scout up once, then run it the same way every time.

01

Create the screening

Click New screening. Paste in the job description, the company, and the role title. Add the candidate's name, their resume, and any context you want Scout to keep in mind — "emphasize Go experience," "remote-first team," "career switcher, explore self-direction."

~30 seconds paste JD optional resume
02

Review what Scout will probe for

Scout reads your JD and notes, then shows you a structured list of what it plans to extract from the call: required signals, strong-preference signals, behavioral signals, and open-ended exploration. Edit, add, or remove anything.

This is the highest-leverage 30 seconds in the entire flow. Recruiters who edit the scope before the call get noticeably sharper output. You're telling Scout what you care about — not what some generic transcription tool guesses.
03

Open the screening on your recording device

Most pilot recruiters bookmark Scout on their phone home screen and open it from there. Any signed-in device works. Persistent auth means no login at call time after the first sign-in on the device.

phone laptop tablet
04

Conduct the call. Scout listens silently.

Tap Start Recording. Run the call exactly the way you always run it — your conversation, your judgment, your relationship with the candidate. Scout is a quiet observer. It doesn't speak, suggest, or interrupt.

Tell the candidate. Two-party consent jurisdictions require it, and Scout's pre-recording screen reminds you. A short line like "I have a notetaker called Scout running — is that okay?" handles it. The candidate's verbal "yes" is captured in the recording itself.
05

Get your output ~5 minutes later

Stop the recording when the call ends. Within about five minutes, Scout produces an executive summary, a JD fit analysis with quoted evidence, a structured candidate profile, observations outside the schema, and the full searchable transcript. Set a disposition — Advanced, Not Advanced, Pending — and you're done.

~5 min processing PDF export copy / paste
Two ways to capture

Pick per call. Whichever fits the moment.

You aren't locked into one capture mode. The choice depends on whether you can put the call on speaker — there is no auto-detect, and there doesn't need to be.

Default · Speakerphone

Local-mic mode

You're in a quiet space and can put the call on speaker. Scout listens via your device's microphone — phone, laptop, tablet, whatever you've signed in on.

  • No bot in the meeting
  • Works for phone calls and any video platform
  • Uploads in the background as the call runs
When you're on headphones

Bot mode

Open office, shared space, or you just prefer headphones. Paste the Zoom or Teams meeting URL into Scout — a participant called Scout Notetaker joins the call and records.

  • Bot is visible to the candidate (extra disclosure)
  • Records full conversation, leaves when meeting ends
  • Same downstream output as local-mic mode
What you get back

A debrief, not a transcript dump.

Generic meeting tools give you a wall of text and call it done. Scout gives you the artifact a hiring manager actually wants to read — formatted the way recruiters already write debriefs.

01

Executive summary

Three to four sentences in recruiter-debrief style. The thing you'd say if a hiring manager grabbed you in the hallway and asked "what'd you think of the candidate?"

02

JD fit analysis

Each requirement marked Strong Signal / Some Signal / Weak Signal / Not Covered, with the actual quoted evidence pulled from the call. No more "where did they say that again?"

03

Structured candidate profile

Work history, capabilities, availability, comp expectations — anything Scout identified as relevant. Ready to paste into your ATS.

04

Observations

Things noted outside the schema. Energy level, motivations, what they kept coming back to. The soft signal that turns a profile into a person.

05

Full transcript

Searchable, with speaker labels and timestamps. Useful for the rare moment you need to go back to the source — and for sharing a verbatim moment with a hiring manager.

06

Disposition closeout

Advanced, Not Advanced, or Pending — with optional reason and notes. A single field, not a Kanban. Edit it any time.

scout.vantumworks.io / screenings / sample

Executive summary

Strong full-stack engineer with 8 years of experience, the last 4 leading a 6-person team at a fintech building payments infrastructure. Direct, articulate, and clearly motivated by ownership over a domain. Comp expectations sit at the high end of the band but within reach. Worth advancing to the hiring manager round.

JD fit

Strong signal
5+ years distributed systems experience
"We were processing about 40 million transactions a day across three regions, and I owned the routing layer end to end."
Strong signal
Led a team of 5+
"I had six engineers reporting in, two senior, four mid-level."
Some signal
Experience with payments domain
"Mostly card-present and ACH. Never touched cross-border or FX, that was a different team."
Weak signal
Go production experience
"I've written Go for side projects but our stack at work is mostly Java and Python."
Scope, on purpose

What Scout does — and deliberately doesn't.

Scout is opinionated about staying small. Several things you might expect from a recruiting tool are missing on purpose, not by accident.

Scout does this
  • Records intake calls (speakerphone or via meeting bot)
  • Extracts structured signal against the JD you provided
  • Produces a hiring-manager-ready debrief in ~5 minutes
  • Keeps a searchable vault of every screening you've run
  • Lets you set a disposition and notes per candidate
  • Exports to PDF; copies cleanly into any ATS
Scout doesn't do this
  • Manage pipeline stages or run a Kanban
  • Send outreach, schedule calls, or chase candidates
  • Integrate with your ATS (you export and paste)
  • Host a candidate database or marketplace
  • Coach you in real time during the call
  • Surface anything to your firm's leadership about you

You have 5 trial screenings.
Use them on real calls.

The trial isn't a tour — it's the actual product. Run it on the next five intake calls on your calendar. We'd rather you find out it works (or doesn't) on real candidates than on a sample script.