Construction site reporting software for contractors and consultants in Kenya
Site teams report the way they already do: on WhatsApp, on the web form or in last week's report. JengaFlow builds the checked daily record, then the weekly and monthly progress reports, with every figure traceable to the site.
Finishes crew · Towers C & D · 25/09/2026
Members: 9
Tower C
4th floor
· Slab reinforcement
· Column formwork
Tower D
Ground & 1st floor
· Electrical conduits
3 photos
Finishes crew · 9 people
| Tower | Floor | Activity |
|---|---|---|
| C | 4th | Slab reinforcement |
| C | 4th | Column formwork |
| D | Ground & 1st | Electrical conduits |
3 photos placed by the bot. Someone who was on site confirms each floor before the report is submitted.
Built from this week's daily records
| Floor | Tower C | Tower D |
|---|---|---|
| 4th | Slab rebar | |
| 3rd | Cast | Formwork |
| 2nd | Cast | Cast |
| 1st | Cast | Conduits |
1,184 man-days14 photos6 deliveries
Built from 4 weekly reports and the month's payment certificates
Floor matrix32 progress photosPayment records
Musters, deliveries, progress and photos arrive all week in chats, forms and spreadsheets. On Friday someone retypes them into the weekly template, and at month end they do it again for the monthly. Photos lose track of their floor, and figures lose track of where they came from.
One pipeline, three reports. Each stage is checked by the right people before it feeds the next.
Every day
Every week
Every month
Nobody starts a weekly report from a blank page. Carry last week's report forward, or upload it from the dashboard or by forwarding it to the WhatsApp bot, and the new week opens with its contract details, scope, matrix and photos already in place.
This week's daily records then fill in what changed on site.
JengaFlow's bot reads the project group: musters, activity updates, delivery notes and photos. It files each message under the right project, day, tower and floor, and answers with what it recorded. Forward a Word or PDF report and type /upload weekly or /upload monthly, or upload it from the dashboard, to bring it into the dashboard.
Enter or correct a day's report directly, team by team, with photos.
Upload a Word or PDF report. JengaFlow reads its tables, text and photos into an editable report.
Software can read a labour muster. It cannot tell which floor a photo was taken on, or whether a slab was ready to cast. JengaFlow keeps those calls with the people responsible for them.
Check where the photos were taken
Move any photo that is on the wrong block or floor, then confirm.
Tower C · 4th floor
Tower C · 4th floor
Tower D · Ground & 1st
Nobody on site changes how they work. The records build around them, and by Friday the weekly report is waiting.
At the gate
The storekeeper photographs the delivery note and posts it. JengaFlow reads the supplier, items and quantities, and records what was accepted. It shows up in the week's materials table.
On the slab
Headcounts and the day's plan go into the group. JengaFlow adds up labour per contractor, points out any crew that has not sent its return, and carries the totals into the weekly labour table.
Before the pour
Cube results from the block's earlier pours decide whether the next pour is cleared, waiting on results or blocked. The decision keeps its test evidence, ready when the client asks for it months later.
Evening update
The day's report is drafted from the group with each photo placed on a tower and floor. Someone who was on site confirms the placement before it is submitted.
Site office
Labour, activities, materials, the floor matrix and photos are already in the weekly report. The engineer reviews it, adds comments and downloads it. At month end, the monthly report builds from the weeks the same way.
Each part of the workspace feeds the weekly and monthly reports, so nothing is typed twice.
Floor-by-floor matrix per block, updated from daily activity and imported baselines.
Daily musters per contractor and trade, site staff, gender totals and missing returns.
Orders, gate deliveries, accepted quantities, consumption and stock.
Casting readiness gates, cube tests, scaffold inspections, shop drawings and inspections.
Safety reports, hazards, toolbox talks and environmental records.
Interim payment certificates, certified and paid amounts, and time elapsed against physical progress.
Also in the workspace: finishes & defects trackerequipmentsite mapsite instructionssite minutes & action itemsconcernssubmittalsscaffold inspectionsWhatsApp broadcaststaff-sheet syncdaily & weekly PDF downloads
Housing projects are tracked the way they are built: every activity, photo and progress figure sits on a block and a floor, from the daily record to the monthly matrix.
Site teams already coordinate on WhatsApp. JengaFlow works from the groups they use, so adoption does not depend on retraining a whole workforce.
Physical progress, time elapsed and certified payments sit next to the site evidence behind them.
Each person sees the projects they are assigned to. The bot only reads groups you connect to a project. AI helps organise messages and documents; it does not approve, certify or sign anything.
Read about security, AI and WhatsApp dataFrom the founder
Caleb MuturiFounder & Developer, JengaFlow Pro
JengaFlow was built from firsthand experience with real construction-site workflows in Kenya: updates scattered across WhatsApp groups, the same figures typed into several forms, and hours spent turning field notes into formal weekly and monthly reports.
I built JengaFlow to fix that. It captures information where the work happens, organises it automatically, and builds the reports from it, with every figure traceable to the message or record it came from.
The goal is simple: give construction teams a clear, checked picture of their project without adding paperwork.
Short answers for the questions site managers ask first.
No. Crews keep reporting in WhatsApp exactly as they do now. Supervisors and engineers use the JengaFlow dashboard in a browser on any laptop or phone.
Daily musters and activity updates, gate delivery notes and their photos, finishes updates from your finishes teams, and Word or PDF reports forwarded with /upload weekly or /upload monthly. Each message is filed under the right project, day, tower and floor before anything is approved.
WhatsApp-built reports stay drafts until someone who was on site confirms where each photo belongs, and only your project administrators approve daily, weekly and monthly reports. Every record keeps the source messages it was built from.
Yes. Each user only sees projects they are assigned to, and the bot only reads WhatsApp groups you explicitly connect to a project. Records, photos and labour figures stay inside your project workspace.
A PDF copy of each daily record, the weekly and monthly progress reports as Word documents and PDFs, and the weekly report also opens as a Google Doc that your project team edits together; your client receives the finished Word or PDF.
From last week. Carry the previous report forward or upload it, and the new week opens with contract details, scope and the matrix in place. The week's daily records then fill in what changed.
Incoming messages are held in a processing queue for up to 14 days and then deleted automatically. The messages a report was built from, up to the last ten per report, stay with that report so every figure can be traced. The details are in our privacy notice and trust page.
In a short demo we set up a project with your blocks, connect a site group and walk through a week: daily records, labour, materials and the finished weekly report.
Joining your team's workspace? Create your account and ask your project admin for access.
