---
title: "Legal Intake Form and Request Tracker: How to Build One"
url: "https://goremy.ai/blog/articles/build-a-legal-intake-form-and-request-tracker-for-your-team"
author: Luis Chavez-Mattos
editor: Luis Chavez-Mattos
editor_title: Director, Product
published: "2026-11-19T19:40:10.095Z"
updated: "2026-11-19T19:40:10.095Z"
topic: Request Tracking Apps
description: Copy a legal intake form template, set up a request tracker with statuses and routing, and use AI to triage emails and chats into clean legal requests.
---

# Legal Intake Form and Request Tracker: How to Build One

> Copy a legal intake form template, set up a request tracker with statuses and routing, and use AI to triage emails and chats into clean legal requests.

Edited by Luis Chavez-Mattos, Director, Product · Published 2026-11-19

## What is a legal intake form?

A legal intake form is a single, structured way for people in a company to ask the legal team for help. Instead of emailing a lawyer or pinging them in chat, the requester fills in the same fields every time: what they need, who is involved, how urgent it is, and which documents apply. Each submission becomes a tracked request with an owner, a status and a due date. Legal gets complete information up front, and the business can see where its request stands.

## TL;DR

- A good legal intake form asks **eight to twelve questions**, not thirty. Every field must either route the request, set its priority, or save a follow-up email.
- The form is only half the job. The **request tracker** behind it (statuses, owners, due dates, a shared view) is what stops requests from disappearing into inboxes.
- Use a **request type** field to drive routing. A vendor contract, an NDA and a marketing claim review go to different people with different turnaround times.
- AI is useful for **turning messy emails and chat messages into clean intake records** and for suggesting a category and priority. A lawyer should confirm both.
- Do not paste privileged or highly sensitive material into a general consumer AI tool. Decide with your security and legal leadership what the intake system may store.
- You can start with a form and a spreadsheet this week, or build a small custom app if you need routing, permissions and reporting.

## Why do legal teams need an intake form at all?

Requests reach legal in whatever form is easiest for the sender. A sales rep forwards a contract with "can you look at this?" A product manager sends a chat message that says "quick question about the terms." An executive mentions something in a hallway. Each one arrives with different information, and each one has to be rebuilt into something a lawyer can act on.

That creates four problems you will recognize:

1. **Missing information.** The lawyer replies with questions, the requester replies a day later, and the clock restarts.
2. **No visibility.** The requester has no idea whether anyone has seen the request. They send a reminder, which adds to the noise.
3. **No priority signal.** Everything is "urgent," so the loudest request gets handled first.
4. **No data.** When leadership asks how many contract reviews legal handled last quarter, or why turnaround is slow, nobody can answer from an inbox.

An intake form fixes the first three directly. A tracker fixes the fourth as a side effect.

## What should a legal intake form include?

Keep it short enough that people will finish it. Here is a template you can copy into Microsoft Forms, Google Forms, a ticketing tool, or an app you build yourself.

### Legal intake form template

| # | Field | Type | Required | Why it is there |
|---|-------|------|----------|-----------------|
| 1 | Your name and email | Auto-filled if possible | Yes | So legal knows who to reply to |
| 2 | Business unit or department | Dropdown | Yes | Reporting and routing |
| 3 | Request type | Dropdown (see list below) | Yes | Drives routing and turnaround |
| 4 | One-sentence summary | Short text | Yes | Becomes the title in the tracker |
| 5 | What do you need from legal? | Long text | Yes | The actual ask, in plain words |
| 6 | Who is the other party? | Short text | If relevant | Counterparty, vendor, customer, regulator |
| 7 | Needed-by date | Date | Yes | The real deadline |
| 8 | What happens if the date is missed? | Short text | Yes | Separates real urgency from habit |
| 9 | Estimated value or exposure | Dropdown (ranges) | Optional | Helps set review depth |
| 10 | Attach documents | File upload | If relevant | Contract draft, policy, correspondence |
| 11 | Does this involve personal data, health data, or a government entity? | Yes / No / Not sure | Yes | Flags privacy and regulatory review |
| 12 | Anyone else who should be kept informed? | Email list | Optional | Fewer "can you add me" messages |

### Request type options

Adjust these to your company, but start with a short list:

- Contract review or negotiation
- NDA request
- Marketing, advertising or communications review
- Privacy or data question
- Employment or HR-related question
- Regulatory or compliance question
- Intellectual property (trademark, copyright, licensing)
- Dispute, complaint or threatened claim
- Policy review or drafting
- Other or not sure

Add a short line at the top of the form: "For urgent matters involving a threatened lawsuit, a regulator contact, or a potential data breach, call [name or number] instead of using this form." Some situations should never wait in a queue.

### Optional conditional questions

Show these only when the request type calls for them, so the form stays short:

- **Contract review:** Is this our paper or theirs? What is the term and renewal? Has procurement or security already reviewed it?
- **NDA:** Is it mutual or one-way? Is there an existing NDA with this party?
- **Marketing review:** Where will it run? What claims does it make? Does it mention a competitor or a customer?
- **Privacy:** What data, about whom, and where is it stored?

## How do you set up the request tracker?

The tracker is the table every submission lands in. Whether it lives in a spreadsheet, a ticketing tool or a custom app, it needs the same bones.

### Fields beyond the form

Add these columns that only legal fills in:

- **Request ID** (a running number, so everyone can refer to "LEG-0142")
- **Assigned to**
- **Status**
- **Priority** (set by legal, not the requester)
- **Date received** and **date due**
- **Date closed**
- **Outcome** (approved, approved with changes, declined, referred to outside counsel)
- **Internal notes** (visible to legal only)
- **Matter type tag** for reporting

### Statuses that work

Keep to a handful. More than seven and people stop updating them.

| Status | Meaning | Who moves it |
|--------|---------|--------------|
| New | Submitted, not yet looked at | Automatic |
| Needs information | Legal asked the requester a question | Legal |
| In review | A lawyer or paralegal is working on it | Legal |
| With counterparty or business | Waiting on the other side or on the requester's edits | Legal |
| Complete | Answer delivered | Legal |
| Declined or redirected | Not a legal matter, or sent elsewhere | Legal |

Separate "Needs information" and "With counterparty" from "In review." They are the two states where the delay is not legal's, and you want that visible when someone asks why a request took three weeks.

### Routing rules

Write down who gets what before you build anything. A simple version:

| Request type | Default owner | Target first response |
|--------------|---------------|-----------------------|
| NDA | Paralegal or legal ops | 1 business day |
| Contract review | Commercial counsel | 2 business days |
| Marketing review | Marketing counsel | 2 business days |
| Privacy or data | Privacy counsel | 2 business days |
| Dispute or claim | Senior counsel | Same day |

The turnaround times above are examples. Set yours with the team that has to meet them, then measure what actually happens for a month before publishing them company-wide.

### Views to create

- **Triage view:** New requests, oldest first. The person on intake duty works from this.
- **My queue:** Each lawyer's open requests sorted by due date.
- **Overdue and at risk:** Anything past its due date or due within two days.
- **Requester view:** The person who submitted can see only their own requests and statuses.
- **Monthly summary:** Count by request type, department, and average days to close. This is the view executives will ask for.

## How do you build it step by step?

You have three realistic options, from lightest to heaviest.

### Option 1: Form plus spreadsheet (a few hours)

1. Build the form in the survey tool your company already licenses.
2. Send responses to a shared spreadsheet or list.
3. Add the legal-only columns from above.
4. Turn on an email notification to a shared legal mailbox for each new response.
5. Add a filter view for each lawyer.

This works for small volumes. It breaks down when you need the requester to see status, when you need permissions (not everyone should see every request), or when requests number in the hundreds.

### Option 2: Your existing ticketing or workflow tool

If your company already runs an IT or workflow system, ask whether a legal queue can be created in it. Benefits: single sign-on, notifications and reporting already exist. Costs: you depend on another team's backlog, and the forms are often clunky. Bring the template and routing table above so the request is specific.

### Option 3: A small custom app

Build this when you need conditional questions, per-person permissions, automatic routing, a requester portal and a dashboard in one place. The spec is the hard part, and you can write it in plain English. Here is a starting spec to adapt:

```
Build an internal legal request app.

Requesters sign in with company email and can:
- Submit a legal request using a form with these fields: [paste the 12 fields]
- Show conditional questions based on request type
- See only their own requests, their status, and legal's replies

Legal team members can:
- See all requests in a triage view sorted by date received
- Assign a request to a lawyer based on request type
  (routing table: [paste your routing table])
- Change status: New, Needs information, In review,
  With counterparty or business, Complete, Declined or redirected
- Add internal notes the requester cannot see
- Set priority and a due date
- Attach documents to a request

Automatic behavior:
- Give each request an ID like LEG-0001
- Email the assigned lawyer when a request is assigned
- Email the requester when status changes
- Flag requests past their due date

Dashboard for the head of legal:
- Open requests by type and by owner
- Average days to close by request type
- Overdue requests
- Requests per department per month

Keep a record of who changed what and when.
```

## How can AI help with legal intake?

AI is most useful at the messy edge: the emails and chat messages that still arrive outside the form. Three uses are worth setting up.

### 1. Turn an email or chat message into an intake record

Paste the message and ask the AI to fill the form fields, marking anything it could not find.

```
You are helping a legal team log incoming requests.
Below is a message someone sent to the legal team. Extract the
following fields. If a field is not stated in the message, write
"NOT STATED" and do not guess.

Fields:
- Requester name
- Department
- Request type (choose one: Contract review, NDA, Marketing review,
  Privacy or data, Employment, Regulatory, Intellectual property,
  Dispute or claim, Policy, Other)
- One-sentence summary
- What is being asked of legal
- Other party
- Needed-by date
- Consequence if date is missed
- Mentions personal data, health data or a government entity?
  (Yes / No / Not sure)
- Questions legal will need to ask the requester before starting

Message:
[paste message]
```

The last item is the useful one. The AI drafts the follow-up questions, and you can send them with one edit.

### 2. Suggest a category and a priority

Give the AI your routing table and your priority definitions, then ask for a suggestion with its reasoning. Priority definitions must be yours, in writing, for example: "High: a deadline within three business days with a stated business consequence, or any regulator or claim." Without definitions, the AI will invent its own.

### 3. Summarize the queue

Once a week, paste (or export) the list of open requests and ask for a short summary of what is overdue, what is waiting on the business, and which request types are growing. This is a reporting job, and AI handles it well when the data is clean.

### What to check, and where not to trust AI

- **Check every extracted date.** "Next Friday" in an email sent on a Thursday is a classic error.
- **Check the category.** A message about "a quick change to our terms" might be a contract review or a marketing claim. A person decides.
- **Never let AI decide privilege, risk or the legal answer.** Intake is administrative. The legal judgment stays with lawyers.
- **Mind confidentiality.** Contracts and dispute details can be privileged or restricted. Use only tools your company has approved for that content, and ask your security and legal leadership before sending request text to any outside AI service. When in doubt, leave attachments out and extract fields from the message alone.
- **Do not let AI send replies to requesters unreviewed.** Drafts are fine. Autosent legal responses are not.

## What does a filled-in example look like?

A marketing manager emails legal: "Hi, we're launching a campaign next week saying our product is 'the most secure option for small business.' Can someone check? The agency needs final copy by Tuesday. Deck attached."

Run through the prompt above, the record comes out like this:

| Field | Value |
|-------|-------|
| Requester | Marketing manager (name from the email) |
| Department | Marketing |
| Request type | Marketing review |
| Summary | Review "most secure option" claim in launch campaign |
| Ask | Confirm whether the claim is supportable and suggest alternative wording |
| Other party | Creative agency (not a contract issue) |
| Needed by | Tuesday (confirm date) |
| Consequence if missed | NOT STATED |
| Personal data / government entity | Not sure |
| Follow-up questions | Where will the campaign run? What evidence supports "most secure"? Does it name competitors? What is the exact Tuesday date? What happens if the date slips? |

The record lands in the triage view, routes to marketing counsel, and the follow-up questions go back to the requester with status "Needs information." The lawyer never had to reconstruct the request from a forwarded thread.

## How do you get people to use it?

The form is easy to build and harder to adopt. A few things that help:

- **Make it the easiest path.** Put the link in the legal team's email signature, pin it in the legal chat channel, and put it on the intranet page people already visit.
- **Respond to email requests with the link, once.** Reply with a short note: "Thanks. To get this to the right person quickly, please submit it here. I've logged your message as LEG-0142 this time." Log the first one for them, then hold the line.
- **Show people their status.** Requesters stop chasing when they can see "In review, assigned to Priya."
- **Publish turnaround times** only after you can meet them.
- **Review the first month.** Look at which fields people skip or answer with "N/A," and remove or reword them.

## What are the common mistakes?

- **Too many required fields.** People abandon the form or enter junk to get through it.
- **Letting the requester set priority.** Capture their deadline and consequence, then let legal assign priority.
- **No owner for triage.** Someone must be on intake duty each day, with a backup. A tracker nobody watches is a slower inbox.
- **Treating the tracker as a record of legal advice.** Decide with your legal leadership what goes in notes, who can see them, and how long records are kept.
- **Skipping permissions.** An HR matter or a dispute should not be visible to every requester or every member of the team.

## Should you build your own legal request tracker?

If your volume is low and one person handles it, a form and a spreadsheet is enough. If you handle many requests across several lawyers, need confidential matters restricted, or want a dashboard without exporting data by hand, a purpose-built tool pays off. Buying specialist legal workflow software is one route. Building a small internal app is the other, and it suits teams whose process is specific to their company.

## Can you build this without writing code?

Yes. The spec above is the work. Tools that build apps from a plain-English description can turn it into a working intake form, tracker and dashboard. [Remy](https://goremy.ai) is one: you describe the app, and it builds and deploys a full-stack application with a database, sign-in and role-based access, so requesters see their own requests while legal sees the whole queue. It can also receive inbound email, which helps with requests that still arrive by message. You own the code, which matters if you later want to move it. Bring your security team in early to confirm where legal data may be stored.

## Frequently Asked Questions

### What is the difference between a legal intake form and a legal request tracker?

The intake form is how a request enters: the questions the requester answers. The tracker is where it lives afterward: statuses, owners, due dates and history. You need both. A form without a tracker gives you a tidy inbox, and a tracker without a form gives you incomplete records.

### How many questions should a legal intake form have?

Aim for eight to twelve questions on the first screen, with extra questions appearing only for certain request types. Every question should either route the request, set its priority, or prevent a follow-up email. If you cannot say which, remove it.

### Can AI fill in the legal intake form for me?

It can draft the fields from an email or chat message, and flag what is missing. A person should confirm the dates, category and anything about personal data before the record is final. Do not use AI to decide the legal answer, and check your company's rules before putting confidential documents into any AI tool.

### Do I need special software for legal intake?

No. A survey form and a shared spreadsheet is a legitimate starting point. Move to a ticketing system, a legal workflow product or a custom-built app when you need permissions, routing, a requester portal or reporting that the spreadsheet cannot give you.

### What should happen to urgent legal matters?

Urgent matters such as a threatened lawsuit, a regulator contact or a suspected data breach should not wait in a queue. Put a phone number or a named contact at the top of the form for these, and make sure the people who might encounter them know to use it.
