Business Process, Documentation and Resourcing
Documentation written from your configured system, gap analysis that costs every deviation, and consultants who work inside your team. The acceptance test for everything here is whether someone else could pick the work up unaided.
Documentation from the system, not the whiteboard
We do interview people, but we reconcile what they say against what the system shows. The gap between the two is usually the most valuable finding in the engagement, and it is the thing that never appears in a workshop output.
Gap analysis as arithmetic
Every gap is costed three ways: build it, configure around it, or change the process. The upgrade and support cost of each customisation is stated, so the build-versus-change decision stops being a matter of opinion. You are still free to buy the customisation; you will be buying it knowingly, with a decision log an auditor can read in three years.
People inside your team
Named consultants work within your processes, priorities and tooling. Allocation is stated in days per month and reviewed monthly, and any replacement includes a handover overlap at our cost.
Get the readiness checklist for this work
Twelve questions we ask before quoting. Answer them yourself and you will know whether you are ready to buy.
Key points
- Documentation is written from the configured system, not from memory.
- An SOP passes when someone new completes the task unaided.
- Every gap is costed three ways before a recommendation.
- Conflicting numbers are a definitions problem, not a tooling problem.
- Embedded consultants work under your delivery direction.
Common situations, and the service that fits
The questions that determine scope
| Question | If the answer is yes | If the answer is no |
|---|---|---|
| Do interviews and the system agree about the process? | Documentation is straightforward | The divergence is your finding |
| Could someone new follow your procedures unaided? | Your SOPs work | They have not been tested properly |
| Is every gap on your list costed three ways? | You can decide | You have opinions, not arithmetic |
| Does one person own each reported number? | Dashboards can be built | Start with a metric dictionary |
| Do you hold delivery direction? | Resource deployment | A fixed-scope project fits better |
Common questions
How long does process documentation take?
Four to fourteen weeks depending on scope and how much of the system we can read directly. We scope by process count and depth level, and we tell you which processes are not worth documenting.
Can documentation be reused for audit and for training?
Yes, and it should be. The same captured process feeds the process map, the SOP and the training material, which is why we produce editable source you own rather than a PDF.
Do embedded consultants report to us or to OMAV?
To you, for day-to-day work. OMAV holds their development, quality and escalation, so they have colleagues to ask when something is outside their depth.
Marked up as FAQPage structured data, matching the visible text exactly.
Tell us what you are trying to fix.
A short conversation about the objective, the constraints and the timing. If we are not the right fit, we will say so.