Action

Readability

Gate on capture quality

Readability checks that a photo or scan is clear enough to trust — in focus, well-lit, and large enough to make out the small print — before the workflow tries to read it, and sorts each capture into pass, review, or reject instead of guessing on a bad image.

How it works

Readability is a quick quality check that runs before any reading happens. When a document arrives as a phone photo or a scan, it looks at whether the image is actually clear enough to trust — in focus, evenly lit, and high enough resolution to make out the small print — and sorts each one into pass, review, or reject.

This matters most when people capture documents in the field. A delivery slip snapped at a loading dock, a receipt photographed on a car seat, a form run through an old copier — some come through perfectly and some are blurred, glared, or cut off. Without a gate, the workflow reads all of them the same way and quietly gets the bad ones wrong. Readability stops that: clear captures flow straight through, questionable ones get flagged for a person, and unusable ones are turned back for a retake before anyone relies on them.

It uses no AI and adds almost nothing to a job, so it is cheap to put in front of every intake. Wire the pass path to your reader, and send review and reject to a person or a 'please retake' message. The result is that the automation only ever acts on captures it can actually trust.

Common use cases

Real situations where this node earns its place in a flow.

Catch bad delivery-slip photos

When drivers snap bills of lading at the dock, turn back the blurry or glared shots for a retake before they ever reach data entry.

Screen field-captured receipts

Receipts photographed on the go vary wildly; pass the clean ones straight through and flag the unreadable ones for a person.

Guard any phone-photo intake

Put it in front of forms, statements, or IDs captured by camera so the reader only works on images it can actually trust.

Readability in a workflow

A simple example of where this node sits in a flow.

File upload Upload one or more files Readability Gate on capture quality Extract PDFs → structured data Dojobase write Write records to a Dojobase

What you set up

  • Put your intake (an upload or an email attachment) just upstream so there is an image to check.
  • Optionally tune how strict each check is — blur, resolution, lighting, contrast — per job, or leave the sensible defaults.
  • Wire the three outputs: pass to your reader/extractor, review to a person, reject to a retake prompt.

Common questions

What if it can't tell whether a capture is good?

Anything borderline goes to the review path, not the pass path. The gate is built to err toward a human look rather than let a shaky capture through.

Does it work on scans, not just phone photos?

Yes — it checks scanned pages the same way. Anything it can't read as an image passes through untouched rather than blocking the job.

Will it slow things down or cost much?

No. It uses no AI and only a moment of processing, so it's practical to place in front of every document that comes in.