Trigger
The named event or schedule that starts the loop.
Oliver Hitchings · Automation systems
Automation, opened up.
Small systems for repeat work—mapped, built, reviewed and handed over so your team can inspect every moving part.
- TRG.01
Trigger
The named event or schedule that starts the loop.
- SRC.02
Inputs
The source material and evidence the system is allowed to use.
- RUL.03
Rules
Explicit decisions and boundaries applied before model interpretation.
- HUM.04
Human review
A person checks uncertain or consequential work before it continues.
- STP.05
Failure path
Retries, stop conditions and escalation are named before a bad run.
- RUN.06
Action
Only the approved next step runs against the intended system.
- LOG.07
Evidence
The result, failure or review decision is recorded for inspection.
- OWN.08
Handover
Prompts, logs, run instructions and change notes stay with the owner.
System anatomy
Every moving part stays visible.
Inputs
The source material and evidence the system is allowed to use.
Rules
Explicit decisions and boundaries applied before model interpretation.
Human review
A person checks uncertain or consequential work before it continues.
Failure path
Retries, stop conditions and escalation are named before a bad run.
Action
Only the approved next step runs against the intended system.
Evidence
The result, failure or review decision is recorded for inspection.
Handover
Prompts, logs, run instructions and change notes stay with the owner.
Example pattern — not a client case study
Inbox triage
Classify, route and prepare for review; final sending stays with a person.
- Trigger
- A message enters the inbox.
- Inputs
- Message content and explicit routing rules.
- Review
- A person checks the proposed route and any prepared response.
- Output
- A classified message prepared for the approved next step.
Example pattern — not a client case study
Research monitoring
Monitor named sources, remove duplicates and prepare a review queue.
- Trigger
- A scheduled source check begins.
- Inputs
- Named sources and previously seen items.
- Review
- A person reviews the deduplicated queue.
- Output
- A review queue with duplicate items removed.
Example pattern — not a client case study
Recurring reporting
Collect scheduled inputs, flag gaps and prepare a consistent report with a source trail.
- Trigger
- The reporting schedule starts the run.
- Inputs
- Named scheduled inputs and their source references.
- Review
- A person checks gaps, source trail and report before use.
- Output
- A consistent draft report with gaps flagged and sources retained.
Operating principles
A system should make sense on a bad day.
Inspectability
Visible prompts, rules, assumptions and logs.
STP.05 → HUM.04 → LOG.07
Failure path → human review → evidence
Retries, stop conditions and escalation lead to a named review and a visible record.
Handover
Material needed to operate, review and change the system.
Commercial hand-off
Choose the smallest useful first step.
Task Map
EnquireFirst Build
EnquireOperator System
EnquireOngoing support
EnquireGuide prices. VAT, third-party software, model usage and hosting are separate where they apply.