Governance & operated workflows
Nothing runs live until it has earned the right to.
Some recurring work is better run than handed back. When Fortress runs a workflow with you, it runs under named human ownership, with authority earned on evidence and a runbook your team can pick up. This page shows exactly how.
What gets operated
High-volume, rule-bound work. Never the judgment calls.
The candidates are workflows where consistency matters more than judgment and your team's time goes to throughput rather than decisions. Work that decides something about a person or releases money stays with you.
| Value stream | Typically operated | Always stays with you |
|---|---|---|
| Healthcare revenue cycle | Denial management, A/R follow-up, eligibility verification, claim status and queue management | Clinical judgment, coding decisions, patient relationships |
| Insurance operations | Claims intake and triage, underwriting data assembly, renewal preparation, policy administration transactions | Coverage decisions, pricing authority, claim settlement |
| Revenue growth | Market intelligence, list building, pipeline hygiene, commercial reporting | Selling, negotiation, pricing authority |
| Customer operations | Intake routing, status response, knowledge maintenance, escalation triage | Relationship ownership, commercial decisions |
| Finance operations | Invoice handling, collections follow-up, A/P processing, reconciliation preparation, recurring reporting | Approval authority, payment release, financial judgment |
The authority ladder
Authority is earned on evidence, never granted at signature.
Every operated workflow runs at a defined level. Work starts at the bottom and moves up only against evidence agreed in advance.
| Level | What it can do | Human review |
|---|---|---|
| 0 · Inform | Retrieves, summarizes and monitors while behavior is baselined. Nothing is acted on. | Full |
| 1 · Recommend | Proposes actions for a person to decide. | Every recommendation reviewed |
| 2 · Prepare | Assembles and stages work for human approval. | Every item approved before release |
| 3 · Execute within bounds | Acts inside an explicitly defined envelope. | Risk-weighted sampling plus full exception review |
| 4 · Autonomous within domain | Acts independently in a tightly governed domain. | Reduced sampling plus full exception review. Never zero. |
Fortress operates client workflows to Level 3 unless you explicitly authorize otherwise, a restraint Fortress chooses. Your own governance sets the ceiling: an organization without working policy, ownership, review cadence and exception handling cannot run a workflow at a high level, however well the tool performs. Closing that gap becomes part of the work, and you hear about it before you sign.
What never changes
At every level, the same six controls.
A named owner on both sides
On your side, the person who directs and supervises the workflow and who the runbook is written for.
Entry and exit criteria
Defined for work in the queue, with an exception path for anything outside scope.
Change control
No change to scope, authority or standards without a reason, a test, sign-off and a log entry.
A published runbook
Detailed enough for a qualified person to resume the work without Fortress.
Human review
Reduced as evidence allows. Never removed.
Decisions that stay yours
Fortress does not operate a workflow that makes a final adverse determination about a person.
Keeping the tool fit
Fit for the job, and still fit six months later.
| Control | What it means |
|---|---|
| Selection on evidence | Tools are chosen on measured performance against your workflow. Data handling terms are verified in writing before anything of yours reaches them. |
| Version pinning | Versions we can pin, with notice of changes. |
| Evaluation sets | Cases with known-correct outcomes, drawn from your real work and reviewed by your subject expert. |
| Regression testing | The full set re-runs before any change reaches production. A failed run blocks the change. |
| Drift monitoring | Performance is tracked against the set. Decline pauses advancement and triggers investigation. |
Standards, data and incidents
Stated plainly, so you can inspect them.
Service standards
Four measures, set against your own baseline rather than a generic benchmark: throughput, quality (sampled), turnaround and exception rate. Exceptions are treated as a design signal, not only a performance one. Targets are agreed per workflow after Diagnose and are not promised in advance.
The monthly pack
The same template every month: performance against baseline, volume and trend, the exception log, current authority level and its evidence, every change since last review, and open risks with owners and dates.
Your data
The free readiness assessment collects nothing. Target operating model design extracts nothing and retains nothing. Operated workflows need access to your systems of record, so the full posture applies: least-privilege access you grant and can revoke, multi-factor authentication, access logging, and a business associate agreement before any protected health information. Client data is never used to train third-party tools.
When something goes wrong
Critical issues are reported to you immediately. Major issues get same-day notice, a remediation plan within one business day, and reduced authority until resolved. Minor issues are logged and reviewed monthly. Every critical or major incident gets a written review, whether or not you ask.
Getting out
Nothing here is designed to trap you.
Every operated workflow carries a runbook your team can use to resume the work. On exit, transition assistance is contractual: documentation, knowledge transfer and a handover to an agreed schedule. We would rather you stayed because the work performs.
Ask us to show you any of it.
Everything here is a mechanism rather than an intention, so it can be inspected. If you are evaluating Fortress for regulated work, ask for the security and data handling overview.