Vacancy, evidence and application matrix

Original educational examples; no real candidate or application is represented. Copy into your preferred editor; this guide does not store your answers.

Worked vacancy matrix

Fictional role: operations assistant.

Your copy

Read a vacancy as a set of decisions

A vacancy mixes activities, working conditions, mandatory requirements and preferences. Separate these layers before editing your resume. In a fictional customer-support role, ‘resolve requests’ describes the work; ‘Saturday availability’ is a condition; ‘English for customer conversations’ asks for a demonstrable capability; ‘industry experience is a plus’ carries a different meaning from an explicit requirement.

Create three columns: what they ask for, what evidence I have, what needs clarification. For ‘monitor indicators’, a spreadsheet you maintained to identify delayed orders says more than ‘analytical mindset’. Record a gap when you do not meet a requirement. Do not automatically treat a preference as disqualifying, or claim a licence or availability you do not have.

Target one family of roles per version. A resume simultaneously selling customer support, engineering and design makes your contribution harder to understand. Keep a broad evidence inventory and select from it for each application. The vacancy guides selection; it does not justify copying duties you have never performed.

Build an evidence inventory

Before searching for impressive words, recover real situations. For each job, project, course or volunteering activity, note the problem, your action, collaborators, tool or method, observed outcome and a source that helps you recall it accurately. That source might be your own file, a public deliverable or a private note; it need not accompany the application.

Illustrative case: someone organized a shop’s orders. Their inventory could say ‘spreadsheet with order, deadline and owner; daily updates; identified unassigned orders; handed them to the team’. Even without reliable numbers, this supports a specific contribution. ‘Increased revenue’ would require different evidence.

Separate individual and team work: ‘created the spreadsheet’ differs from ‘helped implement it’. Keep an explanation of one difficulty and one decision, because an interview may explore them. Remove customer data, confidential information and internal documents from public samples. Access to a work file does not mean you may publish it.

Quick reference: select a coherent application

Start a version with the vacancy description and your evidence inventory. Identify activities, requirements and conditions. In the matrix, connect each important point to truthful evidence and record what you cannot yet demonstrate.

• Target: does the version present a recognizable family of roles?
• Match: does each central capability have an action, project or relevant study example?
• Limits: are preferences distinguished from requirements?
• Selection: does the strongest relevant evidence receive enough space?

For operations support, an order-checking example may matter more than an unrelated old course. Preserve titles, dates and context; tailoring means selecting and explaining. If a skill is genuinely missing, the useful next action may be creating a real learning sample rather than adding the word to the resume. The matrix material includes a completed case and copyable fields.

Quick reference: check the file, fields and submission

Use the requested format. Open the final file, inspect text and test links. In the form, compare imported information with the document and answer vacancy-specific questions.

• Readability: do name, contact details, titles and dates remain in the right sequence?
• Accuracy: is the attachment the version you just reviewed?
• Fields: was information omitted, merged or put in the wrong place?
• Privacy: is unnecessary personal or third-party information included?
• Confirmation: did the service confirm receipt or show an error?

Keep your own copy of the vacancy and submitted version. Without a parsing preview, local checks reduce some problems but cannot establish how the system interpreted everything. Confirmed submission records an application; it does not confirm review, interview or selection. Checkmenot does not apply on your behalf or mark understanding when you open a template.

Quick reference: improve without guessing the algorithm

No response is insufficient evidence that ‘the ATS rejected me’. Compare observations: was there an upload error? Were fields wrong? Did the role require something missing? Did an interview reveal difficulty explaining an experience? Each situation suggests a different investigation.

• File or form: correct the observed defect and check again.
• Role fit: review requirements, target role and selected evidence.
• Explanation: prepare a concrete case behind a vague claim.
• No information: retain uncertainty rather than buying an approval promise to fill the diagnostic gap.

You can keep application notes to observe patterns, but small samples, different vacancies and market changes make it difficult to attribute an outcome to one sentence. Improving clarity and fit is verifiable; guaranteeing selection is outside your control. Use the next version to address an identifiable problem while preserving truthful facts.

References

• Harvard MCS — resume writing
• National Careers Service — CV
• Greenhouse — unsuccessful resume parsing
• Gupy — application data and features

Checked September 26, 2026. Guidance and platform behavior may change.