Letting a Field Team Collect Form Data Without Giving Them Your Account

Short answer: give each person scoped collector access to the specific forms they work on rather than sharing a login. They submit and see their own jobs; they do not see billing, settings, or anyone else's data. As of August 2026 BotForms includes five collectors on Pro at $79/month and unlimited on Business at $199/month.

Every service business hits this. The office builds the forms; the work happens somewhere else. The crew needs to submit completion reports, upload photos and see the jobs assigned to them — and none of that should require handing over the keys.

What people do instead, and why it breaks

Sharing one login. The default, because it is free and takes zero setup. It breaks in three escalating ways: everyone can see everything including other clients and your billing; nobody can tell who submitted what, so any dispute is unresolvable; and removing access from a leaver means changing the password for the entire team, which is enough friction that people simply do not, and former staff keep access for months.

Texting photos and details to the office. Works at two people. At six, it is an unsearchable stream of images with no structure, and somebody spends an hour a day transcribing them into whatever the real system is.

Paper, retyped later. Still extremely common, and the cost is not the paper — it is the delay and the transcription errors. A form completed on site and typed up two days later is a form with two days of decay in it.

Buying a full field-service platform. Sometimes correct. Often an enormous jump in cost and complexity to solve what is fundamentally a permissions problem, and it brings scheduling, dispatch and invoicing modules nobody asked for.

The permissions problem has a permissions-shaped answer.

Scoped collector access

A collector is a person with a login of their own, assigned to specific forms. They can submit to those forms and view submissions for those forms. That is the whole scope.

They cannot see billing. They cannot change settings. They cannot see forms they are not assigned to, which means a subcontractor working for you on one client's job cannot browse another client's intake data. And every submission they make is attributed to them.

That last property is the one that changes daily operations most. "The form was filled in wrong" stops being an anonymous complaint and becomes a conversation with a person. Quality patterns become visible — one crew consistently skipping photo uploads is a trainable problem, and under a shared login it is invisible.

Approach	Sees others' data	Attribution	Removing someone	Setup cost
Shared login	Everything	None	Password change for all	None
Texts and photos	Only what is sent	By phone number	Stop texting them	None
Scoped collectors	Assigned forms only	Per person	Revoke that person	Minutes
Full field-service platform	Configurable	Per person	Deactivate user	Weeks, and a migration

Designing forms your crew will actually complete

Access is the easy half. The harder half is that a form completed on a phone, outdoors, possibly in gloves, is a different design problem from a form completed at a desk.

Assume the worst conditions. Bright sun, one hand, poor signal, a cracked screen. That is the real environment, not the one in your browser preview.

Ask the minimum. Every field is a field somebody types standing up. The instinct to capture everything while you have them there produces forms that get rushed, and rushed data is worse than absent data because you trust it.

Prefer taps to typing. Dropdowns, buttons, checkboxes. Free text is where completion quality collapses in the field, and it is also where you get "done" as a description of the work.

Photos are the highest-value field. For most trades, images are worth more than any text field on the form. Make the upload prominent, allow several, and say explicitly what you want photographed — "photo of the meter before work" gets you the photo; "attach photos" gets you one blurry wide shot.

Timestamp automatically. Never ask someone to enter a time. They will round it, or fill it in later, and the value is then fiction.

Make it work on one screen where possible. Or use steps with clear progress. A long scrolling form on a phone is where field completion rates go to die — multi-step forms that adapt to answers covers the pattern properly, and the step-level visibility is a genuine bonus for spotting where crews stall.

The two-form pattern

The setup that works for most field businesses is two forms, not one.

Form one: intake. Public, on your site. Customer describes the problem, gives an address, uploads photos. This form is optimized for conversion — short, low friction, asking as little as you can get away with.

Form two: completion. Private, collector-only. The technician records what was done, parts used, photos of the finished work, and anything needing follow-up. Optimized for accuracy rather than conversion, because the person filling it in is being paid to.

The two have opposite design goals and mixing them into one form serves neither. Intake fields on the completion form waste a technician's time; completion detail on the intake form kills your conversion rate.

What links them is the job record and, usually, a document. The technician needs the intake details on site, and the practical way to deliver that is a generated PDF per job rather than read access to your whole intake form — it works offline in a basement, which a web dashboard does not. That workflow is in turning every submission into a branded PDF.

Rollout that survives contact with a crew

The technology is the easy part. Adoption is where these projects die, and the failure is predictable.

Start with one form and one crew. Not the whole company. You want to find the problems with five people who will tell you honestly.

Have them fill it in front of you, on their own phone. Not yours, not a demo device. You will learn more in ten minutes of watching than in a month of feedback requests — and you will discover that the field label that was obvious to you means something else to them.

Fix the two things they complain about immediately. Fast response to the first complaints buys you enormous goodwill, and the complaints are usually correct. A field they say is pointless usually is.

Do not run paper in parallel for long. A week to build confidence is reasonable. A month means paper wins, because it is the path of least resistance and you have given people permission to take it.

Explain what happens to the data. "This goes straight to the customer's file so nobody has to call you about it later" gets better completion than "management needs it". People fill in forms properly when they understand who downstream is helped.

Seats, and the cost question

This is where the licensing model matters and it is worth checking before you design a process around it.

If a platform prices per user, a rotating subcontractor pool gets expensive fast, and the workaround people reach for is — inevitably — a shared login, which puts you back at the start.

On BotForms, collectors are included from Pro: five seats at $79/month, unlimited on Business at $199/month, with individual extra collectors available as a $10/month add-on. The practical read: a small fixed crew fits Pro; anything with a large or churning casual roster is generally cheaper on Business than accumulating add-ons. Full limits are on the pricing page.

Worth also checking submission volume rather than just seats. A crew of eight submitting completion forms daily consumes more of a monthly allowance than an office assumes — the arithmetic is jobs per day times crews times working days, and it is usually larger than the guess.

What this does not do

It is not scheduling. Collector access controls who can see and submit which forms. It does not assign jobs, route a route, or tell anyone where to be. If you need dispatch, you need a dispatch tool, and a form platform is not pretending otherwise.

It is not offline capture. A browser form needs a connection at the moment of submission. Most of the time this is fine — a phone finds signal eventually — but if your crews genuinely work in dead zones, that is a real requirement and worth naming before you commit.

It does not fix bad process. If nobody looks at completion forms, collecting them faster changes nothing. Decide what the data is for before you deploy it, or you have built a well-attributed archive that nobody reads. Our piece on which form metrics matter is a reasonable starting point for deciding what you would actually do with it.

Getting started

Build the completion form first — it is the one with a clear owner and an obvious payoff. Add one collector, have them submit a real job from their own phone, and read what comes back. If the data is usable, add the rest of the crew. If it is not, the form needs work before more people touch it.

Collectors are included from Pro. See features for what collectors can and cannot do, pricing for seat limits, or start a 30-day trial and test it with one person before committing the team.