Service 01
Flight operations consultancy that survives contact with the line.
Operational procedures, workflows and implementation support for organisations flying in regulated environments — written to be used at 06:00 on a bad day, not to sit in a binder.
What this is
The gap between the manual and the line.
Most operators do not have a procedures problem on paper. They have a gap between what the manual says and what actually happens when the schedule slips, the aircraft goes tech, and the crew is at the end of a duty day. That gap is where findings come from, and it is where this work is aimed.
Engagements start on the operational side rather than the documentary one: how dispatch and crews actually make decisions, where the workarounds are, and which of those workarounds are load-bearing. Procedures get rewritten around what the operation genuinely needs, then traced back to the regulation — not the other way around.
The output is procedures people follow because following them is easier than not, and an audit trail that shows why each one exists.
Scope
What the work covers.
Operational procedure design
Standard operating procedures written against the way the operation actually runs, not a template.
Operational control and dispatch
Decision authority, release processes and the handover points where responsibility changes hands.
Workflow and process improvement
Finding the steps that exist only because someone once had a bad day, and retiring them properly.
Digital workflows and automation
Replacing spreadsheet-and-email processes with tooling that keeps its own audit trail.
Operations manual architecture
Structuring Parts A to D so a crew member finds the answer in under a minute.
Interface management
The seams between operations, engineering, training and quality, where most findings originate.
Change implementation
Rolling a change out to the people who have to live with it, and adjusting when it does not survive.
Post-implementation review
Checking six weeks later whether the new process is being used or quietly bypassed.
Typical engagement
How the work runs.
Sized to the organisation. A four-week review and a six-month implementation follow the same shape.
Discovery
Scope, stakeholders and constraints established in the first conversation, not the third.
Deliverables
Procedures, workflows or manual sections, agreed in writing before any work starts.
Implementation
Put into practice with the people who will use it, and adjusted against how the operation actually runs.
Handover
Documentation and traceability, so nothing depends on us still being there.
Questions
What clients ask first.
Straight answers, including where the answer is that we are not the right people for it.
Usually the second. Most operators have procedures that were correct when written and have drifted since. Rewriting from scratch throws away institutional knowledge that is genuinely load-bearing, so the default is to audit what exists, keep what works, and rebuild only the parts that have stopped matching the operation.
As support, not as a replacement. Accountability stays with your nominated postholders throughout — an external consultant cannot hold a Part-ORO accountability, and any arrangement suggesting otherwise should worry you. The work produces material your postholders own and can defend.
Most of it, yes. Documentation, review and process design work remotely without loss. Discovery and implementation are better on site — you cannot see where a procedure breaks down by reading it. A typical engagement mixes both.
Small and mid-sized operations, where there is no in-house team to absorb this work and the alternative is a postholder doing it at weekends. Large carriers have their own departments and need something different.
Elsewhere on the site
Tell us what needs to happen.
Describe the operation, the standard you are working to, and the deadline. We reply within one working day.