One site visit.
Every finding together.

Record inspection findings, such as missing safety labels or loose cables, and assess hazards in one form. Review the complete inspection before filing it.

See the plugins See how it works

Wand workshop audit 2 findings

One visit. Separate findings.

Inspection finding Storage area · Add labels

Recorded

Hazard assessment Walkway · Loose cable

Review

Auditor · Rowan Rune

Illustrative experience

Separate observation and hazard lists
Shared visit and auditor details
Review before submission

The finished experience

A complete inspection in one submission.

The auditor can add as many observations and hazards as the visit needs without starting a new inspection form for each one.

A good fit for
Teams collecting field inspections and site audit records with repeatable observations.

1

Make an observation and a hazard form.

Create one child form for observations and recommendations, and another for hazards with the risk-matrix choices your audit requires.

GP Nested Forms
2

Keep the visit details on the parent.

Collect the inspection date and auditor once. Use Gravity Forms’ native {user:display_name} field default for a signed-in auditor, and add both child forms as Nested Form fields.

Gravity Forms
3

Review the complete inspection.

Add a preview before the final submission so the auditor can check the visit details, observations, and hazard assessments together.

GP Preview Submission

Written up, step by step

Create Shareable Health And Safety Audits With Gravity Forms How To · September 2021 In this article, we show you how to use Gravity Forms to create shareable Health and Safety audits that your technicians and auditors will love. Read the tutorial

What you’ll need.

Start with Gravity Forms. Add the capabilities this solution needs, then make the experience your own.

GP Nested Forms

Collects repeatable observations and hazard assessments under the same inspection.

Explore GP Nested Forms

GP Preview Submission

Shows a review of the inspection before the auditor submits it.

Explore GP Preview Submission

Taking it further

Add these optional plugins when your project calls for more.

Optional

GP Populate Anything

Optionally looks up additional auditor or site records. A simple signed-in display-name default uses native Gravity Forms and does not require this Perk.

Explore GP Populate Anything

Optional

GP Entry Blocks

Optionally provides an inspection list and edits for authorized auditors or staff, with explicit ownership filters and edit permissions.

Explore GP Entry Blocks

Before you start

An inspection parent form and two child forms.
Your observation types, risk-matrix choices and inspection questions. A signed-in auditor account is needed for the native {user:display_name} default; otherwise collect the name normally.

Get this built.

A plan covers how many of our plugins you run at once, and on how many sites. Here is what this one needs.

Required

GP Nested FormsPerks
GP Preview SubmissionPerks

Optional

GP Populate AnythingPerks
GP Entry BlocksPerks

Gravity Perks Advanced $169 /year

2 perks need Advanced or above — on up to 3 sites.

Gravity Perks Pro $299 /year Taking all 2 optional perks too makes it 4 in all, which needs Pro.

See plans for this solution

Every plan renews at the same price, and you can upgrade any time for the difference.

Make it fit
your project.

What counts as an inspection finding?

A finding records what the auditor noticed, such as missing labels in a storage area or a loose cable across a walkway. The form can collect the details and a recommended action, with a separate child form for assessing hazards.

Are observation and hazard records the same child form?

This recipe uses two child forms. Each can hold the fields that suit its job, while both belong to the same parent inspection.

What if the auditor is not signed in?

The tutorial leaves the auditor field fillable when there is no signed-in user to populate it from.

Does this decide whether a site meets a safety standard?

It collects and previews the inspection data you define. Your team supplies the audit questions, risk choices, and assessment process.

Can auditors revisit their inspection records?

An optional GP Entry Blocks page can list and edit inspections. Require authenticated access, filter records to the authorized auditor or staff role, and configure edit permissions. Test with an unrelated account; a visible list or a login by itself does not establish ownership.

Why does the tutorial use Populate Anything for the auditor’s name?

That is the historical setup. The current recipe can use the native {user:display_name} default for this single value. Add Populate Anything when you need more complex auditor or site-record lookups.