Capability and Direction Written for diligence, not for enquiry.

Procurement teams at large accounts, prospective partners and investors ask a different set of questions from a shop owner with a package to draw.

They want to know what is actually delivered as against what is aspirational. They want the method rather than the promise. And they want to see where the boundaries are, because a supplier who cannot state their own limits has usually not thought about them.

Everything in this section is written to that standard. Where something is committed, it says so. Where something is direction, it says that instead.

Engineering documentation since 2003, across a firm of 150+ professionals.

The millwork practice covers nine service lines, from the first approval submittal through to the data that drives a machining centre. Those lines are set out in full, with their tier, in the service register.

The register distinguishes three states: what is marketed and delivered today, what is listed and quoted on enquiry, and what appears on the capability map as direction. That distinction is the most useful thing in this section for anyone assessing scope.

The delivery model sets out how work is composed, checked and issued.

Two things hold across every engagement. Every deliverable is checked by someone other than the person who produced it, then reviewed by a named senior reviewer before it reaches the client. And every quote carries a committed calendar date.

The quality methodology covers what is checked and how, and what is measured.

The Track B roadmap sets out the direction the practice is developing in, and the conditions attached to each step.

Separately, horizon practices records adjacent areas that appear on the capability map as direction. Those are not offered, and the page says so plainly rather than leaving them to be inferred as capability.