A work inspection request (WIR) is the formal request a contractor raises to the consultant or client’s engineer to inspect a defined piece of completed work — an elevation, a level, a zone — before it is accepted and before the next activity covers it. It carries a reference, the location and scope, the date raised, and the inspector’s verdict, commonly coded A (approved), B (approved with comments), C (revise and resubmit) or D (rejected). A material inspection request (MIR) is different: it asks for inspection of material delivered to site before it is used. The order matters. Material is inspected (MIR), then installed, then the installed work is inspected (WIR). A WIR raised before its MIR is approved, or before installation is complete, asks for inspection of work that cannot yet be accepted.
For contractors who fabricate what they install, the WIR is where the factory’s work meets the consultant’s signature, so Muthari OS treats the sequence as a gate rather than a reminder.
A WIR cannot be raised on a zone until its material inspection is approved and installation is recorded complete. The system refuses, and says why. Installation itself is recorded as additive daily entries that can never exceed the zone quantity, so “complete” means the quantity, not a tick.
The verdict is recorded as A, B, C or D and drives the zone’s state: C sends it round the resubmit loop, D rejects it and opens a typed rework round. The record carries who raised it, the consultant’s comments, and photos stamped with name and time and tied to that zone and that request.
The handover stamp on a zone requires the MIR approved and the WIR approved; it cannot be forced past either. Once handed over, the zone record locks. Repeat inspections are stamped as repeats and the rounds are counted, so the history of a difficult zone is visible, not tidied away.