Building a Governed Business Workflow
Scouts operate at the intersection of the platform's tools — capturing data through workflows, routing it through approval flows, and monitoring the result. A governed business workflow is when those three pieces compose into a single end-to-end operational reality: a customer submits a request, the request travels through the approval chain you helped configure, and the outcome surfaces in the dashboard you watch.
This tutorial walks through composing such a flow for a vendor-onboarding business process. The data capture is via a Paperless workflow (form + submission steps), the approval is via Maker-Checker, and the monitoring is via Lookout. The Scout's job is to assemble the pieces; the Pathmaker's job is to author the underlying configurations; the Warden's job is to verify the audit trail.
Prerequisites
- A Scout-role account on the project
- A Paperless workflow for vendor onboarding (configured by your Pathmaker; the workflow contains the ingress form and the submission target)
- A Maker-Checker approval graph for vendor approvals (configured by your Pathmaker; see Authoring Maker-Checker Approvals)
- A Lookout dashboard slot (your Pathmaker provisioned it; you assemble the widgets)
Step 1 — Confirm the workflow is live
In the Console, navigate to Paperless → Workflows → vendor-onboarding. Verify:
- Status:
Published - URL:
https://your-domain.com/forms/vendor-onboarding - Fields: company name, contact email, services offered, jurisdiction, requested budget
- Submission target:
vendorscollection
If anything is missing, your Pathmaker is the right person to surface it to. Workflows are Pathmaker-authored, not Scout-authored.
Step 2 — Submit a test entry
From a private browser session, submit the workflow's ingress form with test data. This produces:
- A new row in
vendors(status:pending_approval) - A trigger event into the Maker-Checker approval graph
- An entry in the approval queue for whoever is configured as the primary approver
You should see this happen end-to-end within seconds.
Step 3 — Watch the approval queue
The approval queue surfaces in the Console at Workflows → Pending approvals. As a Scout, you see queues your role has visibility into (typically read-only — Scouts observe, Wardens or named approvers act).
Filter to workflow: vendor-onboarding. You should see your test submission queued. The detail view shows:
- The submitted form contents (with PII fields masked per the analytical view configuration)
- The primary approver (the role pool, plus any specific subjects on call)
- The cooldown deadline
- The audit-correlated form-submission event
Step 4 — Confirm the audit trail
Open Audit → Recent events and filter for the request ID from your form submission. You should see the cross-surface trace:
| Time | Event | Notes |
|---|---|---|
| T+0s | Paperless workflow submission event | Subject: anon (workflow is public); fields hashed; request_id req_X |
| T+0s | data.vendors.insert | Subject: paperless-workflow-handler service; status: pending_approval |
| T+0s | maker_checker.initiated | Workflow: vendor-onboarding; gate-token: gate_Y |
| T+0s | notification.email.sent | To: vendor-approver role pool |
The same request_id ties the form submission to the approval initiation. The forensic chain from "an anonymous user submitted a form" through "the approval graph fired" is contiguous.
Step 5 — Assemble the monitoring view
Navigate to Lookout → Dashboards → vendor-pipeline (the slot your Pathmaker provisioned). The dashboard is empty initially — you add widgets relevant to your operational concern.
Drag widgets from the palette:
Funnel widget — "Submissions by stage"
- Source: Paperless workflow submission events filtered to
workflow: vendor-onboarding - Stages: submitted → in approval → approved → onboarded
- Conversion rate per stage, time-in-stage averages
Time-to-approval widget — "Approval latency"
- Source:
maker_checker.*events forworkflow: vendor-onboarding - Metric: median, p95, p99 time from initiated to approved
- Bucket: daily
Queue depth widget — "Current pending approvals"
- Source: live gauge from the approval graph state
- Threshold: amber if >5, red if >15
Rejection-reason breakdown — "Why rejections happen"
- Source:
maker_checker.rejectedevents - Group by: the rejection reason field captured by the approver
Save the dashboard configuration; it persists per your account.
Step 6 — Set up alerts
For pieces of the dashboard you want to react to:
Alert: queue depth exceeds 15
- Channel: your in-app inbox + the operations email distribution
- Cooldown: 1 hour (do not alert again until the condition clears + the cooldown elapses)
Alert: p95 approval latency exceeds 48 hours
- Channel: the operations email distribution
- Cooldown: 24 hours
Alerts are role-scoped: alerts fire to the role pool you target, not just to you personally.
Step 7 — Operate the flow
Day-to-day, the workflow is now self-sustaining. As Scout, you:
- Watch the dashboard for pipeline health
- Surface bottlenecks to the relevant owner (Pathmaker for workflow re-routing, Warden for policy questions)
- Pull periodic reports for stakeholders (see Generating Audit-Ready Operational Reports)
You are not in the approval chain (approvals are done by named approver roles); you are not authoring policy (Pathmaker does that); you are not investigating audit anomalies (Warden does that). You are the operational eyes — the role that sees the system as a flowing whole and surfaces things to the right specialist.
What just happened
You connected three platform tools — Paperless for capture, Maker-Checker for routing, Lookout for monitoring — into a single operational flow, end-to-end. The flow is governed (every step audit-logged), identity-scoped (every event ties back to the originating subject), and observable (the dashboard surfaces the whole pipeline state).
The Scout role is the operational steward of flows like this. You did not need to be a developer; you did not need to write policy; you used the platform's compositional surfaces to make a coherent operational picture.
Next
- Configuring Identity-Scoped Telemetry Alerts — extend the alerting surface beyond this workflow to broader operational concerns.
- Generating Audit-Ready Operational Reports — pull structured reports from the audit trail for stakeholder review.
- Pathmaker → Authoring Maker-Checker Approvals — the upstream configuration this flow relies on.