- Can metadata fields vary by document type?
- Yes. The loan/program configuration determines which fields appear for each type (e.g., proposal amount/work type, address match checkbox, license expiry).
- Why validate documents one by one?
- Archiving, tagging, compliance, flexibility, and automation. A controlled, per-document review guarantees correct classification, captures the right metadata, produces reliable AI training data, applies rules programmatically, and creates a complete audit trail. Bulk/unstructured review can't ensure these outcomes.
- Is one by one slower?
- Case handlers don't waste time piecing together the overall state or guessing what's already been checked. The structured flow reduces rework, prevents errors, and cuts back-and-forth with applicants. Reviewing each file takes only seconds when everything is presented clearly and consistently.
- What happens if a document is invalid or unclear?
- Mark it invalid and request a replacement via Request Extra Documents. The applicant receives a reason and deadline; the new file returns directly to the validation queue.
- How does the system know when the document step is finished?
- When all document requirements defined by the loan program rules are met (types present, metadata satisfied), the step completes automatically.
- What if I don't require anyy doucment uploads?
- Then this step simply doesn't appear. Programs that require zero documents skip Applicant Document Validation entirely. Keeping the workflow clean and friction-free.