BE Teck — the technology arm of BE
Notes
Working notes from BE Teck: the gaps we keep finding in ordinary daily work, how a gap becomes something built, and what we have built so far.
The site and the head office are looking at different numbers
The site records what physically happened and the office records what was ordered and paid. They diverge for structural reasons, not because anyone is lying.
Reported progress and real progress
The percentage in a weekly report is a judgement made by the person who will be blamed if it is low. Quantities and binary milestones survive that pressure.
Why a lorry surprises the gate
The office knows a load is coming and the man at the barrier does not. What the gate needs before a vehicle arrives, and what goes wrong when it has nothing.
A snag list that actually closes
Most snag lists never close because a snag has no identity, no owner and no closure test. What a list needs if it is to shrink instead of being reissued.
What belongs in a handover file
The handover file is assembled at the end, which is why it is always incomplete. What belongs in it, why each item is needed later, and the habit that fixes it.
The paper trail a query demands
Years later somebody asks you to substantiate a decision. What survives is a dated record, a named author, an unedited document and proof it was sent.
One project, many contractors, and the gaps between them
A project split across trades loses most of its time in the handovers between them, not inside any one of them. Where the boundary fails, and what fixes it.
One builder, many companies, one set of records
A developer runs several legal entities for sound reasons. The cost is operational, and it lands on staff time, shared material and money between accounts.
Cost heads that survive a project
A cost structure is designed for the budget and filled by the invoices. Why heads at the wrong grain fail, and what makes a coding structure last three years.
Two payment ladders that never line up
Buyers pay on certified stages, contractors on measured quantity, and the space between the two schedules is what a developer's working capital actually is.
Leads that die in an Excel sheet
Every project starts with a sales sheet, and it fails for mechanical reasons — no history, no two people at once, and a date in a cell that never rings.
Working with brokers without a fight at payout
The dispute with a channel partner is almost never about the rate. It is about who brought the buyer, and about when the money is due to be paid.
What a lead record should actually hold
Field by field, what belongs on an enquiry record in a primary sales office, what does not, and the one test that settles every argument about a new field.
Who owns the lead
An enquiry with no named owner is not a lead. The assignment rules have to be written before the first dispute, because moving a lead moves money.
One buyer, three enquiries, three salespeople
The same person arrives through a portal, a hoarding number and a broker. Exact matching will not catch it, and a merge is an ownership decision.
The site visit is the whole funnel
Almost nothing sells without a visit, so every stage before it exists to produce one and every stage after depends on what was recorded during it.
Follow-up is a schedule, not a feeling
A follow-up that lives in somebody's memory is not a follow-up. Every conversation ends with a dated next action, or the lead closes with a reason.
From booking to agreement: the document ladder
The paper between a verbal yes and a registered agreement, rung by rung, and the places a booking file quietly goes missing while everyone assumes it is fine.
Demand letters, reminders, and the buyer who says nobody told him
A construction-linked demand is a document plus a delivery. Most collection disputes are about the second half, and the reconciliation is worse than both.
A CRM and a task system are not the same thing
One is organised around a person outside the company, the other around work inside it. A builder needs both, and they should meet only at the crossing events.
After the booking comes the longer job
The years between booking and possession are where a builder's reputation is actually made, and most sales offices are neither staffed nor organised for them.
How to choose construction software without regretting it
Most of these purchases fail in the evaluation, not in the product. Follow three real transactions end to end, then watch for the parallel register.
The demo is not the product
A demo is a rehearsed path through clean data. Bring your ugliest challan, ask for the keyboard, and insist on a dated written list of what was promised.
A pilot that tells you something
Most trials are run by the enthusiast, on the best site, with the vendor typing. Design one whose outcome is informative rather than political.
What a price list does not tell you
The licence is the visible part. Migration, training, per-user pricing and the cost of leaving are larger, arrive later, and are rarely quoted at all.
Getting your data back out
Every system ends. A report is not an export and an export is not a backup, and the difference decides what you are holding on the day you leave.
Ask to see the audit trail before you sign
Every vendor says the history is kept. The way to find out is to make a record, change it, cancel it, and ask to see that one record's history on screen.
How to test a "works offline" claim in ten minutes
Every vendor says the app works offline, and the word means four different things. A cheap phone in flight mode settles it faster than any meeting.
Software your staff can actually read
The storekeeper, the guard and the munshi have to use it too. What Hindi support usually turns out to mean, and how to find out before you buy.
Approval chains worth asking about
Every vendor can draw a workflow diagram. The questions that separate a real approval system from a picture are about the cases nobody draws.
One WhatsApp number, or one per person
Behind every WhatsApp integration is one decision nobody raises in the meeting: does the message come from the company, or from a person who knows them.
Getting paid on time, from the contractor's side
A correct bill can still sit unpaid for weeks. There are only four places it stops, and knowing which one you are in changes what you should ask.
The challan that protects the supplier
A delivery challan is usually described from the receiving side. Written from the supplier's side it is evidence, and six months later it settles the argument.
What a work order should say
Read it before you sign it. The clauses that decide whether a job is profitable are rarely the ones anyone reads, and three lines are usually missing.
Signing a document from a phone
Three different things are called a signature on a phone, and they prove very different amounts. What to check before your thumb touches the screen.
Keep your own copy
At final account the argument is settled by whoever can produce a dated document the other side cannot contradict. Usually that is the larger party.
What a site engineer should record, and what they should not
The site engineer witnesses most of what happens on a project. Here is what of that must survive in writing, and what should never enter the record.
Month-end at a builder's accounts desk
The last four days of a month at a developer's accounts department, what must be true before the books close, and why it is always a scramble.
Quoting a rate you can live with
What actually sits inside a construction rate, the two costs contractors forget, and the conditions that decide whether a quoted rate survives the job.
When your ledger and theirs disagree
Balance confirmations never agree the first time. Reconcile events rather than totals, classify every difference by cause, and the argument becomes arithmetic.
The complaint names the wrong thing
One link was reported broken twice in a single day. Nothing was ever wrong with that link. Two unrelated faults were eating clicks and looked identical.
Paying a labour contractor
Attendance, measured work, advances and recoveries. How labour contract payments actually run on an Indian site, and where both sides end up cheated.
Capitals are a contrast, not a volume
One line of styling put a whole application into capital letters. It read as deliberate for about a week, and after that it just read as shouting.
Written, and never wired
The code to undo a wrong stock entry already existed and had no callers. Nobody had asked for the button, because a workaround was already doing the job.
Filed as chatter
A document was waiting on one person's signature, and the request reached them as a line in a digest. Not a training gap. A row in a routing table.
A fact that had no owner
A payment made in instalments was invisible to half an application, because one plain fact was being worked out separately by every screen that needed it.
How we find our own problems
Nothing here starts with a market report — it starts with hitting the same wall for the tenth time. Notice, build, keep alive, and why stage three decides it.
The five instruments of Kshetron
Terrex, Classic, Kaagaz, Tempo and BEAi — what each instrument of Kshetron is for, and why land in India needed them assembled into one readable surface.
What a delivery challan is, and what it proves
A delivery challan travels with the goods and says what left the seller's gate. It is not a bill, and on its own it is not proof that anything arrived.
What a goods receipt note is, and why it is not the challan
The GRN is your own record of what arrived, written by your side. Confuse it with the vendor's challan and you have no independent check on anything.
Three-way matching, and the case it always misses
Order, receipt, invoice. Hold the three against each other before you pay. The method is simple; the failures are all in the cases nobody enumerated.
How to read a bill of quantities
A BOQ is a priced list of the work, written so that two people can compete on the same job. Reading one well is mostly knowing what it deliberately leaves out.
Concrete grades: what M25 actually means
The number in M25 is a characteristic strength in newtons per square millimetre at 28 days. Not an average, not a mix ratio, and not a promise about today.
The concrete cube test, and the four weeks you wait
Cubes are cast on site, cured, crushed and recorded. Most of what goes wrong with the test happens in the first ten minutes, long before the crushing.
The slump test, and why water is the real argument
Slump measures how far fresh concrete settles when its mould is lifted. It takes two minutes, and it is the only check between you and a weaker structure.
Why measured and docketed quantities disagree
The number on the docket and the number your side measures are rarely identical. Most of the gap is ordinary physics and method. Some of it is not.
Running a site store so the numbers survive
A site store is a warehouse run in mud by one person under pressure. Four disciplines keep its numbers usable; everything else is a matter of preference.
Wastage on site: allowance, loss and arithmetic
Wastage is the difference between what you bought and what ended up in the structure. Most of it is not waste. Almost none of it is measured properly.
The bar bending schedule, and steel by weight
A BBS turns drawings into a cutting list and a weight. The arithmetic is simple and the errors are systematic, which is what makes them worth understanding.
The unit of measure is where the money leaks
A rate agreed per tonne and invoiced per quintal is a factor of ten, and it looks like an ordinary line. Units are the quietest expensive error in purchasing.
Physical stock against book stock
Stock reconciliation is a comparison between what your records claim and what is actually on the ground. The variance is not the finding. The pattern is.
Retention money is a balance, not a memory
Retention is money you have earned, been billed for, and not been paid. It is held against defects and released later, and most people track it in their heads.
Running account bills, and what "running" means
An RA bill is cumulative. Each one restates the whole job to date and subtracts what was already certified, which is why the arithmetic confuses everyone.
A mobilisation advance is not an advance payment
One is a loan against future work, recovered from every bill. The other is a payment made early. Booking them the same way is how advances get paid twice.
Set-off, and what it costs you to use it
Netting what you owe against what you are owed is quick and tempting. It also collapses two records into one and removes the evidence for both.
Why staged payments break accounting systems
Most systems store one paid date per bill. A payment in stages never writes it, so every screen asking "is this paid?" goes blind on exactly the biggest orders.
Reconciling a vendor bill against what actually arrived
A vendor's invoice is a claim, not a fact. Checking it is a five-step comparison, and four of the five steps fail for reasons that are not the vendor's fault.
TDS on construction payments, explained as a mechanism
Tax deducted at source moves a slice of a payment from the payer to the government on the payee's behalf. Understanding the mechanism prevents most of the errors.
Input tax credit, and why your vendor's filing is your problem
GST credit lets you offset tax paid on purchases against tax you collect. The conditions attached to it are what make vendor discipline a finance function.
Paying less than agreed is a statement, not a typo
A short payment carries a decision inside it. If the system accepts the smaller number silently, the decision is lost and only the discrepancy survives.
Work order or purchase order: which one you are issuing
One buys a thing, the other buys an outcome. The paperwork looks similar and the risk, measurement and payment mechanics are completely different.
Why one person should never move the company's money
Two different people on every payment is not distrust. It is the cheapest control there is, and every convenience that erodes it erodes the whole thing.
Money before material, and how to sign for it honestly
Paying before delivery is normal in construction. What is not normal is a system that hides which payments are advances and which are for goods already in.
Matching a bank line to the thing it paid for
A bank statement gives a date, an amount and a scrap of text. Turning that into "this paid that invoice" is a guess, and the rules around the guess matter.
Writing off money that is never coming
A write-off is a decision, not a correction. The amount matters less than the reason, and the reason is the first thing most systems throw away.
Why tasks stall between people
Work rarely stops because somebody refused. It stops in the handover, where one person has finished and the next has not been told they are now waiting on.
What makes a handover fail
A handover fails when knowledge that lived in one person's head was never written down, and nobody discovers which knowledge that was until it is needed.
A gate register somebody will actually keep
The gate is the only place every lorry passes. Most gate registers fail for design reasons, not discipline ones — they were built for a desk, not a barrier.
WhatsApp is the interface, whether you designed for it or not
On Indian construction sites the real reporting system is a group chat. Fighting that costs years; reading it properly takes a few weeks and works immediately.
Attendance on a site with no signal
An attendance system that needs a network will be wrong on exactly the days it matters. Queueing punches is easy; the rules that keep the data honest are not.
The daily progress report nobody reads
Most DPRs are written by somebody who gains nothing from writing them, for somebody who does not read them. There is a version that survives that fact.
A site photograph is a record, if anything reads it
Thousands of site photographs are taken every month and almost none become records. The bottleneck is not capture. It is that nothing ever looks at them.
Escalation without shame
Most escalation systems require somebody to name a colleague. That is why they go unused, and why problems reach management only after they are unfixable.
Work slips before it is late
By the time a task is overdue, the decision that made it late was taken weeks earlier. The signals were all present and none of them were being counted.
The voice note is the report
A site engineer sends a voice note because his hands are dusty and the screen is in the sun. For years ours were stored as blobs that nobody ever opened.
Who is allowed to decide what
Most permission systems answer "what may this person see". The harder question is what they may decide, and organisations usually cannot state their own answer.
What an audit trail is actually for
Not catching thieves. An audit trail exists so that a decision made a year ago can be reconstructed, including by the person who made it and now has to defend it.
Append-only: why a correction should never overwrite
A record that can be edited answers only today's question. Adding a correcting entry instead costs one row and keeps the history that makes the number defensible.
Tamper-evident, not tamper-proof
You cannot stop somebody altering a copy of a document. You can make any alteration detectable, and that is a much more useful property than it sounds.
The machine proposes, a person decides
An automatic link that turns out wrong is not just an error. It is an error that looks like a record, and nobody reading it later can tell nothing was agreed.
The app should tell you why
A refusal with no reason, an empty screen with no cause, a score with no basis. Each teaches that the software is arbitrary, and arbitrary things get routed around.
A default is a decision somebody made once
Defaults are set in the abstract, by somebody not thinking about your case, and then apply for years without ever looking like a choice again.
Offline-first is a data decision, not a network one
Queueing requests is the easy part. Offline changes what a record means, because it was created by a device nobody was watching, at a time nobody can verify.
Name it what the site already calls it
Our software recognised a delivery photo only if the caption said one of four words. Against four hundred real captions, those four words matched exactly two.
An alert that rings for everything is an alert nobody hears
Priority is the wrong axis, because everybody's work is important. Sort by what the message asks the reader to do, and there are only three answers.
One outage should be one ticket
Systems that raise an alert per symptom flood at exactly the moment attention is scarcest, and the flood is usually one cause wearing many names.
An import you cannot reverse is an import you should not run
Bringing history into a live system is a one-way door unless you build the way back first. Two properties make it safe, and both are cheap before the write.
A test that describes the code will defend a bug
A regression test anchored on how the code works, rather than on the rule it is meant to enforce, will guard a defect as loyally as a feature — and report green.
The gap you stopped noticing
Most broken things at work are not unsolved — they are worked around so smoothly nobody calls them broken. Breaking that habit is why BE Teck exists.