Run a Contracting Site from WhatsApp: 8 Messages

A single contractor may be running three sites at once: crews clocking in and out, materials moving in and out, a subcontractor waiting for approval, and an owner waiting for a report. The usual method is familiar: the supervisor photographs the attendance sheet into a WhatsApp group, the storekeeper writes issued materials on a paper log, and the accountant pulls it together at month end into a late, disputed progress claim.

The problem is not WhatsApp. The problem is that a message stays a message: it never becomes an entry you can aggregate and compare later. Below is a practical way to run a site from your phone using eight daily messages, so the team keeps its habit while what it writes turns into an organised record.

Why site follow-up breaks down

• Too many groups: one group per project, one for procurement, one for management — and the same fact appears in all three, worded differently each time.
• Reliance on memory: "the supplier promised delivery Monday" lives only in the supervisor's head.
• Cost arrives late: real project cost only surfaces after the month closes, which is after the window to correct anything has passed.
• Pictures instead of data: a photo of an attendance sheet cannot be summed or compared against plan.
• Disputes over claims: with no agreed daily record, settling with an owner or subcontractor becomes an argument about estimates, not documents.

Eight messages that cover a site day

Each person writes one short message at the moment it happens, and it is filed straight into the right place instead of waiting for later data entry:

1. Morning attendance: the supervisor sends headcount per activity, and it is booked against that project rather than the company as a whole.
2. Material request: "we need 40 bags of cement at the Narjis site" becomes a purchase request tied to the project, waiting on your approval instead of the supervisor's judgement.
3. Supplier receipt: when the truck arrives, what was actually received is logged with quantity and supplier, so it can be matched to the invoice later.
4. Issue from store to site: anything leaving the central store is charged to the project that consumed it, so you see per-project usage instead of one lump figure.
5. Subcontractor work: what was completed today and what was approved, so his entitlement builds up gradually instead of being reconstructed at month end.
6. Petty cash: a transport fee or an urgent spare part is recorded on the spot with a photo of the receipt, so the cash float never turns into an unexplained gap.
7. Obstruction report: a late supplier, rain, a power cut — logged as a documented cause for any schedule variance.
8. Day close: one line on progress and what is planned for tomorrow, giving you a project timeline instead of scattered impressions.

These messages are the source of everything that follows: the site report, the subcontractor account, project cost, and the progress claim.

From site request to supplier invoice

Materials are where cost most often escapes in construction, because the cycle passes through three points that are usually disconnected: the request from site, the delivery from the supplier, and the actual issue to work. When all three are recorded against the same project reference, "how much have we spent on Narjis so far?" has an immediate answer rather than being a two-day exercise, and when the supplier's invoice arrives you already have the received quantities to check it against. That cycle is covered in more depth on the WhatsApp inventory management page.

Progress claims and collection

A progress claim is a roll-up of what was completed and approved during the period. If daily approval already exists, it is assembled from a live record instead of rebuilt from memory and photos. Issuing the invoice itself, however, falls under Saudi e-invoicing requirements, whose details and phase dates are published officially by the Zakat, Tax and Customs Authority at zatca.gov.sa; review that source or your accountant before adopting any new invoicing cycle.

Then comes collection. A project that is profitable on paper but stuck in collection is still a cash problem, so it helps to be alerted about overdue receivables rather than checking by hand every fortnight.

A quick comparison

A checklist before you start

1. Clear project codes that every supervisor knows and quotes in every message.
2. Decide who approves a purchase request and who approves subcontractor work — one person per decision.
3. Keep cost headings few at first: labour, materials, subcontractors, petty cash. Expand later.
4. Run one project as a trial before rolling the method out to the other sites.
5. Hold a short weekly plan-versus-actual review instead of one long monthly one.