Workflow & User Interface

From an end-user perspective, is manual acceptance required, or can documents be auto-populated and pushed through automatically?

This is fully configurable.

Documents can be automatically populated and pushed through the workflow based on a defined confidence threshold. For example:

  • Documents scoring ≥95% confidence can be automatically returned with an Approved status and proceed without manual intervention.

  • Documents scoring below the threshold can be routed to a Needs Review queue for human validation.

This configuration allows organizations to balance automation efficiency with quality control requirements.

How is failure handled if below 50% or content issues? Does the bot create a workflow or query?

Currently, automatic workflow or query creation is not enabled, though this capability is under development.

If confidence falls below a defined threshold (e.g., 50%) or if content validation issues are detected—such as a missing date or invalid signature—the system flags the document with a low-confidence score and surfaces the identified issues directly in the front end.

The document is then routed for human review, ensuring a human remains in the loop to validate, correct, or complete the required actions before progression in the workflow.

How do end users know when automation populated metadata versus a human?

Everything is logged in an audit trail, so users can see that the last activity was metadata fulfilled by Automate. Additionally, the confidence score is displayed in the metadata panel of Veeva.

Can end users see in Veeva that metadata was updated by automation versus a human?

It’s logged in the audit trail (‘metadata fulfilled by Automate’). The confidence score is visible in the metadata panel. Also show a big visual indicator like an ‘Automate score’.