Skip to main content

Defining Workflows

In Evalium, you define the "blueprints" for your work verification in the form of Protocols.

A Protocol is a reusable template that defines exactly what needs to be captured, who needs to verify it, and how the results should be calculated.

1. Creating a Protocol​

When you define a new workflow, you are designing a repeatable process. You can mix and match different capture types based on your needs:

  • Checks: Simple confirmations or multiple-choice options.
  • Rubrics: Structured criteria for observers to rate.
  • Evidence Requests: Requirements for photos or documents to be uploaded.

Setting Verification Strength​

For each Protocol, you decide how much proof is required to satisfy your quality or compliance standards:

  • Self-Verified: The operator completes the work and records it themselves.
  • Supervisor-Verified: A manager or verifier must review and sign off.
  • Verified Context: The system automatically records the time, location, and device used to ensure the record is truthful.

2. Managing Versions​

Evalium uses a strict versioning system to ensure your historical records remain accurate.

  • Drafts: You can edit and change a Protocol as much as you like while it is in Draft.
  • Published Versions: Once published, a version becomes fixed. This ensures that every task performed using that version is measured against the exact same rules.
  • Updating: To change a process, you create a new version. Your Activity History will always show exactly "what was used at the time" for every past event.

Why it matters: Defensibility​

Because every action is backed by a specific, versioned Protocol, your business records are defensible. If a result is questioned a year from now, you can show exactly which rules were in place, what evidence was captured, and who verified the work.