Most contractors know their bank balance. Very few know their per-project profit. That gap is where money quietly disappears: one profitable site subsidises a losing one, and you only find out at year-end — if ever.
Say you run three work packages: a substation civil job, a tunnel cabling package and a small building contract. Your bank shows money coming in and going out, and overall you're "doing fine." But if the cabling package is losing ₹80,000 a month while the civil job earns ₹1,50,000, your "fine" business is really one good project carrying a bad one. Without project-wise books, you'll keep quoting the losing type of work at the same rates.
Advances to labour: an advance is money out of the project the day you pay it. When you later deduct it from salary, don't count the deduction as income — it's a ledger adjustment, not cash in. (Most spreadsheets get this wrong and inflate project income.)
Shared costs: a vehicle serving two sites can be split by usage, or simply assigned to the site that uses it most — consistency matters more than precision.
Client retention/withheld amounts: on cash basis they simply haven't arrived yet; track them separately as receivables so a "losing" project that's owed ₹5 lakh isn't misjudged.
The reason contractors abandon project accounting is data entry. The fix is capturing payments automatically — from bank SMS and UPI notifications — and only adding the project tag in a two-minute evening review. That turns project P&L from a bookkeeping job into a habit.