Most teams that outgrow Google Forms have not outgrown the form. The form is fine. The questions are right, people fill it in, the answers land neatly in a spreadsheet.
What they have outgrown is everything after the submit button. Someone has to read row 42, decide something, tell the requester, remember to loop in finance, and then be able to explain the decision six months later. Google Forms has no view on any of that, and it was never trying to.
This post is about where that line falls, because it is a genuinely useful line to know. On one side, Google Forms is excellent and free and you should keep using it. On the other side, you end up being the software.
What Google Forms is genuinely good at
It is fast. You can have a working form in ten minutes with no training and no budget conversation. Everyone already knows how to fill one in. It validates answers, it can send people to different sections based on what they picked, and responses drop straight into Sheets where you can pivot and chart to your heart's content.
For surveys, event RSVPs, quizzes, feedback collection, sign-up sheets, and any situation where you care about the responses in aggregate, it is very hard to beat. If nobody has to act on any individual response, you are already using the right tool.
The line: a response versus a request
A response is data. You read it alongside 300 others, you count it, you chart it, and no single row demands anything of anyone.
A request is a piece of work. Somebody has to pick it up, make a call on it, and somebody else is waiting on the answer.
Google Forms is built for responses. Almost every complaint about it starts at the exact moment a team begins treating responses as requests. The symptoms are consistent enough to be diagnostic:
- Someone added a Status column to the sheet by hand, and a colour code to go with it
- People ask, in a chat thread, whether anyone has looked at row 42 yet
- Responses get forwarded to managers manually, by copy-paste
- There are now two versions of the sheet and nobody is sure which one is current
- One person has quietly become the chaser, and it is most of their week
- Somebody asks who approved a particular request, and the honest answer is "let me search my email"
None of that is a Google Forms failure. It is a tool being used one step past what it does.
What actually breaks
The form branches, but the work doesn't
Google Forms can branch. That branching moves the person filling it in to a different section: pick "Hardware" and you get the hardware questions.
What it cannot do is branch the submission to a different person. If your policy says anything over $5,000 needs finance sign-off, Google Forms will happily collect the amount and then treat a $50 request and a $50,000 request identically. The rule lives in a policy document and in the heads of whoever remembers it, and it gets applied inconsistently, which is the part that eventually causes the problem.
A spreadsheet row has no owner and no clock
A row does not belong to anyone. It does not appear in a queue, it does not have a due date, it does not send a reminder, and it does not notice that its assigned reviewer has been on leave for two weeks.
So the work of remembering falls to a human, and it is invisible work. The requests that sit for a month look exactly like the ones submitted this morning.
There is no way to send it back
This is the one that surprises people. An approver opens a request and finds the quote is missing. In Google Forms there is no "return for changes" — the response is already recorded, unchangeable and complete-looking. So the approver emails the requester, the requester re-submits (now you have two rows), or replies with an attachment that lives only in that inbox. The sheet, meanwhile, says nothing has happened.
Nobody can answer "where is my request?"
The requester cannot see anything after they hit submit. So they ask. And because asking works, they keep asking, and answering those questions becomes a real part of somebody's job. A meaningful share of "our approvals are slow" turns out to be "nobody could see where anything was, so everything got chased."
The record isn't really a record
Sheets have cell history, in the sense that a forensic investigation is possible. What they do not have is a record of who decided what, when, on what basis, and what the request looked like at the moment of the decision. Rows get edited after the fact. Columns get re-sorted. Nothing is tamper-evident.
For a lot of processes that genuinely does not matter. For grant applications, admissions decisions, vendor onboarding, policy exceptions, and anything an auditor or a regulator might one day ask about, it matters a great deal, and you find out which category you were in at the worst possible moment.
In fairness: add-ons and a bit of Apps Script can bolt approvals and notifications onto Google Forms, and for a single simple process that is a completely reasonable thing to do. The catch is that you now own a script. It routes one way, it breaks quietly, it is understood by exactly one person, and every new rule is a change request to that person.
What the next step up looks like
The useful version of "more than a form" is not a heavyweight process suite that takes a quarter to roll out. It is a form builder that also knows what happens after submit.
That is what we built stepbase to be. The form part stays familiar: drag fields on, including file uploads and repeating tables for line items, show or hide fields based on earlier answers without writing formulas, and feed dropdowns from your own lists of cost centres, sites, or teams so the options are never stale. Share it as a public link, a QR code, or an embed, with no account needed to submit, and set links to expire or be single-use if you need to.
The difference is the second half. You draw what happens after submit: the steps, who holds each one, and the rules that pick the path.
Concretely, an equipment request might run like this:
- Anyone submits the form from a link on the intranet. No login.
- Under $1,000 with a valid cost centre goes straight to IT to fulfil.
- Over $1,000 goes to the requester's manager first, then finance.
- Finance opens it, sees the quote is missing, and sends it back with a comment. The requester gets a notification, adds the file, and it returns to finance — same request, same thread, no duplicate row.
- Every approval is recorded with who, when, and what the form said at that moment.
- The requester can see where it is. So can you.
- At the end of the quarter you can see that approvals average 3.4 days and that they pile up at finance, not at managers, which is the kind of thing everyone has an opinion about and nobody has evidence for.
Nothing there is exotic. It is just the process people are already running by hand, written down somewhere the system can actually execute it.
And the decisions that don't need a person
Some steps in these processes are not really decisions. They are sorting: what category is this, is this complete enough to review, is this the routine case or the unusual one, does this description match the policy or not.
Those can go to an AI step, and the guardrails matter more than the capability. It only runs on the steps you place it on. It reads only the fields you allow it to read. You write the instruction in plain language, and you set a confidence bar — below that bar, or if the call fails, the step goes to the person or team you nominated instead. Every AI decision lands in the audit trail with its reasoning and its confidence, so it is reviewable rather than mysterious.
The useful framing is not "AI approves things." It is that the boring 70% stops queueing behind the 30% that genuinely needs judgment.
When you should stay on Google Forms
Stay where you are if:
- You care about responses in aggregate, not individually — surveys, feedback, research
- Nobody has to make a decision on any single submission
- The process is one step: collect, done
- It is a one-off, and the sheet is the deliverable
- Exactly one person reviews everything, it takes them a minute, and it is working
Switching tools has a cost, and a working process does not owe anyone an upgrade.
A quick way to tell
Count how many of these are true of your form today:
- A person has to make a decision on each submission
- Different answers should go to different people
- Something bad happens if a submission sits too long
- People ask you for status updates
- You would need to prove, later, who approved something and why
- Somebody maintains a spreadsheet column that tracks state by hand
One or two, and you can live in Google Forms with a bit of discipline. Three or more, and the discipline is the job — you have become the routing engine, the reminder service, and the audit log for a process that could be doing that itself.
Moving without a migration project
You do not have to import anything. Point a new form at the same audience and run it alongside the sheet for a couple of weeks; the responses you already collected stay exactly where they are.
Building it is closer to Google Forms than to a workflow platform: you can describe the process in a sentence — "when someone submits an expense claim, anything over $500 goes to their manager first, then finance approves it" — and get a draft of the form and the steps to edit rather than a blank canvas to stare at. Or start from a ready-made template for purchase requisitions, leave requests, vendor onboarding, or grant applications.
The free plan covers 5 users, 3 flows, and 50 requests a month, with no card required, which is enough to run one real process end to end and see whether the difference is worth it for you.
If your form is really a request, it deserves better than a spreadsheet row and a good memory.