A clearer lender and investor update from the records you already have

A useful project update answers three questions: what changed, what does it mean, and what needs a decision? For a developer building two houses, the answer may be scattered across a cost spreadsheet, contractor emails, photographs and the latest programme.

AI can help assemble those records into a consistent draft. The opportunity is to reduce the time spent collecting and rewriting information, while giving you more time to check what the figures actually say.

Start with the recipient's requirements

Ask your lender or investor which format, reporting date and supporting evidence they need. Record these once in a reusable checklist. A short management update should support any required formal reporting. It cannot replace the lender's independent monitoring surveyor, site inspections or agreed drawdown procedures. RICS describes that monitoring role as independent technical advice for development finance providers in its UK practice information on lender's independent monitoring surveyors.

Give every update the same five parts

1. Costs and forecast. Show the approved budget, costs incurred, unpaid commitments and current forecast to complete. Explain material movements since the previous report. Keep contingency visible and distinguish approved changes from estimates awaiting confirmation. Make clear whether figures include VAT.
2. Programme and progress. Compare planned and actual milestones. Explain any movement in the expected completion date, the cause, and the action being taken. A photograph can support a progress statement, but it does not certify the value or quality of completed work.
3. Sales and funding, where relevant. Separate enquiries, reservations, exchanges and completions. Show expected cash receipts and payments using approved assumptions. For funded projects, identify upcoming drawdown requirements and documents still needed. Do not describe a funding request as approved.
4. Risks and decisions. List the few issues that could materially affect cost, completion or cash. Give each an owner, next action and deadline. State exactly which decisions you need from the reader and when.
5. Supporting evidence. Link the cost report, programme version, variation register and dated photographs. Include the relevant approvals or correspondence so the reader can check an important statement without searching through an inbox.

This is a suggested management format, to adapt to your project and reporting obligations. Keep the front page short; put the detailed schedules behind it.

Build a repeatable monthly workflow

Choose one reporting cut-off and collect the approved records in a project folder. Name an owner for each input: costs, programme, sales and site progress. Keep the previous issued report alongside the new material so changes can be compared.

Use AI to extract proposed updates into a review table before it writes the narrative. Each row should contain the proposed statement, its source, the source date and anything that needs confirmation. If two files disagree, the output should flag the conflict rather than silently select a number.

Calculate totals and variances in the approved spreadsheet or accounting report. AI can explain those calculations, but should not reconstruct the cost position from fragments of prose. In particular, prevent the same cost appearing in both money already spent and remaining commitments.

Then produce the five-part draft, a list of missing information and an evidence index. The developer or project lead reviews the narrative; the person responsible for costs checks the figures. Only the approved version is issued, with its reporting date and version recorded.

An illustrative two-house example

The site team's update says the roof is complete. A recent email says a rooflight is delayed. The latest programme still shows the original weather-tight date.

A useful draft records the discrepancy: roof coverings complete, rooflight outstanding, effect on weather-tight date awaiting confirmation. It asks the project manager to confirm the revised milestone and whether internal works are affected. It does not turn the three documents into an unsupported statement that the project is on schedule.

Test it on one completed reporting period

Take a report you have already issued and the records behind it. Ask the draft workflow to reproduce the key facts and identify the changes. Compare it with the approved report: are the figures traceable, are missing records visible, and are the decisions clear?

Measure preparation time, correction time and the number of follow-up questions. That gives you a practical basis for deciding whether to extend the workflow. AI Workflow Planning can help define the template, evidence checks and approval steps around the way your projects already operate.