How do agencies validate technical talent before client submission? 6 steps that protect your fee

How do agencies validate technical talent before client submission? The ones clients keep coming back to treat every shortlist as their own reputation on the line: they test the skill, check the evidence and say exactly what was checked before a single CV leaves the office. Send a welder who cannot pass the client's test piece, or a developer who cannot explain their own project, and you can lose the fee, the next vacancy and the client's trust in one week.
This guide sets out the technical validation steps a recruitment consultant can run before submission, the questions that separate real skill from good wording, and a sample submission note that tells the client what you confirmed and what you did not.
Why technical candidates need more than a CV screen
A technical CV is easy to fill with the right words. Job ads publish the keywords, and candidates copy them, often honestly and sometimes not. A line such as "experienced in PLC programming" or "TIG welding on stainless pipe" tells you what the candidate wants you to believe, not what they can do on a client site next Monday.
The general checks every agency should run, such as identity, employment dates and referees, are covered in 7 things to verify before you submit a candidate. This article goes one layer deeper: proving the technical skill itself.
What a client is really buying
When a client pays an agency fee for a technical hire, they are paying for a filter. They expect the people you send to be able to do the core tasks of the role without being re-tested from scratch. Every weak submission tells them your filter is loose.
Step 1: turn the client brief into testable skills
Technical validation starts before you look at a single CV. Most briefs mix must-have skills, nice-to-have skills and vague wishes. Sit down with the hiring manager and split them.
- List the 3 to 5 tasks the person must do in the first month. "Fault-find on conveyor drives", "weld 6G pipe to code", "maintain a payment API".
- For each task, ask what good looks like. A finished weld that passes inspection, a fault traced in under a shift, a code change that passes review.
- Agree which licences or tickets are required by law or by the site, and which are just preferred.
- Ask how the client tests these skills themselves. If they run a trade test or a technical interview later, your screen should point the same way.
Write the answers down and send them back to the client. That short note becomes your validation plan, and it protects you if the brief changes later.
Step 2: a technical screening call run by the right person
A general recruiter can confirm motivation, availability and salary expectations. Testing technical depth needs either a consultant who knows the field or a short call with a technical assessor the agency trusts.
Questions that test real experience
- "Walk me through the last fault you found. What did you check first, and why?"
- "Which machine, software version or material did you use most on that job?"
- "What went wrong on that project, and what did you change?"
- "What would you check before signing off this job as finished?"
People who did the work tend to answer with specific steps, names of equipment and a few mistakes. People repeating a CV tend to stay general. Treat a vague answer as a reason to dig further, not as proof of anything. Nerves, language and interview style all affect how people answer.
Step 3: see the work, not just the words
The strongest evidence of technical skill is the work itself. Depending on the role, that can be a short practical test, a work sample, a portfolio review or a recorded demonstration.
| Type of role | Useful evidence before submission | What to watch for |
|---|---|---|
| Welders, fabricators, boilermakers | Test piece at a workshop, photos and videos of past welds, ticket numbers | Photos that cannot be linked to the candidate |
| Electricians and technicians | Fault-finding scenario on a call, licence check, examples of past jobs | Licence class that does not match the work |
| Mechanics and diesel fitters | Diagnostic walkthrough, brands and engine types worked on, workshop referee | Brand lists copied from the job ad |
| Software and IT roles | Short take-home task or live review of a past project, code they can explain | Projects they cannot explain line by line |
Keep any test short, paid where it is more than a brief exercise, and related to the real job. For trades, the post on running a practical trade test without losing good candidates covers how to set one up fairly.
Overseas candidates you cannot meet
When the candidate is in another country, recorded evidence matters more. Ask for short videos of the candidate doing the work, with their face and the task in the same clip where it is safe to film. Then use the call to ask about what the video shows.
Step 4: technical reference checks, not character references
A referee who says "great worker, very reliable" tells you little about skill. Ask the referee technical questions that match the client's must-have tasks.
- "Which jobs did they do without supervision by the end?"
- "What equipment or systems did they use every week?"
- "Would you put them on a job like this one on their own?"
A list of questions built for trades is in reference check questions that actually test the work. Always confirm that the referee was in a position to see the work: a supervisor or lead hand, not a friend from another team.
Step 5: check the tickets and qualifications that the role depends on
For many technical roles, a licence or certificate is not a bonus but a legal or site requirement. Check each required one with the issuing body or its official register where one exists, and record the number, class and expiry date. Do not rely on a photo of a card alone.
If a qualification was earned overseas, note that it was confirmed as issued, and be careful not to tell the client that it is recognised in their country unless the relevant authority has said so.
Step 6: write a submission note that shows your work
A short validation note with each CV makes your shortlist easier to trust. It also makes clear what you did not check, which protects you later.
Example submission note (fictional candidate): Sam Perera, maintenance electrician. Technical screen 40 minutes with the agency's assessor: strong on VSD fault-finding and conveyor controls, less experience with the client's PLC brand. Licence number and class checked on the issuing register, valid to March 2028. Two referees spoken to, both former supervisors; both confirmed unsupervised fault-finding. Work photos reviewed; video of a panel fault-find seen. Not checked: right to work (client to confirm), the client's site induction.
Notice that the note names gaps honestly. A client who sees "less experience with this brand" trusts the rest of the note more, and is not surprised at interview.
Where verified profiles fit in your process
Some of this evidence can come from the candidate before you start. A candidate's Talent Tabloid profile brings their work history, qualifications, verification badges, a video intro and work evidence together in one link. Candidates can attach work videos, photos and portfolio links, and videos can be linked to a specific skill, which is useful for trades. Evidence is optional for each skill, so treat a profile as a head start on your checks, not a replacement for your technical screen. Agencies can read how this works on the page for recruitment agencies, then create an employer account.
Frequently asked questions
How long should technical validation take before client submission?
It depends on the role and how much evidence the candidate already has. A screening call, a reference check and a ticket check can often be done within a few working days, while a practical test needs more planning.
Should an agency run its own technical test?
Only when the agency has a qualified assessor and the test reflects the client's real work. Otherwise, a structured technical call plus evidence and referees is safer, and the client's own test comes later.
What if a candidate refuses a practical test?
Ask why first. Some candidates have done many unpaid tests before; a short, fair task or a portfolio review may be acceptable to them instead.
Should the submission note mention what was not checked?
Yes. Stating what was not checked sets clear expectations with the client and avoids disputes if a gap appears after the hire.


