Declining Client Inquiries: Five Workflow Mistakes Law Firms Should Avoid

A client inquiry does not yet constitute an accepted retainer. Nevertheless, it must not be left sitting in a general inbox for days on end. Section 44 of the German Federal Lawyers’ Act (BRAO) stipulates: Any attorney who is approached for professional services and does not wish to accept the retainer must declare their refusal without delay. If damage results from a culpably delayed declaration, the provision stipulates a duty to pay compensation.

For day-to-day law firm operations, this does not mean a universal rejection letter, but rather a clear workflow: Identify the incoming request, assess its urgency, verify jurisdiction, make a clear decision, and close the case in a controlled manner.

Most risks do not arise from a deliberate refusal. They arise between the contact form, the acknowledgment of receipt, internal forwarding, and the assumption that someone else will take care of it. This error analysis highlights five typical points of failure and summarizes the safe procedure in the 5E model: Receipt, Urgency, Decision, Explanation, and Closure.

Error 1: The automatic reply already sounds like a commitment

“Thank you very much for your inquiry. We’ll look into your request and get back to you shortly.” This is friendly, but organizationally imprecise. Anyone who has not yet assessed potential conflicts, capacity, or subject-matter expertise should not give the impression that processing has already begun.

A confirmation of receipt should clearly distinguish between three things:

• The message has been technically received.
• This does not imply acceptance of the case.
• Until an explicit confirmation is provided, no deadlines will be monitored and no actions will be taken.

Whether a lawyer-client agreement has already been formed in a specific case depends not solely on a standard phrase, but on the overall conduct and specific statements made. The German Bar Association points out that case law imposes strict requirements on the acceptance of a contract through conclusive conduct. This is precisely why clarity is more sensible than hoping that a misleading process will be interpreted correctly later on.

The user interface is also a factor. A button labeled “Start Case” conveys something different from “Submit Inquiry.” A “Accepted” status must not be set automatically simply because an appointment was booked or a document was uploaded. The legal classification and system status must align.

Mistake 2: Urgent inquiries wait in the same queue as everything else

Section 44 of the BRAO does not specify a fixed hourly or daily deadline. “Without delay” depends on the circumstances. The Berlin Bar Association explains that a reasonable period for review and consideration may exist; however, if an impending deadline is apparent without the need for extensive review, immediate action must be taken. The German Bar Association also emphasizes that, in cases of apparent urgency, a response may be necessary on the very same day.

This does not mean that a law firm must accept every deadline stated in free-text without verification. From an organizational standpoint, it means that urgent notifications must be visible before the normal assignment of cases to specialists.

A practical intake process therefore asks the following questions early on:

• Is there a known deadline or expiration date?
• What date was specified?
• Which document specifies the date?
• Has legal assistance already been retained elsewhere?

This information serves primarily as triage data, not a final deadline calculation. It helps the team decide whether an incoming matter must be immediately assigned to a lawyer. Simply marking a case as “red” without assigning a responsible person is not sufficient. The workflow requires an escalation contact, a substitute, and a time at which an unprocessed alert will trigger a new notification.

The article beA Outage: How Law Firms Ensure Deadlines and Substitute Filings addresses the subsequent emergency situation within an ongoing case. For new inquiries, the crucial protective step comes earlier: The law firm must quickly clarify whether it will take on the case at all.

Mistake 3: “We’ll look into it” remains without status or accountability

Many law firms have only a vague intermediate state between “new inquiry” and “case.” A message is forwarded; someone checks the opposing party; another person assesses capacity—and for the person who made the inquiry, it remains unclear whether action is already being taken.

This can be avoided with five defined statuses:

Each status requires an assigned owner and a maximum internal processing time. These timeframes are not universal statutory deadlines. They are organizational checkpoints that must be tailored to the firm’s size, availability, and case structure.

For the conflict check, the process should also avoid hastily collecting complete case details and document packages. The article Check Opponents First, Then Open the File explains why identifying the parties involved and conducting a limited preliminary review often come before the detailed intake.

Mistake 4: The rejection is polite but ambiguous

Phrases such as “We are currently refraining from handling this matter” or “Unfortunately, we are unable to assist you at this time” can leave unnecessary room for interpretation. A rejection should make it clear that the firm will not accept the case and will not perform any work.

Section 44 of the Federal Lawyers’ Act (BRAO) does not prescribe any specific form for a rejection. The Berlin Bar Association recommends a written statement for documentation purposes and clarifies that a justification is not required. Whether the law firm nevertheless provides a brief reason is a matter of communication strategy and may require particular discretion in cases of conflicts of interest or confidential circumstances.

A robust boilerplate text objectively answers four questions:

1. Is the case being accepted? – No, stated unequivocally.
2. Are any measures or deadlines already being monitored? – If not, make this explicitly clear.
3. Is there any apparent time pressure? – Indicate that other legal counsel should be sought immediately, without providing an unverified assessment of the legal situation or deadlines.
4. What happens to submitted documents? – Explain in a transparent manner whether they will be returned, made available upon request, or processed further.

A general rejection should not mimic individual legal advice. In particular, the team should not casually assess the prospects of success or calculate a specific deadline if the firm has explicitly declined to undertake such an assessment. However, in cases of apparent urgency, the wording must be clear enough that the person making the inquiry does not wait for a further response from the law firm.

For statements made outside the firm’s offices, receipt is also practically relevant. Section 130 of the German Civil Code (BGB) links the effectiveness of a declaration of intent requiring receipt to an absent party to its actual receipt. A rejection saved in a draft folder is therefore not a completed process. The law firm should document the delivery channel, the time of sending, and—if available—the delivery status, and follow up on undelivered messages.

Mistake 5: Sending the email only ends the email itself, not the process

After a rejection, tasks often remain unresolved: originals or uploads must be handled, a contact remains on a marketing list, access rights are still in place, and the conflict check may require a limited data set.

The follow-up article Rejected Client Inquiry: What Law Firms Should Delete distinguishes between complete case data, a minimal conflict-check lock core, and technical system logs. This separation should be triggered by the “rejected” status.

Under data protection law, principles such as purpose limitation, data minimization, and storage limitation apply in accordance with Article 5 of the GDPR. A rejection does not automatically result in the same deletion period for every data record. However, the process should prevent a rejected request from being permanently treated as an active mandate—or used for marketing—without a new purpose.

The case must also be closed internally: remove open tasks, cancel appointments, terminate responsibilities, and prevent accidental subsequent processing. A rejection with a still-active “Check Deadline” task is just as dangerous as a deleted task without an explanation having been sent.

The 5E Model for a Controlled Rejection Workflow

The five errors can be translated into a compact workflow.

1. Inbox

All channels—forms, email, phone notes, and in-person submissions—lead to a shared inbox. The confirmation explicitly designates the entry as an inquiry, not as an accepted mandate. The team knows where new engagement proposals will appear.

2. Urgency

A clear triage step checks for identifiable dates and deadlines without pretending to perform a technical deadline calculation at this stage. Notable incoming requests are immediately forwarded to a designated attorney. Rules for representation and escalation apply even during vacation or sick leave.

3. Decision

Conflicts of interest, professional jurisdiction, capacity, and economic acceptance criteria are reviewed in a defined order. Only an authorized person sets the status to “accepted” or “rejected.” Scheduling an appointment or uploading a document does not replace this decision.

4. Notification

Acceptance or rejection is communicated clearly, verifiably, and through an appropriate channel. In the event of rejection, it is made clear that no work will be undertaken and no deadlines will be monitored. Apparent time pressure is addressed objectively, without providing unverified advice on individual cases.

5. Closure

Outgoing communications are monitored, returned items are processed, and documents and data are subjected to a documented closure process. The process is retained only to the extent that a specific purpose and a legal basis are documented.

How Law Firms Test the Process Without a Major Project

For a practical test, the last ten rejected inquiries are sufficient to start with. For each case, reconstruct the time of receipt, the first human review, any apparent urgency indicators, the time of the decision, and the actual sending of the rejection.

Afterward, don’t just examine the average processing time. The exceptions are more interesting: Which request took the longest? Why? Was there a message that was assigned to multiple people at the same time or to no one at all? Did a confirmation of receipt sound like an acceptance? Was a return notice noticed? What data remained in the systems afterward?

From these cases, create a brief set of work instructions that include status, responsible parties, escalation procedures, and boilerplate text. Automation is only worthwhile once this workflow is functioning properly. An unclear process simply becomes unclear more quickly when automated emails are used.

Jurono Perspective: Intake Requires Decisions, Not Just Forms

Jurono views digital client onboarding as a structured transition from initial contact to a processable client record. The same principle is central to the rejection workflow: Information must not only be received but must lead to a transparent decision that specifies responsibility and the next step.

The specific status, notification, and documentation options available in a given Jurono implementation—and which are suitable for your firm’s organization—should be evaluated based on the current scope of functionality. Jurono does not replace the legal assessment of accepting a case nor the case-by-case review required under § 44 BRAO. However, a demo can simulate a real inquiry process from receipt through conflict and urgency checks to a clear decision.

Conclusion: A Good Rejection Starts at the Point of Receipt

A secure rejection of a case is not just a single text block. It is the result of a controlled intake process. Anyone who only begins to consider urgency, jurisdiction, and acceptance status when writing the rejection is starting too late.

The 5E model provides a streamlined framework: record the intake, identify urgency, assign a decision, deliver the explanation, and fully close the case. In doing so, the law firm not only reduces liability and organizational risks. It also provides clients with the clarity they need early on to seek alternative assistance in a timely manner.

This article is intended for general organizational and legal guidance and does not constitute individual legal advice. Whether a retainer agreement has been formed and what response is required in each specific case must be examined on a case-by-case basis.

Sources

1. Federal Ministry of Justice / Federal Office of Justice – “§ 44 BRAO – Notification of Refusal of an Engagement,” current version of the law, https://www.gesetze-im-internet.de/brao/__44.html,, accessed: August 13, 2026. Supporting statement: Obligation to decline immediately and to compensate for damages resulting from culpable delay.
2. Federal Ministry of Justice / Federal Office of Justice – “§ 43a BRAO – Fundamental Duties,” current version of the law, https://www.gesetze-im-internet.de/brao/__43a.html,, accessed August 13, 2026. Supporting Statement: Confidentiality and prohibition on acting in cases of conflicting interests.
3. Federal Ministry of Justice / Federal Office of Justice – “§ 121 BGB – Period for Challenging a Contract,” current version of the law, https://www.gesetze-im-internet.de/bgb/__121.html, Retrieved: August 13, 2026. Supporting statement: statutory wording “without culpable delay (immediately)”; its application to § 44 BRAO is further clarified by the Berlin Bar Association (RAK Berlin).
4. Federal Ministry of Justice / Federal Office of Justice – “§ 130 BGB – Effectiveness of a Declaration of Intent with Respect to Absent Parties,” current version of the law, https://www.gesetze-im-internet.de/bgb/__130.html,, accessed: August 13, 2026. Supporting statement: Service of a declaration of intent requiring acknowledgment of receipt on absent parties.
5. Berlin Bar Association – “The Obligation to Immediately Notify of a Decline pursuant to § 44 BRAO,” no publication date indicated, https://kammerton.rak-berlin.de/ausgaben/ausgabe-drucken/?id=197&single=1,, accessed: August 13, 2026. Supported statement: Organization of incoming mandates, case-by-case review period, immediate response upon recognition of an expiring deadline, form, and liability consequences.
6. German Bar Association / Anwaltsblatt, Antje Jungk – “Declining a Mandate – No, Thank You?”, February 24, 2023, https://anwaltsblatt.anwaltverein.de/de/themen/kanzlei-praxis/mandat-ablehnen,, accessed August 13, 2026. Supporting statement: no general obligation to enter into a contract outside of specific statutory cases, clear refusal, significance of apparent urgency, and possible pre-contractual obligations.
7. European Union, EUR-Lex – “Regulation (EU) 2016/679 (General Data Protection Regulation),” April 27, 2016, in particular Articles 5, 13, and 17, https://eur-lex.europa.eu/legal-content/DE/TXT/HTML/?uri=CELEX:02016R0679-20160504,, accessed August 13, 2026. Supporting Statement: Purpose limitation, data minimization, storage limitation, transparency regarding storage duration and deletion.

This rejection workflow is directly linked to the digital client onboarding process: The receipt and structuring of data are automated, but not the decision regarding acceptance or rejection.