SiteOps Core replaces WhatsApp threads and paper site ledgers with one private system for contractors in Kenya.
How the system is designed to work, one moment at a time.
Fills in the day's log from the phone: weather, crew by trade, machinery hours, deliveries, incidents and photos. The form is built to be finished in under two minutes. If signal drops, the draft stays on the phone and sends when it returns.
Sees that the work does not match the drawing and raises an RFI with a photo, the location and the drawing reference. The architect is emailed straight away, and a timer starts on the answer.
Receives a variation as a link. The page shows the change and its cost first. Approving takes a deliberate tap and a code, and approval locks the record and updates the budget.
| Record | What it holds | Status |
|---|---|---|
| Daily site logs | Weather, crew by trade, machinery hours, deliveries, incidents, photos | In build |
| Change orders | Reason, drawing reference, quantities and local rates, with owner approval by link | In build |
| Client portal and reports | Progress, budget against actual, pending approvals, PDF reports | In build |
| Drawings | Version history, review comments on the drawing, only the approved version shown on site | Planned |
| RFIs | Photo, location, drawing reference, and a timer on the answer | Planned |
| Schedule | Tasks, dependencies, critical path, baseline against actual | Planned |
| Money | Budgets by cost code, purchase orders, invoices, payment certificates, retention | Planned |
| Payroll, tendering and closeout | Pay records from the muster roll, bids side by side, handover pack | Planned |
Who did it, when, and what changed. Approved records are locked.
Your projects never sit in the same system as another contractor's.
A foreman never sees margins.