Route requests to legal to the right lawyer or a template

Fields

• Request to legal
• Requester's team
• Attachment file names

Questions

1. What kind of legal work is this request mainly about? Choice

   Read the request, the requester team and the attachment names. Choose the kind of work the request is mainly about. A customer contract that also contains data terms is a sales contract; the personal data question records the data part.

   • NDA A confidentiality agreement on its own, ours or the other party's.
   • Sales contract A customer contract, order form, renewal or amendment, on our paper or the customer's.
   • Supplier contract Terms for something we buy: software, services, a reseller or a partner.
   • Privacy and data A data processing agreement on its own, a data transfer, a privacy notice, or a question about using personal data.
   • Employment Hiring, contracts of employment, dismissal, a workplace issue or a contractor who may be an employee.
   • Intellectual property Trademarks, copyright, open source licences, patents, or using someone else's content or logo.
   • Marketing review Ad copy, website claims, promotions, competitions or a comparison with a competitor.
   • Dispute or claim A demand letter, a threatened or actual lawsuit, a subpoena, or a customer or supplier dispute that has turned legal.
   • Regulatory Contact from a regulator, a licence, sanctions or export rules, or whether a product meets a law.
   • Corporate Group companies, board matters, shares, equity plans or signing authority.
   • General legal question A "can we do this" question that fits none of the areas above.
   • Not a legal request IT, HR, finance or facilities requests sent to legal by mistake, spam and automatic replies.

2. Could the requester finish this with a self-serve route in the intake policy, without a lawyer? Yes / No

   Use only the self-serve routes listed in the context, with their conditions. A request that asks for changes to a standard document, or involves a dispute or a regulator, is not self-serve. Yes: The request fits one self-serve route and meets its conditions, as the request describes it. No: No self-serve route fits, or the request falls outside a route's conditions.

3. Does the request mention a deadline set by someone outside the company? Yes / No

   Count a date or time limit set by a court, a regulator, a counterparty or a letter: a signing date the other party wants, a response date, a hearing. A date only the requester wants does not count. Do not compare any date with today; code reads the date. Yes: The request mentions at least one deadline set outside the company. No: The request mentions no such deadline.

4. Does the request involve a claim, a legal threat, a lawsuit, a subpoena, a regulator or the police? Yes / No

   Count it whether the request reports it, forwards it or only mentions it in passing. Negotiating contract terms is not a dispute. Yes: The request involves a claim, a threat of legal action, a lawsuit, a subpoena, contact from a regulator, or the police. No: The request involves none of these.

5. Does the work involve collecting, hosting, sharing or transferring personal data? Yes / No

   Count personal data of customers, their users, employees or anyone else, and moving it between countries or to another company. Yes: The request involves personal data in any of these ways. No: The request involves no personal data.

6. Is information missing that legal needs before it can start? Yes / No

   Legal needs the other party's name, what is being asked, and the document when the request is about one. Count a document as supplied when an attachment name or the request says it is attached or linked. Do not judge whether the request is a good idea. Yes: At least one of these is missing. No: The request gives all of them, or needs no document.

7. How soon does this request need a lawyer's attention? Scale

   Rate from deadlines set outside the company and from the harm of waiting, not from how fast the requester would like an answer. Use the words in the request, such as "this Friday" or "tomorrow"; do not compare dates with today.

   • Routine Can wait up to two weeks: no outside deadline and no harm in waiting.
   • This week An outside deadline later this week but more than two working days away, or a deal or task that stalls until legal answers.
   • Within two days An outside deadline two working days away, or a dispute or regulator contact with no date yet.
   • Today A court, regulator or signing deadline today or tomorrow, a subpoena, the police, or harm that grows by the hour.

8. How much legal risk does the request carry for the company? Scale

   Judge the terms and the situation the request describes. Do not weigh the deal value; code compares it with the approval thresholds.

   • Low Standard terms or a routine question: our own template, small changes, nothing unusual.
   • Medium Negotiated terms within normal bounds, or a question with some exposure that a lawyer should check.
   • High A dispute or regulator, unlimited or unusual liability, personal data leaving the EU, or terms far from our standard.

Lens columns

request_type, request_type_probability, self_serve, self_serve_probability, outside_deadline, outside_deadline_probability, dispute_or_regulator, dispute_or_regulator_probability, personal_data, personal_data_probability, missing_details, missing_details_probability, urgency, urgency_average, risk, risk_average