Section 2.3: Custom Intake Forms

Custom intake forms let you collect project briefs from clients and partners in a structured way. Instead of an email or a phone call, the requester fills out a form you designed, and their answers arrive as a Project Request ready for review — or, if you choose, ready for Abram to turn into a fully scoped project automatically.

1. Where to find the form builder

The intake form builder lives under the Clients hub in the sidebar, on its Intake Forms tab. It is not part of Organization Settings.

Building and publishing custom intake forms ("Project Requests") requires a Solo Pro plan or higher. The number of forms you can keep active at the same time is also capped by plan:

You can still create and edit forms beyond your active cap — you just can't turn more than your plan's limit on at once.

2. Creating and managing forms

You aren't limited to one form. Click Create Intake Form to add a new, separately named form — for example, one for general project requests and another tailored to a specific client or project type.

Each form in your list has:

• Configure — opens the builder for that form.
• Delete — permanently removes the form.
• An Active on/off toggle — controls whether the form's link is currently accepting submissions.
• Its own share link, unique to that form.

While you're configuring a form, a live Preview pane shows exactly what a visitor will see as you add, edit, and reorder fields.

3. Standard fields

Every form starts with Project Title, which is always present and always required. Beyond that, you can toggle each of the following standard fields Enabled (shown on the form) and Required (mandatory to submit) independently:

• Description
• Estimated Budget
• Start Date
• End Date
• Start Time
• End Time
• Attachment

The Attachment field accepts PDF, Word, text, and image files up to 10 MB. Download links generated for uploaded attachments are time-limited.

4. Custom fields

If the standard fields don't cover what you need to know, add custom questions. Each custom field can be one of four types:

• Short Text
• Paragraph
• Number
• Dropdown

For each custom field you set a label, a placeholder, and a required toggle. There is no drag-and-drop — reorder fields using the up and down arrows next to each one, and delete a field with its delete control.

Field mapping

Every custom field also has a mapping setting that determines how its answer is used once a request is approved:

• Description Only — the answer is simply added to the project description.
• Custom Metadata — the answer is stored on the project as custom project data.
• Software Requirements
• Equipment Requirements
• Required Skills
• On-site Locations
• Creative Styles

Mapping a field to one of these targets means the answer feeds directly into that part of the project once the request is approved, rather than just sitting in the description text.

5. Access control

Each form has an optional Restrict Email Domains setting. Enter a comma-separated list of allowed domains, and submissions are checked against that list when the form is submitted.

If someone is signed in when they open the form, their name and email are pre-filled automatically.

6. Sharing a form

The copy-link button on a form produces a link ending in /request/new, with that specific form's id attached, for example:

yoursite/your-organization/request/new?formId=…

Each form has its own distinct link, so you can share different forms with different audiences.

7. Reviewing submissions

Submitted requests land in your app's Inbox, on the Project Requests tab. From there you can:

• Search requests
• Filter by status
• See a live count summary
• Export requests to CSV

Opening a request shows every answer submitted, including any attachments. From there, you have three actions available:

• Approve & Setup (Manual) — creates the project in the Planning stage, assigns an owner, and maps the submitted answers into the new project.
• AI Auto-Setup Project — Abram analyzes the brief and automatically builds out the full project, including work packages, work orders, milestones, and deliverables. This uses AI credits, and is blocked for non-admins if your organization is out of credits.
• Reject Request — declines the request.

8. Letting a specific client submit requests

Besides your public share link, you can give an individual client a private way to submit requests through their Client Portal. Manage this from the Clients hub: open the client, then go to their Requests sub-tab. There you'll find:

• A Portal Requests on/off toggle.
• A dropdown to assign which intake form that client sees when they submit a request. If you don't assign one, the client falls back to a simple Basic request form of just a title and details.

Requests submitted through a client's portal land in the same Project Requests queue as everything else, tagged with which client sent them, so you can tell portal submissions apart from public-link submissions at a glance.

For more on setting up and using client portals themselves, see Section 6.4: Client Portal.