← All workflows

BUILT FOR CLIENTS, INSIDE THEIR STACK.

Reserve Study Site-Visit Report

Photos and handwritten site notes in. A drafted reserve-study report out.

Starts
Site visit upload form
Size
37 nodes · 40 connections
Tools
Google Gemini, Airtable, ImgBB, Webhook
Category
Document Processing · enterprise
Status
Built and run, currently paused
reserve-study-site-report.jsonn8n canvas

Drawn by n8n's own canvas from the workflow file, synced 2026-09-29. Click it to pan and zoom. Node settings, credentials, prompts and IDs are removed; names, layout and wiring are exactly as built.

Part 1 The problemWhy teams need this

01 · THE PROBLEM

Every reserve study starts with a site visit and ends with days of desk work: sorting photos, typing up notes, describing each component. At 1,200 reports a year, that write-up time is the whole business's bottleneck. Moving it from days to minutes changes how many studies the same team can deliver.

Part 2 How it worksWhat it does, step by step

02 · WHAT IT DOES

Built for a reserve-study firm that produces over 1,200 reports a year. An inspector uploads the site-visit photos and their handwritten notes. AI analyses every photo, reads the measurements off the notes, builds the component records, writes the report narratives and assembles an HTML report ready for review.

03 · HOW IT RUNS

Step by step, as built.

  1. Upload the visit

    One form takes the property details, the photos and photos of the handwritten notes.

  2. Analyse every photo

    Each photo is uploaded, analysed by Gemini against a fixed schema, and saved with its findings.

  3. Read the notes

    Measurements and observations are read off the handwritten notes with OCR and stored against the property.

  4. Build the components

    Photo findings and note data are combined into component records, and AI writes the narrative for each.

  5. Assemble the report

    The narratives and photos are pulled together into an HTML report, ready for the analyst to review.

04 · WHERE A PERSON STAYS IN

The machine drafts. A person decides.

An analyst reviews and signs off every report. The workflow removes the typing, not the professional judgement.

05 · TOOLS AND APPS

Built around the systems already in the process.

Google GeminiTrigger or source
AirtableProcessing and orchestration
ImgBBProcessing and orchestration
WebhookDestination or delivery

06 · WHEN SOMETHING BREAKS

Failure is designed in.

Standard on every build

  • Schema validation before downstream writes
  • Retry and error routes for external API failures
  • Duplicate-safe processing and idempotent updates
  • Human approval where the action carries business risk
  • Execution logging for support and audit review

Part 3 The impactWhat it's worth, and how we'd build yours

07 · PROJECTED IMPACT

What it should change in the business.

01Site-visit report drafted in minutes, not daysProjected
02Every photo analysed and filedProjected
03Measurements read from handwritten notesProjected

Projections for a typical deployment. The calculation below shows the math, and you can put in your own numbers.

08 · ROI CALCULATION

How it pays back in your business.

The starting numbers are a hypothetical deployment sized to the projections above. Change any of them to your own volumes and costs, and the math updates underneath.

Projected net value per year$113,4002,880 hours back per year
Full-time equivalent freed
1.6 people
Gross value
$115,200
Running cost
−$1,800
Return per $1 of running cost
$64

The math: 100 reserve-study reports × 240 min × 12 months × 60% ÷ 60 = 2,880 hours a year × $40/hour = $115,200. Net value = gross value − $1,800 running cost a year.

09 · HOW WE'D BUILD YOURS

How we'd build yours.

  1. Discover: map the current process, systems, volumes, owners and exceptions.
  2. Design: define the canonical data model, approvals, retries and system boundaries.
  3. Build: implement credentials, nodes, validation and observable error routes.
  4. Prove: run controlled data through success, duplicate and failure scenarios.
  5. Operate: publish runbooks, ownership and measurable service levels.

SAME SYSTEM

Built for clients, inside their stack.

Workflows we built for a home-services contractor, a dental practice, a reserve-study firm and an indoor cultivation facility. Names are kept private; the workflows are real.

YOUR VERSION

Want this, wired to your tools?

Tell us what the process looks like today: the systems, the volumes, the step everyone hates. We'll come back with the n8n version and where a person stays in charge.

Start a project Back to all workflows