1 · Weekly work log
Date, day, hours actually worked and the task completed. Six rows for a six-day week — including the short days, which are the rows that matter.
Every AlcorOne project sends the owner a written weekly report: hours worked each day, the task each day produced, commitments outstanding on both sides, anything that cost the programme time, and dated photographs of the site. Below is a real one — issued during the CHA Republic mall kiosk fit-out in Hyderabad on 10 May 2026 — published in full so you can judge the format before you engage anyone, rather than after.
The format does not change between a small kiosk and a full villa, and it does not change depending on whether the week went well. A report that only arrives when there is good news is not a reporting system.
Date, day, hours actually worked and the task completed. Six rows for a six-day week — including the short days, which are the rows that matter.
What either party owes the project and by when, plus any event that cost time. Recorded while it can still be acted on, not explained afterwards.
What the coming week should deliver, in writing. Next week's report is read against this list, which is what makes the previous week auditable.
Photographs from the reporting week, published against that week's log. Nineteen in the report below.
This is the report as issued, with two changes: the client-side recipient's name is replaced with their role, and one note naming a third party has been reworded to describe the event rather than assign it. The work log, the hours, the commitments, the expected works and all nineteen photographs are unaltered. The project itself is CHA Republic at Aparna Neo Mall, Shamshabad — a 300 sq ft mall kiosk delivered in four weeks.
| Date / Day | Hours | Task accomplished |
|---|---|---|
| 4 May 2026Monday | 10 | Floor guard laid. Fabrication frame cutting started. |
| 5 May 2026Tuesday | 10 | Fabrication frame welding; board-out installation on site. |
| 6 May 2026Wednesday | 8 | Fabrication frame welding and grinding, phase 1 completed — 70% of overall fabrication work. |
| 7 May 2026Thursday | 8 | Wood partition materials reached site. Flooring materials reached site. |
| 8 May 2026Friday | 4 | Half day — site power interruption. Electrical materials reached site. |
| 9 May 2026Saturday | 9 | 50% of wood partition work completed; wall partition electrical cabling done. |
| Total, week to 9 May | 49 | Six working days |



















Most progress updates an owner receives are a number and some photographs. The number is almost always going up, and it never explains itself. Hours worked is a harder thing to publish and a more useful thing to read.
Look at the Friday row in the report above: four hours, against eight to ten on every other day, with the reason stated. An owner eight time zones away now knows the week lost roughly half a day and why, in the week it happened — early enough to matter. A “62% complete” bar would have concealed the same event completely, and the conversation would have happened at handover instead, when the only thing left to do is apportion blame.
The same logic drives section 3. Committing in writing to what the coming week should produce is what makes the current week checkable: the next report is read against the last one's list. A contractor who publishes that list every week has removed their own room to reinterpret history later. Percentages still appear where they measure something defined — “70% of overall fabrication work” counts frames against a known total — but they supplement the log rather than replace it.
Anything that costs the programme time is recorded in the week it occurs, including a delay caused by our own side. A blocker named on day three can still be solved.
Section 2 records what the owner, the building and the contractor each owe the project. Approvals waiting on an owner abroad appear there too.
The report goes out weekly whether the week was good or bad. A reporting system that only produces documents at handover is a defence, not a system.
The format matters most when the owner is not in the city. A written report crosses a time difference without needing a call scheduled at an awkward hour on one side or the other, and it can be re-read, forwarded to a spouse or family member, and checked against last week's version.
The report reaches the owner by email and WhatsApp on the same day each week, in the same structure, so the parts that changed are easy to find.
Nothing in the report requires a live conversation to interpret. Owners in the US, UK, Gulf states and Southeast Asia get the same document, at the same time, as an owner living ten minutes from site.
Section 3 of last week's report is the test the current week is marked against — the mechanism that turns a stack of updates into an audit trail.
Milestones in the log map to the same itemised BOQ that scoped and priced the work, so progress and payment reference one list rather than two.
Four sections: a day-by-day work log with date, hours actually worked and the task completed; a commitments and notes block recording what either side owes the project and anything that cost time; an expected-works list for the coming week; and dated site photographs — nineteen in the report above.
Percentage complete is an opinion, and it almost never goes backwards. Hours worked is a fact you can check against the photographs. Percentages still appear where they measure something defined, such as 70% of fabrication.
Yes — the format was built for owners who cannot walk the site. Because it is written rather than verbal, it reads the same across any time difference, with no call to schedule.
Photographs are taken during the reporting week and published against that week's work log. Sequence is the point: comparing one week's frame against the next is how a remote owner sees progress rather than activity.
You just did. The full report above is genuine, issued on 10 May 2026 during a live fit-out, with the client contact name removed and one third-party note reworded. It is also downloadable as a two-page PDF.
Photographs show that something happened, not whether the programme is on track. The report ties images to a dated log, states hours, names blockers while they can still be solved, and commits in writing to what next week should produce.
Share the property, the scope you have in mind and where you are based. We will come back with a written scope and the reporting cadence that would apply — including a sample report for a project of comparable size.