A specialist contractor is a contractor who fabricates what they install — façade and curtain wall, aluminium, glass and glazing, steel fabrication, joinery and millwork, and fit-out companies that manufacture their own elements. The defining fact is not the trade. It is that the same company owns a factory and a site, is measured commercially on installed quantity, and incurs most of its cost weeks earlier, in a workshop, against a drawing that may still change.
That single structural fact is why generic construction project management software tends to fit badly. Those tools were designed for the company coordinating the project, not for the company manufacturing part of it.
A coordinating contractor can reasonably describe a package as 60% complete. A specialist contractor cannot use that number for anything: 60% fabricated and 0% delivered is a cash problem, 60% delivered and 0% installed is a storage problem, and 60% installed but uninspected is a claim problem. The same percentage describes three different situations with different consequences, so progress has to be held per stage and per zone, not as a figure.
In a coordinating model, material is something a subcontractor is responsible for and it appears as a cost. For a fabricator, material is a physical object with an identity: a batch, a heat number, a supplier, a quality decision, a location, and a destination zone. It can be received partially, rejected, quarantined, returned, borrowed against another project and issued in pieces — and each of those is a state the commercial record eventually depends on.
Generic tools treat a drawing as a document to store. For a fabricator it is a control: work built to a superseded revision is scrap. The revision has to travel with the work all the way to the factory floor, and the system has to be able to say which revision a given zone was actually built to, months later, when somebody disputes it.
The operational spine of a specialist contractor runs Engineering → Procurement → Store → Production → Logistics → Site → Quality → Commercial. What makes it a spine rather than a list is that a fact created at one end is the evidence relied on at the other. The category page explains each stage in detail; what matters here is the dependencies that a general tool does not model.
Approval is not a status field. It is the condition that allows a take-off to be issued and a zone to enter fabrication, and its withdrawal has to be able to stop the floor.
The useful question is not "how much aluminium did we buy?" It is "which delivery did the profile in this elevation come from, was it inspected, and who issued it?" Answering that requires the receipt, the batch, the issue and the zone to be the same chain of records rather than four systems. The seven hops are set out here.
Zones move through named stages with a quality decision at the end. A stage stamp is a fact with a person and a time attached; a percentage is an estimate.
What left the factory and what the site accepted are different sets often enough that the difference has to be recorded, not assumed.
A zone contains a known quantity. Installed quantity recorded against it is bounded by that, which is what makes cumulative progress arithmetic rather than opinion — and what surfaces a variation when the work exceeds the contract quantity, before it is installed for free.
At goods receipt, at the end of the production line, and at inspection on site. Treating quality as a final gate misses the two places where a defect is still cheap.
A progress claim that derives previous quantities from the last invoice cannot double-claim. One that retypes them can, and eventually does.
The unit that makes this tractable is the zone: a named, quantified piece of the contract that can be fabricated, delivered, installed and claimed as a unit. On a façade package a zone is usually an elevation or a level; in joinery it is a room; in fit-out it is an area. Breaking the bill of quantities into zones is what allows a single record to carry a piece of work through all eight stages, and it is why status can be computed rather than reported. How to break a BOQ into zones.
Without a zone, progress can only be expressed against the whole contract line, which is precisely the level of resolution at which a percentage becomes meaningless.
Muthari OS is built around this model rather than adapted to it. It is a project operating system for specialist contractors that connects engineering, procurement, store, factory production, logistics, site execution, quality and commercial management, from project award to site handover. Zones are first-class; drawing revisions gate production; goods receipts write stock and call quality; production stages record the revision they were built to; delivery notes carry a QR code per zone; installation is capped at the zone quantity; and claims derive their previous quantities from the last invoice.
It is not a better version of general construction software. It is a different shape, because the company it is for is a different shape. Where general platforms fit, and where they do not.
The chain is the same in every trade; what changes is what a zone is and where the risk concentrates. Façade & curtain wall · Aluminium fabrication · Glass & glazing · Steel fabrication · Joinery & millwork · Fit-out
What is construction project management software? · What is construction operations software? · Specialist vs general contractors · The nine modules · When Rev 04 arrives and the factory is cutting Rev 03 · Glossary