If you screen CVs for a living – or want to review your own CV—or while juggling ten other things—this template turns messy resumes and vague job descriptions into an objective, evidence-based decision. It’s designed for a quick ChatGPT run, and it works for both tech and non-tech roles.

Two input modes: JD + CV or JD-only (framework setup, no scoring yet).

---

Why another template?

Most rejections stem from three fixable problems: unclear role inputs, inconsistent parsing of CVs, and subjective evaluation. This template solves all three with:

• Role Inputs you can fill (or auto-parse from JD)
• Parsing rules that enforce consistency
• A scoring rubric that aligns with function (Tech, Sales/CS, Finance, etc.)

---

How the workflow works

1) Pick your input mode

• A) JD + CV: Use Role Inputs if the hiring manager already provided them; otherwise auto-parse from the JD. Then evaluate the candidate’s CV.
• B) JD-Only: Auto-parse Role Inputs and generate the evaluation framework (no candidate scoring yet). Share it with hiring for alignment.

2) Fill Role Inputs (or auto-parse from JD)

• ROLE_TITLE
• FUNCTION: Tech / Sales / Marketing / Operations / Finance / HR / CS / Admin / PMO
• MIN_TOTAL_YOE: e.g., 3
• KEY TECH/TOOLS (must-have): e.g., React, Node, AWS / Salesforce, Excel (Advanced), SAP
• MUST-HAVE CREDENTIALS/LICENCES: e.g., PMP, SHRM-CP, CA/CPA, RN, Security Clearance
• CLIENT_COMMUNICATION_REQUIRED: Yes/No
• TIMEZONE_OVERLAP: e.g., 3+ hrs with US/EU
• LOCATION (country/state/city if present)
• DOMAIN PRIORITY (optional): e.g., BFSI, Healthcare, IoT
• PORTFOLIO/SAMPLES REQUIRED: Yes/No

Tip: Make any “must-have” explicit. It becomes a hard gate in scoring and rejection flags.

3) Capture the Cultural Operating Context (COC)

Inputs: Country, state/province, city (optional), work arrangement, client geo(s), role language(s), regulated compliance.

Build a COC Matrix to interpret delivery constraints only:

• Workweek/holidays
• Time-zone overlap
• Language for work
• Communication norms (evidence of async/docs)
• Title/tenure norms
• Compliance/licensure
• Notice/shift realities

Use norms only to interpret evidence (e.g., a December–January gap may be Amber in some markets). No stereotyping.

4) Parse the CV (rules that keep you honest)

• Reverse-chronological career table. Treat “Present/Current” as the current month/year.
• If only a year is present → month = “Not specified”.
• Merge consecutive roles at the same employer; show promotions as sub-rows.
• Explicitly mark overlapping roles; do not double-count tenure.
• Distinguish employment type: Perm / Contract / Intern / Freelance.
• Quote short evidence snippets for all judgments.

Spreadsheet helper:

• Tenure (months): =IF(EndDate="Present",DATEDIF(StartDate,TODAY(),"M"),DATEDIF(StartDate,EndDate,"M"))
• YOE dedup: When overlaps exist, compute contiguous ranges per employer first; sum distinct months.

5) Run the evaluation (tasks you’ll output)

1. Career Timeline (table)
2. Gaps & Black Marks (with rationale)
3. Fit vs Role (evidence-based matrix + YOE computations)
4. Common Rejection Reasons (flag only if supported by evidence)
5. Communication Quality Scan (2–4 bullets, severity)
6. Scoring & Verdict (weighted rubric, function tweaks allowed, confidence score, final verdict)

---

What “good” looks like (quick examples)

• Evidence snippet:
  “Built 8-service Node/AWS stack; reduced p95 latency by 42%.” → Outcomes & Tools = strong
• COC interpretation:
  A 2-month break spanning Eid/Diwali with relocation evidence may be Amber, not Red.
• Portfolio gate:
  If JD requires a portfolio for UI/UX and none is linked, flag under Eligibility & Compliance and Experience Alignment.

---

Copy-Ready Template (Markdown)

Paste this into your GPT, or ChatGPT prompt. Fill Role Inputs or let the JD auto-parse them.

Master CV Pre-Screen — Evidence-Based Review

Role Inputs

• ROLE_TITLE:
• FUNCTION: Tech / Sales / Marketing / Operations / Finance / HR / CS / Admin / PMO
• MIN_TOTAL_YOE:
• KEY TECH/TOOLS (must-have):
• MUST-HAVE CREDENTIALS/LICENCES:
• CLIENT_COMMUNICATION_REQUIRED: Yes/No
• TIMEZONE_OVERLAP:
• LOCATION:
• DOMAIN PRIORITY (optional):
• PORTFOLIO/SAMPLES REQUIRED: Yes/No

COC Snapshot (for delivery constraints only)

• Market workweek/holidays:
• Time-zone overlap expectation:
• Language for work:
• Communication norms (async/docs evidence):
• Title/tenure norms:
• Compliance/licensure nuances:
• Notice/shift realities:

Use norms only to interpret evidence (e.g., holiday gaps). No stereotyping.

---

A. Executive Summary (≤120 words)

[Overall fit, key risks, recommendation.]

B. COC Snapshot & Interpretation Adjustments

• [Bullets noting any threshold tweaks, e.g., short-stint threshold set to ≥9 months due to contractor-heavy market.]

C. Career Timeline (latest → earliest)

Employer	Location (City/Country)	Role/Title	Start–End (MM/YYYY)	Tenure (months)	Employment Type	Scope (team/budget/portfolio)	Key Tech/Tools	Project/Domain Keywords

D. Gaps & Black Marks

Issue	Why it matters	Severity (Red/Amber)	Evidence (quote)

E. Fit vs Role (Evidence-Based)

Category	Evidence from CV (short quote/line)	Fit (Good/Moderate/Poor)	Notes
Core Tech/Tools (per JD)
Outcomes & KPIs (quantified impact)
Stakeholder/Client Handling
Domain/Industry Relevance
Agile/Process/Method (Agile, SOPs, CI/CD)
Leadership/People Mgmt (if applicable)
COC: Time-zone/Shift/Language Fit
Compliance/Licensure (if required)

Also compute:

• Total YOE (deduped overlaps):
• YOE in Must-Have Tech/Tools (evidence-based):
• Timezone/Shift Fit (Yes/No + evidence):

F. Rejection Flags (if any) — Quote evidence for each

Eligibility & Compliance

• [e.g., Missing PMP where JD requires it — “Certifications: —”]

Experience Alignment

• [e.g., No AWS where JD lists AWS as must-have — “Stack: Node, MongoDB, Docker”]

Stability & Integrity

• [e.g., Three roles < 9 months with no context — “Jan–Aug 2023”, “Sep–Dec 2022”, “Jan–Apr 2022”]

Delivery Logistics

• [e.g., No evidence of EU overlap where JD requires 4h — “Availability: India business hours only”]

Communication Quality

• [e.g., Severe grammar issues in client-facing summary — quote 6–10 words]

G. Communication Quality Scan

• [Bullet 1 — spelling/grammar, severity]
• [Bullet 2 — clarity/redundancy, severity]
• [Optional — clichés/buzzwords, severity]

H. Scoring & Verdict

Default Rubric (0–100)

• Outcomes & KPIs — 25
• Core Tech/Tools or Functional Tools — 25
• Stakeholder/Client Handling — 15
• Process/Method (Agile/CI/CD/SOPs) — 10
• Domain Relevance — 10
• Stability/Tenure — 10
• Communication Quality — 5

Function Tweaks (optional)

• Sales/CS: Outcomes 35, Stakeholder 20, Tools 15, Domain 10, Stability 10, Comm 10
• Finance: Compliance/Licensure 20 (from Domain), Outcomes 25, Tools 20, Stability 15, Stakeholder 10, Comm 10
• Tech: Tools/Stack 30, Outcomes 20, Process/CI/CD 15, Stakeholder 15, Domain 10, Stability 10

Score Breakdown

• [Category → points]
• Overall Score: X/100
• Confidence: X/100
• Final Verdict: Proceed to Interview / Hold for Clarification / Reject

One-sentence justification tied to rubric.

I. Follow-Up Questions (5–7)

1. [License/cert validity or ID if required]
2. [Portfolio/code samples or case studies if required by JD]
3. [Clarify overlapping dates; confirm actual notice period]
4. [Quantify outcomes/KPIs; provide baseline and tools used]
5. [Confirm time-zone/shift and language comfort for client geo]
6. [Explain < 12-month stints or gaps ≥ 3 months]
7. [Detail team size, scope, budgets, or leadership span]

---

Implementation tips for ATS & spreadsheets

• JD parser macro: extract ROLE_TITLE, FUNCTION, must-haves (Regex on “Requirements”, “Must have”, “Qualifications”).
• YOE by stack: count distinct months where the tool/tech appears in the role’s bullet lines.
• Hard gates: If any must-have is missing → show red badge in the dashboard and cap the max score (e.g., +0 on Tools).
• Confidence score: Start at 100 and subtract for each unknown (e.g., −10 portfolio missing where required, −5 ambiguous dates).

---

Common pitfalls (and fix)

• Responsibilities only (no outcomes): Prompt for 2–3 quantified impacts (latency, revenue, CSAT, error rate).
• Unverifiable freelancing: Ask for client names (masked if needed), scope, deliverables, and dates.
• Portfolio-heavy roles: Treat missing portfolio as a gating item, not an afterthought.
• Overlaps: Always dedup when computing YOE.