What a Saraiya yard runs on BilledUp actually looks like

6:40 am, the gate of the Saraiya yard.

The gate man works through attendance before the first mixer shows up. Twenty-two names, one phone. Ram Bahadur signs in from the Ring Road side. The painting crew comes in from Bhaktapur as a group of six and counts as six, because asking six men to sign six times at seven in the morning is how registers go missing. And the bar-bender who went home to Dhading for the wedding season is marked absent, with the reason attached, so nobody spends the afternoon reconstructing why his line is empty.

Two years ago this took a register, a pencil, and a supervisor who sometimes left the register in the site office. It takes about ninety seconds now, and the numbers reach three places before the chiya goes cold: the owner's phone, the PM's list, and the parts of the client portal that concern the client.

That is the whole trick. The yard is not smarter than it was. The numbers just stay true longer.

One wage card for twelve sites

We run twelve active sites out of this yard. Twelve sets of names, and the sets overlap, because the same electrician works Kalimati on Monday and Baneshwor on Wednesday and neither site knows about the other's hours.

So there is one wage card, not twelve. A man is one person in the system with one daily rate, one baki balance, and one running total for the month, no matter how many sites he touched. On Saturday the yard prints one payout list. The old way was five site registers and an Excel file that Anisha updated at home on Friday night, and every few weeks the Excel said one thing while a register said another, and you settled it by memory at a chaupasi stall.

A yard doesn't run on effort. It runs on whether yesterday's numbers are still true this morning.

Advances get the same treatment. Dashain is coming, which means advance season, which means in the old days every thulo thekedar in the yard was owed something and nobody agreed on how much. Now an advance is a line against a name, entered the morning it was given, and the Saturday list deducts it automatically. The argument moved from the payout table to the phone, where it takes ten seconds instead of one religious disagreement.

What the supervisor's phone actually holds

I want to be honest about this part, because every software pitch says "from a phone in the dust" and the reality decides whether supervisors use it or quietly go back to paper.

The daily log is four fields and photos. Crew count, work done, material in, material out. Concrete poured at Kalimati: 38 m³, pour started 7:20, finished by 2. Two bags of cement issued to the mason line. The mixer diesel slip photographed because paper slips evaporate. That's it. No supervisor has ever asked me for more fields. They ask for fewer, and we say no, because those four are the ones the office actually needs.

The photos are the quiet win. The slab at 11 am, the curing at 5 pm, the shuttering propped the way the engineer wanted it. When a client asks, three weeks later, why the slab took two days, nobody writes a paragraph from memory. They send the picture.

The evening update nobody has to remember

Here is the part clients mention back to us.

At around 6 pm the day's logs close and the portal moves on its own. The milestone percentage at Baneshwor ticks from 60 to 65 because the supervisor filed a pour. Two photos land on the client's timeline. The payment they made through eSewa last Thursday shows as received against Milestone 3, because the office logged it that afternoon and the portal doesn't wait for anybody's evening call round.

Before, the owner spent an hour every evening composing update messages, or more honestly, not composing them, and clients phoned anyway. Kati bhayo? Aaja samma k Bhayo? The calls didn't stop because we promised better communication. They stopped because the client could see it, and what a person can see he does not ring to ask about.

We still get calls. Somebody's uncle saw the photos and wants to know who supplied the aggregate. That call I'll take.

The parts that still run on talk

I said the numbers stay true longer. I'll say what they don't do, because the honest version of this story has edges.

The logs don't choose the mason. When the Kalimati pour slipped a day because the shuttering crew got pulled to Baneshwor, that decision was made on two phone calls at 8 pm, the way such decisions have always been made, and the log recorded it the next morning as history rather than caused it as strategy. Software is good at remembering what a yard did. It is not yet good at deciding what a yard does next, and I don't miss the version of this essay that pretended otherwise.

Vendors are another edge. The aggregate supplier at Dakshinkali runs on trust and a khata of his own, and he doesn't appear anywhere in our system until his truck is counted in a material-in line. Fine. The line is dated, photographed, and matched against his bill on Sunday, which is more than the torn pad of delivery slips ever gave us.

And the gate man still knows things the phone doesn't. Which worker's mother is unwell. Which crew pair shouldn't be split. We didn't digitize the yard. We digitized the ledger, the register, and the photo roll, and left the judgment where it lives.

What we stopped doing

Sunday reconcile, gone. The Friday night Excel session, gone. The register in the site office that was "at the site office" the way your pen is always in your other pocket, gone.

What replaced all of it is boring, which is the compliment. Attendance at the gate, four fields at dusk, one wage card, one ledger, and a portal that tells the truth to the client without a human couriering the truth over.

The yard is the same yard. The dust is the same dust. But Sunday is ours again, and in this trade that is not a small thing.