How to set up Field View: drawings, details and forms that site teams actually use

A Field View project is only as good as its setup. If drawings are out of date, forms don’t match the ITP, or nobody knows which detail applies where, site teams stop using it, and the records you need for handover, payment and Gateway 3 never get made.

This guide sets out how we set up Field View for a package or project so it works from day one.

1. Drawings: the base of every record

• Upload current plans for every level and zone, with clear names and revision numbers, for example “L04 – Drylining layout – Rev C”.
• Remove or archive superseded revisions so nobody records against the wrong drawing.
• Split large buildings into logical areas (level, core, zone or flat) so records can be found and filtered later.
• Set a revision routine: when a new revision is issued, who uploads it, and how open items are moved across.

Every inspection, issue and photo is then pinned to an exact location on the right drawing. That’s what makes records useful as evidence.

2. Details: the standard you inspect against

Inspectors and operatives need to see what “right” looks like at the point of work.

• Attach the key construction details to the relevant drawings and forms: partition types, deflection heads, cavity trays, fire stopping details per penetration type, cavity barrier details.
• Add manufacturer’s installation details for safety-critical products, matching what’s actually approved for use.
• Reference the specification clause in each form question so the acceptance criteria are clear.

This turns “does it look OK?” into “does it match detail FS-03 rev B?”

3. Forms: your ITP, made digital

Each form should mirror a stage in the Inspection and Test Plan.

• One form per inspection stage: for example “Metal stud framing”, “Pre-close fire-rated partition”, “Penetration sealing”, “Cavity barrier pre-close”.
• Clear, checkable questions with pass/fail/N/A answers and space for measurements.
• Mandatory photos on safety-critical questions, so the evidence exists before work is covered.
• Hold point sign-off built in: who inspected, date and outcome.
• Automatic issue creation when a question fails, so defects become trackable NCRs.

4. Registers and lists

• Penetration register for fire stopping: ID, location, service, size, rating, product, installer, status. This is essential for M&E packages.
• Door schedule linked to fire doorset inspections.
• Defect and NCR categories that match how you report: package, trade, severity.

5. People and permissions

• Set up subcontractor companies and users with the right access, so each trade records its own work.
• Decide who can close issues and forms. Usually that’s QA or the main contractor, not the person who raised them.
• Run a short onboarding session for supervisors and operatives, on site or online.

6. Reports

• Agree the monthly QA report format at the start: inspections, pass rates, NCRs, progress by floor.
• Set up exports that can be attached to applications for payment and handed over into the golden thread.

See what the output looks like in our sample monthly Field View QA report.

Setup checklist

• Current drawings uploaded, named and split by area
• Superseded revisions archived; revision routine agreed
• Key construction and manufacturer’s details attached
• Forms built for every ITP stage, with mandatory photos and hold point sign-off
• Penetration register and door schedule set up where relevant
• Users, companies and close-out permissions configured
• Site team briefed; monthly report format agreed

We set up Field View for you, on site or online. Drawings, details, forms and registers ready for your package, then inspections on call at hold points and a QA report monthly or on request. See samples or book a call.

*Field View is a trademark of its respective owner. Construction QA is an independent service provider and is not affiliated with or endorsed by Trimble or Viewpoint.*