Running an audit and following its progress

Starting it

The final step reviews what you have built. Check the standards and the record count, then start the audit.

The two phases

An audit runs in two passes, and the progress indicator names the one it is on:

• Extracting records. Rhazes reads each file and pulls out its content. Progress is counted in files.
• Validating standards. Every record is judged against every standard. Progress is counted in validations, which is why the number here is larger than your file count: ten records against four standards is forty validations.

It updates live

You do not need to reload or wait on a blank screen. Results fill in as they are decided, and a Processing indicator shows while the run is still connected.

An audit moves from pending, to in progress, to completed.

You can read results before it finishes

Records that have been judged show their status immediately, so on a large audit you can start reading the early results while the rest is still being worked through.

Worth doing, because it is the fastest way to catch a standard that is not phrased the way you intended. If the first twenty records are all coming back excluded, your inclusion criteria are wrong, and finding that out at record twenty is considerably better than at record four hundred.

If something fails

A record that could not be read shows as an error rather than being silently dropped. Check whether the file is a real PDF, whether a scan is legible, and whether the document is password protected.