# Automation Blueprint and Test Checklist

Clearweft · Week 5

## Select the recurring job

- Job:
- Why it repeats:
- Current manual steps:
- Observable successful result:
- Approximate frequency based on actual use or a labelled assumption:
- Consequence of a wrong action:

## Workflow definition

Trigger:

Required fields:

Event identifier or duplicate check:

Conditions:

Allowed actions:

Expected output:

Status record:

Failure owner:

Recovery procedure:

## Five layers

| Layer | Responsibility | Source or implementation |
| --- | --- | --- |
| Logic | Rules and allowed actions | |
| Data | Required records and source of truth | |
| Intelligence | Optional bounded AI call | |
| Orchestration | Run steps and handle exceptions | |
| Presentation | Subscriber output and operator view | |

## Implementation choice

Options considered: existing native features / integration workflow / custom code.

Required connections:

Why the chosen option fits:

Running cost and maintenance work:

Current official instructions checked:

## Test matrix

| Case | Input | Expected result | Actual result | Evidence |
| --- | --- | --- | --- | --- |
| Normal request | | | | |
| Same event again | | | | |
| Missing required field | | | | |
| Failed action | | | | |
| Recovery after correction | | | | |

## Maintenance note

Owner:

Where failures appear:

Safe retry conditions:

When to stop and review:

Last successful test:

Next review date:

Completion: the normal case works, an unintended duplicate is prevented and a failure has a practical recovery path.

## Workflow responsibility map
| Layer | Responsibility in this workflow | Owner/system | Check |
| --- | --- | --- | --- |
| Logic | | | |
| Data | | | |
| Intelligence, only if needed | | | |
| Orchestration | | | |
| Presentation | | | |
- Native feature already sufficient:
- Repeated handoff worth automating:
- Exception requiring a person: