# Hiring manager intake meeting requirements: how to stop misaligned role briefs on Mac

> Fix misaligned role requirements before sourcing starts. Run a one-hour hiring manager kickoff, write the must-haves down, and send a recap in Gmail.

URL: https://www.lazur.app/for/recruiters/problems/hiring-manager-intake-meeting-requirements-drift
Updated: 2026-11-09

A hiring manager intake meeting sets what a role needs before anyone starts sourcing. Requirements are misaligned when the recruiter and the hiring manager leave that meeting with different versions of the job. The fix is a short, structured kickoff, a one-page written brief, and a recap that both of you confirm the same day.

## Quick answer

- Misaligned requirements show up as restarted searches, repeated screens and shortlists the hiring manager rejects.
- No study in the research measures this cost directly. The nearest public anchor is SHRM's $5,475 average cost-per-hire for nonexecutive roles.
- Run a kickoff of about an hour and leave with three written outputs: business objectives, attributes and the split of work.
- Send a one-page brief before the meeting, then a same-day recap in Gmail so both sides hold the same list.
- Check a handful of sample profiles before sourcing at volume. Lazur can point, explain, dictate and draft, but it does not run the meeting.

## What misaligned intake requirements costs you

- **Sourcing restarts.** A requirement that changes after sourcing starts can make the search run twice. Candidates you already contacted may no longer fit the brief. You pay for the outreach a second time and explain the change to people who expected a clear role.
- **Repeated screens and interviews.** SHRM reports that screening and interviewing each average 8 to 9 days. A change to the must-haves during those stages can send work back to an earlier step. The cost is calendar time and recruiter hours.
- **Lost candidates.** People with good options do not wait around for a role that keeps moving. A slow, confused process can cost you the candidate you wanted most. This cost is hard to count, but it shows up when strong people stop replying.
- **Higher cost at senior levels.** SHRM's 2025 averages show $35,879 per executive hire, against $5,475 for nonexecutive roles. A confused executive brief is expensive because the hire itself is expensive, so the cost of the mistake grows with the seniority.
- **Trust between recruiter and hiring manager.** When shortlists keep missing, the hiring manager stops trusting the recruiter's picks. The recruiter then sends more candidates to cover the gap, which adds noise and more review time for everyone.

## Why it happens

1. **The job post is copied, not written.** Most briefs start as last year's job post. Old lines stay because nobody has time to rewrite them. The hiring manager thinks the post reflects what they want, and the recruiter takes it as the spec.
2. **Must-haves never get written down.** People agree out loud and move on. Without a written list, each person keeps a private version of the role. The mismatch shows up at the first screen, not in the meeting.
3. **Objectives are not agreed.** A hiring manager may want someone to build a team. A recruiter may search for a specialist. Both descriptions can fit the same title, which is why the title alone does not settle anything.
4. **No rule for late changes.** A strong candidate who misses one skill often triggers a new must-have. Without a rule that says when a requirement may change, the list keeps growing with each interview.
5. **Credential defaults.** A degree or a set number of years gets added because it is easy to check, not because the work needs it. That line narrows the pool before anyone has looked at a resume.
6. **The hiring manager joins late.** If the hiring manager sees candidates only after sourcing starts, their picture of the role was never tested. The first screens expose the gap, and the search restarts from the brief.

## How to fix it

- **Hold a one-hour kickoff with three written outputs.** Greenhouse describes the role kickoff as about an hour and as the first step in structured hiring. Leave with business objectives, an attribute list and a written split of recruiter and hiring manager work. If one output is missing, book a follow-up before sourcing.
- **Send a one-page brief before the meeting.** A brief gives the hiring manager something concrete to mark up. Put the title, objective, must-haves, nice-to-haves and hard limits on one page. Ask for the markup before the meeting, so the meeting time goes to disagreements rather than basics.
- **Build a must-have scorecard in Google Sheets.** Use one row per requirement and a Type dropdown with Must-have or Nice-to-have. Reviewers score every candidate against the same rows. Interview feedback then stays tied to the agreed list, not to whoever spoke last.
- **Send a same-day recap in Gmail.** Write the agreed must-haves, open questions and owners in one email. Send it the same day, while everyone still remembers the decisions. Ask for a reply that confirms the list, so silence is not read as agreement.
- **Check sample profiles before wide sourcing.** Greenhouse suggests that complex roles reconvene at the start of sourcing to review sample profiles. Pull a handful, get the hiring manager's pick and reasons, then edit the requirements where the no answers point.
- **Set a rule for late changes.** A must-have changes only when both sides agree and the change goes into the recap. Anything else becomes a nice-to-have. Write the rule into the brief, so both sides see it before the first interview.

Misaligned intake requirements means the recruiter and the hiring manager leave the same meeting with different pictures of the role. You may agree on the job title and still disagree on the must-haves. The hiring manager wants a senior engineer who has run a team. The recruiter heard mid-level. Nobody says so in the room. The gap shows up later, when the first candidates reach the hiring manager and get turned down for reasons nobody wrote down.

## What misaligned requirements cost you

Start with the costs you can see. A role that gets re-scoped mid-search means sourcing runs twice. Screens get repeated, and good candidates lose interest while they wait. The hiring manager starts to doubt the shortlist, which slows every decision after it. Those costs are real even though no invoice arrives.

The best public number is cost-per-hire. SHRM's 2025 benchmarking report gives an average of $5,475 for nonexecutive roles and $35,879 for executive roles. SHRM describes executive hires as nearly 7 times more expensive. Cost-per-hire covers all hiring spend, so it shows the scale of one hire. It does not isolate the loss from one bad kickoff.

- **$5,475** Average cost-per-hire for nonexecutive roles in SHRM's 2025 benchmarking survey ([source](https://www.shrm.org/about/press-room/shrm-releases-2025-benchmarking-reports--how-does-your-organizat))
- **$35,879** Average cost-per-hire for executive roles, which SHRM says is nearly 7 times the nonexecutive figure ([source](https://www.shrm.org/about/press-room/shrm-releases-2025-benchmarking-reports--how-does-your-organizat))
- **2,371** Members who responded to SHRM's 2025 recruiting benchmark survey, fielded January 9 to March 3, 2025 ([source](https://www.shrm.org/about/press-room/shrm-releases-2025-benchmarking-reports--how-does-your-organizat))

The same SHRM survey reports that screening and interviewing each average 8 to 9 days. Those are the stages where a requirement change does the most damage. If the must-haves move after screening starts, you re-read resumes you already reviewed and repeat interviews that already happened.

Here is what the public data does not show. The research checked here does not measure the cost of misaligned requirements directly. Some vendor reports make strong claims about this gap, but their original data could not be checked, so this page leaves them out. Treat any single figure about misalignment with care.

## Why intake requirements drift apart

Most drift starts with the job post. Someone copies last year's description, adds a few tools and sends it over. The hiring manager assumes the recruiter read every line. The recruiter assumes the list is final. Neither side says which lines matter most.

Greenhouse's kickoff guidance treats the meeting as an explicit agreement. Its expected outputs are business objectives, an attribute map of skills, traits and qualifications, and a documented split of recruiter and hiring manager work. Asking for written outputs suggests that, without a structure, these answers stay in people's heads.

Requirements also grow after the meeting. A hiring manager sees a strong candidate who lacks one skill, then adds that skill to the must-have list. The recruiter has no rule for when a must-have may change, so the list keeps getting longer. Every addition makes the next candidate harder to judge.

![Recruiter at a laptop reviewing notes before a hiring manager intake meeting requirements discussion](https://images.lazur.app/content-images/problem/hiring-manager-intake-meeting-requirements-drift/hiring-manager-intake-meeting-requirements-1-a84e44.jpg)

## Role kickoff meeting checklist for recruiters

Greenhouse describes the role kickoff as about an hour, and as the first step in its structured hiring process. Protect that hour. Less time usually leaves the business objectives vague. More time often goes to arguing about the job title. Send the hiring manager the agenda a few days ahead, so they arrive with their real priorities.

### The agenda that keeps requirements tight

1. Business objectives: what should this hire deliver in the first year?
2. Must-haves: the few skills or traits a candidate cannot do without.
3. Nice-to-haves: skills that help but will not block an offer.
4. Hard limits: pay band, location rules, licences and start date.
5. Split of work: who writes outreach, who screens and who decides the shortlist.
6. Success: how both of you will judge the hire after the first few months.
7. Recap: read the must-haves aloud and get a clear yes from each person.

Outputs matter more than talk. Leave the room with three things on paper: the objectives, the attribute list and the split of work. If one of them is missing, the meeting did not finish its job.

## Must-have vs nice-to-have requirements

The table shows how to write each type so a stranger could judge a candidate against it. Vague words like strong communicator or fast learner cannot be checked. Write what the candidate must show, and how you will check it.

| Requirement type | Write it as | Clear example |
| --- | --- | --- |
| Must-have | What the candidate must show, and how you will check it | Has shipped a feature to production. Check with a work sample or a described project. |
| Nice-to-have | Named, with the rule for judging it | Has used a CRM. Judged from examples, not certificates. |
| Credential or degree | Only when law, a licence or the work itself requires it | Active professional licence required by law for this role. No degree listed. |
| Pay and location | Band, location rule and who approves a change | Remote within the country. Pay band set by HR. Changes need the hiring manager and HR. |
| Interview panel | Names and the one question each person owns | Engineer owns the systems question. Recruiter owns scheduling and the closing call. |

_Write each line so a reviewer can answer yes or no from a resume or interview answer._

## Fixes you can use without buying anything

None of these fixes needs new software. You need a document, a calendar slot and one rule about changes. Start with the brief, because a marked-up page is quicker to fix than a blank meeting.

![Colleagues gathered around a table talking through role requirements in an office](https://images.lazur.app/content-images/problem/hiring-manager-intake-meeting-requirements-drift/hiring-manager-intake-meeting-requirements-2-4f83ee.jpg)

### Write a one-page brief before the meeting

Open a new document in Pages with ⌘N, or use Google Docs. Put the job title, the business objective, the must-haves, the nice-to-haves and the hard limits on one page. Send it to the hiring manager and ask them to mark anything they disagree with. Ask for the markup before the meeting, not during it.

### Turn must-haves into a scorecard in Google Sheets

Make one row per requirement. Add a column called Type and set it to a dropdown with two choices, Must-have and Nice-to-have. In Google Sheets, select the column, then go to Data > Data validation and add the list. Reviewers then score each candidate against the same rows, so the debate stays on the list. For the full steps, see [how to create a dropdown list in Google Sheets](https://www.lazur.app/how-to/create-a-dropdown-list-in-google-sheets).

### Send a recap in Gmail the same day

Write a short recap while the meeting is fresh. List the agreed must-haves, the open questions and the owner of each decision. Send it the same day. If the hiring manager works in another time zone, use Schedule send next to Send in Gmail so it lands at a sensible hour. The recap becomes the record you search when a requirement comes up again. For the steps, see [how to schedule an email in Gmail](https://www.lazur.app/how-to/schedule-an-email-to-send-later-in-gmail).

### Recheck with sample profiles before wide sourcing

Before you source at volume, pull a handful of profiles and put them in front of the hiring manager. Ask which ones they would call, and why. Each no points at a requirement that was unclear or too strict. A fix now costs one conversation. A fix after the first screens costs the work already done.

### Set one rule for late changes

Agree on one rule before sourcing starts. A must-have changes only when both of you agree and the change goes into the recap. Anything else goes on the nice-to-have list. The rule takes a minute to write, and it stops the list growing one interview at a time.

> **Reply with the brief:** When a hiring manager asks for a new requirement, reply with the brief and ask which must-have it replaces. Often the answer is none, and the request becomes a nice-to-have.

> **Candidate and client data:** Briefs can include candidate notes, client names or patient details, especially in regulated jobs like nursing, law and accounting. Follow your employer's rules on where that data can go. Keep it out of personal notes apps and public chats.

## Mistakes that keep requirements misaligned

- Treating the kickoff as a formality. If nobody leaves with the written outputs, the brief is still a guess.
- Reusing an old job post as the brief. Old posts carry requirements nobody needs anymore.
- Adding must-haves in a late debrief with no rule to stop it. The list grows one interview at a time.
- Making a degree the default. Keep it only when a law, a licence or the work itself requires it.
- Skipping the sample profile check, then blaming the talent pool when the first screens disappoint.
- Sending the recap to the hiring manager only. Include the recruiter's steps so both sides see the split.

![Person typing meeting notes on a laptop after a hiring manager intake meeting](https://images.lazur.app/content-images/problem/hiring-manager-intake-meeting-requirements-drift/hiring-manager-intake-meeting-requirements-3-573f53.jpg)

## Where Lazur helps, and where it does not

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. It does not click buttons, edit files or run your applicant tracking system for you. That limit shapes where it fits.

Hold ⌥ ⌘ while an ATS field is on screen and ask what it controls. Lazur can point at the field with a circle and a label. For a click by click setup, ask it to walk you through the steps. It waits for each click, and you do the clicking.

Hold fn to dictate your kickoff notes at the cursor in the brief or sheet you have open. Dictation is unlimited on both plans, so you can talk through a messy meeting without typing every line.

For market context, Lazur can run research in its own Chrome tabs and return a summary and a report. Use it to see how other teams word a requirement, then judge the answer yourself. It does not know your hiring manager's priorities, and it does not decide your must-haves.

Lazur listens and looks at the screen only while you hold the shortcut. Audio and screenshots go to AI providers to answer, and they are not stored. Content is never used to train AI models. Still, follow your employer's rules before you put candidate or patient details on screen.

If your team uses Greenhouse, its Job kickoff form covers these questions inside the product. The support page says the form is on the Core, Plus and Pro tiers, so check which plan your company has. Lazur does not change anything in that form.

## Where to start this week

Start with the next open role. Book a kickoff, send the one-page brief ahead, and bring the table with you. The meeting moves faster when the hiring manager has already read the page and marked it up.

## With Lazur

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ and ask; it sees your screen, answers out loud, points at buttons and walks you through apps. Hold fn to dictate. Free for 3 days, then $18/month: https://www.lazur.app/download

- “Draft a recap of the must-haves we agreed on today.”: Lazur types the draft. You read it, fix any line the hiring manager would dispute, and send it yourself. (Drafts it)
- “What does this field control in our tracker?”: Lazur explains the field out loud while you hold the shortcut, so you know what a change will affect before you make it.
- “Where is the interview plan section on this page?”: Lazur draws a circle and a label around the section on your screen, so you stop scanning the whole page.
- “Walk me through setting a dropdown on this column in Google Sheets.”: Lazur guides you one click at a time and waits for each click. You do the clicking, and Lazur does not operate the app.
- “Hold fn and talk through the meeting notes.”: Dictation types clean, formatted text at the cursor in any app, so the notes land in the brief you have open.
- “Draft the recap of the must-haves we agreed on.”: Lazur types a draft email. You check every line, change anything the hiring manager would dispute, then send it yourself.
- “Research how other teams word this requirement.”: Lazur runs the research in its own Chrome tabs and returns a summary and a report for you to judge.

## A plan you can start this week

- **Monday: Draft the one-page brief.** Write the title, business objective, must-haves, nice-to-haves and hard limits on one page. Send it to the hiring manager and ask for a marked-up copy before the meeting.
- **Tuesday: Hold the kickoff.** Keep it to about an hour. Work through objectives, must-haves, nice-to-haves, hard limits and the split of work. Leave with the three written outputs, or book a follow-up.
- **Wednesday: Send the same-day recap.** Email the agreed must-haves, open questions and the owner of each decision in Gmail. Ask the hiring manager to reply with a yes. Use Schedule send if the timing matters.
- **Thursday: Build the scorecard.** Create one row per requirement in Google Sheets. Add a Type column with a Must-have or Nice-to-have dropdown. Keep the must-have list short enough that a reviewer can hold it in mind.
- **Friday: Check sample profiles.** Pull a handful of profiles before sourcing at volume. Ask the hiring manager which they would call and why. Edit any requirement that causes a no, then update the recap to match.

## FAQ

### What is a hiring manager intake meeting?

It is the kickoff where a recruiter and a hiring manager agree on what a role needs before sourcing starts. Greenhouse calls its version a role kickoff meeting and describes it as the first step in structured hiring. Some teams call it an intake meeting. The name matters less than the written outputs.

### How long should the meeting last?

Greenhouse describes the role kickoff as about an hour. Shorter meetings often leave the objectives vague. If time runs out before you agree on the must-haves, book a follow-up before anyone posts the role or contacts candidates.

### What should we agree on in the meeting?

Agree on the business objectives, the skills, traits and qualifications a successful candidate needs, and the split of work between recruiter and hiring manager. Write each one down before you leave the room.

### What if the hiring manager will not attend?

Send the one-page brief and ask for a marked-up copy by a set time. A short call still beats a long email chain. If the must-haves stay unclear, take the question to whoever owns the headcount, since they decide the trade-offs.

### Does this change for regulated jobs like nursing or law?

Handle it with more care. Licences and credentials are often set by law or the employer, so list them as hard limits. Follow your employer's rules on client or patient data, especially if the brief or candidate notes include it.

### Can Lazur run the intake meeting for me?

No. Lazur listens only while you hold the shortcut, so it does not sit in on the meeting. It can explain fields, point at them, dictate your notes and draft the recap. You still make the decisions.

### Is there a free trial?

The pricing page lists the current trial and plans, and the trial does not need a credit card. Check [pricing](https://www.lazur.app/pricing) for the latest terms before you buy.

## Sources

1. [SHRM Releases 2025 Benchmarking Reports: How Does Your Organization Compare?](https://www.shrm.org/about/press-room/shrm-releases-2025-benchmarking-reports--how-does-your-organizat), SHRM, checked 2026-11-09
2. [Structured hiring: Role kick-off meeting](https://support.greenhouse.io/hc/en-us/articles/360007247092-Structured-hiring-Role-kick-off-meeting), Greenhouse Software Support, checked 2026-11-09
3. [Job kickoff form overview](https://support.greenhouse.io/hc/en-us/articles/4416516351003-Job-kickoff-form-overview), Greenhouse Software Support, checked 2026-11-09