← muthari.com

Fast programmes need a record that keeps up

Muthari OS · the Project Operating System for Specialist Contractors

A twelve-week fit-out does not leave time to reconstruct what happened at handover. Muthari OS is one system where a fit-out contractor’s package runs on site and in the commercial office: zones labelled the way the job is — rooms, floors, areas — with installation recorded daily against each zone’s quantity, material and work inspections (MIR, WIR) with verdicts and photos stamped with name and time, site rejections as rework rounds with cause and cost, and a handover that cannot be stamped until the inspections are approved. Above it sit the submittal register the consultant answers to, an approved budget that gates claims, variations caught when zones exceed the BOQ, and progress claims that carry their own evidence. Built for contractors who fabricate what they install — and for fit-out companies that work like them — by contractors in the trade.

The site record, written the day it happens

Installation is recorded daily per zone; corrections are new entries, never edits, and the cumulative can never exceed the zone’s quantity. Every entry carries who, when and photos. Material inspections and work inspections are raised with their verdicts, and a rejection rolls the zone back through typed stages with the reason on record.

Handover documentation that already exists

Because the inspections, photos and rejections were recorded as they happened, the handover record per zone is the work record itself — not a binder assembled in the last week. Handover locks only when MIR and WIR are approved, and the record cannot be quietly edited afterwards.

The register the consultant answers to

Material submittals, samples, method statements and drawings, with revisions, comments and response ages, so the finish still waiting on approval is visible to the whole team and the time it has waited is on the record.

Commercial that keeps pace with the programme

Budget against actual cost by category, with unrecorded never shown as zero. Zones that exceed the BOQ quantity trigger a variation before you fit them for free. Progress claims derive previous quantities from the last invoice — double-claiming is structurally impossible — and attach goods receipts and inspection records as evidence.

Managing a fit-out package, stage by stage

Fit-out is managed under time pressure across many small areas at once, and it is the trade most exposed to other people's sequence.

Programme, areas and dependency

The package is broken into rooms or areas rather than one line, because they progress independently and are handed over independently. Most fit-out delay is inherited: ceilings cannot close until services above them are inspected, and finishes cannot start until the space is clean and dry. What the record has to show is not only what the package did, but when the area became available — that is what turns a delay into a defensible claim rather than an argument.

Submittals and material approval

Finishes, fixtures and fittings each carry their own approval and their own lead time, and the long-lead items are usually decorative rather than structural. An approval that slips does not delay a drawing; it delays an order, which delays a room.

Procurement, receiving and storage

Many suppliers, many small deliveries, and a site with limited storage. Material is received against the order, inspected, and issued to a specific area — without that, material bought for one room quietly gets used in another and the shortage appears weeks later.

Site execution and daily records

Progress is recorded per area on the day it happens, with photographs stamped with name and time. On a short programme the daily record is the only version of events that survives; anything reconstructed at the end of the month is already an argument.

Inspection, snagging and handover

Material inspection before use, work inspection on completion, and then the part that consumes the most time: snagging. A fit-out snag list runs to hundreds of items across many rooms, each needing an owner, a closure and evidence. Handover documentation assembled from records that already exist — inspections, photographs, non-conformances and their closures — is the difference between handing over in days and handing over in weeks.

Commercial

Variations are constant in fit-out because the design keeps moving. Recording them against the area they affect, as they happen, is what keeps the final account close to the work actually done.

Honest limits: Fit-out is the thinnest fit of the trades Muthari serves. The factory and store modules are optional and will sit idle on a pure fit-out package without a workshop — the value is in site, commercial and documents, and we say so before a demo. There are no structured snag lists or inspection checklists; an inspection is a verdict with remarks and photos. Muthari is not an ERP (it runs beside yours) and not planning software (the programme stays in P6). It needs a connection on site, and the interface is English today.

Also built like you: joinery

Where the fit-out contractor runs its own workshop, the joinery package runs through the full chain — take-off, stock, workshop stages, QC, dispatch and room-by-room handover.

The same operational chain runs every specialist trade — a factory and a site against one contract. Why specialist contractors need a different model, and what construction operations software is. For the broader category, see construction project management software.

Book a free demo  See the whole system →