Why intake forms do not belong on your website

Published 2026-06-30 · Updated 2026-09-02 · Mercury Media

A contact form that asks about symptoms is a records problem waiting to happen. Here is where the line sits and why.

The line, and where it sits

A website form should collect enough to route a person to the right clinician and nothing more. Name, email or phone, preferred format, a general reason for getting in touch, and the best way to reply. That is the whole list for a solo practice.

The moment a form asks about symptoms, diagnoses, medication, substance use, risk or history, it has stopped being a contact form and started being a clinical record. Records belong in your practice management system, which is built to hold them, encrypted, auditable and covered by an agreement between you and the vendor.

Why this matters more than it sounds

A form submission on a typical website travels through a form plugin, an email service and your ordinary inbox, and it sits in all three. None of those were designed to hold clinical information. If a client later asks for their record, or a college asks how their information was handled, an answer that involves an email inbox is not a good answer.

There is also a practical problem. Information that arrives before a therapeutic relationship exists is information you now hold without a clear basis for holding it. It has to be retained, protected and eventually destroyed on a schedule, whether or not that person ever becomes a client.

PIPEDA, provincial legislation and where the data lives

Canadian practices work under PIPEDA and, depending on the province, under provincial privacy legislation as well. Never name American health privacy legislation on a Canadian practice site. It does not apply to you, and it is the fastest way to signal that your policy pages were copied from a template built for another country. It turns up on a surprising number of them.

Where the information is processed matters too. A great many website forms pass submissions through an American service on the way to the practice inbox. For most businesses that is unremarkable. For a counselling practice it is a detail you would rather not have to explain. Canadian hosting and Canadian form processing remove the question entirely, and they let you say so on your privacy page, which is worth something to a cautious reader.

What to do instead

Keep the website form short

Four or five fields. Make the reason field a general one, and label it in a way that tells people not to write clinical detail. A line under the form saying that this is not a secure channel and not for urgent matters does more good than any amount of policy text elsewhere.

Send intake to the practice system

Jane and its equivalents have intake forms designed for the job. They are completed after booking, inside an account, attached to the correct client file. The website's role is to explain that this is what happens, so nobody is surprised.

Say it on the digital communications page

Every practice should have a page covering which channels are used and what each is appropriate for, that email and text are not secure and are not for emergencies, how quickly you reply, which video platform you use and where its data is stored, how digital contact is recorded, social media boundaries, and how a client opts out of a channel. It is one of the most useful pages on a practice site and almost nobody has one.

Group practices have one more problem

A group practice inquiry legitimately needs more information than a solo one, because it has to be routed. Service, format, location, clinician preference, general availability and funding route are all reasonable, and none of them are clinical. That is the distinction to hold on to: routing information is administrative, and history is clinical.

Where those enquiries land matters as well. A shared inbox that four people can read is a different privacy position from one administrator with a named account, and it should be described accurately on the privacy page rather than glossed over.

What a client can ask you for

A client can ask for their record, and you have to be able to produce it and say where it has been. That is straightforward when everything clinical lives in one system and the website holds nothing but a routing message that was deleted after the enquiry closed. It becomes awkward the moment part of the history is sitting in an inbox and part is in a form plugin database nobody has looked at since it was installed.

Your privacy page should be able to answer four questions without hedging: what the website collects, where it goes, how long it is kept, and who can read it. If you cannot answer those four about your own contact form, the form is collecting too much.

The short version

Collect the minimum, keep it in Canada, say plainly that the form is not secure, and move anything clinical into the system built to hold it. None of this makes the website less useful. It makes it defensible, and it removes a class of problem that is genuinely unpleasant to deal with after the fact.

Mercury builds inquiry systems to this standard as part of every project. The services page covers what is included, and you can start a project with a thirty minute call at no charge.

See it built

Grove, a complete practice site

Warm and open, with a marigold block beside a full-height portrait. Everything described above is already in place in it, including the fee block, the funding routes and the booking page.

Look at Grove

Keep reading

Other guides

More answers in the FAQ

Find out what your practice website should be

A thirty minute call at no charge. You come away with a recommended structure, a fixed price and an honest answer about whether Mercury is the right studio for your practice.