Operations for a construction contractor that also trades materials
Walk through a working copy with sample data for Northstone Infra, a made-up waterproofing and repair contractor: four sites, daily reports from the phone, running bills, stores, site cash and a trading desk. Click anything; changes reset every night.
SiteBook is one operations system for a contractor that executes work on site and trades construction chemicals: daily progress reports, attendance, BOQ and running bills, stores, site cash, a director dashboard and a trading desk. Every feature below runs in the live demo above with sample data.
Daily progress reports from the site
The site engineer files one report per site per day from a phone: quantity done against each BOQ line, labour by trade, material used from the site's own stock, weather, issues and up to six photos, shrunk on the phone before upload.
The project manager approves it or sends it back with a note. Only approved work counts toward the site's progress, so the progress bar on every site is something the office has checked.
Each site has its crew. The engineer marks present, half day or absent with one tap per person, or "rest present" for everyone else, and can pull a worker in from another site for the day.
The daily report's labour section fills itself from attendance by trade, and labour cost on the dashboard comes from the same marks.
A site's contract BOQ is copied from the client's accepted quotation or entered line by line. Once work is reported against a line, only its quantity can change, so past bills keep their meaning.
Measurements are recorded against the BOQ (or filled from approved work), and an RA bill takes everything not yet billed: previous, this bill and up-to-date quantities per line, CGST and SGST or IGST, amount in words, as a PDF. Bills move from draft to submitted, certified and paid, and paid goes into the cash book.
Material arrives from suppliers into the godown and is transferred to sites; each site holds its own stock, and material used is taken from it on the daily report. Nothing can be sent or used that is not there.
The daily stock report has the same columns as a stores register kept in Excel: opening, receipt, dispatch and closing per material, for one location or all of them, for a day or a date range, as CSV or print. Materials below their minimum at the godown are flagged.
Each site's in-charge holds a cash float. Spends are recorded from a phone with what they were for, a photo of the receipt and, for GST bills, the shop's GSTIN; anything entered three days late is flagged. A site cannot spend more cash than it holds.
Every Thursday the site submits the week's spends as one claim. Accounts approve it or send it back, approved claims go out in a bank upload file, and paying a claim tops the site's cash back up and lands in the finance book at the same moment.
Each worker's KYC is captured on a phone: Aadhaar (only the last four digits are kept), PAN, bank, UAN and photos of the documents. The same phone or Aadhaar can't be added twice, and a similar name asks whether it is the same person.
The monthly wage register works out days from attendance, PF and ESIC for workers on the company's rolls, 1% TDS for subcontractors past the 194C limits, advances, and totals per gang; each worker is paid once a month. Gate passes need complete KYC, record where the worker stays and print as an ID card.
Each owned machine has a printed QR label. Scanning it on a phone opens the machine: where it is now, and a one-tap move to another site or back to the godown.
Hours run come from the daily report, so the register shows how much each machine actually worked and how many of its days on site it sat idle. Machine days are costed into each site's margin.
The weekly report is put together from the approved daily reports: work done against the BOQ, labour, material, machinery, issues and photos. The PM picks which sections each client sees and downloads the PDF.
Material used is compared with the norm for each BOQ line, so over-consumption on a site shows up the same week, not at the end of the job.
Cost to date is material used on site, labour from attendance and wages, and site cash spent. Against the value of approved work it gives each site's margin so far; scaled to the whole contract, it projects where the site will finish against its estimate.
Sites are marked on track, over budget or losing money, next to a short list of what needs attention today: reports waiting for approval, sites low on cash, materials below minimum.
An inquiry becomes a quote where each product shows godown stock and the last purchase rate; a margin percentage sets the selling rate. The quotation PDF never shows cost or supplier.
The customer's PO is checked on six points, then the order is held until the advance is in or until it fits the customer's credit limit with nothing overdue. It is fulfilled from stock, through the godown, direct from the supplier or as an SEZ supply under LUT, invoiced with GST, and the e-way bill checklist shows what is still missing.
Trading invoices and RA bills carry HSN or SAC codes and the right GST split, and download as PDFs.
Customer receipts, supplier payments, advances and site cash all land in one cash book. Site engineers never see company finances or the dashboard; this is enforced on the server for every request, not just hidden on screen.
Ahrom Labs has built each of these connections for clients before. Two run in this demo; the rest are set up for each company with its own accounts.
WhatsAppSet up per company
The director gets each evening's approved daily reports as one message; customers get quotations, RA bills and payment reminders on WhatsApp; a site engineer can send photos straight into the day's report.
TelegramSet up per company
Each site has a group: the approved daily report, low site cash and stock below minimum are posted there, so the site and the office see the same thing.
TallyPrimeSet up per company
Invoices, RA bills, supplier receipts and site expenses go into Tally as vouchers with the site as the cost centre. Tally stays the statutory book; the app keeps project cost.
E-way bill (NIC)In this demo
The checklist in this demo shows what each dispatch still needs. Live, the e-way bill is generated from the company's own NIC registration, or handed to accounts to file in Tally.
GST returnsSet up per company
GSTR-1 figures come from the invoices and RA bills already in the system, with HSN and the CGST / SGST / IGST split as billed.
Google MapsSet up per company
Site locations and road distance from the godown, for transport costing and the e-way bill; attendance can record where it was marked.
GmailSet up per company
Quotations, RA bills and invoices emailed to the customer from the app, with the PDF attached.
Bank upload fileIn this demo
Approved site-cash claims go out as one bulk-payment file for the bank's portal, so accounts don't retype them.
Cloudflare storageIn this demo
Site photos, receipts and documents stored safely and shown inside the app.
Construction Contractor ERP: Live Demo | Ahrom Labs