Red Flags in LegalTech: When AI Hands a Case to a Lawyer

Short version: Red Flags, also called stop factors, set the conditions under which a LegalTech service (an online tool that automates part of legal services) stops answering on its own and hands the case to a lawyer.

The easiest way to record them is one table: the trigger, the legal basis and the service’s action.

An everyday example: a circuit breaker in an electrical panel. On overload it trips by itself, with no one making a decision, and the circuit opens before a fire starts.

A service needs the same kind of breakers wherever an automatic answer can harm the user.

How are Red Flags different from Triage Logic?

Triage Logic (a way of sorting requests by urgency and risk) chooses a route and a priority: answer, clarify or hand to a lawyer.

A red flag can be treated as the first rule of triage: it is checked before everything else and fires regardless of the other answers.

When a trigger is found, the service stops, even if everything else looks simple and not urgent.

Triage then sets the case’s place in the lawyer’s queue.

Example: a service for a first assessment of personal bankruptcy

Let’s take a fictional service that answers a person in debt on typical bankruptcy questions, for example how the case proceeds. Only the service is made up. The rules are real: Federal Law No. 127-FZ of October 26, 2002 “On Insolvency (Bankruptcy)” and Art. 446 of the Code of Civil Procedure (CCP) of the Russian Federation.

The rules and case law in this article are current as of October 12, 2026.

The service answers almost every question on its own. But there are four situations where a standard answer misleads the person.

Here they are in a table:

Red flag	Trigger in the user’s answers	Basis	Service action
Only home with a mortgage, or too large	There is a mortgage, or the home is very large or expensive	Art. 446(1) CCP, Art. 213.25(3) and Art. 213.27-1 of Law No. 127-FZ, Constitutional Court Ruling of April 26, 2021 No. 15-P	Hands the case to a lawyer with no promises about the home
Transactions with property in the last three years	A gift, sale, marriage contract or transfer of property in the last three years	Art. 61.2, Art. 213.32(1) and (4) of Law No. 127-FZ	Hands the lawyer a list of transactions with no assessment of its own
Managing a company that has debts	The person ran a company, owned more than half of its charter capital, was responsible for accounting or finance, or in practice decided for it	Art. 61.10, 61.11 of Law No. 127-FZ	Hands the case to a lawyer with no talk of debts being written off
Wish to protect property before filing	The user asks how to shield property from creditors	Art. 61.2(2), Art. 213.28(4) of Law No. 127-FZ	Hands the question to a lawyer with no advice

Now each flag in more detail.

Why can the answer “your only home can’t be taken” be wrong?

The standard answer rests on Art. 446(1) of the CCP: recovery cannot be levied on a home that is the only one suitable for permanent residence for the debtor and the family living with the debtor.

In a personal bankruptcy, the financial manager (the arbitration manager who runs the case) removes from the bankruptcy estate everything that cannot be levied on under the CCP (Art. 213.25(3) of Law No. 127-FZ). The bankruptcy estate is the property used to pay the debts.

But this rule has two caveats, and because of them the answer “your only home can’t be taken” can be wrong.

First caveat: a mortgage. The protection does not apply if the home is mortgaged and mortgage law allows recovery against it.

Proceeds from selling the debtor’s only home, if it has a mortgage, are distributed under a special procedure (Art. 213.27-1 of Law No. 127-FZ, added by Federal Law No. 62-FZ of March 23, 2026):

Eighty percent of the proceeds, after the costs of sale, go to the secured creditor, up to the amount of its claims.
Ten percent goes to first- and second-priority creditors if the debtor has no other property to cover them.
Ten percent, but no more than the amount put into the home (the down payment and mortgage payments), goes to the debtor.
The remainder goes back to paying off the mortgage debt, and any sum above the debt goes to the debtor.

Second caveat: a home that is too large. In Ruling No. 15-P of April 26, 2021, the Constitutional Court held that the immunity of a debtor’s only home does not bar enforcement absolutely. A court may set it aside if it finds the immunity unjustified, in particular when the home significantly exceeds what is reasonably sufficient for the family. The condition: the debtor and the family must not be left without housing that meets at least the social housing standard in the same locality.

The Supreme Court refined this position in its Review of Court Practice in Personal Bankruptcy Cases (approved by the Presidium of the Supreme Court on June 18, 2025). Floor area above the standard does not by itself prove luxury: a set of features is assessed, including location and the characteristics of the property (para. 22 of the review).

Area counts only when it is many times larger than the family’s reasonable need (para. 23 of the review).

Selling the home is allowed only when it is economically justified and the interests of creditors, the debtor and the family are balanced (para. 21 of the review).

The service must ask about a mortgage and about the size of the home. If such a trigger is found, the flag fires: the service hands the case to a lawyer and promises nothing about the fate of the home.

Who assesses transactions: the service or the lawyer?

A court can invalidate the debtor’s transactions made before bankruptcy. The grounds are listed in Art. 61.2 of Law No. 127-FZ:

An unequal transaction. The debtor gave up significantly more than was received in return, within one year before the bankruptcy petition was accepted or after (para. 1).
A transaction that harms creditors. It was made within three years before the petition was accepted or after, it harmed creditors, and the other party knew of that purpose (para. 2).

The law presumes that the debtor meant to harm creditors if, for example, the debtor was already unable to pay debts and gave the property away or transferred it to a relative (Art. 61.2(2)). The court determines the actual harm to creditors separately.

A transaction of an individual can be challenged by the financial manager and, under conditions set by the law, by a creditor (Art. 213.32(1)).

A spouse’s transactions with shared property can be contested too, but under family law (Art. 213.32(4)).

A marriage contract is among such transactions: the Supreme Court’s review of June 18, 2025 holds that provisions of a marriage contract that violate creditors’ rights can be challenged under Art. 61.2(2) (para. 42 of the review).

What the service does. It does not know the date the bankruptcy petition will be accepted, so it allows a margin and asks about transactions in the last three years. The period under review runs from the date the petition is accepted and moves forward over time, so this question covers every transaction that could fall into it.

The lawyer decides whether the transactions found can be challenged. The service hands over a list of transactions with dates, parties and price, so the lawyer can quickly separate routine transactions from dangerous ones.

A second reason to stop. Claims that follow from declaring such a transaction invalid (for example, to return property) generally survive bankruptcy (Art. 213.28(5) and (6)). The phrase “bankruptcy will wipe out all your debts” is not acceptable here.

What does subsidiary liability change in a personal bankruptcy?

Subsidiary liability means a person answers for a company’s debts in addition to the company itself. A controlling person bears it if the company cannot pay its creditors because of that person’s actions or inaction (Art. 61.11(1)).

Who counts as a controlling person. Anyone who could give the company binding instructions or otherwise determine its actions. The period considered is three years before signs of bankruptcy appeared, plus the time after, until the court accepted the bankruptcy petition (Art. 61.10(1)).

Unless proven otherwise, these are presumed to be controlling persons:

the company’s head;
a person who owns more than half of the charter capital of a limited liability company;
a person who can appoint the head (Art. 61.10(4)).

When liability is presumed. The law presumes that the company cannot pay because of such a person if, for example:

transactions caused creditors significant harm, including transactions under Art. 61.2 and 61.3;
accounting records are missing or falsified (Art. 61.11(2)).

Business risk alone is not a ground for liability. The company must be unable to pay because of the person’s bad-faith and unreasonable conduct (para. 1 of Supreme Court Plenum Resolution No. 53 of December 21, 2017, as amended on December 23, 2025).

The amount of liability. It equals the creditors’ claims left unpaid for lack of assets, and it is reduced if the person proves the harm was significantly smaller. The court may consider this both when deciding the grounds and when setting the amount (Art. 61.11(11); para. 26(3) of the same resolution).

Time limits. An application to hold someone liable can be filed within three years from the day the applicant learned or should have learned of the grounds. The outer limits: three years after the debtor was declared bankrupt and ten years after the acts themselves (Art. 61.14(5)).

I covered how these periods are counted in the article Former Director Subsidiary Liability: Time Limits.

For the debtor personally. A claim to hold an individual liable as a controlling person generally survives bankruptcy (Art. 213.28(5) and (6)).

Case law makes an exception. In its review of June 18, 2025, the Supreme Court held that such a debt can be discharged. Two conditions apply: the debtor acted without intent or gross negligence, and the debtor behaved in good faith during the bankruptcy (para. 58 of the review).

In the review’s example, the court released from subsidiary liability a member of a collegial body who did not profit and followed the instructions of the main controlling person. Plenum Resolution No. 53 now directly requires establishing each member’s participation in causing the harm (para. 22(1)).

The outcome cannot be predicted in advance, so the service does not promise a write-off.

A service that answers “after bankruptcy your debts will be written off” without asking about the person’s past role in a company is wrong where the cost of an error is highest.

What does the service do when asked “how do I protect my property?”

The fourth flag fires on the user’s intent: the user asks how to shield property from creditors before filing.

The law attaches harsh consequences to such intent:

Knowingly false information given to the financial manager or the court, established by a court ruling, removes the right to a discharge of debts (Art. 213.28(4)).
Concealing or deliberately destroying property when the obligation arose or was performed also leads to a denial of discharge (Art. 213.28(4)).
Transactions made to harm creditors are challenged under Art. 61.2(2).

The Supreme Court confirms this approach: an individual who hid assets or moved them out of reach does not get a discharge (para. 60 of the review of June 18, 2025).

Instead of advice, the service hands the question to a lawyer, who will explain where the line between permitted and prohibited lies.

Red Flags in labor disputes and in personal data

A table like this can be built in any area where a standard answer is dangerous. Here are two more examples.

Labor disputes. A fictional service helps an employer assess, under the Labor Code (LC) of the Russian Federation, whether an employee can be dismissed.

Red flag	Trigger in the user’s answers	Basis	Service action
Pregnant employee	The employer dismisses on its own initiative, the employee is pregnant	Art. 261(1) LC	Hands the case to a lawyer with no conclusion on whether the dismissal is lawful
Employee with family responsibilities	The employer dismisses on its own initiative, the employee is a woman with a child under three or an employee raising a child alone (other cases are listed in Art. 261(4))	Art. 261(4) LC	Hands the case to a lawyer with no conclusion on whether the dismissal is lawful
Dismissal during illness or leave	The employer dismisses on its own initiative, the employee is on sick leave or vacation	Art. 81(6) LC	Hands the case to a lawyer with no conclusion on whether the dismissal is lawful

The flag is checked only on the “dismissal on the employer’s initiative” path. Termination at the employee’s own request or by agreement of the parties does not trigger it, because the service would otherwise send a lawyer every case involving a pregnant employee.

Even on those paths, though, the service adds a warning: the employee may challenge whether the termination was voluntary. For a resignation at the employee’s own request, it is the employee who must prove it was forced (para. 22 of Supreme Court Plenum Resolution No. 2 of March 17, 2004).

Every provision has exceptions. For Art. 261(1) and Art. 81(6), these are the liquidation of the organization or the end of an individual entrepreneur’s activity, and for Art. 261(4) the exceptions are listed in the provision itself.

The employer must prove that the dismissal was lawful and that the procedure was followed (para. 23 of the same resolution). Employee guarantees are limited by the principle that rights must not be abused: for example, an employee may not hide an illness during the dismissal (para. 27).

The flag stops the service from answering “you can dismiss” and leaves the assessment of exceptions to a lawyer.

Personal data. A fictional service helps a company check, under Federal Law No. 152-FZ of July 27, 2006 “On Personal Data,” how it processes the data of customers and employees.

Red flag	Trigger in the user’s answers	Basis	Service action
Data incident	The user reports a leak or access by outsiders	Art. 21(3.1) of Law No. 152-FZ	Sets urgent priority, collects the information needed for the notice and hands the case to a lawyer right away
Special categories of data	Data on health, ethnicity or beliefs is processed	Art. 10(1) and (2) of Law No. 152-FZ	Hands the case to a lawyer with no conclusion on whether consent is sufficient
Data transfer abroad	Data goes to a foreign service or a foreign cloud	Art. 12(3) of Law No. 152-FZ	Hands the case to a lawyer before the data leaves

The first flag is urgent. If an unlawful or accidental transfer of data violated the rights of the individuals whose data it was, the law requires notifying Roskomnadzor within 24 hours of discovery and submitting the results of the internal investigation within 72 hours (Art. 21(3.1)).

For the notice, the service immediately collects:

when the incident was discovered;
what happened;
the suspected causes and the harm;
the measures taken;
the contact person.

If the lawyer has not stepped in by the set deadline, the service passes the case to the next person on duty, following a chain described in advance. I covered what a leak can cost in the article Data Leak: ₽400K Instead of ₽10M.

For special categories, the law allows processing with written consent and in the other cases listed in Art. 10(2). A lawyer decides which basis applies.

The law requires notifying Roskomnadzor in advance of an intention to transfer data abroad (Art. 12(3)).

How to write a red flag into a technical specification

In a technical specification (spec), each flag needs eight items for the developer:

Name. Short, so the lawyer recognizes the flag in the decision log.
Trigger. A direct question to the user and the answers that fire the flag. An AI model can help understand the user’s story, but the stop occurs only when an answer matches a trigger written by the lawyer.
Basis. The provision of law or the court position that explains the stop, and the date it was last checked against the text.
Action. The reply text for the user, a request status while waiting, and the information for the lawyer.
Order of checking. A red flag is checked before the other triage rules.
Response time. How soon the lawyer must step in and what the service does if the time runs out. The service owner sets the value, and it is shorter for urgent flags.
Rule owner. Who reviews the flag when the law changes.
Test situation. An example with a known result.

Stop factors come in two kinds:

Legal. The law does not allow a standard answer.
Informational. There is not enough data to make an assessment: the service asks for a document or a clarification and only then hands the case to a lawyer.

The message to the user at a stop is written in advance. A sample: “Your situation includes a circumstance the service cannot assess. Your answers have been sent to a lawyer, who will get back to you with an assessment.”

If several flags fire at once, all of them go to the lawyer.

Combinations that raise the danger are written into the spec separately. For example, transactions in the last three years together with the question “how do I protect my property?” get higher priority. That combination creates a risk of both challenged transactions (Art. 61.2(2)) and a denial of discharge (Art. 213.28(4)).

Five mistakes in designing red flags

Too many flags. The lawyer gets everything, and automation loses its point. A flag is created where a standard answer misleads and the cost of an error is high.
A flag with no legal basis. A year later no one remembers why it exists. Record the basis and the date of the last check right away.
A stop without an explanation. The user is left without an answer and leaves.
A trigger taken from free text. The word “mortgage” in a story does not yet mean a mortgage on the family’s only home. An AI model can pick up a hint and suggest a clarifying question, but the flag is set by the user’s answer.
No review. The law changes, and the flags stay the same.

A simple question helps against the fourth mistake (“Is there a loan secured by the apartment, including if you are a co-borrower?”). The answer “I don’t know” triggers a request for a document that removes the uncertainty (for example, an extract from the Unified State Register of Real Estate, EGRN), and only then a handoff to a lawyer.

How to test the table of flags

Each flag needs at least one test situation (calibration dataset).

Here are eight situations for our example:

A person lives in an only apartment with no mortgage and made no transactions. Expected route: no flags fire, and the service answers by the general instruction.
The only apartment has a mortgage. Expected route: flag 1, and the case goes to a lawyer.
Two years ago the user gave a car to a brother. Expected route: flag 2, and the lawyer gets a list of transactions.
The user sold an apartment to a stranger at market price two years ago. Expected route: flag 2. The lawyer assesses the transaction.
The user was the director of a company that was closed with debts. Expected route: flag 3.
Two years ago the user gave a car to a brother and asks how to transfer an apartment to a wife before filing. Expected route: flags 2 and 4, both go to the lawyer, and priority is raised.
The user does not know whether the apartment has a mortgage. Expected route: the service asks the user to check an EGRN extract, and if the user cannot, hands the case to a lawyer marked “data incomplete.”
The user bought an apartment with a spouse, the spouse took out the mortgage, and the user is a co-borrower. Expected route: the loan question covers co-borrowers, the answer is “yes,” and flag 1 fires.

The eighth situation tests a missed flag, the most dangerous error: the flag did not fire because the user did not understand the question.

For labor disputes and personal data, tests follow this principle: a situation for each flag plus one control case with no flags.

Frequently asked questions

How are Red Flags different from Triage Logic? Triage chooses a route and a priority from the combination of answers. A red flag is part of triage as its first rule: it fires on a single trigger and stops the service regardless of the other answers.

How many red flags does a service need? As many as there are situations where a standard answer misleads and the cost of an error is high. Start with the most dangerous and add to the list based on the decision log.

Can an AI model decide on its own what counts as a red flag? No. The model helps recognize what the user is asking about, but a stop occurs only when an answer matches a trigger written by the lawyer.

How often should the flags be reviewed? Whenever a provision a flag relies on changes, and after reviewing disputed cases from the log. For regular monitoring of provisions, the service page offers a support format (Legal Maintenance).

Red Flags in LegalTech: When a Legal AI Service Hands the Case to a Human