Financial Advisor Intake Form Templates and Field Checklist
Three copy-ready financial advisor intake form templates — prospect discovery, new-client fact-find and risk-profile — plus a field checklist and compliance-aware best practices.
In short
A financial advisor intake form should match its job. A public consultation-request or discovery form belongs on your website and should stay short — name, email, phone, a rough sense of what the prospect wants help with, and a preferred time to talk — because a public page is the wrong place to gather sensitive financial detail. The deeper new-client fact-find, which captures household, income, assets, liabilities, goals and existing accounts, belongs behind secure onboarding after someone has agreed to work with you, not on a form anyone can load. A risk-profile questionnaire sits alongside the fact-find and turns a client's comfort with volatility into a documented score you can act on and defend. This article gives three ready-to-copy layouts as bracketed field lists, a checklist of what to ask and why, and the practical rules that keep intake compliant — collect the minimum on public forms, gate sensitive data behind consent and secure delivery, show clear disclosures, and archive every submission per your firm policy. None of it is legal advice for your specific situation; treat the field lists as drafts your compliance function reviews before you publish.
Key takeaways
- Use two intake tiers — a short public discovery form to start conversations and a deeper fact-find behind secure onboarding once someone becomes a client.
- Keep public forms minimal — name, contact, a topic and a time — because a page anyone can open is the wrong place to ask for account numbers, income or Social Security details.
- Ask each field for a reason — capture what advances the engagement or meets a suitability obligation, and drop anything you cannot justify collecting.
- Pair the fact-find with a risk-profile questionnaire so a client's stated comfort with volatility becomes a documented, defensible score.
- Show consent and disclosure language on the form, deliver sensitive submissions securely, and archive every response per your firm recordkeeping policy.
Some links to tools we rate — including HighLevel — are affiliate links. If you start a trial through them we may earn a commission, at no extra cost to you. We only recommend tools we would set up for our own clients.
Match the form to its job. A public financial advisor intake form that starts conversations should be short — name, contact, a rough topic and a time to talk — because a page anyone can open is the wrong place to ask for account numbers or income. The deeper fact-find that a plan actually needs belongs behind secure onboarding, after someone has agreed to work with you. And a risk-profile questionnaire sits alongside that fact-find to document how much volatility a client can live with. Below are three ready-to-copy layouts as [square-bracket] field lists, a checklist of what to ask and why, and the compliance-aware rules that keep intake safe.
One principle sits above the rest: collect the minimum on anything public, and gate sensitive detail behind consent and secure delivery. These field lists are drafts, not finished forms — route the fields and the disclosure wording through your compliance function before you publish, and archive every submission per your firm policy. Nothing here is legal or compliance advice for your specific situation.
Why split intake into two tiers?
The mistake that sinks advisor intake is asking one long form to do two jobs. A stranger who found you through an article or an ad will not type their income, account balances and dependents into a form before they have spoken to you — and you should not want them to, because a public page is not a safe place for that data to live.
So run two tiers. The public tier is a short discovery or consultation-request form whose only goal is to qualify a prospect and get them on a call. The secure tier is the new-client fact-find, sent as a gated link or portal step once someone becomes a client, where the detailed and sensitive information belongs. Keeping the two apart is what lets you market an open form to the world while the data that carries real risk only moves after a relationship and the right protections exist. For the broader mechanics of turning form traffic into booked calls, see how to capture leads with forms.
Template 1 — Prospect discovery / consultation-request form
This is the public form. It lives on your website and does one thing: start a qualified conversation. Keep it to five or six fields, because every extra field costs completions and a stranger has no reason to over-share yet.
- [Full name]
- [Email]
- [Phone]
- [What can we help you with?] — short choice list: retirement planning / investing / getting organised / a specific event / other
- [Approximate investable assets] — optional band, e.g. under 100k / 100k–500k / 500k–1M / 1M+
- [Preferred time to talk] — or a booking link
- [Anything you'd like us to know?] — optional free text
- [Consent checkbox] — a short line acknowledging your privacy notice
Notice what is not here: no Social Security number, no date of birth, no account numbers, no exact income. Those do not belong on a public form. The asset band is coarse on purpose — most people will pick a range when they will not type a figure, and a range is enough to qualify or route.
Template 2 — New-client fact-find intake
This is the deep intake, and it belongs behind secure onboarding — a gated link or portal step you send after someone has engaged you and consented, not a page anyone can load. Group it so it feels manageable, and only collect the truly sensitive identifiers through an encrypted channel.
- Household — [Full legal name], [date of birth], [marital status], [dependents and ages]
- Contact and identity — [address], [preferred contact method], [secure identifiers via encrypted upload only]
- Employment and income — [employer], [occupation], [annual income], [expected changes]
- Assets — [cash and savings], [investment accounts], [retirement accounts], [property], [business interests]
- Liabilities — [mortgage], [loans], [credit balances]
- Existing accounts and policies — [current providers], [insurance], [estate documents in place]
- Goals — [primary goals], [time horizons], [target retirement age]
- Risk and preferences — [investment experience], [risk tolerance], [values or exclusions]
- Consent and authorisations — [engagement acknowledgement], [data-use consent]
Only ask for what a plan needs. If a field does not advance the engagement or meet a suitability obligation, leave it off — every sensitive field you collect is something you then have to safeguard and justify.
Template 3 — Risk-profile questionnaire
A risk profile turns a client's comfort with market swings into a documented, defensible score. Capture both willingness to take risk and capacity to absorb losses, because they are not the same thing. Keep the language plain.
- [Time horizon] — when do you expect to draw on this money?
- [Reaction to a decline] — if this portfolio fell 20% in a year, would you sell, hold, or buy more?
- [Income stability] — how secure is your income?
- [Loss capacity] — how much of this could you lose without changing your plans?
- [Experience] — how familiar are you with investing?
- [Goal priority] — is growth, income, or preservation most important?
- [Resulting risk score] — recorded and stored with the client file
Store the result with the rest of the client record so it is there when you need to explain a recommendation later. It is a suitability signal as much as a planning tool.
Which fields matter, and why?
The checklist below covers the fields advisors ask most, why each earns its place, and whether it belongs on a public form at all. Use it to prune anything you cannot justify.
| Field | Why you ask | Required on public form? |
|---|---|---|
| Full name | Address the person and open the record | Yes |
| Email and phone | Reach them and confirm the enquiry | Yes |
| Topic / need | Qualify and route the conversation | Yes |
| Preferred time to talk | Move straight toward a booked call | Recommended |
| Approximate asset band | Coarse qualification without over-collecting | Optional |
| Exact income and balances | Needed for planning and suitability | No — onboarding only |
| Date of birth | Plan timelines and identity | No — onboarding only |
| Social Security / account numbers | Account setup and identity checks | No — secure onboarding only |
| Goals and time horizons | Shape the plan and recommendations | No — onboarding only |
| Risk tolerance | Suitability and portfolio design | No — risk questionnaire |
| Consent / disclosure acknowledgement | Records that the person agreed to your terms | Yes |
What are the best practices for advisor intake?
A few rules keep intake both effective and compliant.
Keep the public form short and the sensitive form gated. The public tier exists to earn a conversation, so it should never ask for anything you would not want sitting in a web form. The fact-find and its identifiers move only through secure onboarding.
Show consent and disclosures on the form. A short, honest line about what you collect, why, and how it is used — linked to your privacy notice — belongs on every form. It builds trust and it documents agreement.
Deliver and archive securely. Route submissions into one system where they are access-controlled and retained, rather than scattered across inboxes, and keep each response for as long as your firm and regulator require. Many advisors let a CRM capture and timestamp responses automatically, which creates a consistent archive with no manual filing.
Respond fast. Speed to the first reply is often what wins the client, so the moment a discovery form lands, the prospect should get a confirmation and a way to book. After the call, keep the momentum with the right message — see these financial advisor email templates for onboarding and follow-up wording.
Where should you embed the form?
Put the discovery form where intent is highest: a dedicated book a call page, beside your service descriptions, at the close of relevant articles, and as the destination for ads and email calls-to-action. Use the same form across those spots so every submission lands in one place. The fact-find, by contrast, is never a public page — send it as a secure link once someone becomes a client.
What tool should host the form?
You can run intake with a standalone form builder that emails you each submission, and for a solo advisor that may be enough. The limitation shows up after the form: someone still has to move the lead into a CRM, send the confirmation, and chase the booking.
HighLevel is one option that hosts the form and routes each prospect straight into a CRM with automated follow-up — a confirmation, a booking link and a pipeline stage triggered the moment someone submits. Honestly, it is more than a single advisor collecting a handful of enquiries a month needs; a simple form tool will do. But if you are also automating booking, reminders and nurture, consolidating those onto one platform can be worth it, and you can start a free HighLevel trial to see whether it fits your practice. Whatever you choose, hold it to the same standard: secure delivery for sensitive fields and a proper archive of every response.
For more on building the systems around advisor intake, browse the Financial Advisor & RIA Agencies hub, and see pricing if you want help getting the whole capture-to-booking flow live.
Frequently asked questions
What is a financial advisor intake form?
What fields should a financial advisor intake form include?
What is the difference between a public form and secure onboarding?
Is it safe to collect Social Security or account numbers on a web form?
How do I make a financial advisor intake form compliant?
Where should I embed a financial advisor intake form?
What is a risk-profile questionnaire and do I need one?
How long should a prospect intake form be?
Should I collect income and asset detail on the first form?
How should I store and archive intake form submissions?
Can I automate what happens after someone submits an intake form?
Are these intake form templates compliant to use as-is?
About the author

Founder, GHL Spark
Farhad is the founder of GHL Spark, where he builds and white-labels GoHighLevel SaaS platforms for agencies and SaaS operators. He writes about the parts of GoHighLevel that actually break in production — A2P registration, onboarding, support load and automation.
More from Farhad