What a Vio scorecard tells you that a CV does not.

Hiring managers read CVs every week, and most know their limits. Two engineers with the same certifications and the same years can be very different on site. One finishes the cutover and hands over a clean pack. The other needs the method rewritten twice and leaves no backups.

The interview is meant to find that difference. It often finds a confident speaker instead. This article explains what a Vio scorecard records, how it differs from a CV and how to use one on a shortlist.

What a CV is good for, and where it stops.

A CV is a fair summary of where someone has been. It lists employers, projects, platforms and certifications. It is a good place to start a conversation.

It has three limits. It is written by the person it describes. It treats every claim the same way, whether checked or not. And it says almost nothing about how the work was done.

Research on hiring supports a more structured approach. A 2022 review in the Journal of Applied Psychology re-examined decades of studies on what predicts job performance. Structured interviews came out on top, with job knowledge tests and work samples also in the top five (SIOP summary, 2022). What those methods share is structure: the same questions, scored against the same standard, for everyone.

A scorecard applies that idea before the interview starts.

Six dimensions.

Every engineer in the Riviot network is scored on Technical depth, Execution, Judgment, Communication, Reliability and Range. A CV covers the first at best. The other five are what decide whether a deployment goes to plan, and they are the ones clients tell us they wish they had known about before day one.

In short, here is what each dimension covers:

• Technical depth. What they know: protocols, hardware, standards and the reasons behind them.
• Execution. What they have delivered: deployments completed to plan, on live estates, to a documented standard.
• Judgment. What they do when the drawing is wrong: stop, escalate, adapt or push on.
• Communication. How they keep a program informed: handover packs, daily updates, plain English.
• Reliability. Whether they are where they said they would be: attendance, access windows, shift discipline.
• Range. How far they can stretch: adjacent skills, unfamiliar vendors, new site rules.

The radar on the card shows all six at once. Its shape tells you more than any single score.

Declared versus checked.

On a CV every certification looks the same. On a scorecard a certification is marked as declared until a Riviot reviewer has checked it, and then it is marked as reviewer-approved. The difference is visible on the card. You know what has been looked at and what has not.

This matters most when a certification is a hard requirement. Some client standards require a named certification for anyone touching the estate. If the card shows it as declared, ask for the document before the start date. If it shows it as reviewer-approved, that step is done.

The same rule applies to experience. A deployment the engineer describes but has not yet evidenced stays declared. It still counts as information. It is weighed differently.

Evidence of execution.

The Execution dimension is built from deployments the engineer has actually completed, described in a structured way and reviewed for consistency. An engineer who has done three enterprise cutovers describes them differently from one who has watched three. Reviewers are trained to tell the difference and the score reflects it.

In practice, a structured description covers the same points for every deployment. The scope and scale. The engineer’s own role. What went wrong and what they did about it. What they handed over at the end. Gaps and contradictions stand out when every account follows the same shape.

How to read a shortlist of scorecards.

A shortlist of three or four cards reads quickly once you know what to look for. Work through it in this order.

1. Start with the must-haves. Check each required certification. Note which are reviewer-approved and which are declared.
2. Match the shape to the job. A live cutover needs Judgment and Communication. A greenfield build at pace needs Execution and Reliability. Look for the shape that fits.
3. Read the lowest score. Every card has one. Ask whether this project would expose it.
4. Read the evidence behind the top score. It should describe work like yours.
5. Plan the interview from the gaps. Use the card to decide what you still need to find out.

Two cards with the same average can describe very different engineers. The shape is where the useful information is.

What it does not do.

A scorecard does not replace the conversation. It tells you which conversation to have. When the card shows strong Technical depth and a lower score on Communication, the interview can be about how the engineer reports and hands over, rather than a repeat of the CV. That is a better use of everyone’s hour.

It does not predict fit with your team, your manager or your site culture either. Those still need people talking to people. What it removes is the hour spent confirming facts that could have been checked in advance.

A scorecard does not replace the conversation. It tells you which conversation to have.

Using it in the interview.

The research above favors structured interviews. A scorecard makes them easier to run. Pick the two dimensions that matter most for the role. Write two questions for each, based on a real situation from your project. Ask every engineer on the shortlist the same questions, and note the answers against the same standard.

For Judgment, describe a drawing that does not match the room and ask what they would do. For Communication, ask them to talk you through the handover pack from their last deployment. For Reliability, ask how they handled a shift that clashed with something at home.

You will finish with answers you can compare side by side. That comparison, more than any single impression, is what leads to a good hire.