Nobody likes writing the daily report at 6 p.m. in a truck. And the ones written from memory the next morning are the ones that cost you in a dispute.
Chantro's daily reports start from what the system already knows about the day, then ask the superintendent to correct and confirm it.
What gets filled in for you
For each project and each local day, a report is composed from:
- the tasks worked and the calendar activity for that day
- the photos taken
- the crew, from assignments and records
- the weather for the site
So when Luis Herrera, the superintendent on the Maple Street Duplex, opens the report, work performed and crew are already there with the weather chip. He is editing a draft, not facing a blank page.
What only the site knows
Some things cannot be inferred: a delivery that showed up wrong, an inspector who came early, a sub who left at noon. The field review screen has quick-add chips for a delay, a note or a sub. It works at phone width in the browser, so Luis can do it from the site.
Then one tap on "Looks right, confirm," and the status changes to Confirmed.
The life of a report
- Auto: the system drafts it.
- Confirmed: the superintendent says it is right.
- Approved: optional. Your workspace can add an approval step, or skip it.
If a report has not been confirmed, a notification nudges the right person.
The digest
An AI daily digest writes a plain-language narrative of the day and flags risks. A manager can also see trends across projects, such as repeated delays, and a portfolio digest for the whole job list. The trend flags are rule-based, not guesses. The digest uses credits, and they are charged only after the digest is saved.
Who sees what
A report follows the project's visibility. Someone who is not on the project does not see its reports, on any path.
Time zones
Reports are built per local day for each project's own time zone, including the ones that are off by half an hour. A crew in one place does not get a report cut at someone else's midnight.
What it does not do today
| Not yet | What that means |
|---|---|
| Phone app screens | Daily reports are web only, though the review page works at phone width |
| PDF export | There is no PDF of a daily report |
| Equipment and materials sections | Not part of the report |
| Subs | Listed by hand |
| Worker updates | Crew comes from assignments and records, not a feed |
We would rather list this than let you find out when an owner asks for a PDF. If you need a printed daily report today, this is not the tool for that part.
Why it is built this way
A report written from the actual tasks and crew is more consistent than one written from memory. A report a person confirms is more trustworthy than one nobody read. Doing both is the whole idea: let the system write what it can see, and keep the superintendent in charge of what only he can see.
If you already keep tasks and a calendar current on the project, the report costs you almost nothing. If you do not, the report will be thin, and that is a useful signal too. The draft is only as good as the day's record.
A week in practice
Monday the framing crew is on the duplex, so the report lists the framing tasks, the crew on them and a dry forecast. Tuesday it rains, and the weather chip says so before anyone types a word. Luis adds a delay chip for the lumber drop that came a day late, confirms, and moves on. By Friday the week reads as a connected record instead of five separate memories.
When a manager opens the portfolio view, a run of delays on one project shows up as a flag, not as a surprise in the next owner meeting.
