How to Use Google AI Form Builder for a Builder's Site Visit Checklist

Open a new form in Google Forms, click "Help me create a form", and paste a prompt that lists your visit types and checks. Then finish by hand: add sections, a photo upload question and a linked response sheet, because the AI builder drafts one flat form. It needs an eligible Workspace or Google AI plan.

Two limits shape everything below. Google's help pages say the feature does not create multi-section forms and replaces anything already in the form, so treat its output as a question bank, not a finished checklist. And photo upload questions need responders to sign in to a Google account, which matters for subcontractors who have none. Plan on 30 to 45 minutes from blank form to a tested checklist.

Follow me on Instagram@sagnikteaches

What Gemini in Forms will and will not do for this job

Google's announcements list "Help me create a form" for Workspace Business Standard and Plus, Enterprise Standard and Plus, and the Google AI Pro and Ultra consumer plans, plus some education plans. Business Starter is not on the list, and Google says users need smart features and personalisation turned on to see Gemini in the side panel; on a Workspace account the administrator sets the default. If you run a free or Starter account, skip to the fallback at the end of this section.

Connect on LinkedInSagnik Bhattacharya

To use it, open forms.google.com and start a blank form. A prompt window opens on the new form, or you can click "Help me create a form" in the toolbar. Type a prompt, click "Create", review the draft, then click "Create form" to keep it. To change it, edit the prompt at the top of the draft and click "Recreate", but note that Google's help article says once you create a new version you cannot go back to the previous one. Using the feature on a form that already has content replaces that content, and the earlier announcement says you get a warning first.

Subscribe on YouTube@sagnikteaches

You can also base the draft on a file. Google says it can work from Docs, Sheets, Slides and PDFs in Drive. For a builder that is a real shortcut: if you have a paper pre-start checklist, scan it to PDF, put it in Drive and point the prompt at it, so the draft starts from your questions rather than a stranger's. What it will not do, by Google's own account, is create a multi-section form, edit an existing form in place or set quiz settings. It lists multiple choice, checkbox, grid, short-answer and long-answer questions for generated quizzes and does not mention file upload for forms, so assume you will add photo questions yourself.

If the button is missing, the fallback is simple. Ask any assistant for the question list in plain text, with each question and its answer type on one line, and paste the questions into a blank form yourself. Everything after this section works the same way. For the survey-and-summary side of the same feature, see Gemini in Google Forms: build a customer survey and summarise replies.

Decide the three visit types before you write the prompt

The mistake that makes site forms useless is one long checklist for every visit. A pre-start walk, a Tuesday progress visit and a pre-handover snagging (punch-list) round need different questions, and a form that asks all of them trains people to tick everything. Start by writing down the three visit types and what each must capture.

Every visit opens with the same four questions: which site (a dropdown), the date, who is visiting, and the visit type (multiple choice). The visit type answer will steer the rest of the form, which is why it must be a multiple choice or dropdown question. Google's branching page says "Go to section based on answer" is only available for Multiple choice and Dropdown question types, and although the question-types page also mentions checkboxes, the branching page is the stricter one, so build on a multiple choice question and you are safe.

The prompt to paste, and the draft you will get back

This prompt asks for what the AI can do well, which is wording and coverage, and leaves the structure to you.

Create a site visit checklist form for a small building firm. Visit types: pre-start, progress, pre-handover snagging.
Start with: site name (dropdown with three placeholder sites), visit date, visitor name, and visit type (multiple choice).
For each visit type, write 8 to 10 checks as Pass / Fail / Not applicable questions, each with an optional comment, covering access and parking, welfare, housekeeping, hazards and protection, quality of completed work, deliveries, and changes noticed. End with: overall rating (linear scale 1 to 5), actions needed (paragraph) and any other concerns (paragraph).
Plain wording, short questions, one idea per question. No client or personal information.

A realistic draft (illustrative) is one long page of about 30 questions. By Google's own description it will not be in sections, so the three visit types sit in a single list with nothing dividing them. Expect these faults, and fix them in this order:

1. Vague questions. "Is the site tidy?" and "Is everything OK?" cannot fail. Replace them with checks someone can disprove: "Are walkways and stairs clear of materials, cables and waste?"
2. Invented intervals. The draft includes "Scaffold inspected in the last 7 days?" The right interval depends on where you work and on your own safety policy. Delete any figure that did not come from your rules.
3. Duplicates. Housekeeping appears three times in slightly different words. Keep the best one.
4. Inconsistent answers. Some questions use Yes/No and others Pass/Fail. Choose Pass / Fail / Not applicable for every check, so the response sheet can count Fails with one formula.
5. No photo prompts. The draft knows nothing about uploads, so you add them.
6. Required settings. Make the visit details and the Pass/Fail checks required, and leave the comments optional.

A filled-in extract of the progress section after editing:

Turning the flat draft into sections and branches

This is the part the AI cannot do for you, and it is the part that makes the form pleasant to use on a phone. Google's help page allows up to 300 pieces of content and 75 sections in a form, so a three-visit checklist of 30 to 40 questions is nowhere near the ceiling.

1. Section 1: Visit details. Keep the four opening questions here: site, date, visitor and visit type.
2. Add the visit-type sections. Where each visit type's questions start, click "Add section" and name it "Pre-start checks", "Progress checks" or "Snagging checks". Add a final section called "Sign-off" for the overall rating, actions needed, other concerns and the photo question. If sections end up in the wrong order, use More, then "Move section".
3. Branch on the visit type. On the visit type question, click More at the bottom right, choose "Go to section based on answer", and send each answer to its own section.
4. Send every visit-type section on to the sign-off. At the bottom of each section, set where people go next. If you skip this step, Forms moves on to the next section in order, and a progress visit walks straight into the snagging questions.
5. Test every path on a phone. Fill in the form three times, once per visit type, and count the screens. If a progress visit takes more than five or six, trim the questions.

For the sites dropdown there are two choices. You can keep it current by hand, adding and removing sites as jobs start and finish. Or you can make one pre-filled link per site: in the form, click More, choose "Pre-fill form", pick the site in the dropdown and click "Get link". Save each link in the job folder, or pin it in the site's group chat. Pre-fill only the site, never the date, because a pre-filled date is fixed when you copy the link. The visitor opens the link, the site is already chosen, and what is left is the date, the visit type and the checks. That removes the commonest data error, which is a visit logged against the wrong job.

If you later want a separate form for a subcontractor's own checks, "Import questions" copies a set of questions from an earlier form, so you are not rebuilding from nothing. For the checklist content itself, the pre-start checklist and long-lead items tutorial and the snagging report template are good sources for questions to borrow.

Photo fields: what Forms allows and what trips crews up

A site checklist without photos is an opinion. Forms has a File upload question for this, and its limits matter more than its features. Google's help page for question types says:

• Responders must sign in to a Google Account to answer a file upload question.
• For the form owner, uploaded files are stored in a new folder in Google Drive.
• You can set which file types responders may upload, the maximum number of files and the maximum file size.
• You cannot use this question type if the form is stored in a shared drive, or if your administrator has turned on Data Loss Prevention.

The publishing page adds that a form containing a file upload question cannot be embedded in an email. Those four points produce three practical decisions. First, store the form in the owner's own Drive, not a shared drive, or the upload question will be unavailable. Second, tell subcontractors without a Google account how else to send photos, because the form will not accept them. Third, put the upload question where it helps: one "Photos of issues found" question per section, set to images only and a sensible number of files, rather than a separate upload under every check. Twelve upload prompts on one screen make people skip all of them.

A quick sum shows why storage deserves a thought. Four sites with three visits a week is 12 visits, and at six photos a visit that is 72 photos a week, or about 3,700 a year. If each photo is around 4 MB (your phone's quality setting decides, so check it), that is nearly 15 GB a year in the form owner's Drive. Plan for the storage of the account that owns the form, and remember that Google says deleting responses from a form does not delete the attached files. When a job closes, tidy its photos on purpose.

The response sheet: set it up so the office can use it

Responses pile up in the form itself, but nobody wants to read a site checklist one response at a time. Send them to a spreadsheet. In the form, open the Responses tab, then the Summary tab, click More at the top right and choose "Select destination for responses". Pick "Create a new spreadsheet" and click "Create". Form collaborators get access to the new sheet automatically, but Google notes that later permission changes do not synchronise, so if you remove someone from the form, remove them from the sheet as well.

To be told about new responses, open the Responses tab, click More and choose "Get email notifications for new responses". Google's help page points to a separate Form notifications add-on if you want more options, such as customised follow-up emails; treat any add-on as another thing that needs checking before it sees client addresses.

Two formulas turn the raw sheet into something a contracts manager reads in 30 seconds. Adjust the column letters to your sheet.

Conditional formatting, custom formula, applied to the whole table:
=COUNTIF($E2:$AJ2,"Fail")>0

Total Fails in the sheet (put it in a cell above the table):
=COUNTIF(E2:AJ1000,"Fail")

The first colours any row red if a single check failed, including rows added tomorrow. The second gives you the week's number for the Friday meeting. Add a filter view for each site, and the office can answer "what did we find at the school extension this week?" in two clicks. An illustrative extract of three rows:

The second and third rows would turn red. For prompts that summarise a sheet like this in plain English, Google Sheets AI prompts has ready-made wording, and Gemini in Sheets is only on some plans, so check yours first.

Settings that quietly break a site checklist

Forms ships with defaults designed for surveys, and several of them are wrong for a form that the same six people fill in every week. Check each of these before you share the link.

• "Limit to 1 response" (Settings, Responses). Google's publishing page says it makes users sign in and allows one response each. On a recurring site checklist that means each person can submit exactly once, then they are locked out. Leave it off.
• "View results summary" (Settings, Presentation). When on, responders get a link to a summary of everyone's answers, which Google says is visible to anyone who can respond. Leave it off, because a subcontractor does not need to see your Fails.
• "Disable autosave for all respondents" (Settings, Presentation). By default, draft responses are saved for 30 days after the last edit. Google suggests turning autosave off for repeated data entry and shared devices. On a site, a half-finished draft from last week reappearing is a good reason to switch it off.
• "Allow response editing" (Settings, Responses). On, a visitor can correct a same-day slip. Off, the record is cleaner for audit. Pick one deliberately, and say which in your checklist's instructions.
• "Collect email addresses" (Settings, Responses). The Verified option makes responders sign in and records their Google account's email address, so every visit has a name behind it. That is the cheapest accountability you can add.
• Confirmation message (Settings, Presentation). Use it for the one instruction that matters: "Saved. If any check was marked Fail, tell the contracts manager today."

Six people, four sites: what the first week looks like

Consider a six-person building firm with four live jobs. Two site managers share the visits, about three per site each week, so 12 visits. Each visit used to take 12 minutes to fill in on paper and another 6 for someone in the office to scan, type up and file: 18 minutes a visit, or 216 minutes a week. With the form, the visit takes 10 minutes on the phone, including six photos, and the office spends 2 minutes checking each response. That is 12 minutes a visit, 144 minutes a week, a saving of 72 minutes. These are assumptions, so log one real week of each before you believe them.

The time saving is modest. What changes is what the office can see and when. Suppose each form has about 28 Pass/Fail checks. Twelve visits give 336 answers, and the first week produces 11 Fails, which is 3.3%. Nine of the 11 come with photos. On paper, those 11 would surface when someone typed up the sheets, often days later. With the form, the red rows appear the same morning, and the contracts manager works down them: three housekeeping fails go to the site manager, two missing edge-protection fails to the scaffolder, and so on. By Friday, eight of the 11 are closed and the remaining three are on the agenda for Monday.

That is the case for doing this at all: not minutes saved, but a Fail that reaches the person who can fix it before the next visit. If your sites already have an app that does this, you do not need a form. If they do not, a form is a cheap way to find out whether the habit sticks before you pay for software. For the narrative side of a visit, such as writing the client update afterwards, writing client updates and snag lists with AI for builders picks up where the form leaves off.

Where Forms stops, and what to use then

Google Forms was built for surveys, and a site checklist pushes on several of its edges. Know them before you promise the crew a perfect tool.

• No signature question. The list of question types on Google's help page includes short answer, paragraph, multiple choice, checkboxes, dropdown, file upload, linear scale, rating, two grids, date and time. There is no signature field, so a client sign-off needs another route.
• Signed-in uploads only. Anyone adding photos needs a Google account, as covered above.
• No stated offline mode. The pages I read do not describe one for responders. Test the form where your signal is worst before you rely on it.
• Branching on two question types. Sections can branch from multiple choice and dropdown questions, which is enough for visit types but not for "if this check fails, ask these three follow-ups" on a Pass/Fail grid. Use a comment and a photo prompt instead.
• No finished report. A response is a row in a sheet. Turning it into a branded PDF for a client needs more tooling.

When two or three of those start to hurt, move on. Some job software now ships its own form builder; JobTread's AI features page lists an "AI Form Builder" for forms collecting information from customers, vendors and the team, and Simpro's form builder for job sheets and safety checklists covers a similar route with ChatGPT drafting. Whichever route you take later, build the form first. A week of using it will tell you more about what your sites need than any feature list.

Questions builders ask about the Google form

Do I need a paid Google plan for the AI form builder?

Google's announcements list Business Standard and Plus, Enterprise Standard and Plus, and the Google AI Pro and Ultra plans. Business Starter and free accounts are not on that list, and smart features and personalisation must be turned on for the user. If the button is missing, draft the questions in another assistant and paste them into a blank form.

Can subcontractors upload photos without a Google account?

No. Google's help page says responders must sign in to a Google Account to answer a file upload question. A subcontractor without one needs another route, such as sending photos to the office by message, or a version of the form without upload questions that a site manager completes for them.

Will the form work on a site with no signal?

Google's help pages do not describe an offline mode for people filling in a form, so test it where your signal is worst before relying on it. If dead zones are common on your jobs, a purpose-built inspection app with offline saving is a better fit than a form.

Where do the uploaded photos go?

Into a new folder in the form owner's Google Drive, according to Google's help page. Deleting responses from the form does not delete attached files, so clear out the folder yourself when a job closes, and plan storage for the account that owns the form.

Further reads

• Construction Photo Documentation App: What AI Adds, and Which Plan — Photo documentation apps and which plan adds AI.
• What Gemini in Google Workspace Includes on Each Business Plan — What Gemini includes on each Workspace plan.
• Is Gemini Safe for Confidential Business Data in Workspace? — Data handling before client details go near Gemini.
• Gemini in Google Sheets for Small Businesses: 10 Practical Uses — Summarise the response sheet with Gemini in Sheets.
• Five AI Apps for Construction Site Work: Photos, Logs, Checks — Five AI apps for photos, logs and checks.
• AI in the Construction Field: Photos, Voice Notes and Punch Lists — Photos, voice notes and punch lists in the field.
• Scaffolding Inspection Records: A Digital Form and AI Summaries — A digital inspection record built the same way.
• Glide Mobile App Builder: A Snag List Photo App for a Building Firm — A no-code photo snag-list app for when a form runs out.
• AI Automation for Contractors: Qualify, Book and Confirm Site Visits — Five steps from a new enquiry to a confirmed site visit, with a qualifying rubric, booking options, prep lists, reminder timing and consent wording.
• Architect Site Visit Report: Notes and Photos to a Clear Report With AI — A worked notes-to-report example for architects: observation, instruction and action columns, photo captions, and a rule that keeps unseen items out.
• EV Charger Site Survey Checklist: Consumer Unit, Cable Run and AI Summary — A grouped checklist for the EV charger survey, with why each item matters and how to verify it, plus a prompt that turns photos and notes into two summaries.
• Typeform AI Form Builder: A Quote Request Form for a Fencing Firm — A step-by-step fencing quote request form built with Typeform AI: the prompt, branching questions, photo uploads, estimator alerts and what each plan allows.
• Can AI Answer Building Code Questions? A Builder's Safe-Use Routine — A builder's routine for using ChatGPT or Claude on building code questions: find the section, check the edition, confirm with the building department.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Google Docs Editors Help articles on creating forms, question types, showing questions based on answers, publishing, and managing responses, and the Gemini in Google Forms help article and Workspace Updates posts, all read in November 2026. Sample forms and figures are illustrations.