Skip to main content
← Back to BlogCONSULTING PRACTICE · SVR · 13 SEP 2026
CONSULTING PRACTICE · SVR · 13 SEP 2026

Site Visit Report
Discipline —
Format & Photos.

A good SVR takes 60 minutes to write on-site, not 3 hours back at the office. 12 fixed sections, 5+ photos, 48-hour distribution. Without discipline, the next consultant has nothing.

AH
Amit Haridas
Founder · ConcreteInfo
| September 13, 2026| 12 min read
SITE VISIT REPORT FORMAT · PHOTOS · DISTRIBUTION [PHOTO 1] [PHOTO 2] [PHOTO 3] [PHOTO 4] SIGNATURE & SEAL DRAFT REVIEW PUBLISH IS 456 Cl 19 · IS 14687 · IS 516 · IS 1199

Codes referenced

IS 456 Cl 19
Inspection of Structures

Defines the consultant's inspection scope and authority.

IS 14687:1999
Falsework for Concrete Structures

Formwork inspection criteria for SVR documentation.

IS 516
Cube Testing Procedure

Test witnessing records in SVR.

IS 1199
Slump & Sampling

Fresh-concrete test results in SVR.

Why disciplined SVRs matter

Three reasons: (1) handover continuity — when consultant changes mid-project, the SVR trail tells the new consultant what has happened; (2) audit trail — every QC decision references prior SVRs; (3) dispute prevention — the SVR dated X is the contemporaneous record of what was actually on site. Without it, every dispute becomes a "who said what when" swearing match.

The 12-section SVR format

01
Header

Project, date, time on/off site, weather

02
Attendance

Who was on site, role, organisation

03
Work in progress

Activity, location, % complete

04
Tests witnessed

Slump, cube cast, AIV, UPV — with results

05
NCRs raised

Number, severity, location, root cause

06
Safety observations

PPE, scaffolding, housekeeping

07
Photos

Min 5, captioned, geotagged

08
Measurements

Cover, plumb, level, dimensions

09
Next-visit hold points

What must happen before next visit

10
Distribution

Who gets a copy, email timestamp

11
Consultant signature

Digital sign or scanned signature

12
Attachments

Test results, delivery tickets, photos

Photo discipline — 5 categories

1. Progress

Wide shot showing scope of work that visit. Establishes what was happening.

2. Defect

Close-up of any NCR or non-conformance. Critical for dispute evidence.

3. Evidence

Test in progress (slump, cube cast). Documents the test was actually performed.

4. Context

Site location, weather, access conditions. Establishes visit authenticity.

5. Safety

PPE compliance, scaffolding, housekeeping. Especially when safety is the visit driver.

Distribution within 48 hours

The 48-hour rule is not arbitrary. After 48 hours, the consultant's memory of details degrades, photos get lost, action items get deprioritised. Standard distribution list: client PM + site engineer + lab in-charge + consultant's own QA file. Format: PDF + DOC (searchable). Email subject line must follow the convention: SVR-ProjectNo-VisitNo-YYYYMMDD.

Storage & retrieval

Naming convention: SVR-ProjectNo-VisitNo-YYYYMMDD (e.g., SVR-P-250-024-20260815). File path: /projects/P-250/consultant-reports/SVR-250-024-20260815.pdf. Searchable by project number, date, or visit number. Backup to off-site storage with retention matching the engagement letter (typically 5-10 years).

Worked example — one-page SVR for M30 column pour

SectionContent (90 chars max)
HeaderP-250 / Block-A / 2026-08-15 / 09:30-13:00 / 28°C overcast
AttendanceSite Engr R. Kumar, QC S. Patil, Cons. A. Haridas
WIPM30 column pour, 12 columns, 60 m³ total
TestsSlump 110 mm (OK); 2 samples cast, 3 specimens each, all at 28 days
NCRsNone
Photos8 photos: form, cover, slump, cast, vibrate, place, finish, ambient
Next-visit holds28d cubes on 2026-09-12; strip after 7d
DistributionClient PM + site + lab + QA file at 11:42 same day
SignatureA. Haridas, FIE, CEng
AttachmentsSlump record, 6 cube IDs, mix design ref

Common deviations seen on Indian sites

· "No photos"

Photos are the contemporaneous evidence. Without photos, the SVR is just opinion. Every SVR must have at least 5 captioned, dated, geotagged photos.

· "Reports sent 2 weeks late"

Defeats the purpose. By 2 weeks, the activity is complete and forgotten. 48-hour distribution is the standard; nothing later.

· "Photos without context"

A photo with no caption or location is useless. Every photo needs: where, when, what, why-it-matters. 30 seconds of captioning saves hours of dispute later.

· "Reports not filed systematically"

A naming convention and folder structure are essential. Without them, "SVR-3" might be the third visit or the third project — chaos when disputes arise.

Field-checklist blocks

A short questionnaire, an inspector's checklist, and three worked examples that show how the 12-section format resolves into an evidence-grade record rather than an opinion.

Questionnaire — asked at the close of the visit, before the report is issued

  1. Does the report carry all 12 sections in the fixed order? Header, attendance, work in progress, tests witnessed, NCRs raised, safety observations, photos, measurements, next-visit hold points, distribution, consultant signature, attachments. No improvisation, and no section quietly dropped because there was nothing to put in it.
  2. Does Section 04 record the actual results of the tests witnessed? Slump, cube cast, AIV, UPV, with the numbers. On the sample M30 column pour, that is a slump of 110 mm at delivery against a target of 100 ± 25 mm, which is 10 mm above target and inside the band.
  3. Are there at least 5 photos, geotagged and captioned, spread across the five categories? Progress, defect, evidence, context, safety. The sample SVR carries 8 photos covering form, rebar cover, slump test, cube cast, vibration, placement, finishing and ambient.
  4. Does every photo answer where, when, what and why it matters? Thirty seconds of captioning at the time saves hours in a dispute, and a photo with no caption or location is not evidence.
  5. Are the next-visit hold points dated and traceable to the visit date? On a pour visited on 2026-08-15, the 28-day cube test falls on 2026-09-12, which is the cast date plus 28 days, and the formwork stripping on 2026-08-22, which is the cast date plus 7 days.
  6. Is the distribution list complete, with the email timestamp recorded? Client PM, site engineer, lab in-charge, and the consultant's own QA file. The sample report reached all four at 11:42 the same day.
  7. Is the file named to the convention and filed where it can be found? SVR-ProjectNo-VisitNo-YYYYMMDD, for example SVR-P-250-024-20260815, stored under /projects/P-250/consultant-reports/, searchable by project number, date or visit number.
  8. Is the report typed and signed, rather than left as a handwritten field note? Handwritten notes are fine in the field. The formal report has to be typed and PDF-signed, because handwritten SVRs are inadmissible in arbitration.

Inspector's checklist — what to verify on site

  1. Header and attendance: project, date, time on and off site, weather, and who was on site with their role and organisation. Without the attendance list, nobody can be asked what they were told.
  2. Work in progress: activity, location, percentage complete. This is the section that carries the handover value when the consultant changes mid-project.
  3. Tests witnessed and measurements: slump, cube cast, AIV and UPV with results, plus cover, plumb, level and dimensions. The sample pour records 2 samples cast with 3 specimens each, all at 28 days, giving 6 cube IDs in the attachments.
  4. NCRs raised: number, severity, location, root cause. The sample SVR records none, and says so in Section 05 rather than leaving the section blank.
  5. Safety observations: PPE, scaffolding, housekeeping.
  6. Photos: minimum 5, captioned, dated, geotagged, drawn from the five categories. Check the caption reads as a sentence, not a filename.
  7. Next-visit hold points: the dated items that must happen before the next visit, and the condition that triggers them.
  8. Distribution, signature and filing: the four recipients with the email timestamp, the consultant's digital or scanned signature, the attachments, and the filename and path matching the naming convention. Retention matches the engagement letter, typically 5 to 10 years, with a minimum of 5 years after handover and 10 years for structural elements.

What happens if… three worked examples

Example 1 — the report goes out two weeks after the visit

What happens. Two weeks is 14 days against a 48-hour rule. By then the activity is complete and forgotten, the photos have been buried in somebody's phone, and the action items have been quietly deprioritised. The deeper loss is that the SVR was supposed to be the contemporaneous record of what was actually on site, and 14 days later it is no longer contemporaneous. Every dispute becomes a "who said what when" swearing match, which is the one thing the report exists to prevent.
Likely outcome. The 48-hour rule holds, and it is cheaper than it sounds. The sample M30 column pour SVR was distributed to the client PM, the site, the lab and the QA file at 11:42 the same day. Same-day distribution takes minutes while you are still on site, and it is the difference between a record and an opinion.

Example 2 — the photos are there, but none of them is captioned

What happens. A photograph with no caption, no location and no date is opinion, not evidence. It cannot be tied to a place, a moment or a defect, so it proves nothing when it is needed. With no photos at all, the SVR is simply an opinion document, and it is the weakest thing you can put in front of an arbitrator. Either way the report fails the format: minimum 5 photos, captioned, dated, geotagged, across the five categories.
Likely outcome. The 8 photos in the sample SVR each do a job: the form and rebar cover shots establish that the reinforcement was in place before the pour, the slump and cube cast shots are the evidence category, the vibration and placement shots carry the defect check, and the ambient shot is the context that makes the others believable. That is 8 photos covering 5 categories, and it took a minute at the pour.

Example 3 — the file is saved as "SVR-3" and never filed

What happens. "SVR-3" could be the third visit or the third project. Nothing in the name says which pour it covers, when it was made, or who received it. When the consultant changes mid-project, the new consultant opens the folder and finds a trail that cannot be followed, which destroys the handover continuity the SVR exists to protect. When a dispute comes, the chain of evidence breaks at the filing step, not at the inspection step.
Likely outcome. Name to the convention and file to the path: SVR-P-250-024-20260815, stored at /projects/P-250/consultant-reports/SVR-250-024-20260815.pdf, searchable by project number, date or visit number, backed up off-site, and retained on the engagement letter's terms. Thirty seconds at the keyboard, every visit.

Frequently Asked Questions

What's the minimum photo count for an SVR?
5 photos minimum, but quality beats quantity. Every photo should communicate one specific fact (defect, evidence, progress, context, safety). Geotag and timestamp enabled. Caption with location + subject.
Can site visit reports be handwritten?
Yes for field notes — but the formal report must be typed and PDF-signed. Handwritten SVRs are inadmissible in arbitration; typed reports with consultant signature are evidence-grade.
How long should SVRs be retained?
Minimum 5 years after project handover (RERA), 10 years for structural elements (limitation period under Indian Contract Act), permanent for any opinion that may be cited in future litigation.

Related articles

AH
About the author

Amit Haridas

Founder & Proprietor, ConcreteInfo. 25+ years experience in construction QA/QC, concrete technology, RMC plant operations, consulting and technical training across India. For engagement-letter templates or consulting engagement setup, contact amit@concreteinfo.in.

Newsletter

Technical updates, not sales emails

One email when a new article goes out on concrete technology, QA/QC and construction quality. No promotions, and your address is never sold or passed to advertising networks. Subscribing is separate from making an enquiry.

You are on the list.

One email when a new article goes out. Every issue carries an unsubscribe link.

Need hands-on help?

Reading is one side.
Building is the other.

Engagement-letter templates, consulting engagement setup, code-referenced consulting on your project — we cover the rest.