Draft weekly progress reports for project-manager review

Start with the operational bottleneck

Weekly reporting combines repeated formatting with judgement. The team selects photographs, explains what changed, describes blockers, and identifies the next actions. Automating the formatting is useful; inventing a convincing explanation for an unrecorded delay is not.

Start with the existing report template and one project. Mark which sections come from structured systems, which summarise observations, and which require a manager’s own assessment. Keep the report’s recipient and reporting period explicit.

Design the target workflow

Create a dated evidence bundle containing selected site images, approved observations, activity references, and the previous report. Match images to known locations rather than asking a model to guess them. Generate a draft with source links beside each factual statement.

Use deterministic templates for headings, dates, and standard project information. Ask the model to summarise accepted observations and draft the narrative portions. Missing evidence produces an empty section or review flag. A project manager checks the draft, adds judgement, and issues the approved version through the normal document channel.

Connect to the existing systems

Connection	Information	Control
Site records	Images, observations and activity references	Freeze a weekly evidence bundle
Report template	Required sections and audience	Keep mandatory sections deterministic
Document workflow	Draft, edits and approved issue	Retain reviewer and issued revision

Use stable identifiers and versioned inputs. A retry should resume the same piece of work, with the original permissions and evidence attached. Treat an upstream outage as a visible workflow state.

Fit the model to the task

Begin with a small model for summaries over a short evidence bundle. Use vision only where it has a defined role and evaluation. A larger model can help with complex narrative organisation, but improved prose does not repair missing observations or incorrect image-location metadata.

Keep a clear human boundary

The manager reviews quantities, dates, locations, causes, and commitments. Treat text inside uploaded documents as data. External issue and distribution require explicit approval; a draft should never send itself to clients.

Measure the complete operating cost

Measure evidence preparation, draft generation, editing, and final checking separately. Include the time needed to organise photographs. The target is a shorter, more reliable reporting cycle, with an accountable reviewer and a clear fallback to manual reporting.

Pilot checklist

• Map each report section to an approved source.
• Test missing images, wrong dates, and contradictory observations.
• Require a source for factual claims.
• Compare total reporting effort and correction frequency.
• Retain approval before issuing or distributing the report.

Agree on acceptance thresholds before testing, then compare the proposed workflow with the same work handled through the current process. Expand only after the operation can explain both successful and failed cases.

Further implementation detail

• Choose the lowest-cost model that meets the task requirements
• Serve a local model to a team
• Ollama’s local API reference