The Legal Lead Generation Standard

Status of this document

This is a working draft of a technical and market-conduct standard for legal lead generation and consumer case-request distribution. It is intended for public review by legal-aid organizations, state bar access-to-justice committees, consumer-protection stakeholders, attorney referral-service reviewers, law firms, legal marketing vendors, and legal technology providers.

The standard does not regulate attorney advertising, attorney referral fees, fee-splitting, solicitation, or professional responsibility. Those questions remain governed by state law, state bar rules, ABA Model Rules where adopted, and platform-specific terms. This standard addresses the infrastructure layer between the consumer's first request for legal help and the attorney or organization that may receive that request.

This is not a certification claim. FlowLegal products are works in progress against this standard and are not represented as certified or fully conforming.

Commercial disclosure

FlowLegal Partners LLC is the technical author of this working draft and operates products designed to implement parts of this baseline over time: FlowLawyers as a free public legal directory and intake surface, and FlowCounsel as a firm-side Growth and matter operating platform. The author has a commercial interest in the adoption of this framework. Products that implement consumer-protective lead distribution, firm-owned intake records, and auditable routing are advantaged in a market that adopts those requirements. That interest is disclosed here.

This standard is specified at the protocol and conduct layer, not as a FlowLegal-only implementation. Any directory, marketplace, law firm, answering service, legal aid organization, CRM, intake vendor, or marketing platform should be able to implement it.

1. Background

Legal lead generation has become a private market around public legal need. A consumer searches for help, completes a form, makes a call, or answers questions in a chat flow. That case request may then be routed, sold, re-sold, matched, auctioned, or handed off through systems the consumer never sees.

The market has useful parts. Lawyers need distribution. Consumers need paths to attorneys. Small firms need acquisition channels that do not require them to become advertising operators. The problem is not that legal demand is matched with legal supply, or that a marketplace may charge for access to a consumer case request.

The problem is dark-marketplace behavior: the matching layer often optimizes for arbitrage before it optimizes for consumer protection, legal-aid fit, attorney fit, consent, or accountability.

AI increases the urgency. Automated chat, voice, SMS, and form-processing systems make intake cheaper to scale. Without a standard, lower intake cost can produce more harvesting, more resale, more opaque routing, and more pressure on consumers who already do not understand the market they have entered.

This standard defines a baseline for case-request distribution that is compatible with attorney advertising rules, legal aid, private representation, and firm growth, while rejecting the most harmful forms of lead arbitrage.

A standards-aligned marketplace may charge attorneys or firms for case-request access, provided the consumer has consented, distribution is capped, economics are disclosed, legal-aid and pro bono routing are preserved where relevant, and the receiving firm retains a structured intake and provenance record after acquisition.

2. The problem this standard is designed to solve

A consumer who asks for legal help should know:

• whether their information will be shared
• who may receive it
• how many attorneys or firms may receive it
• whether any receiving attorney paid for access
• whether legal aid or pro bono options were considered before a paid path
• whether the platform is ranking attorneys because they paid more
• how long their intake information will be retained
• how to withdraw consent where withdrawal is still meaningful

In many current systems, the consumer does not know those things. The attorney often does not know enough either. The firm receives a "lead" without a clear provenance record, consent state, distribution history, acquisition cap, source page, routing reason, or legal-aid screen posture.

That is not just a marketing problem. It is an infrastructure problem.

3. Scope

Applies to:

• directories that collect consumer case requests and route them to attorneys or firms
• marketplaces where attorneys pay to receive, review, acquire, or respond to case requests
• call centers, chat providers, answering services, AI receptionists, and intake vendors that route consumer legal requests for compensation
• law firm marketing vendors that host forms, landing pages, chat flows, phone flows, or routing logic
• CRMs or intake systems that receive case requests from paid intermediaries
• AI-assisted and non-AI case-request distribution where compensation affects routing, access, priority, or contact rights

Does not apply to:

• a consumer contacting a law firm directly through the firm's own website, phone number, or office, unless a third-party intermediary controls routing or resale
• legal aid intake that does not route consumers to attorneys for compensation
• private attorney referral between lawyers where the consumer has already authorized the referral and professional-responsibility rules govern the relationship
• attorney-side evaluation of a case request after the attorney receives it

3.1 Normative language

"Must", "must not", "required", "shall", and "shall not" indicate mandatory baseline requirements. "Should" indicates a recommended practice. "May" indicates an allowed implementation choice.

4. Baseline requirements

4.1 Free public discoverability

A compliant directory or public legal-help surface must support a free baseline attorney or firm profile. The baseline profile must allow consumers to identify the attorney or firm, practice areas, jurisdiction, contact path, language capacity where offered, accessibility information where provided, and whether pro bono, reduced-fee, or limited-scope services are available.

Paid enhancement may exist. Paid enhancement must not be required for basic discoverability, and it must not obscure whether the profile is a paid placement.

4.2 No pay-to-rank routing

Payment must not determine the order in which attorneys are presented as the best substantive match for a consumer's legal need. Sponsored placement is allowed only if clearly labeled as advertising and separated from match-quality claims.

Where a platform presents matched attorneys, the ranking basis must be stated in plain language. Acceptable ranking factors include practice area, geography, bar status, language capacity, availability, conflicts posture where known, legal-aid eligibility fit, and consumer-stated preference. Bid amount is not an acceptable match-quality factor.

4.3 Distribution cap

A consumer case request must not be distributed without a cap. The cap must be visible in the consumer disclosure before submission.

Reasonable policy values include:

1. exclusive distribution to one attorney or firm
2. shared distribution to no more than three attorneys or firms
3. legal-aid or pro bono referral paths where the receiving organization determines capacity under its own rules

Bulk resale is prohibited. Re-distribution after a declined matter requires consumer notice, renewed consent where practicable, and a new distribution record.

4.4 Consent before transfer

Consumer case-request content must not be transferred to an attorney, firm, advertiser, broker, or downstream intermediary until the consumer has seen and accepted a disclosure that states:

1. the platform is not the consumer's lawyer
2. submission does not create an attorney-client relationship
3. attorney response is not guaranteed
4. the consumer's information may be shared with up to N attorneys or firms
5. attorneys or firms may pay to receive or review the request
6. the platform does not recommend an attorney merely because the attorney paid
7. legal aid or pro bono options may be more appropriate for some consumers
8. the consumer may withdraw or limit consent where the request has not already been transferred

Consent must be recorded as a durable event with timestamp, disclosure version, source surface, and transfer scope.

4.5 Legal-aid and pro bono branch

Where the matter type and geography make legal aid, pro bono, court self-help, or public agency referral potentially relevant, the platform must not route immediately into a paid-attorney funnel without surfacing a public-benefit branch.

The platform does not need to determine final legal-aid eligibility. It must preserve the possibility of legal-aid routing before monetized distribution takes over. When the platform performs means testing, the output must be framed as "may qualify", not as final eligibility.

4.6 Transparent economics

The platform must disclose the economic structure behind case-request access in plain language. The consumer does not need to see each attorney's price, but the consumer must know whether the platform charges attorneys or firms for access, review, priority, sponsorship, subscription, or routing.

Attorneys and firms must receive a written explanation of:

• whether they are paying per case request, per exclusive request, per shared request, per month, per profile, or per campaign
• whether competitors may receive the same request
• whether the consumer was told the distribution cap
• whether the request came from paid advertising, organic search, directory discovery, referral, social media, phone, chat, or another channel
• whether the platform or an affiliate retains the consumer record after handoff

4.7 Source and provenance packet

Every routed case request must carry a provenance packet. At minimum:

• source surface
• source URL or phone line
• campaign identifier where applicable
• practice area or matter category
• geography
• disclosure version
• consent state
• distribution cap
• recipient list or recipient count, subject to privacy constraints
• routing reason
• legal-aid branch posture
• timestamp of transfer
• retention posture
• AI involvement flag where any model influenced classification, summarization, routing, or follow-up
• safe-contact preferences and contact restrictions where the consumer supplied them
• sensitive-legal-need safety posture where applicable, without exposing unnecessary narrative facts

The receiving firm should not have to reconstruct where the request came from by reading a vendor dashboard screenshot.

A routed case request involving sensitive legal need must preserve the consumer-approved safety constraints that govern contact and handoff. The provenance packet should tell the receiving attorney or organization how to contact the consumer safely, what channels should not be used, and whether legal-aid, pro bono, emergency, or safety-related routing was surfaced, without turning the consumer's full narrative into unnecessary resale inventory.

4.8 Attorney credentialing

A platform that routes case requests must verify that the receiving attorney or firm is eligible to receive that type of request. At minimum, the platform must collect jurisdiction, license status or attestation process, practice area fit, receiving entity, and contact authority.

Credentialing does not create a platform endorsement. It is a baseline control against routing consumers into obviously mismatched or unverified channels.

4.9 Data minimization and retention

The platform must collect only the information reasonably needed to classify, route, and hand off the request. It must not collect unrelated demographic, financial, behavioral, or marketing-profile data unless that data is necessary for legal-aid screening, accessibility, language access, or consumer-requested matching.

Consumer-identifiable case-request data must not be retained indefinitely by default. The platform must publish a retention policy and must provide deletion or suppression mechanics where legally and operationally available.

4.10 No surveillance on intake

Consumer legal intake and case-request forms must not include third-party advertising pixels, data-broker tags, retargeting scripts, or behavioral surveillance tools that transmit consumer-identifiable legal need to ad networks or unrelated third parties.

Aggregate analytics for quality, reliability, fraud prevention, and routing performance are permitted if they do not expose consumer-identifiable legal need to advertising or data-broker ecosystems.

Sensitive legal need must not be used for lookalike audiences, retargeting, enrichment, data-broker matching, or behavioral advertising. This includes immigration, domestic violence, criminal, housing, employment retaliation, benefits, disability, trafficking, custody, protest, political-activity, and other safety-risk categories where disclosure or inference could expose the consumer to enforcement, retaliation, surveillance, economic harm, or violence.

5. Required audit events

A compliant implementation should be able to emit content-minimized audit events, including:

• lead.disclosure.presented
• lead.consent.captured
• lead.legal_aid_branch.presented
• lead.routing.recommended
• lead.transfer.completed
• lead.distribution_cap.recorded
• lead.recipient.credentialed
• lead.redistribution.requested
• lead.redistribution.consent_captured
• lead.retention.transitioned
• lead.deletion.requested
• lead.ai_involvement.recorded
• lead.safe_contact_preferences.presented
• lead.safe_contact_preferences.captured
• lead.contact_restrictions.recorded
• lead.sensitive_legal_need.posture_recorded

The audit event should prove that the required control occurred without transmitting raw narrative facts to a standards auditor.

6. Relationship to the Consumer Legal AI Intake Standard

The Consumer Legal AI Intake Standard governs AI-assisted or AI-influenced intake conversation, classification, legal information, citation provenance, eligibility triage, and data handling.

This standard governs the market layer that receives, prices, distributes, and transfers consumer case requests. The two standards overlap where AI influences routing or where an intake record becomes a compensated case request.

7. Relationship to FlowLawyers and FlowCounsel

FlowLawyers is designed around free public profiles and consumer-facing legal help. FlowCounsel Growth is designed to let firms receive intake, run CRM, manage attribution, and understand marketing performance in a system the firm controls.

FlowCounsel Marketplace is intended to be a standards-aligned marketplace pattern, not a dark lead-resale pattern: case requests should carry consent state, disclosure version, source, attribution, distribution cap, legal-aid posture, routing reason, and post-acquisition intake retention for the receiving firm.

This standard is not written to require use of those products. It is written to define the minimum behavior any legal lead-generation infrastructure should satisfy if it handles consumer legal need.

8. Open questions for review

1. What is the right default distribution cap for shared consumer case requests?
2. What economic controls should apply to case-request access, subject to legal, ethics, and antitrust review: disclosed ranges, administrative-fee models, audited cost-recovery formulas, after-the-fact review, or another consumer-protective structure?
3. What attorney credentialing evidence should be mandatory versus optional?
4. What retention period should apply when a request is routed but no attorney accepts it?
5. How should legal-aid routing be handled when the relevant legal-aid organization lacks capacity or a public intake endpoint?
6. What data should a receiving firm be required to return to improve routing quality without exposing privileged or confidential matter facts?

9. Closing position

Legal lead generation should not be an opaque resale market for urgent human problems.

A healthier market is possible: free public discoverability, disclosed economics, capped distribution, legal-aid-first routing where appropriate, firm-owned intake records, and auditability from source to handoff.

That is the minimum standard.