Skip to main content
Application Review turns your job description into a clear Ideal Candidate Profile, then classifies every applicant against it. The result is a prioritized overview with transparent reasoning — helping you focus your review on the most relevant candidates and make more informed hiring decisions.
A seven-minute walkthrough of the whole flow, from importing a role to reviewing a full pipeline.

When to Use Application Review

Application Review is built for roles where inbound volume is the bottleneck — a job goes live and hundreds of applications arrive before anyone has time to open the first one. Rather than working through them in whatever order your ATS presents, or spot-checking and hoping, every application gets read against the same standard, with reasoning you can check. That tends to matter most in three situations:
  • A newly opened high-volume role, where you want to be through the first pass before your hiring manager asks.
  • A backlog you have not been able to face, where candidates have been waiting and each one still deserves a proper look.
  • A shifting brief, where priorities change once the first interviews happen and the whole pipeline needs re-reading against the new bar.
The point is not to hand over the decision. It is to spend less time deciding who to read, and more time speaking to candidates.

How AI Application Review Works

To start a review, open Metaview and click Application Review in the sidebar. From here you can start a review in one of two ways:
  • From a role in your connected ATS — pull candidates directly from a selected pipeline stage, with progress and rejection decisions synced back to the ATS.
  • By uploading CVs — add role context, refine an Ideal Candidate Profile, and upload PDF or Word CVs. No ATS connection is required for this route; decisions for uploaded CVs stay in Metaview. You can add more CVs later through Add applicants.
The rest of the review flow is the same for both routes:
  1. Select a starting point. For an ATS-connected review, pick a role and the pipeline stage to pull candidates from. This defaults to the Application Review stage, but you can select any stage. As part of setup, you can also optionally configure how rejections are handled:
    • Default rejection reason: Select a reason that will automatically be applied in your ATS when candidates are rejected. This helps keep your data consistent and saves time during review.
    • Rejection email: Choose which email template to send to candidates when rejecting them. These email templates will come straight from your ATS. This allows you to tailor communication based on stage or role. If no email is selected, no automatic rejection email will be sent.
    For an upload-based review, give the review a name and the role context you want to evaluate against (default rejection reason and rejection email don’t apply here, since decisions stay in Metaview).
  2. Add context For ATS-connected reviews, Metaview automatically pulls what it can from your ATS — the job post itself, plus any scorecard or application questions attached to the role — so you start with context already in place. For upload-based reviews, you provide the role context directly. In both cases you can add anything else that defines the role: a fuller job description, a competency framework, or your hiring manager’s intake notes. This step is optional, but the more context you add here, the better the Candidate Profile, and the better every classification that follows.
  3. Refine the Candidate Profile Using all the role context now in place, Metaview will generate a draft Ideal Candidate Profile (ICP) that summarizes the key requirements: experience, skills, education, red flags, and positive signals. Edit as needed and once it looks right, click Start Reviewing .
    Application Review Icp

    You can write the ICP in plain language. If you want to weight certain criteria more heavily, just say so (for example, "Python experience is a hard requirement and should be weighted above all other criteria"). The AI reads the ICP the same way a human would.

  4. Review candidates Once you accept the Candidate Profile, Metaview classifies each candidate individually against the ICP — pulling them from the selected ATS stage, or using the CVs you uploaded. Each candidate gets written reasoning covering their strengths, gaps, and an overall match category:
    • Strong match: Closely aligns with the ICP across key criteria
    • Good match: Aligns with most requirements, with some gaps
    • Partial match: Some alignment, but notable gaps remain
    • Low match: Limited alignment with the ICP
    • Inconclusive: No CV was uploaded, the file was corrupted, or the resume could not be parsed These ratings are intended to support — not replace — your review. The written reasoning behind each rating is provided so you can apply your own judgment and context when assessing candidates.
  5. Provide feedback to refine results As you review, mark candidates as Yes / Maybe / No and add feedback. After a few ratings, you can choose to refine your search — Metaview uses your input to adjust how candidates are evaluated, so the results better reflect what matters to you. You can also edit your Candidate Profile or create a new one at any point. When you do, Metaview re-evaluates candidates against the updated profile.
  6. React to potential candidates Once you have identified the right people, you can take action directly from Metaview. For ATS-connected reviews:
    • Progress candidates: move them forward to the next stage in your ATS
    • Reject candidates: reject them in your ATS, with a rejection email sent using the template you configured during setup
    For upload-based reviews, progress and rejection decisions stay in Metaview — connect an ATS later if you need those changes written back to a system of record. You always make the final call. Metaview never auto-rejects anyone.
To add sources to an existing review, open its Ideal candidate profile and select Context, then click Add context. Choose Text for written context or Screens for completed screening interviews.

Start from an intake call

You can also start a review directly from a recorded role intake call. Open the intake call and select Review applicants in the Actions panel. Before you begin: Application Review must be enabled for your workspace, and you need permission to create reviews. If a review has already been created from the call, anyone with access to it can still open it from here. What happens next depends on whether a review already exists for the call:
  • If a review is already linked to the call, Metaview opens it with its existing ICP and draft preserved — nothing is re-evaluated.
  • If no review exists yet, Metaview prepares a new one: it matches the call to an open role in your ATS, selects the review stage, and drafts the Ideal Candidate Profile from the intake transcript and job description.
If the role or stage can’t be matched confidently, Metaview opens the standard setup flow with the intake retained as context — including when you change the suggested role, so your choice drives the review while the intake stays attached. Preparing a draft this way doesn’t start the evaluation. Review and refine the ICP as described in step 3 above, then click Start Reviewing to begin evaluating candidates against it.

What You See in the Review

Each candidate appears as a row in the review, so you can read the shape of the whole pipeline before opening anyone.

Candidate insights at a glance

Alongside the match category, Metaview surfaces the details you would otherwise dig out of each CV yourself:
  • Current role, current company, education, and location
  • Current tenure — how long they have been in their present role
  • Average tenure — how long they typically stay in a role
  • Total years of experience
These come from the application materials, so you can scan a pipeline without doing the arithmetic on every CV.

Skill-by-skill alignment

The match category tells you how a candidate aligns with your ICP as a whole. Metaview also breaks that down: each core competency in your ICP becomes its own column, showing how strongly that candidate matches that specific skill. This helps when your priorities are narrower than the role. You can sort and filter by overall alignment, or by a single competency — for example, pulling up everyone with strong revenue ownership experience because that is what your hiring manager wants to see first. Because these columns come from your ICP, editing the competencies in your ICP changes the columns you get.

Filter applicants

Use filter groups when applicants can meet one of several requirements. In the review’s filter bar, select + and choose Filter group. Add your rules and press Enter after typing each filter value. Choose and between rules to require every rule to match, or or to accept a match on either rule. You can add another Filter group from the + menu inside a group to combine alternatives with other requirements.
A demo Application Review filter group matching Job Title containing Engineer or Company containing Stripe

Use or to match either rule in a filter group, and nest groups when you need more complex conditions.

The candidate detail view

Click into any candidate to see everything behind their classification in one place:
  • A condensed summary of their experience
  • The written reasoning for their match category, criterion by criterion
  • Their application integrity assessment
  • Their full CV, as submitted
  • Any application questions they answered
From here you can progress or reject the candidate, and leave the feedback that sharpens later evaluations.

Ingesting New Candidates

For ATS-connected reviews, new applications that arrive in your selected stage are picked up and evaluated against your current Candidate Profile. For upload-based reviews, use Add applicants inside the review to upload more PDF or Word CVs at any time. In both cases, new candidates appear alongside your existing pool with the same written reasoning and match ratings, so your review stays up to date without starting over.

Reviewing Application Integrity

Recruiting teams increasingly deal with fraudulent, automated, or low-effort applications. Application Review helps you spot them by automatically checking each submission for signs of inauthentic or automated activity. These checks are performed solely on the application materials themselves. Signals fall into two categories:
  • Consistency signals — whether details within the application are complete and internally consistent.
  • Automation signals — whether the application shows signs of being submitted through an auto-apply service or contains templated, low-effort content.
These signals are indicators, not conclusions — they surface information about the submission for your consideration and do not make any determination about an application or candidate. After reviewing an application, you can update the integrity status and optionally add a justification based on your own assessment.
Application Review surfaces signals of potentially inauthentic submissions — such as internally inconsistent details, auto-submitted applications, or templated content — but never automatically rejects or deprioritizes any application. Your team always makes the final call.

Pausing and Managing Reviews

You can stop an Application Review either temporarily or permanently, depending on your needs. If you pause a review, Metaview will stop evaluating new candidates. For ATS-connected reviews, when you resume, all candidates currently in the selected ATS stage who have not yet been evaluated will be processed — including those who applied during the pause. This may use credits for all newly accumulated candidates. Candidates who were progressed or rejected in your ATS while the review was paused will not be re-evaluated. For upload-based reviews, pausing stops evaluation of CVs that are already in the review but not yet evaluated. When you resume, those pending CVs are evaluated. CVs you add through Add applicants while the review is paused will also be evaluated on resume.
Please be mindful that resuming a review may use credits for all newly accumulated candidates.
If you want to stop reviewing candidates entirely, there are two options depending on your situation. For ATS-connected reviews, to prevent new applications from being processed, close or unpublish the role in your ATS (e.g. Greenhouse, Ashby), which stops new candidates from entering the pipeline. For upload-based reviews, simply stop uploading new CVs through Add applicants. In both cases, if the role is complete and no further review is needed, you can delete the Application Review in Metaview. Deleted reviews are archived and no longer consume credits.

Using Best practices

We understand you may have questions about best practices when using Application Review. We’ve put together a guide for your team covering how to set up effective ICPs, review match categories, and stay aligned with compliance expectations — take a look here.

Application Review Credits

Application Review uses credits when candidate applications are evaluated. The credit rate and available allowance depend on your workspace’s billing setup. For shared credits, check Settings → Credits & billing. See Application Review Credits for rates, allowances and how pausing a review affects credit use.

Getting Help

If something isn’t behaving as you expect — candidate counts that don’t match your ATS, a CV that won’t parse, an evaluation that seems stuck, or a rejection email from the wrong sender — see FAQs & Troubleshooting.