Run the Same Job Over Many Documents.
A workflow is the same job done over many documents, with a person in the loop where it matters. Describe it in plain language and edit the steps it builds.
What should happen to each document?
STEPS
No steps yet. Describe the job above, or add steps by hand below.
ITEMS
Updating every few seconds…
⚑ needs review: no signed consent page found
What needs to change?
Sent back to Flag with your note.
⚑ needs review: consent signed, but the date is missing
Approved. It continues to Generate.
Built from a description. Describe the job in your own words. The steps are built for you, and each one can be edited.
The run. Each document moves through each step. Anything uncertain is flagged, and the run pauses for a person.
A person at the gate. Approve an item, reject it, or send it back with a note to the step it came from.
How a Workflow Works
Built From a Description
Say what the job is. Seniorverse builds the steps, and you edit them. Teach it by example instead of writing a schema: show it one to three samples and it proposes the fields.
- Composed in plain language
- Fields proposed from samples or from your description
- Or let it name whatever it finds
- Edit any step before you run it
Steps That Do the Work
Each step either runs on every item or acts as a barrier across all of them.
- Extract: named fields, or whatever it finds
- Analyze: a freeform pass with your instructions
- Generate: a document from a template
- Flag: judgment against plain-language criteria, where uncertain always flags
- Compile: one report across every item
- Export: a spreadsheet of per-item values
A Person at the Gate
A review gate pauses the run. Approve an item, reject it to drop it, or ask for changes with a note that sends it back to the step it came from.
- Every item, or only the flagged ones
- Reject drops the item from the run
- Ask for changes rewinds it with your note
- Anything it was unsure about is flagged, not guessed
