← muthari.com

The hidden cost of status chasing

Muthari guides · for contractors who fabricate what they install

Status chasing is every call, message and scroll whose only purpose is to find out where something is — the drawing, the glass, the truck, the payment. It costs a contractor in three ways. The engineer who knows becomes a search engine and stops engineering. Decisions get made on a status that was typed days ago and negotiated since. And the truth lives in a few heads, so it leaves the building every evening and leaves the company when those people resign. The cause is structural, not personal: Excel, WhatsApp, email and the ERP are each good tools, and none of them holds one live state of the project. The fix is not a better tracker. It is making the work itself write the record.

Reported status versus derived status

Reported status is a number a person typed. The tracker cell says 85% — 85% of what, counted how, and by whom? Every layer between the site and the owner rounds up a little, because nobody wants to be the one carrying bad news, so a red project arrives at the top as an amber report. Reported status is not a lie; it is an opinion with a date on it.

Derived status is computed from records that already exist for other reasons: the goods receipt, the stage stamp, the installation entry, the inspection verdict. Nobody can polish it, because there is nothing to type. If the receipt says 300 of 500 arrived, the order is 60% received, and the number cannot be argued with — only the receipt can.

The one-question test

For any number on any report, ask: who typed that? If the answer is a person, you are looking at reported status. If the answer is a receipt, a stamp or an inspection, you are looking at derived status. Run every management number through this test once and you will find out how much of your reporting is opinion.

The human search engine

Every contracting company has one: the engineer or coordinator who knows where everything is. Everyone calls him — the owner, the site, the store, the client. He is the most useful person in the building and the most interrupted. Two things follow. First, a large share of his day is spent answering "where is it?" instead of doing the work he was hired for. Second, the company's real system of record is his memory, which means the company forgets the moment he is on leave, sick, or gone.

The tell is easy to spot: when the client asks for a status, somebody makes three calls and then builds a report. The report is the output of a search, not a reading of a record.

Why WhatsApp groups lose truth

WhatsApp is the best tool on most projects, and that is the problem. It is instant, it crosses company lines — supplier, consultant and client in one group — and it carries photos without effort. So the project's truth ends up in a chat. But a group is a conversation, not a record, and it fails in three specific ways:

The practice: make the record the status

How Muthari OS handles this. There is no field to type a progress percentage into. Project and zone status are computed from the records: a goods receipt updates the stock, the purchase-order balance and the QC queue by itself; a production stage stamp carries actor, role and time; installation entries are additive and cannot exceed the zone quantity; inspections carry a verdict, photos and the raiser's name. Each zone shows its current stage and how long it has sat there, with amber and red ages. A per-zone material view walks take-off → request → order → received → QC → allocated → issued, and prints unknown where the trail breaks rather than guessing. The Command Center lists every project worst-first with the age of each stall, so the owner reads the record before anyone calls. Built by contractors in the trade, for the mornings described above.

Book a free demo  See the whole system →