# How Fetch checks each file

Fetch checks every upload as it arrives. Is it the document you asked for, and can it be read? If not, the client is told why and asked again.

Documents with Fetch · Updated October 11, 2026 · https://userookery.com/help/document-checks/

A wrong file found a week later costs you another round of emails. So Fetch checks each upload the moment it arrives, while the person is still on the page.

## What Fetch checks

- **Is it the right kind of document?** A bank statement when you asked for a bank statement, not a utility bill.
- **Can it be read?** Not a blank page, and not a blurry scan.

Fetch is easygoing about format. A photo of a receipt is fine if it's clear.

## When a file passes

1. The client sees **Received and checked**.
2. The item shows **Received** in your conversation.
3. Fetch adds a note, like: Received "Bank statement": it looks right.

## When a file isn't right

1. The client sees a short, polite reason, like "This looks like a bill, not a bank statement."
2. Their button changes to **Upload a new file**, so they can fix it right away.
3. In your conversation, the item shows **Needs a new file**, with the reason.
4. Fetch adds a note saying what looked wrong.
5. The next reminder lists the item again, with the reason.

## Good to know

- Fetch doesn't check dates or names yet. A statement from the wrong year, or for someone else, can still pass. Give each file a quick look.
- If Fetch can't check a file at all, it leaves a note asking you to open it and review it yourself.
- Every upload is saved in **Documents**, even ones that didn't pass. Click **Download** to see it.
- **Fetch got it wrong?** Click **Accept anyway** next to the item. It counts as received, reminders stop for it, and the timeline records that you accepted it.

> **Coming soon:** a **Redo** button, so you can ask for a new file with your own reason.
