Use a native Notion form for client intake when you want a short request to become a record in your workspace. Create it against a private intake database, ask for a contact email, and give every new request an owner and a next action. The form handles collection; you still need to decide who reviews the request and how the client hears back.
I would start with a separate intake database rather than a form attached directly to the main client directory. A prospective client can describe a project without becoming a client record, seeing other clients, or being treated as a confirmed booking.
Decide what the form needs to collect
Ask only for information that changes your next decision. For an initial freelance inquiry, that is usually the requested work, an email address, and enough context to decide whether to continue the conversation. A detailed onboarding questionnaire belongs later, when the scope and working relationship are clearer.
| Client-facing question | Database property | Why collect it? |
|---|---|---|
| What do you need help with? | Request — Title | Give the record a useful name. Make this required. |
| What email should I reply to? | Contact email — Email | Provide a reply destination. Make this required. |
| Your name or business | Client name — Text | Help identify the inquiry; require it only if your review needs it. |
| Which service are you considering? | Service — Select | Route different kinds of work without asking the client to choose an internal owner. |
| What date are you aiming for? | Desired date — Date | Check availability. Label it as a preference, not an accepted deadline. |
| What budget range are you considering? | Budget range — Select | Support qualification when a range affects whether you can take the work. |
| Anything else I should know? | Brief — Text | Capture optional context without turning the first contact into a long assignment. |
These use Notion’s documented database property types. Keep Intake status, Owner, Next action, Next review, Reply sent, and Retention review as internal properties, outside the list of form questions. They describe your work after submission.
Leave attachments out unless they help you qualify the request. If files are necessary, explain which material you need and tell clients to omit passwords, payment details, and unrelated private records. Check upload constraints against the workspace plan: Notion’s Free plan lists a 5 MB file-upload limit.
Create the form against the right database
Create and customize the form in Notion’s desktop or web app; clients can fill it out on desktop or mobile. All Notion plans include forms. Choose the route that matches what you already have.
If you do not have an intake database yet
Start on an internal page that only your intake reviewers should use. Type /form and select Form. Notion connects the new form to a database and creates a Respondent property. That recorded identity does not replace your Contact email question: respondents to a public form are automatically anonymous.
Add the client questions from the model above. Use + underneath the last question to add another question; each question connects to a database property. Give the form a title such as “Project inquiry” and a description explaining that you will review the request before confirming scope or availability. Add the internal review fields in the Responses table after the questionnaire is ready.
If you already have an intake database
Use the original database as the destination. Adding a form to an existing database requires Full access; editing the form requires Can edit or Full access. This is a permission prerequisite, separate from whether your Notion plan includes forms.
- Open the intake database. Select + beside its views, or open the current-view dropdown and choose Add view.
- Select Form, then the Create {#} questions option. Review the questions generated from the database properties.
Configure either form before sharing it
- Review the question list against your intake plan. Internal workflow fields belong in the response database, and the form shouldn’t ask the client to assign an owner or choose a review status. If the form generated a question for an internal field, open that question’s ••• → Delete question option to remove it from the questionnaire.
- Give the form a clear title and a short description. Explain what happens after submission and that sending a request does not reserve a date.
- Open each question’s ••• menu to set Required, add a description, or adjust its question type. Use Long answer for a brief that needs more room.
- If the question should read “What email should I reply to?” while the stored field stays “Contact email,” turn off Sync with property name. Otherwise, changing the question’s wording also renames its database property.
- Select Preview. Check the wording, order, required questions, and the experience on the device clients will use.
If Form is missing from the view menu, check whether you opened a linked data source. Forms must be added to the original database containing that data source. Open the database settings and inspect Manage data sources; a source listed under Linked points you back to its original database.
Using a duplicated template? Recreate its form from scratch against your own destination database. Notion warns that forms copied as part of a template can send responses to the original creator. Renaming a copied page is not a sufficient routing check.
Share the form without opening the response database
Changing a form’s sharing settings requires Full access to its connected database; Can edit alone is not enough for this step.
For a prospective client who does not use Notion, open Share form → Who can fill out → Anyone on the web with link. Notion documents that this option accepts people outside the workspace, including people without a Notion account. Send the form’s URL, rather than the database page’s URL.
That setting accepts anyone who has the link, which makes the form an open submission route. Keep the response database’s sharing restricted to the people who review inquiries. A public form isn’t a reason to publish the database.
| Sharing choice | Who can respond? | What to watch |
|---|---|---|
| Anyone on the web with link | People with the link, including non-Notion users. | Responses are automatically anonymous in Notion’s respondent tracking. Ask for an email explicitly; do not treat a typed email as verified identity. |
| Anyone at your workspace with link | Workspace members with the link. Guests also need access to the connected database. | For a workspace-only form with anonymous responses turned off, Access to submission can grant respondents access to their submitted record. |
The form sharing and anonymity rules separate the identity Notion records automatically from the answers someone types into a question. “Anonymous” doesn’t stop your form from asking for a person’s name or email. It means you can’t rely on the respondent-tracking property to prove who submitted a public response.
I would use the public form for the first inquiry and arrange ongoing collaboration separately. Inviting a client as a guest just to submit an inquiry adds a database-access decision you may not need. If they later need a project page, follow the client portal permissions checklist for that separate task.
Before sending the link, check the database’s parent page and teamspace too. Notion inherits parent-page permissions and respects the broadest access granted to a person. Restricting one visible page does not cancel a wider grant elsewhere. Enterprise workspace controls can also prevent forms from being shared to the web.
Make the response lead to an owned action
Notion stores form responses in a database table named Responses by default. Use that table as a review queue. For a solo freelancer, the owner can simply be you; a small team needs an explicit person responsible for the first reply.
Open Responses and add properties with the + beside the right-most table property. The following names are a suggested review model, not required Notion defaults:
- Intake status — Select: New, Waiting for information, Qualified, or Closed.
- Owner — Person: the workspace member responsible for this inquiry.
- Next action — Text: the specific question or decision needed next.
- Next review — Date: when the owner will return to the inquiry.
- Reply sent — Checkbox: whether the first reply has been sent.
- Retention review — Date: when you will review whether to keep the submitted information.
Keep these fields out of the client questionnaire. A new submission supplies the client’s answers; it does not make your assignment, reply, or scheduling decision for you. Leave Reply sent unchecked until someone sends that first reply.
Start with manual triage. Search for the contact email, compare the project details with existing requests, then choose a status such as New, Waiting for information, Qualified, or Closed. A repeated email can be a follow-up or a separate project. Flag the possible duplicate for review before merging or deleting anything.
| Submitted information | Internal decision |
|---|---|
| Request: Website launch Contact email: harbor@example.com | Compare it with existing inquiries from the same email. Keep both records until you understand whether they describe the same work. |
| Desired date: 30 November 2026 | Check capacity and clarify the scope before accepting a delivery date. |
| Brief: Design and build a small marketing site | Set Owner = Maya, Next action = Clarify page count, and Next review = 2 November 2026. Maya and these dates are example values; choose the actual responsible member and review date for your inquiry. |
Keep unanswered inquiries visible
Retain an unfiltered Responses view as the complete queue. Add a separate Table view called Awaiting first reply for open requests that have not received a reply. In that view’s settings, select Filter under View settings, then choose Add advanced filter. Combine two conditions with AND: Reply sent is unchecked, and Intake status is not Closed. Notion documents this filter-group setup and its personal or Save for everyone scope. Select Save for everyone if this is the team’s shared review view.
The two conditions exclude a request that already received its first reply and a request deliberately closed by the reviewer. They do not hide an open, unanswered request simply because its owner or next review date is still blank. Use the unfiltered view to spot missing assignments and to investigate anything that seems absent from the narrower queue.
When an inquiry is qualified, move the agreed information into your client CRM workflow. Mark the intake record’s outcome clearly so it doesn’t sit beside active work indefinitely. Then pick a retention review rule that fits the information you collect and your obligations.
Separate the submit screen from an email acknowledgement
Open Form settings → Submit screen to customize the Confirmation title and Confirmation body. A useful message says what was received and what the client should expect next. For example: “Thanks—we’ve received your request. We’ll review the scope and reply by email. Your requested date is not a confirmed booking.”
In those settings, you can also choose to receive an email copy of each submission. That is different from deciding how you will acknowledge the client. Do not promise a follow-up email until you have a person or an automation responsible for sending it.
For a manual reply, use the address in Contact email, ask for the next missing piece of scope, and check Reply sent only after sending it. If you are now waiting for the client, set Intake status to Waiting for information and give the inquiry a Next review date. The checkbox records a completed reply; it is not an email-sending action.
Manual replies are enough for a small intake queue. If volume justifies automation, Notion’s database automations support a Page added trigger, property updates, internal notifications, and a Send mail to action. Editable database automations require a paid plan and Full access; the email action uses a connected Gmail account. Record who owns that connection, what happens if it fails, and how unacknowledged requests will be spotted.
Choose the plan or form tool around a specific need
Stay with a basic native form while a short questionnaire and manual review meet your needs. Removing Notion branding from a public form requires a paid Notion plan. Conditional logic for multiple-choice questions requires Business or Enterprise; it can show a follow-up question based on an earlier answer.
If you need features such as signatures, password or CAPTCHA protection, or more extensive form customization, compare a dedicated tool on those requirements. For example, NoteForms lists those features for forms that write into Notion. Check its plan conditions and data access before choosing it. A third-party form service has its own permissions, billing, and maintenance; it does not remove the need to protect the response database.
Check the whole path before sending the client link
Use fictional information for your own pre-launch checks, then run each item below against the form you’ve configured.
- Destination: a completed request appears in your intended response database, with each answer in the right property.
- Required and optional answers: missing required answers prevent submission; blank optional answers do not leave the reviewer unable to act.
- External access: the public link works for someone outside your workspace, while the response database and other clients’ records remain inaccessible to that person.
- Duplicate handling: a second inquiry with the same fictional email is reviewed according to your rule, rather than silently discarded.
- Files, if used: the allowed sample file reaches the correct record, and the form explains any limits the client needs to know.
- Follow-up: you can see who owns the request, the next action, and whether the promised acknowledgement was sent.
To stop taking new responses, set Share form → Who can fill out → No access. Keep reviewing the requests already received. Closing the collection route and deciding what to retain are two different jobs.
