Client onboarding form, shared folder or portal?
Choose a client onboarding setup by comparing structured answers, file storage and review status. Includes a practical workflow and trial checklist.
Forms, shared folders and client portals solve different parts of onboarding. A form collects structured answers. A folder stores files. A portal may bring requests and status into one place. The useful choice depends on where your projects lose information and whether the proposed setup makes the next action clearer for the client and the delivery team.
Start with the failure you want to remove
Review a recent project that started late or required repeated clarification. Was the problem an unanswered question, an inaccessible file, an unapproved draft or uncertainty about who should respond? Each suggests a different improvement. Buying a portal will not automatically resolve a missing internal approver.
If the main issue is inconsistent answers, a short form with well-written questions may be enough. If files are scattered, a structured shared folder may help. If requests arrive over time and must be reviewed individually, a checklist with response status can make the workflow easier to manage.
Write the problem in a sentence before evaluating tools: “We cannot tell which page copy is approved” is actionable. “Our onboarding needs to be more professional” is too broad to test. The question-writing guide can improve any of these setups without requiring a new product.
Compare what each option actually does
A form is good at gathering a consistent first set of answers. It may be less convenient when the client needs to return repeatedly with partial information. A folder makes files available but does not inherently explain which asset is missing, who owns it or whether the team has reviewed it.
A dedicated collection workspace can connect requests, responses and review status. Check its actual capabilities rather than assuming that the word “portal” includes file hosting, project management, e-signatures and billing. A focused tool can be useful without doing all of those things.
For Gather, files remain in your chosen storage service; the product organizes answers and file links. Paid client response links support submitting those inputs for your review. It is a single-owner account workflow, so verify the current plan details if your evaluation depends on separate team seats or permission roles.
Scroll sideways to see all columns.
| Job | Simple starting point | What to check |
|---|---|---|
| Consistent initial answers | Form | Can clients save or return with missing details? |
| Asset storage | Shared folder | Are permissions and versions clear? |
| Ongoing input collection | Request checklist or portal | Can you distinguish received from reviewed? |
| Final project handoff | Reviewed summary | Does each unresolved item have an owner? |
Reduce the number of places the client must inspect
A workable setup can use more than one tool, but it needs one clear starting point. Tell the client where to find the current request list and where files should live. Avoid creating a form, a folder, a spreadsheet and an email thread that each contain a different version of the outstanding work.
For example, the checklist can be the current request register, while a shared folder holds the approved assets. Each checklist item links to the relevant file. The email points back to the checklist rather than restating an increasingly stale list. This gives every tool a defined responsibility.
Think about the client’s effort too. If a request requires copying the same information into several systems, the workflow may be optimized for your internal reporting at their expense. Test the process with someone unfamiliar with it and watch where they hesitate.
Run a trial with incomplete inputs
A perfect submission is an easy demonstration. Test a more realistic one: the client knows the business goals, has only half the copy and cannot access the logo folder. Can they submit what they have? Can you ask for one correction without making them complete the whole process again?
Then test the review side. Mark a file received, discover that it is the wrong version and request a replacement. Confirm that the team can still see what is outstanding. Check whether the system preserves enough context to avoid asking the same question twice.
Use the client kickoff template as the sample project. It gives the comparison a consistent set of inputs. Measure success by whether the client knows what to do next and whether the delivery owner can explain what is ready.
- Submit a partial response.
- Open a file link as the intended recipient.
- Request a correction to one item.
- Identify the remaining blockers without reading every email.
Choose the smallest setup that stays accurate
For a one-off project with few inputs, a form and a carefully maintained folder may be entirely adequate. As requests become more numerous or iterative, a dedicated collection process may reduce the work of chasing and reconciling answers. The threshold is a workflow judgment, not a universal client-count rule.
If you switch, define how the old records will be retained and which system becomes authoritative. Keep the first rollout small enough that you can correct confusing questions before reusing them across every project. Reuse the structure, but remove previous client answers before creating the next checklist.
Try Gather’s free website kickoff checklist with your next set of inputs. Use the repeatable kickoff guide to refine the routine. The best onboarding setup is the one that continues to show the truth after the first tidy demonstration.
