UST workflow coverage
The details that determine fit.
Compare your required forms, records and outputs with Stratum’s workflow. Confirm the exact configuration before you start.
What the workflow covers.
| Area | What Stratum does | What to confirm |
|---|---|---|
| Quality review | What Stratum doesReturned records move through an approve/reject review queue. | What to confirmAgree who reviews the return and how rejected or unclear work is resolved. |
| Configured forms | What Stratum doesField information is collected through configured forms. | What to confirmConfirm the required fields, form version, intended device, and team workflow. |
| PDF mappings | What Stratum doesCollected information maps into configured PDF fields. | What to confirmCheck the exact template, field mapping, and rendered output together. |
| Packet templates | What Stratum doesConfigured templates and connected records form the packet. | What to confirmIdentify its required components, source records, and completeness checks. |
| State exports | What Stratum doesConfigured state-regulator exports use reviewed records. | What to confirmConfirm the exact jurisdiction, format, current requirements, and available configuration. |
| Shared reports | What Stratum doesRecipients can access authorized read-only reports shared with them. | What to confirmAgree which recipient sees which reports and how they receive access. |
| Scheduling | What Stratum doesThe obligation calendar organizes planned work. | What to confirmCheck the relevant obligations, recurrence, and assignment process. |
| Time records | What Stratum doesTime is tracked against the work record. | What to confirmAgree how your team records time and uses it in operations. |
| Invoice records | What Stratum doesInvoice records sit alongside operational work. | What to confirmThis does not establish full accounting, payment collection, or bookkeeping replacement. |
A workflow area does not establish support for every test method, form edition, import format, device, or integration. Your authority and qualified people determine applicable requirements; software scope needs its own review.
Bring one requirement into focus.
A normal job and its expected output are enough to start.
- Work
- What task does the team perform?
- Input
- Which site, equipment, form version and source information does it need?
- Exception
- What changes when information is missing or the result fails?
- Output
- What must the recipient receive, and in which format?
- Acceptance
- Who can confirm the result works for your operation?