Reviewing uploads
Every upload is read and checked before it reaches you. The verdict is advice — you're still the one who accepts it.
What the check does
When a file lands, Claude reads the document itself — PDFs and images directly, no separate scanning step — and answers four questions:
| Check | The question it answers |
|---|---|
| Type | Is this actually the document you asked for, or a payslip where a bank statement should be? |
| Period | Does it cover the dates you need, or is it last year's? |
| Readable | Can it be read at all — or is it a blurred, cropped, glare-covered photo? |
| Complete | Is anything obviously missing, like page 3 of 4? |
Each file comes back as pass, warn or fail, with a plain-language list of anything wrong, plus a suggested filename so you're not renaming downloads by hand.
Expiry dates
For documents with a validity window — a passport, most obviously — the expiry date is read off the page and checked against the dates on the request. A passport that expires two weeks after the return flight gets flagged before it becomes an airport problem. This check is on every plan, including Solo.
The AI never decides
The verdict is advisory. Nothing is accepted, rejected, or sent back to your client automatically. It exists to tell you which files need your eyes and which are routine, so a stack of twelve uploads becomes two you actually inspect.
Treat a warn as "look at this one", not as a rejection. Models misjudge unusual documents, and you know your client's paperwork better than it does.
Accepting, or asking again
Two buttons on each item:
- Accept — the line is closed. Your client sees it as accepted and there's nothing more for them to do. Once every required item is accepted, the request is complete and reminders stop.
- Ask again — the line reopens with your note attached. Your client sees "Needs update" in red on the same link they already have, with your note explaining what to fix. No new link, no new message to find.
Write the note as an instruction, not a verdict. "Needs the page showing the closing balance" gets the right file back. "Rejected — incomplete" gets you a reply asking what's wrong.
Asking again is cheap; guessing isn't. Clients re-upload from the same link in seconds. Accepting a marginal document to avoid an awkward message is how bad files end up in your files.
What we do with the file while checking it
The check runs on a temporary copy held in memory only, for as long as the pass takes, and then it's gone. We store the verdict — the four checks, the issues, the suggested name — and never the document's contents. Nothing from inside your clients' documents is logged.
Full detail in Storage and security.
Still stuck? Email dev@inpresencelab.com and a human will answer.
ChaseDocs