# Employer Brand and EVP: Comparing the Promise with Onboarding Experience

Compare what was presented during recruitment with feedback after joining using a review grid and follow-up actions, without drawing conclusions about future retention.

- Canonical URL: https://www.harmate.com/en/blog/employer-brand-and-evp-why-your-employee-promise-can-lower-recruitment-costs
- Author: Harmate Team
- Published: 2026-05-04
- Updated: 2026-10-12T03:00:52.171677+00:00
- Language: en

## Content

# Employer Brand and EVP: Comparing the Promise with Onboarding Experience

An employer promise matters when someone experiences the work day to day. The first days and weeks can confirm some things described during recruitment, qualify others, or reveal gaps. To understand them, the team needs to listen to recent hires and review their answers in context.

The aim is not to score a new employee or predict whether they will stay. It is to compare what was presented with what was experienced, separate a fact from an impression, and decide which improvements belong to the organization.

## From the EVP to the onboarding experience

An employee value proposition (EVP) brings together what an organization says and what people can reasonably expect from the work: responsibilities, autonomy, support, learning, schedules, team practices, or working conditions. These elements need to be concrete enough to discuss after someone joins.

A statement such as “we trust everyone” is hard to compare with experience. Reframe it as an observable situation: “Managers give the person room to choose the order of tasks within agreed priorities.” The team can then ask whether that room was understood, available, and supported.

Onboarding is an opportunity to explain responsibilities, objectives, ways of working, and key contacts. The [CIPD guide to employee induction](https://www.cipd.org/en/knowledge/guides/employee-induction/) highlights the value of clarifying the role, responsibilities, and expectations. It is a practice reference, not a guarantee of results for any particular organization.

## Ask questions after someone joins

Choose a moment when the person has enough experience of the role to answer, without assuming they have encountered every situation. A short set of open questions can help identify topics to review:

- What has most closely matched what you were told before joining?
- What has worked differently in practice? Can you describe a specific situation?
- Have you been able to understand priorities, responsibilities, and whom to ask for help?
- What do you still need to do your work in good conditions?
- Is there anything from the job posting or interview that you would like clarified?

Answers are accounts of a particular experience at a particular time. One person’s response does not by itself prove an organization-wide practice, and not mentioning an issue does not mean everything is working well. Preserve the person’s wording, review excerpts with the question that prompted them, and avoid conclusions about their motives or personality.

## Compare the promise, experience, and evidence

For each important part of the EVP, record separately what was presented, what the person reports, and what the team can verify. The examples below are fictional.

| Promise or expectation | Experience reported | Example or context provided | Gap to examine | Question or action |
|---|---|---|---|---|
| “You will have regular check-ins with your manager” | The person says the first two check-ins were postponed | They describe two weeks when no check-in took place | The expected rhythm and available support are unclear | Ask the person and manager what happened; agree on a next check-in |
| “You can suggest improvements” | The person says they do not know where to share ideas | No channel or time has been explained yet | The option may exist, but how to use it is unclear | Explain the intended channel and ask whether it is accessible in day-to-day work |

Do not automatically label answers “positive” or “negative.” One situation may have several explanations: information was missed, a busy period intervened, team practice differs from the stated process, or the promise was too broad. Record what is known, what remains uncertain, and who can check it.

## A review template to reuse

Copy this template for each promise you want to examine. Keep recruitment information and post-hire feedback in their respective contexts. An answer given as an applicant and an answer given as an employee may address different questions.

| Promise or expectation presented | Question asked after joining | Reviewed answer / source excerpt | What it supports | What remains unknown | Check or action |
|---|---|---|---|---|---|
| [concrete item] | [open question] | [wording and context] | [limited observation] | [limitation or other explanation] | [owner and agreed next step] |

For each row, ask:

1. Was the promise specific enough for the recruiter, manager, and new hire to understand it in the same way?
2. Was the reported experience directly observed, or is it an interpretation?
3. Does the gap concern one situation, an unclear expectation, or a repeated practice?
4. What other source could help check the point without dismissing the person’s account?
5. What concrete action can be taken, by whom, and when can the person say whether it helped?

An action may be straightforward: explain an unclear responsibility, arrange an expected conversation, make a resource accessible, or correct an overly broad promise in future recruitment conversations. Do not promise a change that has not been decided or cannot be delivered.

## Interpret carefully and protect the relationship

Explain why you are asking for feedback and how it will be used. Limit collection to questions that help with onboarding, and share answers only with people who need them to act. When an issue concerns an individual difficulty, use an appropriate conversation rather than drawing a conclusion from a table or summary.

If several people mention the same gap, that is a reason to check the relevant practice; it does not establish how common it is across the organization. If one person raises a problem, their experience still deserves a response. Do not calculate an overall promise-alignment score to rank employees or predict departures.

In Harmate, reviewers can read written answers alongside source excerpts in [Open Questions](/en/product/open-questions). [Response Import](/en/product/response-import) supports structured CSV, JSON, and XLSX files. These workflows help people read the available answers; they do not assess onboarding quality, determine whether a promise has been fulfilled, or predict retention, and they do not replace human review of context.

## Turn a reported gap into an improvement

At the end of the review, separate three outcomes:

- **Supported by the reported experience:** the person describes an example that corresponds to something promised;
- **Needs clarification:** the wording, expectations, or circumstances are not yet specific enough;
- **Needs correction:** the team identifies a concrete difference between the promise made and what it can currently offer.

These are working statuses for reviewing the promise, not evaluations of the person. Share useful findings with those responsible for onboarding and, where appropriate, with the new hire. Set a realistic next step, then follow up to learn whether it addressed the need.

A credible EVP is not demonstrated by a polished statement or a questionnaire alone. It is examined through experiences that people describe, reviewers read, and the team puts in context. This helps an organization understand what it says, what people experience, and what it can improve, without claiming to predict their success or loyalty.

To examine gaps during recruitment conversations, continue with the [employer branding guide](/en/blog/employer-branding-why-great-messaging-no-longer-matches-the-reality-on-the-ground). For feedback gathered later in the employee journey, see the [employee retention guide](/en/blog/employee-retention-the-weak-signals-companies-notice-too-late), without using these accounts to infer an individual risk of leaving.