Every file selected for verification, and every discrepancy anywhere in the record, must be assessed against the criteria — the Application and Verification Guide for that award year, 34 CFR 668, and your own verification, SAP and professional judgment policies — and the determination documented.
An estimated 75% of the preparation removed
from a case carrying a discrepancy.
On our task decomposition the same administrator covers roughly two and a half times as many of these cases in the same hours, because a 95-minute review becomes about 35 minutes — an estimated 75% of the preparation and 63% of the whole review, with the judgement time unchanged. These are our figures, not measurements on your files — we go through the working against your own case timings in the demo.
The assessment is mandated. The judgement is your administrator’s. Outcomer maps the file against every requirement and reports the position — so the same team covers more cases in the same hours, with the judgement time unchanged.
Applications arrive in a peak. Every one of them has to be assessed against all the requirements that apply to it — the Application and Verification Guide for that award year, 34 CFR 668, and your own verification, SAP and professional judgment policies.
Your specialists understand the requirements. What takes the time is the manual mapping of the evidence against them — and that is the part we remove and return to your team, as capacity for review.
Every specialist starts with the same orientation report, and every case carries an audit record of what evidence was considered against each requirement.
Not a summary and not a recommendation. Every requirement that applies to this application, listed for consideration, with the evidence for why it is met or why it is not. Produced in seconds.
This is technology we have applied in other regulated review workflows. We now want to show what it does for your team, configured on your own historic cases.
More applications, and more requirements to assess them against. Outcomer raises your team’s assessment capacity without expanding your permanent or temporary headcount — because the part it removes is the manual mapping, not the judgement.
When a verification case is picked up, your administrator runs a Case Orientation Report and works from that — instead of assembling the position by hand first. They open a prepared position rather than a raw file, and spend their time on the judgement.
One dependent undergraduate selected for verification, with a discrepancy in the file. Every requirement it engages has been checked against what was submitted.
The administrator starts here — rather than reconciling the ISIR, the transcript, the W-2s, the worksheet, the registrar record and two policies by hand.
Outcomer runs against two requirement sets at once. The published rail — the FSA Handbook, free at fsapartners.ed.gov and reissued for each award year, together with 34 CFR 668. And your own rail — your verification policy, your SAP policy, your conflicting information policy and your professional judgment policy. Each requirement is traced to whichever issued it. Critical describes how far the absence blocks a decision on this file — not the student’s circumstances, which are the administrator’s to weigh.
The parent tax return transcript records wages from two employers totalling $61,240. One W-2 is on file, for $38,900, leaving $22,340 unaccounted for. The intake note records ‘AGI matches transcript’, which addresses the adjusted gross income and not the wage reconciliation. Asterion Verification Policy v8 §4.2 requires each income source to be documented.
The requirement comes from the AVG. And the date decides which version applies: three editions of the Handbook are live at once, so a 2025–26 file in the same queue is measured against different dates and a different base tax year.
ISIR transaction 02 was received on 6 September 2026 and nothing on the file records that it has been reviewed. Volume 2 Chapter 3 is explicit: even where a school has already verified the information on a student’s ISIR, it must review all information on subsequent ISIRs.
This is the larger obligation, and it does not depend on selection. The Handbook requires the institution to resolve discrepancies in all FSA-related information received by any school office, and states that the duty is not confined to students selected for verification — it can arise across the institution’s wider Title IV population. It is an administrative capability requirement.
This is what two rails means in practice. The federal requirement sets the duty; your own policy sets the evidence standard, and under professional judgement that standard is explicitly yours. Outcomer reports against both, and names which one each line comes from.
Our task decomposition for a verification carrying a discrepancy, not a measurement on your files. The judgement rows are unchanged by design — resolving the conflict and deciding whether aid may be disbursed stay with the administrator. We go through the working against your own case timings in the demo.
Illustrative case. Asterion College is a fictional entity; the student, household and documents are invented. The requirement set is real and current.
The federal rail does not change between institutions. What changes is the student — and with it, which requirements the file engages.
Parent and student tax data, household size, number in college — and what the registrar knows that the aid file does not.
You decide: which figure is correct, and whether aid may be disbursed.
AVG 2026–27 tracking group V1 · Volume 2 Chapter 3 · your verification policy
View the report →No parental data, an income change since the base year, and an adjustment requested under section 479A.
You decide: whether an adjustment is warranted, and on what figures. Outcomer never exercises professional judgment.
HEA §479A · AVG 2026–27 · your own PJ evidence requirements and approval route
View the report →Verification narrows; satisfactory academic progress and the loan position carry the weight.
You decide: the SAP determination, any appeal, and the award.
34 CFR 668.34 · annual and aggregate limits · your SAP policy
View the report →Configured to the requirements that apply to you. The FSA Handbook and 34 CFR 668 are the same for every Title IV institution. Your verification, SAP, conflicting information and professional judgment policies are yours — and much of that rail is already published on your own website.
Your student information system and your document collection platform continue to hold and manage the file. Outcomer reads it and reports the position — it writes nothing back, holds no case state, and replaces nothing.
The report is a point-in-time statement of the file against the requirements that govern it. Nothing is held between runs. Run it again when a document arrives, or when a subsequent ISIR does.
The FAFSA cycle runs twenty-one months, so two award years overlap for several months and three editions of the Handbook are live at once. The crunch runs from the March priority deadlines through June status checks to the August payment deadlines.
And the Department’s electronic announcement of 29 May 2026, on preventing FAFSA fraud, tells institutions to route later-arriving ISIRs, NSLDS changes, address changes and reports from other offices into a review queue — warning that an institution which only checks at initial packaging is likely to miss later-developing indicators.
The work arrives on the deadline whether or not the posts are filled.
We configure Outcomer to your own verification, SAP and conflicting information policies and run it against a set of closed files from a completed award year — so your administrator sees what they would have had in front of them. Closed files, no deadline, nothing installed.
No live student decisions. No integration. Completed files only, from an award year that has closed. We capture your current baseline before we start, so the comparison at the end means something.