How does the tool know which applicant a document belongs to?

By its subfolder, and by nothing else. Inferring the applicant from the name read inside the document would be cleverer and far more dangerous: one misread name would make one more applicant, and therefore one more incomplete file.

What if the applications are in ZIP archives?

They are opened, and the inner subfolder makes the applicant. One archive per applicant works too.

How many files at once?

As many as the tab holds: a thousand files have been read and verified without it falling over. The check itself is instant.

Can the table be sent to the landlord?

It carries only the names of the files, their state and what is missing: nothing from inside them, no amounts. It is made to circulate.

Check twenty applications at once

Twenty applications for one property, ten new hires in a month: the same check, done twenty times from memory. Drop the folder that holds them all, and read one table.

Or drop the folder holding one subfolder per applicant here. Nothing is sent: everything stays in this tab.

When to use it

An agency receives twenty files for one property and must tell each one what is missing, without mixing up applicants.

Or an HR team follows ten arrivals in a month and wants to know which are ready for payroll.

What this tool does

One subfolder per applicant is the only rule. That is how applications arrive, and that is what the tool takes for a file: it does not guess groups from the names read inside the documents.
Incomplete files come first. They are the only ones with anything to do about them; complete files read at a glance at the bottom.
One chasing message per applicant, ready to copy, with their own list. You do not chase twenty people with one message.
The tracking table as CSV: one row per file, its state, what is missing. It carries no file names, because it circulates.
Situation boxes apply to the whole batch (employed, with a guarantor): it is the same listing and the same property.

What it does not do: no document passes from one applicant to another, and a test checks it. In exchange, a document left at the root of the drop belongs to nobody: it is counted in no file.

What is read in the document

The path of each document, which says which file it belongs to, then its type, its date and the person it concerns.

No file is uploaded: the folder is read by your browser, in this tab, and the page is not allowed to open a connection to any other site.

Frequently asked questions

How does the tool know which applicant a document belongs to?: By its subfolder, and by nothing else. Inferring the applicant from the name read inside the document would be cleverer and far more dangerous: one misread name would make one more applicant, and therefore one more incomplete file.
What if the applications are in ZIP archives?: They are opened, and the inner subfolder makes the applicant. One archive per applicant works too.
How many files at once?: As many as the tab holds: a thousand files have been read and verified without it falling over. The check itself is instant.
Can the table be sent to the landlord?: It carries only the names of the files, their state and what is missing: nothing from inside them, no amounts. It is made to circulate.

The other tools

Check against a list of expected documents : The heart of the tool: present, missing, doubtful, extra.
Mortgage application file : The documents of a mortgage file, per borrower and co-borrower.
Rental application file : The documents a rental applicant may be asked for, and those they may not.
Public tender application : The certificates of an application, with their validity dates.
New employee file : Onboarding documents, and those an employer may not demand.