Sheaf

Every file, against
every requirement.

How matching works
Match Engine / 16 requirements · 11 covered

Identity2 / 2

Government photo ID Driver Licensepp. 1–2 Approved
Borrower identity affidavit Signature Name Affidavitp. 3 Approved

Income2 / 4

Income, tax year 2022 1040 + Schedule Cpp. 4–19 Approved
Employment verification Pay Stub ×2pp. 20–23 Recommended
W-2, most recent year W-2, tax year 2021pp. 24–25 Superseded
Written verification of employment no document found Missing

Assets2 / 3

Asset statement, 60 days Bank Statement ×2pp. 26–33 Approved
Large deposit explanation Letter of Explanationp. 34 Recommended
Gift letter, donor signed no document found Missing

Collateral3 / 4

Executed purchase agreement Purchase Agreementpp. 35–48 Approved
Appraisal, full interior Appraisal Reportpp. 49–71 Pending
Title commitment Title Commitmentpp. 72–83 Approved
Flood determination Flood Certificatep. 84 Approved

Compliance2 / 3

Hazard insurance binder no document found Missing
Notice of right to cancel Notice of Right to Cancelpp. 85–87 Approved
Taxpayer consent, 4506-C Form 4506-Cp. 88 Recommended

Arrived, not required2

Nothing on the checklist asks for this Utility Billp. 89 Unassigned
Filed under a different application Prior Loan Estimatepp. 90–92 Unassigned
01 / INPUT

Bring the mess.

Do not prep. Do not sort. Do not clean up. Just point Sheaf at the raw intake and let the engine handle the reality of operational documents.

Scans
Phone Photos
Merged Packets
Application Dumps
Wrong-order Pages
Junk Pages
Dense Tables
Signatures
02 / PROCESS

Closing the checklist.

Your policy says what an application needs. Sheaf binds what actually arrived to what was actually required, and names the difference.

Require

Read the checklist.

Your policy is the list of things that must be satisfied. It varies by product, by program, and by applicant, and Sheaf takes it as given.

Candidate

Line up the files.

Everything that arrived is a candidate, including the documents nobody labelled and the ones filed under the wrong application.

Bind

Satisfy, or don't.

Binds each document to the requirement it actually satisfies, with a confidence attached, and abstains rather than guessing when the evidence is thin.

Gap

Name what's missing.

Reports the requirements nothing covered. The chase list writes itself, and it is the same list your auditor would have built.

Technical detail How matching works, and where extraction joins it Read the spec →
03 / OUTPUT

Structured payload.

The file doesn't need to arrive perfect, but the data leaves that way. Ready for your existing infrastructure.

Coverage against your checklist, requirement by requirement, with the document that satisfied each one and the confidence behind it.

What's outstanding comes back as a list you can act on, not a percentage you have to interpret.

{
  "checklist_id": "chk_8849-2A",
  "satisfied": 6,
  "outstanding": [
    { "requirement": "hazard_insurance" },
    { "requirement": "gift_letter" }
  ],
  "complete": false
}
Compare