meetergo
A generic form template on the left being cut down and rebuilt into three specific forms on the right: intake, consultation request and feedback

Google Form Templates: How to Adapt 3 for Client Work

|13 min read
Dominik Rapacki
Dominik Rapacki
Dominik Rapacki is the CEO and founder of meetergo.com, driving GDPR-compliant scheduling innovation. Featured in leading podcasts, he’s a recognized expert in SaaS, sales, and digital transformation

Key Takeaways

  • The gallery has no template for the three jobs people usually want. Client intake, consultation requests and post-meeting feedback all get built by editing something adjacent, so the template you start from matters less than the edits you make to it.
  • Branching decides your layout. Section logic only works from Multiple choice and Dropdown questions (checked 2026-11-01), so anything you route on has to be a closed option set, not a text box.
  • File upload questions force a Google sign-in. Respondents must sign in to a Google Account to answer one, which rules the field out for most client-facing intake.
  • Sections are pages, so one template can serve several paths. You can add up to 75 sections and 300 pieces of content in one form, more room than any gallery template uses.
  • Decide the handoff before the questions. A form that collects answers but triggers no booking, contract or reminder leaves the real work in your inbox.

You will not find a client intake template in the Google Forms gallery, or a consultation request template, or a post-meeting feedback template. The gallery is built for personal and generic office use, so anyone hunting google form templates for client work ends up opening the closest match and rewriting most of it.

That rewriting is the real skill, and nobody documents it. Below are the five edits any gallery template needs, plus example questions for the three workflows the gallery skips.

Skip this if: you need the form to take a deposit, carry a signature, or drop the respondent onto a calendar at the end. Those are not editing problems, and the last two sections explain why.

The gallery sits behind the template button on the Forms home screen, grouped into personal, work and education categories. Counting them is harder than it looks: Google's help documentation doesn't publish the gallery contents, which is why third-party listicles claim anywhere from seven to twenty-plus. Treat any count you read, including here, as a snapshot.

The names that recur across independent write-ups are contact information, RSVP, party invite, event registration, event feedback, job application, order form and customer feedback. Three are worth opening for client work: contact information as the base for intake, event registration for a consultation request, customer feedback for a post-meeting form.

All of them draw on the same twelve question types: short answer, paragraph, multiple choice, checkboxes, dropdown, file upload, linear scale, rating, multiple choice grid, checkbox grid, date and time (checked 2026-11-01). Every template is a rearrangement of those twelve. That's the real ceiling, and knowing it beats an hour of styling.

Reuse is the first wall people hit. A nine-comment thread in r/googlesheets describes wanting a repeatable fillable form holding customer name, quantity, material and machine program numbers; the replies drift into spreadsheet workarounds fast. Forms has no save-as-template of its own.

The order here matters. Doing the sign-in decision last is how people end up rebuilding a form they already sent out.

Cut it down to the fields you will act on

Gallery templates are padded for generic use. Delete every question whose answer would not change what you do next. A contact information template typically carries name, email, address, phone and a comments box; a consulting intake needs the first two and rarely the third.

The test is specific: name the action each answer triggers. If you can't, cut the question.

Convert anything you want to route on into a closed option set

Section logic is only available on multiple choice and dropdown questions (checked 2026-11-01). No branching on a text answer, no number comparison, no AND/OR condition builder. So if people who pick "existing client" should see a different page from people who pick "new enquiry", that question has to be multiple choice before anything else works.

Writing the option set is its own job, and the patterns in our guide to multiple choice survey question examples transfer directly. Options have to be exhaustive, because a respondent who fits none of them picks the nearest wrong one.

Split the form into sections, one per path

Each section starts on a new page, and you can add up to 75 of them with up to 300 pieces of content (checked 2026-11-01). One form can serve three audiences without showing anyone questions meant for someone else.

A workable shape for intake: section one asks who they are and what kind of enquiry it is, then routes to section two (new client, longer), section three (existing client, shorter) or straight to submit. Set the next-section destination at the bottom of each section so nobody falls through.

Decide who has to sign in

Three settings quietly force a Google account on respondents, and each one costs completions:

  • File upload questions. Respondents must sign in to a Google Account, and the question isn't available if the form sits in a shared drive or your administrator has data loss prevention turned on.
  • Limiting to one response per person. Requires sign-in by design.
  • Workspace defaults. Access is restricted to people inside your organisation until you turn that off in the response settings. A form sent to external clients without that change won't open for them.

Email capture gives you verified or responder input (checked 2026-11-01). Verified pins the response to a confirmed Google account; responder input asks them to type it, which is what you want for client work. Before promising anyone confidentiality, our walkthrough of when a form is genuinely anonymous covers the metadata side.

Set the destination and the notification

A form with no response notification is a form you check on Tuesdays. Point responses at a sheet, turn the notification on, then check who else can read them: any editor you add can change any part of the form including the responses and where they're saved. On an intake form holding commercial details, keep that list short.

Giving respondents their own copy is a separate setting and easy to miss. We covered it in sending respondents a copy of their responses.

Client intake: example questions

Start from the contact information template, delete the address and comments fields, and build toward something you could hand a new client before any call.

QuestionYour name
TypeShort answer
Why it's that typeNothing routes on it
QuestionWork email
TypeShort answer
Why it's that typeKeep it separate from the collected address
QuestionCompany and role
TypeShort answer
Why it's that typeOne field, not two
QuestionWhat do you need help with?
TypeMultiple choice
Why it's that typeThis is your routing question
QuestionWhich of these apply?
TypeCheckboxes
Why it's that typeScope signals, multi-select
QuestionTarget start date
TypeDate
Why it's that typeSorts your pipeline for free
QuestionBudget range
TypeDropdown
Why it's that typeRanges, never a number box
QuestionAnything we should know before we talk?
TypeParagraph
Why it's that typeThe one open question

Eight questions, one page of branching, and the budget dropdown doing most of the qualifying. Keep the open-ended question to exactly one; our notes on open-ended survey question examples explain why each extra free-text box costs you submissions.

Eight is not arbitrary. Baymard Institute's checkout research from June 2024 found the average online checkout carried 11.3 form fields and argued that most flows need only eight, with 17% of shoppers abandoning over complexity. Client intake is a different context and the number won't transfer exactly, but the direction holds.

What this form cannot do is carry a signed engagement letter or take a deposit. Both live outside Forms, and pretending otherwise is how intake turns into a four-email thread.

Consultation requests: example questions

A consultation request is an intake form with a scheduling problem bolted on, so the event registration template is the better starting point. It already has the shape of "tell me about yourself, then pick something".

  • What kind of consultation are you requesting? Multiple choice, and this one branches. Different consultation types need different follow-ups.
  • Have you worked with us before? Multiple choice. Returning clients skip the whole discovery section.
  • Which days generally work? Checkboxes, not a date question. You're collecting a window, not a commitment.
  • Preferred time of day Dropdown, three or four buckets. Exact times are a calendar's job.
  • What would make this consultation worth your time? Paragraph, one box, the most useful answer on the form.

Forms will not show your availability, hold a slot, or confirm anything. You get a request, then somebody writes back with three options. The prompts in our discovery call script and questions template are a better use of your time than adding more questions to the form.

Post-meeting feedback: example questions

The customer feedback template is close to usable, which makes it the one most people over-edit. Resist. Post-meeting feedback has a response-rate problem, not a question-design problem, and the fix is brevity.

  • How useful was this meeting? Linear scale, 1 to 5, labelled at both ends.
  • Did we cover what you came for? Multiple choice: yes, mostly, no.
  • What should we do differently next time? Paragraph, optional.
  • Is there a next step you're waiting on from us? Short answer, optional.

Four questions, under ninety seconds, sent the same day. Two optional on purpose: the scale and the coverage question trend across meetings, and the open boxes explain it when a number moves. Our longer treatment of client feedback surveys covers what to do with the answers.

Don't gate this one behind a sign-in. That setting is what kills post-meeting response rates.

Some of the limits are editing problems. These aren't:

  • No payments. There's no way to take a deposit or a fee inside a form, so no-show risk stays where it was.
  • No signature. An engagement letter or consent form can't be signed in the form, only attached to it, which means a file upload and a Google sign-in.
  • No booking. Collecting availability preferences is not filling a calendar slot.
  • Styling is limited to themes. Hence third-party workarounds like the styling tool discussed in a nine-comment thread in r/GoogleSitesNinjaClub. That puts an external script between you and your client data, which is a decision worth making deliberately.
  • Embedding has conditions. You can copy embed HTML into a site or blog, but a form containing a file upload question, a rating question, an image in a question or option, or a secured quiz can't be embedded in an email (checked 2026-11-01). A seven-comment thread in r/smallbusiness shows that friction for someone who wants a submittable form on their own site.

Hitting three or more of these means the template was never the problem. Our rundown of Google Forms alternatives and the wider field of online form creators are the better next read.

Tools that close the handoff

meetergo is a Cologne-built scheduling and client-pipeline tool with coverage across consulting, sales, healthcare, legal and other verticals, and its forms are built to end at a booking rather than a spreadsheet row. For the three workflows above, two things matter: the field library, and what happens after submit.

25+ field types, including the ones Forms doesn't have

Text, rating and yes/no sit alongside signature, file upload, IBAN and bank details, GPS location, image upload with camera capture, and a composite contact field taking name, address, phone and email in one block (checked 2026-05-08). The signature field is what removes the attach-a-PDF step from intake.

Conditional logic that reads more than two question types

Show and hide fields based on previous answers using AND/OR operators with EQUALS, CONTAINS, BLANK and GREATER THAN comparisons, evaluated in the browser. A numeric budget field can drive branching, which a dropdown workaround only approximates. At the end of a multi-step form, those same answers route the respondent to the right team member, calendar or service, so a consultation request arrives as a booked slot rather than a request to answer.

A meetergo routing form builder showing conditional rules that send different answers to different hosts
Conditional rules read the answers and decide who the respondent lands with.

Fortified Electronic Signature on the form itself

eIDAS-aligned signing with email one-time-password verification, SHA-256 tamper detection on every signed PDF, and a full audit trail. Paired with the e-signature app and deposit collection, that covers the two things no gallery template can do.

A meetergo form with typed intake fields and a signature field on the same page

One thing that matters for client intake specifically: meetergo forms are 100% GDPR compliant, with servers in Europe and no US corporate parent in the chain holding your clients' answers. Nobody signs in to a third-party account to upload a document either, which removes the sign-in trade-off entirely.

Honest limitations. There is no Google Forms import: nothing carries a gallery template, its questions or its responses across, so switching means retyping. meetergo also ships no browsable template gallery comparable to Google's, so you start from a blank form. And multi-step forms, funnels and smart lead routing sit on the Suite tier at €29.90/mo rather than the free plan (regular €34.90, see current pricing). If all you need is eight questions landing in a sheet, Forms is the right tool and you should stay there.

For consultancies juggling several engagements, the pattern worth testing is intake and scheduling in one step. meetergo's professional services workflows are built around it, and the same field library powers its survey tool for feedback. Start free with meetergo to try the routing step; no credit card required.

Common mistakes

Styling the template before cutting it. Theme colours are the most visible edit and the least valuable. Delete questions first; half the design work disappears with them.

Using a paragraph question for something you need to sort by. Budget, region, service type and urgency all end up as free text in forms built from gallery templates, and none of them can drive branching or sort cleanly. Our list of survey questions worth reusing beats inventing them.

Adding a file upload in case somebody needs it. One optional upload field turns your whole client-facing form into a sign-in-gated form. If you need documents, collect them in a second step after the conversation.

Sending one form to new and returning clients. Returning clients abandon discovery questions they've already answered, and that abandonment reads as disinterest in your pipeline. Two sections and one routing question fix it.

Treating the submission as the finish line. The gap between a response landing in a sheet and someone being booked is where intake forms leak. Close it with automated reminders or a routing form, but decide before you send.

100% GDPR compliant

Booking + video conferencing in one tool.

No downloads.No extra costs.Set up in 30 seconds.
Use for free

FAQs

Can I create my own Google Forms template?

There's no save-as-template function. The native equivalent is adding a question, choosing import questions, picking a form you already built and selecting the questions you want (checked 2026-11-01). Most people keep a master form and duplicate it.

How do I share a template-based form with a colleague?

Adding them as an editor lets them change the form, and it also lets them see and edit the responses and where those are saved. If they only need to fill it in, send the responder link or the shortened URL instead (checked 2026-11-01).

How do I stop respondents needing a Google account?

Remove any file upload question, don't limit responses to one per person, and in a Workspace org turn off the restriction to users inside your organisation under the response settings.

How many questions should a client intake form have?

Eight or fewer on the first page, everything else behind a routing question. The real limit isn't the platform's 300 pieces of content, it's the point where a respondent decides to email you instead.

Can a Google Form book an appointment at the end?

No. It collects preferences, and somebody still converts those into a calendar invite. Forms that end on a live availability view are a different product category, and our standardised form patterns piece covers where that boundary sits.

Pick the closest template, delete two-thirds of it, make your routing question multiple choice, and check the sign-in settings before you send a link. Then decide what happens after submit, because no template in any gallery will choose that for you.

See meetergo more often on Google

One click marks meetergo as a preferred source. Our articles then show up more often in your search results, in AI Mode and in AI Overviews.

Make us preferred on Google
GDPR-compliant. Hosted on EU servers.

Replace five tools with one. Add only the apps you need.

Start with scheduling. Turn on forms, video, CRM and AI notes only when they fit your workflow.

No credit card required. Cancel anytime.