How Long Does a Scan Take

Most documents return a complete report in under five minutes. A short RAMS often comes back in a minute or two; a long, dense document with several attachments takes longer.

What makes a scan slower

• Length. A 60-page document takes longer to read than a 12-page one.
• Multiple files in one submission, which are read individually and then cross-checked against each other.
• Complex layouts — heavy tables, multi-column pages, content in headers and footers.
• Queue position at busy times. Growth has priority processing over Starter, and Enterprise has dedicated processing with a guaranteed response time.

You do not have to wait on the page

The scan runs on our side, not in your browser. You can close the tab, switch device or go and do something else — the report will be in your document list when it is done, and progress is shown live if you stay.

If it looks stuck

1. Refresh the page. The progress display occasionally loses its connection while the scan itself continues normally.
2. Check your document list — the report may already be there.
3. Give it fifteen minutes in total before treating it as a failure.
4. If it has genuinely failed, the document shows as failed rather than sitting in progress, and a failed scan does not consume an allowance.
5. Still stuck after fifteen minutes? Contact us with the document name and roughly when you uploaded it.

Speed is the point, but not the whole point

Five minutes is worth comparing to what the same read takes by hand: a careful manual review of a full RAMS is rarely under an hour, and how long a RAMS review should take works through where that time actually goes. The scan replaces the mechanical part of it, not the judgement.