Track Which CV Got Replies With Erioun

If you have ever wondered which resume gets more responses, the honest answer is that you can't tell until you can see which CV version was attached to each reply you got. Erioun keeps that link for you. Every application records the exact CV you sent, and every reply stays tied to it, so the pattern becomes visible instead of a guess.

Most people are running blind here. You send out a handful of CVs, a few replies trickle in over the next two weeks, and by then you genuinely can't remember whether the recruiter who responded got your general version or the one you rewrote at midnight. So you keep sending all of them and hope. That's a lot of effort with no feedback loop.

Why you can't tell which resume gets more responses

The problem isn't your CV. It's that nothing connects the file you sent to the outcome you got. Three things usually break the link:

• Time. Replies often arrive days or weeks after you applied. By then the memory of which file went out has faded.
• Volume. Once you're past ten or fifteen applications, the versions blur together. CV_v2, CV_v2_tailored, CV_marketing_short all start to look the same.
• Scatter. The reply lands in your personal inbox. The CV sits in a Downloads folder. The job lives on a board somewhere. Nothing holds them together.

When those three things pile up, you lose the one comparison that actually matters: did the version you put real effort into perform better than the one you fired off quickly? Without that, every "improvement" to your CV is a hunch. You might be polishing the version that never gets read and ignoring the one that quietly does the work.

How Erioun links replies back to the exact CV version

In Erioun, a CV isn't a loose file. When you log a job in your tracker, the application record carries everything about that pursuit together: the role and company, the stage it's at, your follow-up date, your notes, the replies, and the CV version you used.

That last field is the one that changes everything. Because the version is recorded on the application, and the replies are recorded on the same application, a reply is automatically connected to the file that earned it. You don't have to reconstruct anything later. Open the record, and the answer is right there: this role, this version, this response.

Two pieces make this work in practice:

1. The CV version field on each application. When you create or update an application, you attach the version you sent. If you keep a tidy set of base CVs, this is a quick choice from the ones you already use. If you're new to keeping versions straight, it's worth learning to pick the right CV version for each job first so the labels stay meaningful.
2. Replies that attach to the application. Through the alias-based Email Hub, replies from your job search land against the right application instead of getting lost in your main inbox. The response and the CV that prompted it end up on the same record.

Put those together and you have something most job seekers never get: a clean, automatic record of which CV was in play when someone wrote back.

Reading the pattern across your pipeline

One reply doesn't tell you much. The value shows up when you zoom out and look across many applications.

Say you've sent three CV versions over the past month. A general one, a version that leans hard into a specific skill, and a shorter version for roles that ask for brevity. If you've tagged each application with the version you used, you can scan your pipeline and notice things like:

• The skill-focused version sits behind most of your interviews, while the general one mostly leads to silence.
• The short version gets opened and replied to for one type of role but lands flat for another.
• A version you assumed was your best actually has a worse response rate than the quick one you almost stopped using.

These are patterns, not proof. A reply depends on the role, the timing, how well you matched the posting, and plenty of things outside the document. So read the signal with some humility. A version that's pulling more responses is a strong candidate to build from, not a guaranteed winner you should blindly reuse. The point is to replace "I think this one's better" with "this one has actually been getting replies."

Turn what's working into your next application

Once you can see which version earns responses, the next move is obvious: start from the one that's working and tailor from there, instead of starting from scratch or from a tired default.

Here's a simple loop that keeps the feedback honest:

1. Apply, and record the version. Every time you send something, log the application and attach the CV version. No version, no data later.
2. Let replies attach themselves. Keep your job-search mail flowing through the Email Hub so responses connect to the right record on their own. If your inbox is currently a mess of recruiter threads, it helps to first get your job-search emails organised.
3. Review weekly. Once a week, look across your pipeline and notice which versions sit behind replies and which sit behind silence.
4. Tailor from the winner. When you find a role you want, start from the version that's been responding well, then adjust it for that specific posting.

That fourth step is where a CV Fit Score earns its place. Before you send, it compares your chosen version against the job description and flags the keywords you're missing. It won't promise you a reply, and it doesn't pick the file for you. It just tells you how closely your strongest version lines up with this particular role, so you can close the gaps you'd otherwise miss.

A quick word on what "working" means

It's tempting to treat a single great reply as the verdict. Don't. One enthusiastic recruiter for one dream role tells you about that role, not about your CV in general. Look for repeated patterns across several applications before you decide a version is your strongest. And keep tailoring per job regardless. The version that gets the most responses is a better baseline, not a one-size-fits-all answer.

What this saves you over the long run

The obvious win is time. You stop rewriting CVs on instinct and start improving the version evidence points to. But the quieter win is confidence. A job search has long stretches where nothing seems to happen, and it's easy to assume everything you're doing is wrong. When you can open Erioun and see that one version is genuinely pulling replies, you have something solid to stand on. You know what to send, what to build from, and what to retire.

You also keep a clean history. Months from now, if you're job hunting again, you won't be guessing which file worked last time. The record's still there: the role, the version, the response, all together.

If you want to start seeing which resume gets more responses for your own search, the easiest way in is the 14-day free trial. Log a few applications, attach the CV version to each, and let the replies connect themselves through the Email Hub. After a couple of weeks you'll have something you've probably never had before: a clear, honest picture of what's actually working.