LuMayEverything AI. One Platform.
Products
Specialized AI solutions
AI products for business functions, industry workflows, and enterprise operations.
Production ReadyLuMay Legal Agents(Lexintis)Legal ops, compliance, billing, and document intelligence.
Production ReadyLuMay Voice Agents(Voxentis)Conversations, orchestration, actions, and follow-up.
HealthcareIntake, scheduling, care, and clinical operations.
Financial ServicesBanking, insurance, compliance, and finance workflows.
ManufacturingQuality, supply chain, operations, and field service.
Explore All ProductsFlexible deployment across SaaS, Azure, private cloud, hybrid, and on-prem.
Don't see your use case? Choose a suitable product or bring your workflow. We'll build it quickly.Book a Demo
Platform
Built once · governed · deployed anywhere
The runtime, connectors, governance, and analytics behind every LuMay agent.
Core Agent EngineRuntime for every AI agent.
Orchestration EngineCoordinates agents, approvals, and actions.
Connectors & AdaptersConnects systems, data, documents, and voice.
Security & GovernanceAccess, audit, privacy, and human review.
Deployment & AnalyticsDeploy anywhere. Measure ROI from week one.
Explore PlatformOne enterprise AI operating layer. Any deployment.
Need help turning workflows into AI agents?Book a Platform Call
Services
Generative AI · agents · enterprise · advisory
Build, integrate, and run AI with engineering and advisory support.
Generative AI DevelopmentCustom generative apps and copilots.
LLM DevelopmentFine-tuned, domain-specific models.
RAG DevelopmentGrounded retrieval over your own data.
AI Agent DevelopmentTask and workflow agents in production.
AI Automation ServicesAutomate manual, repetitive operations.
AI Integration ServicesConnect agents to systems and data.
Explore All Services
New to AI?Not sure where to start? We'll map your first use cases.Book Discovery
Pricing
SaaS · your cloud · on-prem · air-gapped
Plans, packaging, and deployment options for every team size.
Product PlansPer-agent plans and what's included.
Services PricingAdvisory, implementation, and support.
AI AcademyTraining and enablement programs.
Deployment OptionsSaaS, your cloud, on-prem, air-gapped.
Explore Pricing
Need a custom quote?Talk to a pricing expert for volume or enterprise terms.Contact Sales
Company
Mission · people · community · ecosystem
Who we are, how we work, and the partners we build with.
About LuMayCompany story, mission, and platform vision.
Leadership TeamExecutive and AI delivery leaders.
Advisory TeamStrategic advisors and industry experts.
Culture & ValuesHow LuMay builds, serves, and scales.
Life at LuMayHow teams work, learn, and grow.
CareersBuild the next generation of enterprise AI.
Explore Company
Build · partner · growWant to build, partner, or grow with LuMay?Contact LuMay
Resources
Proof · insights · learning · explore
Proof, frameworks, and learning to evaluate and adopt enterprise AI.
Case StudiesCustomer outcomes and production AI examples.
GalleryDemos, screenshots, and product visuals.
Success StoriesBusiness wins, adoption, and ROI proof.
LinkedIn PostsLatest updates and insights.
NewsletterEvents, milestones, and enterprise AI updates.
Explore Resources
Not sure where to look?Tell us the problem and we'll point you to the right resource.Talk To Us
Book demo
Book demo
LuMay logo

Building the Autonomous Workforce behind every Business Function.

sales@lumay.ai
+1 (320) 228-4730
ISO 27001 CertifiedSOC 2 Type II Certified

Platform

  • Agentic Core
  • Our Agents
  • Pricing & Engagement
  • Architecture
  • Deployment

Solutions

  • LuMay Legal Agents (Lexintis)
  • LuMay Voice Agents (Voxentis)
  • Insight Agents
  • Workflow Automation Agents
  • All Agents

Services

  • Generative AI Development
  • LLM Development
  • RAG Development
  • AI Agent Development
  • AI Automation Services
  • AI Integration Services
  • All Services

Resources

  • Case Studies
  • Blog
  • ROI calculator
  • Enterprise AI Framework
  • Trust & Security
  • AI Governance Framework
  • Learning Hub

Company

  • About
  • Leadership
  • Advisory Team
  • Partnerships
  • Life at LuMay
  • Careers
  • Contact

Request an AI Summary

Learn more about how LuMay is transforming enterprise AI adoption for leading businesses.

ChatGPTClaudePerplexity

Make LuMay a Preferred Source

QR code linking to lumay.ai
©2025 - 2026 LuMay Inc · All rights reserved
PrivacyCookiesTermsTrustLLM PolicyE-Verify
SOC 2 Type II & ISO 27001 Certified
Home>Blogs>What Is Block Billing? Examples, Billing Risks, and AI Review Checks

What Is Block Billing? Examples, Billing Risks, and AI Review Checks

Editorial Team

Sarath Babu

Content Writer and SEO Specialist at Lumay

Creates insightful content on SEO, AI-powered marketing, digital growth, and emerging technologies. He simplifies complex topics into practical, research-backed guidance.

Editorial Team

Written by

Sarath Babu

Palanisamy

Palanisamy

CEO and Founder at LuMay

27+ years leading enterprise-scale AI, data, and systems architecture initiatives, delivering mission-critical platforms focused on trust, governance, and reliability.

Palanisamy

Reviewed by

Palanisamy

Published date: October 15, 2026

Expert Verified13 min read

Summarize with AI

ChatGPTPerplexityClaudeGeminiGrok
Editorial Team
Editorial Team

Legal AI Expert

Table of Contents
1. What Is Block Billing?2. Simple Block Billing Examples3. Acceptable vs. Problematic Time Entries4. Is Block Billing Always a Problem?5. Why Block Billing Creates Review Difficulties6. Common Billing Risks7. Outside Counsel Guideline Concerns8. How Reviewers Traditionally Identify Block Billing9. How AI Can Detect Potential Block Billing10. NLP Analysis of Time-Entry Narratives11. Detection of Multiple Tasks in One Entry12. Duration and Narrative-Pattern Analysis13. Billing-Rule Engines14. Anomaly Detection15. Outside Counsel Guideline Checks16. Human-in-the-Loop Validation17. False Positives and Limitations18. Why Human Review Is Still Necessary19. How Timekeepers Can Correct Block-Billed Entries20. Block Billing Review Checklist21. Where LuMay Legal Agent Fits22. Your Next Step23. Frequently Asked Questions
Block billing examples, billing risks, and AI review checks

Block billing examples, billing risks, and AI review checks

Block billing is the practice of putting several tasks into one time entry with a single total, so no one

can see how long each task took. It makes legal billing review harder because a reviewer cannot judge

whether the time spent on any one task was reasonable. AI can flag entries that look block billed, but a person

still has to decide whether an entry is actually a problem.

What Is Block Billing?

Block billing groups multiple activities under one block of time. For example, an entry may list a settlement-call

prep, research and a draft response with only a total such as 3.4 hours. Brightflag defines it in similar terms:

one invoice line, a list of tasks, and no time shown for each. The FDIC's outside counsel guidance describes it

the same way, as an entry that includes more than one task so that the time for each task is not recorded

separately (FDIC OIG report).

It is not always dishonest. A busy timekeeper may simply record a day's work in one line. The problem is what

the line hides from the person paying for it.

Related LuMay legal billing guides: Compare the best tools for detecting block billing and duplicate time entries, review how to automate legal billing, and see how firms move from billing violations to automated compliance.

Simple Block Billing Examples

Block-billed entryHoursWhy it is flagged
Prepare for settlement call; research issue on second claim; draft response to opposing counsel3.4Three distinct tasks, no time for each
Review documents, confer with client, update case chronology4.0Three activities, one total
Attend hearing; follow-up email to client; revise brief6.5Different activities, likely different task codes

The first row follows the pattern in Brightflag's own example, which bundles three tasks into a single 3.42-hour

entry. The other rows are illustrative and not drawn from any real invoice.

Acceptable vs. Problematic Time Entries

A clearer entry usually has one task, one outcome and one time value. Related steps of a single task can still sit together.

Problematic entryClearer entries
"Research, draft motion, call with client re: strategy" (4.5 hrs)"Research venue case law for motion to dismiss" (1.8 hrs); "Draft motion to dismiss, sections I and II" (2.0 hrs); "Call with client re: motion strategy" (0.7 hrs)
"Prepare for and attend mediation, follow up with team" (7.0 hrs)"Prepare mediation statement" (2.5 hrs); "Attend mediation" (4.0 hrs); "Debrief with team on mediation outcome" (0.5 hrs)
"Review correspondence, analyze discovery, prepare deposition questions, confer with associate, email client" (4.1 hrs)"Analyze opposing party's discovery responses" (1.4 hrs); "Prepare deposition questions" (1.7 hrs); "Confer with associate on deposition strategy" (0.6 hrs); "Update client on deposition preparation" (0.4 hrs)
"Case work" (3.0 hrs)"Review and annotate deposition transcript of J. Smith" (3.0 hrs)

The last row is a related but separate problem. "Case work" is not block billing, but it fails review for a similar

reason: it does not say what was done.

Is Block Billing Always a Problem?

Not always. Whether an entry is a problem depends on the client's rules, the level of detail and the context.

  • Many clients allow small exceptions. The FDIC's outside counsel deskbook, quoted in its Inspector

General's report, does not accept block billing except for multiple related activities that take no more than

30 minutes in total (FDIC OIG report).

  • Some clients allow none. The State of New Jersey's outside counsel guidelines say block billing will not

be accepted, that invoices containing it will be returned, and that only a designated state official can waive

the requirement (NJ Attorney General guidelines).

  • Courts apply their own standards. In Welch v. Metropolitan Life Insurance Co. (9th Cir. 2007), the court

noted that a state bar report found block billing "may increase time by 10% to 30%." It still held that a 20%

cut to all hours was error, because only slightly more than half the hours were block billed. This is a

fee-award case, so it does not set rules for ordinary client invoices.

The practical question is not "does this entry contain more than one task?" It is "does this entry give enough

information to judge the work and the time?"

Why Block Billing Creates Review Difficulties

Reviewers need to compare time against task, staffing and the guidelines. Block billing removes the detail that

comparison needs.

  • No per-task time. A long entry can hide an unreasonable amount of time on one task. Rees Morrison's

example, as quoted by Brightflag, is a 3.4-hour email on a discrete issue that was impossible to detect

inside a larger 8.7-hour block.

  • Mixed task codes. One entry may cover work that belongs under several UTBMS codes, which distorts

spend reports.

  • Slower approvals. Reviewers must query the firm, and rejected invoices must be corrected and

resubmitted.

  • Weaker budget tracking. Phase and task totals become less reliable.
  • Inconsistent decisions. Different reviewers may treat the same entry differently when the guideline is

silent or unclear.

Common Billing Risks

The risks fall on both sides of the relationship.

  • For clients: Harder cost control and less confidence that the time billed was reasonable.
  • For firms: Invoice rejections, payment delays, write-downs and strained client relationships.
  • For ethics: ABA Model Rule 1.5(a) says a lawyer shall not charge or collect an unreasonable fee. Block

billing does not violate that rule by itself, but it makes reasonableness harder to show.

  • In fee-shifting disputes: Courts may reduce hours when entries are block billed, as the Welch case

shows.

Rules and court practice vary by jurisdiction and by court. Confirm what applies to your matters.

Outside Counsel Guideline Concerns

Outside counsel guidelines (OCGs) are the client's billing rules for its law firms. Many prohibit block billing,

and some also set rules on time increments, vague narratives or task coding. The New Jersey guidelines, for

example, require time in tenths of an hour and separate entries for each distinct task. Requirements differ by

client, so each OCG must be read on its own terms.

UTBMS provides the task, activity and expense code sets used to classify legal work. LEDES defines the

electronic billing formats that carry those codes. Brightflag notes that traditional LEDES invoices call for one

activity code and one task code per line, so a block-billed line cannot be coded cleanly and may be rejected.

Task codes alone do not prevent block billing, because a narrative can still combine several activities under

one code.

How Reviewers Traditionally Identify Block Billing

Manual legal invoice auditing relies on pattern recognition and a close reading of narratives.

  1. Get the client's OCG and find its block billing rule and any exceptions.
  2. Scan for long entries, especially those over several hours.
  3. Look for lists of tasks separated by commas, semicolons or "and."
  4. Check whether the narrative matches the single task code on the line.
  5. Compare the entry against the OCG and any matter budget.
  6. Query the firm for a corrected or split entry when needed, and record the reason for the decision.

This works, but it is slow and varies from reviewer to reviewer. Volume is the main constraint.

How AI Can Detect Potential Block Billing

AI legal bill review can score entries for the signs above and put the likeliest ones in front of a reviewer. It flags

entries for review. It does not decide that an entry is improper. Some e-billing vendors do this already:

Brightflag says its software flags lines with multiple activities and can split time across UTBMS codes, a

vendor claim worth testing on your own invoices.

NLP Analysis of Time-Entry Narratives

Natural language processing reads the text of each narrative. It can pick up list structures, semicolons,

conjunctions and verbs that suggest separate activities, such as "review," "draft" and "call."

Detection of Multiple Tasks in One Entry

A model can estimate how many distinct tasks an entry describes and compare that count with the hours

billed. This works best when the client's guideline defines block billing precisely.

Duration and Narrative-Pattern Analysis

Long durations paired with long, list-like narratives are a stronger signal than either alone. Round numbers

across many entries from one timekeeper can also be a pattern worth a look.

Billing-Rule Engines

Rules encode checks that are clear-cut, such as a maximum hours threshold, a banned phrase or a 30-minute

exception. They are transparent but rigid, and they miss entries that avoid the keywords.

Anomaly Detection

Statistical methods compare an entry against peers, such as similar tasks on similar matters. This supports

invoice anomaly detection, but "unusual" does not mean "wrong."

Outside Counsel Guideline Checks

OCG checks apply a client's specific rules to each line. The rules must be configured and kept current, since

they differ from client to client.

Human-in-the-Loop Validation

The reviewer sees the flag, the entry and the reason, then approves, queries, adjusts or rejects. Their

decision, not the flag, is the outcome of record, and it should be logged.

ApproachWhat it surfacesMain limitation
NLP on narrativesTask lists, multi-verb textCannot see actual time per task
Multi-task detectionEntries with 2+ activitiesRelated steps may be one task
Duration patternsLong, list-like entriesLegitimate long tasks exist
Rule enginesClear OCG violationsRigid, keyword-dependent
Anomaly detectionOutliers versus peersOutliers are not always errors
Human reviewJudgment and contextNeeds time and consistency

False Positives and Limitations

Automated flagging will be wrong sometimes. Treat the output as a prioritized queue, not a verdict.

  • Related steps in one task. "Drafted and finalized motion" or "Prepare for and attend mediation" may be a

single task, not two.

  • Missing context. The system may not know the matter's scope or a client's exceptions.
  • Short entries missed. A 0.5-hour block can slip through length-based checks.
  • Unknown true time. No tool can tell how long each task took unless the timekeeper recorded it.
  • Changing rules. Guideline updates can make configured checks stale.

A good tool shows why it flagged an entry, so the reviewer can disagree.

Why Human Review Is Still Necessary

Whether an entry is reasonable depends on the matter, the client's guidelines and the lawyer's work. That is

billing and legal judgment, which software supports but does not replace. Reviewers should also keep an

audit trail of what was flagged and what was decided. LuMay's article on AI agent audit trails covers what to

log, and its guide to AI tools for contract risk flagging shows the same flag-then-judge pattern in another legal

workflow.

How Timekeepers Can Correct Block-Billed Entries

Fix entries before they reach the invoice.

  • Record time per task as the work happens.
  • Split multi-task entries into separate lines with their own times.
  • Use specific verbs and objects, such as "Draft," "Review" or "Call."
  • Match each line to one task code and one activity code.
  • If a time must be estimated, follow your firm's policy and the client's guideline, and do not present a guess

as a record.

Block Billing Review Checklist

Before questioning or adjusting an entry, ask:

  • Does the entry describe one task or several?
  • Are the activities closely related or clearly different?
  • Can a reviewer tell roughly how long each task took?
  • Does the client's OCG prohibit block billing, and does it allow an exception?
  • Does the task coding match the narrative?
  • Could the flag be a false positive?
  • Has the reason for the final decision been recorded?

Where LuMay Legal Agent Fits

Block billing review is one part of a wider legal AI workflow that also includes intake, review and approvals.

LuMay Legal Agent is LuMay's set of agents for legal workflows.

Within it, BillingGuard checks rates, approvals, matter setup, billing requirements and supporting information

before invoices are submitted, and lists OCG rules among the rules it applies. Reviewers can approve, deny

or request information on flagged items, and the page says judgment stays with billing and finance teams.

LuMay also states SOC 2 Type II and ISO 27001 certification.

The BillingGuard page does not describe block billing detection. If narrative-level review matters to you, ask

what is supported today and test it on your own entries.

Your Next Step

Take 50 to 100 recent time entries and your top client OCG. Sort them into acceptable, problematic and

unclear, then use that set to test any tool. If you want to see how BillingGuard handles pre-submission

checks, you can book a LuMay demo.

This article is general information, not legal advice. Billing rules, ethics rules and fee-award standards vary by jurisdiction

and client, so verify what applies to you.

Tags:

#Legal Billing#Legal Technology#OCG Compliance

Frequently Asked Questions

Everything you need to know about Legal AI

1. What is block billing in simple terms?

Block billing records multiple tasks under one time entry with one total. The reader cannot tell how much

2. What is a simple example of block billing?

"Review documents, call client, update chronology: 4.0 hours." The same work is clearer as three entries,

3. Is block billing unethical?

Not automatically. Model Rule 1.5(a) prohibits unreasonable fees, and block billing can make

4. Do outside counsel guidelines ban block billing?

Many do, but not all, and the wording differs. Some allow a small exception for related tasks, such as the

5. How is block billing different from vague billing?

Block billing combines tasks in one entry. Vague billing gives too little detail about a single task. Both can

6. Are all multi-part narratives block billing?

No. A narrative can describe one task in detail, or closely related steps of one task, without being block

7. How do reviewers check an invoice for block billing?

They look at long entries, task lists in the narrative and mismatches with the task code. They then compare

About the Editorial Team

Sarath Babu

Sarath Babu

Content Writer and SEO Specialist at Lumay

Creates insightful content on SEO, AI-powered marketing, digital growth, and emerging technologies. He simplifies complex topics into practical, research-backed guidance.

Palanisamy

Palanisamy

CEO and Founder at LuMay

27+ years of experience leading enterprise-scale AI, data, and systems architecture initiatives, delivering mission-critical platforms with a strong emphasis on trust, governance, and reliability.

Make LuMay a Preferred Source

SHARE

Table of Contents

What Is Block Billing?Simple Block Billing ExamplesAcceptable vs. Problematic Time EntriesIs Block Billing Always a Problem?Why Block Billing Creates Review DifficultiesCommon Billing RisksOutside Counsel Guideline ConcernsHow Reviewers Traditionally Identify Block BillingHow AI Can Detect Potential Block BillingNLP Analysis of Time-Entry NarrativesDetection of Multiple Tasks in One EntryDuration and Narrative-Pattern AnalysisBilling-Rule EnginesAnomaly DetectionOutside Counsel Guideline ChecksHuman-in-the-Loop ValidationFalse Positives and LimitationsWhy Human Review Is Still NecessaryHow Timekeepers Can Correct Block-Billed EntriesBlock Billing Review ChecklistWhere LuMay Legal Agent FitsYour Next StepFrequently Asked Questions

Ready to Get Started?

Deploy enterprise agentic AI in under four weeks with LuMay.

Get Demo

8. Can AI detect block billing?

AI can flag entries that look block billed, such as those with several tasks in one narrative. It cannot confirm

9. Why does AI produce false positives?

Narratives that list related steps of one task can look like several tasks. A system also may not know the

10. How should a firm correct a block-billed entry?

Split it into separate lines with accurate times and specific descriptions. If times must be estimated, follow

11. What should I look for in legal billing software or AI bill review tools?

Ask which narrative checks it runs, how OCG rules are configured and how flags are explained. Also

12. Does LuMay Legal Agent detect block billing?

LuMay's BillingGuard page describes pre-submission checks on rates, approvals, matter setup and billing

Related Articles

7 Best Tools for Detecting Block Billing and Duplicate Time Entries in 2026

October 2026

7 Best Tools for Detecting Block Billing and Duplicate Time Entries in 2026

Compare seven legal billing tools for block billing detection, duplicate time entries, invoice auditing, OCG enforcement, and AI-assisted legal bill review.

7 AI Tools for Contract Risk Flagging in First-Pass Legal Review (2026)

October 2026

7 AI Tools for Contract Risk Flagging in First-Pass Legal Review (2026)

Compare seven AI contract risk flagging tools, including LegalOn, Spellbook, Luminance, Ironclad, Juro, Ivo, and Agiloft Screens, with playbooks, redlining, security, pricing, workflows, and FAQs.

How to Verify AI-Generated Legal Research Citations Before Using Them in a Brief

October 2026

How to Verify AI-Generated Legal Research Citations Before Using Them in a Brief

Verify every AI-generated citation by confirming the authority exists, reading the opinion, matching each quotation, testing support for the proposition, checking current validity…

Recent Posts

  • Multilingual AI Receptionists for Law Firms: 7 Questions to Ask Vendors
  • Legal CRM Integration Checklist for AI Voice Agents: Clio, MyCase & Lawmatics
  • AI Voice Agents for Law Firms: Call Recording, Consent & Confidentiality Checklist
  • 9 Access Controls for AI Agents That Read Data and Take Actions
  • 7 Intelligent Document Processing Platforms Compared for Enterprise AI Projects
  • AI Staff Augmentation vs Project Outsourcing: Which Fits Your AI Build?
  • AI Agent Audit Trails: What to Log and How to Review
  • When Should a Law Firm AI Receptionist Transfer a Call to a Human?
  • How to Test AI Voice Agents for Interruptions, Latency & Failed Handoffs
  • Self-Hosted vs Managed LLM Deployment: Which Fits Your Enterprise?