Daily Site Diary: How to Document Your Build Properly
A daily site diary is your best protection when things go wrong. Whether it's disputes over payments, defective work, or delays, contemporaneous records carry far more weight than memories or reconstructed timelines. Here's exactly what to document and how to organize it.
Why You Need a Site Diary
Most people think "I'll remember what happened." You won't. Three months into a build, you can't recall whether the plumber was on site on Tuesday the 15th or Wednesday the 16th. You can't remember if you told your builder about the electrical issue before or after he ordered the kitchen.
But when disputes escalate to mediation or court, dated, contemporaneous records are gold. They're far more credible than:"Well, if I recall correctly..."
Legal weight: Courts and mediators heavily favor written records made at the time events occurred over reconstructed timelines or verbal recollections created during disputes.
Real Scenarios Where Site Diaries Save You
- Payment disputes: Builder claims he did work you say wasn't done—your diary shows he wasn't on site those days
- Defect arguments: Builder says damage was pre-existing—your photos from week 2 show it wasn't
- Delay claims: Builder blames rain—your diary shows it was dry for 10 days straight
- Scope creep: Builder claims extra work was agreed verbally—your diary has no record of that conversation
- Insurance claims: Theft, damage, or injury—detailed records support your claim
What to Record Daily
Daily Checklist
- Date and time of visit (even if you just drove past)
- Weather conditions (wet, dry, temperature if extreme)
- Who was on site: Names, trades, approximate arrival/departure times
- What work was done: Specific tasks completed or in progress
- Materials delivered: What arrived, quantities, condition
- Conversations had: Any instructions, concerns, or decisions made
- Issues or defects noticed: Describe them, photograph them
- Photos: Minimum 10-15 photos per visit showing overall progress
- Any delays or stoppages: Reasons given for no work happening
What Good Entries Look Like
Example: Good Entry
Monday, 15th February 2026 - Site visit 8:30am
Weather: Dry, mild, no rain overnight.
On site:
- Dave (main builder) - arrived 8:15am
- Two laborers (didn't get names) - arrived 8:30am
- Electrician Simon - arrived 10:00am, left 2:30pm
Work completed:
- Blockwork on side wall finished to DPC level
- First fix electricals started - cables run for kitchen sockets
- Doorway opening formed in existing wall
Material deliveries: 50 blocks delivered 9:00am, stack looks short (counted ~45)
Issues raised: Noticed crack in existing brickwork near door opening. Discussed with Dave, he says it's old and not structural. Took photos. Will monitor.
Photos taken: 18 photos - overall room views, blockwork detail, electrical cable routes, crack in existing wall.
Bad entry: "Builder on site. Did some work. Looks okay." This is useless—no specifics, no evidence, no legal value.
Photography Strategy
Photos are more valuable than written notes. They provide objective evidence that can't be argued with.
What to Photograph
- Before work starts: Comprehensive documentation of existing conditions
- Daily progress: Wide shots showing overall state of work
- Close-ups of critical work: Damp proofing, insulation, complex joints
- Hidden work before it's covered: Services in floors/walls before screeds/plasterboard
- Deliveries: Materials as they arrive, especially quantities
- Any damage or defects: Multiple angles, with ruler/scale if possible
- Site conditions: Access, mud, weather impact, health & safety hazards
Photo tip: Take photos at the same angles/positions each visit. This creates a visual timeline showing progression, making it obvious when work stopped or went backwards.
Photo Organization
Don't just dump photos in your phone's camera roll:
- Create folders by date: "2026-02-15", "2026-02-16" etc.
- Upload somewhere cloud-based: Google Photos, iCloud, Dropbox—protects against phone loss/damage
- Add captions/notes: "DPC level blockwork left wall" not just "IMG_2847"
- Timestamp matters: Don't edit photos or you lose EXIF data proving when they were taken
Recording Conversations
Verbal instructions and promises are worthless unless documented:
In-Person Conversations
- Write down key points immediately: Don't wait until evening
- Send confirmation emails/texts: "Just to confirm our chat today about [X], we agreed [Y]"
- Note who said what: Especially important if multiple people present
- Record agreements: Changes to scope, additional costs, deadline adjustments
WhatsApp & Text Messages
Great news: these are already timestamped and hard to dispute. But:
- Back them up regularly: Export conversations monthly to PDF or cloud storage
- Don't delete anything: Even if relationship sours, keep all messages
- Screenshot important messages: Backup in case app data is lost
- Keep non-work chats separate: Makes evidence clearer in disputes
Tools & Methods for Site Diaries
Paper Notebook
Pro: Legally robust (harder to argue it's fabricated), no battery issues
Con: Can be lost/damaged, photos stored separately making it useless, time-consuming to maintain, impossible to share with your builder
Note-Taking Apps (Apple Notes, Google Keep, Evernote)
Pro: Timestamped, cloud-synced, can embed photos directly
Con: Generic tools not designed for construction. Can't track payments, tasks, or link conversations to specific work. Just a glorified notepad.
Project Management Tools (Trello, Asana, Monday.com)
Pro: Good for task tracking
Con: Massive overkill. Not built for construction sites. No payment tracking, receipt management, or builder collaboration. You'll spend more time managing the tool than your actual project.
Use Ted Instead
Why it actually works: Ted is purpose-built for home renovations. Every photo, note, payment, and conversation is automatically timestamped and organized by project. Photos link to payment records. Builder can acknowledge payments and update task status. Everything in one place—exactly what you need for disputes or just staying sane during your build.
The reality: Paper notebooks get lost. Note-taking apps become cluttered chaos. Project management tools are way too complex. Ted just works because it's designed for exactly this problem.
Stop Juggling Multiple Tools
Track everything in Ted—daily photos, payment records, builder conversations, receipts, and tasks. All timestamped, all organized, all ready if disputes arise.
What Happens When You Don't Have Records
Real example from a mediation case:
Homeowner claim: Builder took £12,000 for first fix electricals and plumbing but didn't complete it properly. Says builder was barely on site during weeks 8-10.
Builder claim: Work was completed correctly. Says he was on site every day during that period. Homeowner is trying to avoid paying final invoice.
Mediator: "Do either of you have contemporaneous records showing who was on site when?"
Reality: Neither had records. Case became he-said-she-said. Mediation failed. Went to court. Homeowner lost because burden of proof was on them to show builder didn't do the work. Cost them £25,000 in legal fees plus they still had to pay the builder.
If the homeowner had kept a simple diary noting "Builder not on site" for those weeks, plus photos showing unchanged state of work, they'd have won easily.
Critical point: Absence of evidence is not evidence of absence. If you don't have records proving your version, you'll lose, even if you're telling the truth.
How Often to Update the Diary
Depends on your involvement level:
- Daily site visits (living nearby): Update diary every visit, 5-10 minutes
- 2-3x per week visits: Update each visit, include what builder reported via WhatsApp between visits
- Weekly visits: Minimum—take extensive photos, get verbal update from builder, document it
- Remote projects: Rely on builder to send daily photos/updates, save all messages, visit weekly minimum
Reality check: Even 3 minutes per day writing 5 bullet points is infinitely better than nothing. Don't let "I don't have time for detailed notes" become an excuse for no records at all.
Organizing Financial Records with Your Diary
Your site diary should cross-reference financial transactions:
- Link invoices to work done: "Paid £8,000 for roofing materials - delivered today (see photos)"
- Note payment dates: "Paid progress payment £15,000 via bank transfer - work 60% complete"
- Record verbal quotes: "Builder quoted £450 to fix drainage issue - awaiting written quote"
- Photograph receipts: Keep digital copies linked to diary entries
Sharing Access with Others
If multiple people are managing the build (partners, parents, project manager):
- Use shared digital tool: Everyone updates one central record
- Assign roles: One person does photos, one does written notes
- Regular sync meetings: Weekly review of diary to ensure accuracy
- Don't create multiple diaries: Confusing for disputes, stick to one master record
When to Show Your Diary to the Builder
Generally: don't. Your diary is for you, not for sharing.
Exception: If working collaboratively and builder is responsive, you can share factual progress notes to keep everyone aligned. But don't share notes about concerns, defects, or anything that could be used against you later.
If disputes arise, your diary becomes evidence. Showing it to the builder beforehand lets them prepare counter-arguments or claim you're fabricating things.
How Long to Keep Records
Building disputes can surface years later when defects emerge. Professional recommendation:
- Structural work: Keep 10-12 years (statute of limitations for building defects)
- All other records: Minimum 6 years (general contract law)
- Photos: Forever—they're tiny files, no reason to delete
Cloud storage is cheap. Just keep everything.
Final Thoughts
Keeping a site diary feels like bureaucracy when the build is going smoothly. But the one time you need it, it's worth 100x the effort.
It's not about being suspicious or adversarial—it's about being professional and protected. Good builders respect clients who keep records because it shows you're serious and organized.
Start today. Even if you're already mid-build, starting now is better than never starting at all. Pick a method (app, notebook, whatever), and commit to 5 minutes per site visit documenting what you saw. That's it. Simple, effective, potentially life-saving.