Skip to content

Process Template

Executive Summary

This is the mandatory template for future Algosure Business Processes. Every future process must use this structure unless the Chief Product Officer and Enterprise Architect approves an exception.

Why This Exists

A shared template keeps process definitions consistent, governable, measurable, automatable, and aligned to the Algosure Blueprint.

Owner

The owner is the Chief Product Officer and Enterprise Architect. Each completed process must identify one owning Practice.

Business Value

The template accelerates process design, improves review quality, and ensures every process includes ownership, approvals, events, KPIs, exceptions, auditability, and automation readiness.

Required Template

---
title: <Process Name>
version: 0.1.0
status: draft
owner: <Owning Practice>
classification: Business Process
last_updated: YYYY-MM-DD
---

# <Process Name>

## Executive Summary

<Short description of the process and the business outcome it produces.>

## Why This Exists

<Explain why the process exists and what problem it solves.>

## Owner

<Name the owning Practice and accountable role.>

## Business Value

<Explain measurable business value.>

## Scope

<Define what is included and excluded.>

## Trigger

<Define event, schedule, request, risk signal, or workflow state that starts the process.>

## Inputs

| Input | Source Owner | Purpose |
| --- | --- | --- |
| <Input> | <Domain or Practice> | <Usage> |

## Roles

| Role | Responsibility |
| --- | --- |
| Owning Practice | <Operational accountability> |
| Digital Professional | <Assigned execution role> |
| Domain | <Facts or events referenced> |
| Human Approver | <Approval responsibility> |
| AIOS | <Orchestration responsibility> |

## Procedure

1. <Step>
2. <Step>
3. <Step>

## Approval Gates

| Gate | Trigger | Approver | Evidence Required |
| --- | --- | --- | --- |
| <Gate> | <Condition> | <Role> | <Evidence> |

## Events

| Event | Trigger | Consumers |
| --- | --- | --- |
| <Event> | <Trigger> | <Consumers> |

## Exceptions

| Exception | Response | Escalation |
| --- | --- | --- |
| <Exception> | <Response> | <Escalation> |

## Outputs

| Output | Owner | Use |
| --- | --- | --- |
| <Output> | <Owner> | <Use> |

## KPIs

| KPI | Definition | Target |
| --- | --- | --- |
| <KPI> | <Definition> | <Target> |

## Audit Evidence

<List records required for audit.>

## Automation Level

<Level 0-5 and rationale.>

## Version History

| Version | Date | Change | Owner |
| --- | --- | --- | --- |
| 0.1.0 | YYYY-MM-DD | Initial draft | <Owner> |

Template Rules

  • Do not remove ownership, approval, event, KPI, exception, audit, or automation sections.
  • Use Domain references instead of duplicating source facts.
  • Include Mermaid diagrams where workflow clarity benefits.
  • Keep language professional and business-oriented.
  • Maintain YAML front matter.