People decide. Engineers build. Every change is tested.
Human Automated Engineering is a way of working, not a product. This page explains what it means for a project with HAE.
The method
People decide.
Every project starts with people: yours and ours. We agree what to build, why it matters, what good looks like, and what is out of scope. These decisions are written down. AI does not make them.
Engineers build.
Our engineers design and build the automation and software in small steps, each one aimed at a specific, agreed outcome.
Every change is tested.
Nothing reaches you unread. An engineer reviews every change for correctness, security and fit. Automated tests run on every change. If either check fails, the change does not go in.
The loop
Decide.
Agree the next small piece of work and what done looks like.
Build.
Engineers build it, in a small step.
Review.
An engineer reads every change.
Test.
Automated tests and checks run on every change.
Release.
The change reaches you, with a note on what changed and why.
Then the loop runs again, until the work is done.
The quality gates, in plain words
Each piece of work passes the same gates.
If it does not pass, it does not move on.
- Scope agreed in writing.
What we will deliver, what we will not, and the fixed price, before work starts.
- Every change reviewed.
An engineer reads every change before it is merged, whatever produced it.
- Tests on every change.
Automated tests run each time the code changes. A failing test blocks the change.
- Checks before release.
Accessibility, security and performance are checked before anything goes live.
- Your go-ahead for live systems.
Nothing changes in a system your business depends on without your agreement.
- Documented as we go.
Decisions, set-up and how to run it, written down while the work happens, not afterwards.
Security and data handling
Least access.
We ask for the minimum access needed, prefer read-only, and use separate accounts that you can switch off.
Your accounts, your assets.
Code, hosting, domains and services sit in accounts your business owns, from the start.
No secrets in the open.
Passwords and keys live in a password manager or a secrets store, never in chat, email or code.
Personal data kept to a minimum.
We work with test or masked data wherever we can, and personal data stays in your systems.
Clear agreements.
We sign a confidentiality agreement and a data processing agreement before any data is shared.
Access removed at the end.
When the work ends, our access is removed and we confirm it in writing.
UK GDPR by default.
Where a system handles personal data, data protection is part of the design, not a later addition.
What you receive each week
Every week during an engagement, you get:
- A short written update: what was done, what is next, what we need from you, and any risks.
- Something to see: a demo, a working link or a walkthrough of the week’s changes.
- The current plan, with anything that has changed marked.
- A list of open decisions, each with our recommendation.
You never have to ask how it is going.
Our principles
Say what we will do, write it down, then do it.
Small steps, reviewed and tested, beat big launches.
Build what can be maintained by someone who was not in the room.
Everything we make for you belongs to you.
If something is not working, say so early.
Plain language, in the code, the documents and the meetings.
See the method on your own problem.
Book a call, or start with the two-week Automation Audit. We reply within one working day.