A legal request form template is a ready structure of fields that the business completes when it needs help from legal, designed so every request arrives with enough information to route, prioritize, and start the work. A good one saves your lawyers the first email exchange on every request.
This article gives you a working template, section by section, written for in-house legal departments. It also covers the mistakes that make downloaded templates fail.
What is a legal request form template?
The template is the standard set of questions, field types, and notices behind every request your department receives. For context, in a 2025 survey of in-house legal teams, 54 percent named streamlining intake and matter management as a top priority. It defines what the requester must tell legal, what the platform fills in automatically, and which questions appear only for certain request types.
The template matters because it shapes every legal service request as a record with an owner, a status, and a history. The fields become your reporting categories and routing inputs. Changing them later breaks comparisons with older data, so get the structure right before launch.
Most templates found online come from law firm client intake, where the goal is screening prospective clients and running conflict checks. In-house forms serve a different purpose: routing internal work quickly to the right lawyer.
What should a legal request form template include?
A legal request form template should include six sections: requester details, request classification, parties and dates, value and risk, documents, and notices. For most request types that comes to eight to twelve visible questions, with further questions appearing only when an earlier answer calls for them.
The first rule is to ask the requester only what nobody else can tell you. With single sign-on, each requester’s division, region, and cost center can be placed on the form automatically, which makes the later reporting trustworthy. Anything your directory already knows should never be typed.
The second rule is to design the form around the data you will want to report on. An intake workflow should capture business data such as key dates and requests alongside behavioral data such as turnaround and waiting times. The sections below cover the first kind, and the platform records the second.
Which requester and request details belong on the form?
The requester and request details that belong on the form are identity, request type, a plain description, and the business objective. These four fields tell legal who is asking, what kind of help they need, and why it matters to the company.
- Requester (pre-filled). Name, email, business unit, region, cost center, and manager, all supplied by single sign-on and the HR directory.
- Request type. A short list of six to ten options, such as contract review, NDA, privacy question, dispute or claim, employment matter, regulatory inquiry, and general legal question.
- Description. One free-text box asking what the requester needs from legal, in their own words, with a two-line example underneath.
- Business objective. What the requester is trying to achieve, such as closing a sale or onboarding a supplier, so the lawyer can advise on the outcome.
Keep help text short and specific: “Describe the deal in two or three sentences” gets better answers than “Provide details.”
Which parties, dates, and value fields does legal need?
The parties, dates, and value fields legal needs are the counterparty, the deadline with its consequence, the estimated value, and the jurisdiction and legal entity involved. Together they drive most routing and prioritization decisions.
- Counterparty. The full legal name of the other party, with an option to add related parties when the matter involves more than one.
- Deadline and consequence. The date the requester needs an answer, plus a required question asking what happens if that date is missed.
- Estimated value. A range selector, such as under $50,000, $50,000 to $250,000, and above $250,000, which is easier to answer accurately than an exact figure.
- Jurisdiction and entity. The country or state involved and the contracting entity, which together decide approval paths and specialist review.
The consequence question is the one most templates omit, and it does more for prioritization than any priority dropdown.
Which documents and routing details should the form collect?
The documents and routing details the form should collect are the relevant attachments, whose paper the agreement is on, and whether sensitive data is involved. These fields decide whether a request goes to self-service, a generalist, or a specialist.
- Attachments. An upload field for the draft agreement, notice, or correspondence, required for contract review and dispute request types.
- Third-party paper. A yes or no question on contract requests, since the counterparty’s template usually needs more review time than your own.
- Data sensitivity. A yes or no question on whether personal, health, or financial data is involved, which triggers the privacy branch of the form.
If your form serves several countries, remember that intake forms across regions need translated labels, help text, and validation. Translate the options too, or reporting categories split by language.
What notices belong on a legal request form?
The notices that belong on a legal request form are a privilege and confidentiality note, a privacy acknowledgment, and a clear instruction for urgent matters. They take a few lines at the top or bottom of the form and prevent the most common handling mistakes.
The privilege note tells requesters that communications with legal may be privileged and should not be forwarded outside the request. The privacy acknowledgment explains how the information will be stored and who can see it. The urgent-matters instruction gives an on-call contact for emergencies, such as a court deadline within 24 hours.
Law firm templates often include a non-engagement disclaimer stating that submitting the form creates no attorney-client relationship. In-house forms rarely need it, because the requester is already an employee of the client.
What do most legal request form templates get wrong?
Most legal request form templates get the balance wrong: they ask too much of every requester and too little about the things that decide routing. The result is abandoned forms and email workarounds.
- Asking what the organization already knows. Name, department, and manager fields that the directory could supply add effort and introduce typing errors.
- One long form for everything. A single form with 25 questions for every request type makes an NDA take as long as a complex dispute.
- A priority dropdown. Requesters mark nearly everything high, so the field stops meaning anything.
- Free text where options would work. Typed request types and business units cannot be reported on, while a controlled list can.
A legal intake process gets used when it is faster than sending an email, and a long form is one of the easiest barriers to fix.
How should the template change for different request types?
The template should change for different request types through conditional questions that appear only when an earlier answer calls for them. The core sections stay the same for every request, and each type adds its own short branch.
A contract review branch asks about third-party paper, contract value, and the target signature date. An NDA branch asks whether the counterparty will accept your standard form, and if so, can generate it immediately through self-service. A privacy branch asks where personal data is processed and which vendors have access. A dispute branch asks for the incident date and any response deadline.
Test every branch before launch, because a hidden required field can block submission with no clear error.
How do you know your legal request form is working?
Your legal request form is working when most submissions arrive complete, route correctly on the first attempt, and reach triage quickly.
- Complete-submission rate. The share of requests legal can act on without going back to the requester, with an operating target of 90 percent or more.
- Follow-up rate. The share of requests needing contact purely for missing information, ideally under 10 percent.
- Correct-routing rate. The share of requests reaching the right queue with no reassignment, with a target of 95 percent.
- Time to triage. Hours from submission to the first triage decision, which shows whether the form gives triage enough to act on.
The Thomson Reuters Institute’s 2025 LDO Index research found that service-centric metrics such as cycle time are tracked by fewer than 20 percent of legal departments. A well-structured form is where that data starts.
Conclusion
A legal request form template works when it asks the requester only what they alone can answer and lets the platform supply everything else. Pre-fill identity, keep the core to a handful of questions, replace the priority dropdown with a deadline and its consequence, and branch by request type. Then measure completeness, follow-ups, and routing accuracy, and trim what causes trouble.
How Basla can help
Basla provides delivery teams for legal intake and request management software implementation. Those teams design, configure, and test legal intake forms on Onit and related platforms. Basla has built a Legal Service Request implementation with 8 Front Doors covering language and country variations, and supported legal technology across 100+ jurisdictions for a global retail organization.
Basla analysts turn your request types into form requirements, developers configure them, and QA tests every branch before launch. Basla delivers legal technology services through staff augmentation or a Basla-managed delivery unit, and stays on through hypercare. That takes the weight off your legal operations team while the new form beds in.
Frequently asked questions
What is a legal request form template?
A legal request form template is a standard set of fields that employees complete when they need help from legal. It captures who is asking, what they need, the parties, dates, value, and documents, so legal can route and prioritize without a follow-up email.
How many questions should a legal request form have?
A legal request form should show eight to twelve questions for most request types, with extra questions appearing only when an earlier answer calls for them. Identity details should be pre-filled and never count toward that total.
Should a legal request form include a priority field?
A legal request form works better with a deadline field and a required question about the consequence of missing it. Requesters tend to mark most requests as high priority, which makes a priority dropdown unreliable for triage.
Can one legal request form cover every request type?
One legal request form can cover every request type if it uses conditional branches. The core sections stay the same, and each request type adds only the few questions it needs.
What notices should a legal request form include?
A legal request form should include a privilege and confidentiality note, a privacy acknowledgment, and instructions for genuine emergencies. In-house forms usually do not need the non-engagement disclaimer found on law firm templates.
How do you measure whether a legal request form works?
A legal request form is measured by complete-submission rate, follow-up rate, correct-routing rate, and time to triage. Weak numbers on one request type usually point to a specific question worth rewording or removing.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*