The monthly drawdown cycle
You act as monitoring surveyor for a lender on a residential development. Each month, the developer sends a drawdown pack: the contractor's valuation, invoices for professional fees, an updated cost to complete, a programme update and a request for funds. You visit site, look at progress, and write a report for the lender covering cost, programme, quality observations, risks and a view on the drawdown.
The pack arrives as a folder of PDFs and spreadsheets in a different order each month. The report is a Word document edited from last month's, with figures updated by hand and sections rewritten where things changed. With several developments for several lenders, each in their own format, the monitoring team's month is a cycle of assembling and rewriting.
Why monitoring reports eat time
- Drawdown packs are inconsistent, so finding the numbers takes reading.
- Figures are copied from the pack into the report by hand.
- Comparing this month's cost to complete with last month's is manual.
- Site observations and photos are collected on a phone and sorted afterwards.
- Each lender wants its own template, with its own headings and order.
The cost to the monitoring team
The surveyor's time goes on assembly rather than scrutiny. Movements in the developer's figures can be missed when the comparison is done by eye. Reports reach the lender later than they would like, which delays the developer's funds and puts pressure on everyone. And a report that carries forward a sentence that is no longer true is a risk in a document a lender relies on.
| Report section | Source | What the workflow adds |
|---|---|---|
| Cost to complete | Developer's pack | Extracted and compared with last month |
| Contractor valuation | Pack | Figures read and checked against contract sum |
| Programme | Updated programme | Key dates compared with previous report |
| Site observations | Surveyor's visit | Captured on tablet with photos by area |
| Risks and commentary | Surveyor | Carried-forward text flagged for review |
How we build the monitoring workflow
- Each development is set up with its budget, contract sum, key programme dates and the lender's report template.
- The developer uploads the monthly pack to a link, and the workflow reads the key figures from the valuation, cost to complete and invoices, marking anything it is unsure of.
- Figures are compared with the previous month and with the budget, and material movements are listed for the surveyor.
- On site, the surveyor records observations by area and trade with photos on a tablet.
- The report is drafted in the lender's template, with updated figures, the movement list, site observations and last month's commentary, where every carried-forward paragraph is marked for review.
- The surveyor reviews, writes their view and signs off, and the issued report is locked and filed.
The recommendation on a drawdown and the view on cost, programme and quality are the monitoring surveyor's. Lending decisions are the lender's. The workflow assembles the evidence and the draft.
A shorter month
The surveyor opens a draft with this month's figures in place and a list of what moved. Site observations are already sorted by area. Time goes on the questions the lender needs answering, such as whether the cost to complete is credible or whether a programme slip affects the facility. Reports go out sooner, and the carried-forward text is always reviewed.
Across a portfolio, the team lead can see which developments have packs outstanding, which reports are drafted and which are issued, without asking round the office.
Is this how your monitoring month runs?
- Monthly reports are edited from the previous month's Word file.
- Finding figures in developer packs takes reading every document.
- Movements in cost to complete are compared by eye.
- Site photos are sorted after the visit.
- Each lender's template is maintained by hand.