For careers services

Choosing a Resume Tool for a Career Centre

An evaluation checklist for careers offices buying a CV tool: fabrication, student approval, what the office sees, seat caps, data handling and country coverage.

Most CV tools demonstrate well. They all produce a score, they all say something sensible about a bullet point, and forty minutes with a sales engineer will not tell you which one is safe to put in front of four thousand students. The questions below will.

They are written to be asked of any vendor in this category, including us. If a competitor answers them better for your cohort, buy the competitor.

What the category currently looks like

Two reference points, described from their own material, so you know what the market assumes.

CareerSet sells six tools around document feedback: CV scoring with line-by-line comments, CV targeting against a job description, cover letter feedback, interview practice, a LinkedIn review and a career exploration map. For institutions it provides analytics dashboards covering uploads, active users, score improvement and where students are applying, exportable at institutional and individual level.

VMock is described by the careers services that license it as an instant resume scoring platform: Georgia State University's careers service describes a score benchmarked against the student's own peer group, feedback grouped into impact, presentation and competencies, a SMART Editor giving bullet-level sample suggestions, and a LinkedIn optimiser called Aspire, with upload allowances capped per year or per term.

Both do the thing they describe. Neither is a job board, and the difference matters for what your service ends up doing at four in the afternoon in October.

The questions

1. What happens when the model cannot support a claim?

This is the fabrication question, and the answer separates the field faster than any other. Ask the vendor to describe the system's behaviour, not its intention. Does it decline? Does it insert a placeholder? Does it write the plausible sentence anyway and leave the student to notice?

Good answers are specific. Involve Resume's answer is that a fabrication guard rejects any token with no source in the student's original resume and throws rather than shipping the document. Whatever the vendor's mechanism is, ask to see it fail on purpose during the demo: hand it a thin CV and a senior job description and watch what appears. A student who defends an invented achievement at an assessment centre has been damaged by your procurement decision, which is why this failure mode deserves testing rather than assurances.

2. Does the student approve every change, and does the original survive?

Two separate questions. First, is there an explicit approval step before a document is final, and does the student see what changed and why, or only the finished text? A before-and-after diff with a reason attached to each edit is the difference between a student learning something and a student receiving a file.

Second, is the base document overwritten? A student who tailors eleven times over a term should still have the CV they actually wrote, unaltered. Ask where that original lives and how they get it back.

3. What does the office see, and what did the student agree to?

Dashboards vary from aggregate readiness reporting to per-student document access with export. Neither is wrong, but they carry different obligations. Ask for a written description of every field the office can see, whether individual documents are included, whether the export contains personal data, and what the student is told at sign-in.

Then ask the harder version: what will your service actually do with it. Cohort readiness before a careers fair is a real use. A dashboard nobody opens is a data protection liability with a login page.

4. Seat caps, identity and what happens at renewal

Ask how a seat is claimed. Domain-verified sign-in scales without you maintaining a list; uploaded lists go stale within a term. Ask what the cap is, what happens when you hit it mid-year, and whether seats can be recovered from graduating students.

Then ask about the exit. If you do not renew, what happens to student documents and to the office's own data, on what timetable, and can students take their material with them. Get the answer in the contract rather than in an email.

5. Data handling, in specifics

Four questions that produce useful answers:

1. Where does processing happen, and does the CV leave the student's device at all? Involve Resume runs parsing, scoring, tailoring, the fabrication guard and both file writers in the student's own browser, which shortens this conversation considerably.
2. Is student data used to train models, by the vendor or by any sub-processor? Get this in writing, with the sub-processor list attached.
3. What is the retention period for documents and for logs, and who inside the vendor can read them?
4. What does sign-in require? OAuth through providers the institution already trusts avoids a new password estate.

6. Does it cover the countries our students apply into?

For a European business school this is not a detail. A cohort applying into the UK, Germany, the Netherlands, France, Switzerland and the Gulf is producing six conventions, not one document with the dates reformatted. Photo rules alone diverge sharply, and a tool that applies a single template quietly damages half the applications it touches.

Ask which country formats are supported by name, and test one your students actually use. Our own coverage runs to thirteen, and the country differences in CV length show why the question is worth asking rather than assuming.

7. What does the student do after the score is good?

The honest limitation of a scoring product is that a well-scored CV is not an application. Ask whether the tool supplies live roles, how often the board is refreshed, what happens to expired postings, and whether the source of each listing is visible.

Then ask the automation question directly, because it is where vendors differ most and disclose least. Does the tool submit applications on the student's behalf? Is the apply route labelled before the student clicks? What is the policy on platforms whose terms prohibit automation? Involve Resume labels every listing as auto, extension, manual or blocked, blocks LinkedIn automation unconditionally, and excludes Workday because it requires employer-issued credentials, flagging those roles for the student to complete personally.

8. Whose consent does an institutional licence carry?

Ask whether anything in the institutional version acts on a student's behalf without the student present. Our position is that automatic application is excluded from the campus licence entirely, because a school cannot consent to an application a student will later be asked to defend. Whatever a vendor's answer is, make sure it is a considered one rather than a feature that was never examined.

9. What evidence of value will exist at renewal?

Decide this before you buy, not in month eleven. Engagement counts are easy to produce and prove little. Better measures tend to be advisers reporting that appointments start further along, a shift in the mix of questions students bring, or readiness improving across a cohort between two fixed points in the year.

Be careful with score improvement as a headline. A tool that scores its own output will show improvement by construction.

A short scoring sheet

None of this requires a long procurement. It requires one demo where you drive, using a real student CV with permission and a real job posting from the market your students apply into, and a vendor willing to answer in writing. If you want ours in writing, the product is free to browse and our comparison with CareerSet sets out where we are and are not the right fit.