> ## Documentation Index > Fetch the complete documentation index at: https://assembly.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Client intake form > Collect what you need to know before work starts with a guided, multi-step form your clients fill in and your team reviews before kickoff. > [!NOTE] > > **Template.** You can change anything about this app by describing it in its build chat. See [App templates](https://assembly.com/docs/building-new-apps/app-templates.md). Collect the details you need before kickoff in one guided form. Clients answer one section at a time, their progress saves as they go, and they submit when they're ready. Your team sees every intake in one list, reviews the answers, keeps kickoff notes beside them, and marks each one reviewed. **Category:** Onboarding · **Used by:** your team and your clients · **Works with:** CRM ## Features * A step-by-step form with one section per step, and progress that saves automatically * A form builder with sections and five question types: **Short answer**, **Paragraph**, **Dropdown**, **Date**, and **File upload** * Required questions that clients must answer before they can submit * An intake list with a tab for each status: **Not started**, **In progress**, **Awaiting review**, **Reviewed**, and **Archived** * One intake per company, or one per client, depending on the intake scope you choose * A review page with the client's answers, internal kickoff notes, and a **Mark reviewed** button * A PDF download of any submitted intake * Notifications when an intake is submitted or updated ## How to use it ### For your team > [accordion] Set up the form > > 1. Open the app and click **Form settings**. > 2. Click **Add section** and give the section a title. Each section is one step for the client. > 3. In a section, click **Add question** and pick a question type. > 4. In **Edit question**, enter the **Label**, optionally add **Helper text**, and turn on **Required** if the client must answer it. For a dropdown, add its options with **Add option**. > 5. Click **Save question**. Drag sections and questions to reorder them. > 6. Switch to the **Client preview** tab to step through the form the way a client will. > 7. Click **Save form**. > > The template starts with four sections: **How can we help?**, **Background & context**, **Timeline**, and **Supporting materials**. Edit or remove them to fit how you work. Intakes that were already submitted keep the questions they were answered with. > [accordion] Choose who an intake belongs to > > In **Form settings**, use **Intake scope** to choose **Company** or **Client**. With **Company**, each company has one shared intake that anyone in it can work on. With **Client**, each client fills in their own. The intake list switches to show companies or clients to match. > > With **Company** scope, clients who aren't in a company see an empty page. Add them to a company, or use custom visibility in the app's settings to hide the app from them. > [accordion] Track intakes > > The intake list shows every company or client with the status of their intake. Click a tab such as **Awaiting review** to filter the list, search by name, and sort by name or **STATUS**. The list refreshes on its own while you have it open. > [accordion] Review an intake > > 1. Click a company or client in the list to open their intake. > 2. Read their answers under **Intake details**, and download any files they uploaded. > 3. Add anything your team needs to know under **Internal kickoff notes**, then click **Save notes**. > 4. Click **Mark reviewed**. > > Click **Download PDF** to save a copy of the intake. You can also open an intake from a client's or company's page in your CRM. > [accordion] Archive an intake > > Only reviewed intakes can be archived. Open the intake and choose **Archive** from its actions, or use the archive button in the list. Archived intakes are under the **Archived** tab, where you can **Unarchive** them. Your team reviews intakes but can't fill them in or submit them. Only clients do that. ### For your clients > [accordion] Fill in the intake > > 1. Open the app and answer the questions in the first section. > 2. Click **Next** to move to the next section, or **Back** to return to one. > 3. On the last section, click **Submit intake**. > > Answers save automatically, so clients can leave and come back. Questions marked required must be answered before they can move on or submit. A file upload question takes one file, and date questions only accept today or later. > [accordion] See or change a submitted intake > > After submitting, clients see their answers and can click **Download PDF** to keep a copy. To change something, they click **Edit and resubmit**, update their answers, and submit again. Once an intake is archived, clients can still see it and download it, but can't change it. Clients only see their own intake, or their company's intake when the scope is set to **Company**. ## Notifications * **When a client submits an intake**, your team gets an email and an in-product notification, with a summary of the answers. * **When a client edits and resubmits**, your team is notified that the intake was updated. Only team members who have access to the client's company are notified. To change who's notified or what the messages say, see [Configuring notifications](https://assembly.com/docs/building-new-apps/configuring-notifications.md). ## Set it up **1. Add the template** Click **Add App** in the Dashboard sidebar. Find **Client intake form** under **Start from a template**, or scroll down to **Browse all apps** and pick the **Onboarding** filter. **2. Try it as your team** The app lands in your sidebar as a draft. Open **Form settings**, choose an intake scope, and adjust the questions. **3. Check the client side** In the builder's **Client view**, pick your test client, fill in the intake, and submit it. Then review it as your team. **4. Publish it** Publish the app with visibility set to **Hidden from all people**, or on plans with custom visibility, limited to your test client. Sign in as your test client to try it in the real client experience, then make it visible to the clients who should use it. See [Launching apps](https://assembly.com/docs/building-new-apps/launching-apps.md). ## Change it with the app builder This app is a template, so you can change anything about it by describing what you want. **1. Open the build chat** Open **Client intake form** from your Dashboard sidebar, click its name at the top, then click **Switch to builder**. **2. Describe the change** Write what you want the way you'd ask a teammate. Say who it's for and where it shows up, such as your team's intake list or the client's form. **3. Check the preview** The app builder makes the change and updates the preview. Switch between **Team view** and **Client view** to check both sides, and pick a client to see it as them. **4. Publish** Click **Publish** when you're happy. Until you do, your clients keep seeing the last published version. Changes people often make to this template: * "Ask for the client's tax ID only when they're a business" * "Let clients upload more than one file per question" * "Notify the client by email when we mark their intake reviewed" * "Add a Checkboxes question type to the form builder" * "Send the client a reminder if their intake is still in progress after a week" * "Add a Service type column to the intake list and let us filter by it" See [Iterating on apps](https://assembly.com/docs/building-new-apps/iterating-on-apps.md) for how to describe changes well and how to go back to an earlier version. To rename the app, or change who can see it and how it notifies people, click its name at the top and choose **Rename app** or **Manage app**. ## Related > [card] [Client onboarding](https://assembly.com/docs/apps/client-onboarding.md) > > A multi-step onboarding flow with saved progress > [card] [Document collector](https://assembly.com/docs/apps/document-collector.md) > > Request documents with an upload checklist [View this template on assembly.com](https://assembly.com/templates/new-client-intake) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.