42 Missed Deadlines: What One Attorney-Discipline Case Teaches About Litigation Workflow
An isolated late task can happen in a busy practice. A filing is delayed, someone catches it, and the team corrects course. That is different from a pattern in which deadlines repeatedly become visible only after a court notice arrives. The distinction matters because the second problem is not just about an individual date. It is a workflow failure: the firm lacks a dependable way to see, assign, review, and confirm deadline work across its active matters.
The Iowa Supreme Court's 2025 attorney-discipline decision involving Karmen R. Anderson is a useful, sober example. It does not mean every late filing leads to discipline, and it does not supply a universal rule for every jurisdiction. It does show how repeated breakdowns can accumulate when the process for handling deadlines is not dependable.
What happened in the Anderson case
Over almost four years, Anderson missed 42 appellate deadlines in 24 matters. The clerk issued 24 default notices, and Anderson was removed from four cases. She paid $3,600 in default penalties. The court noted that none of the underlying appeals were dismissed because of her lack of diligence, but the missed work delayed or could have delayed their resolution.
On Supreme Court review, Anderson did not contest the rule violations; the parties disputed the appropriate sanction. The court reviewed sanctions case by case, weighing aggravating and mitigating circumstances instead of applying an automatic consequence. Anderson's prior discipline mattered to that analysis. Her 2019 public reprimand involved the same rule violations after default notices in eleven appeals. Because the earlier discipline concerned similar conduct, the court treated it as a significant aggravating factor.
The key mitigating factor was the lack of prejudice to Anderson's clients. None of the underlying appeals were dismissed due to her conduct, no client filed a complaint, and she paid the penalty assessments. The court also considered her service to underserved clients and corrective measures, including reducing her workload and implementing a new calendaring system. After balancing the record, the court imposed a second public reprimand rather than the suspension recommended by the grievance commission.
That result should not be read as a safe harbor. The court emphasized that the facts, history, harm, and corrective action matter. A different record could lead to a different outcome.
A default notice is not a deadline-management system
The opinion closes with a pointed warning drawn from prior Iowa discipline cases: using the appellate clerk's notices of default as a "private tickler system" is unacceptable. The phrase is not a critique of any particular calendar product, and it does not say that every notice reflects misconduct. It identifies the operational problem when a notice from the court becomes the mechanism that finally surfaces a deadline.
Court notices can be important inputs to a practice. They can identify a problem, confirm a status, or prompt a response. But they arrive after an external event. A workflow built only around catching those notices is reactive. The point is to have an internal process that puts the deadline, its owner, and the required review in view early enough to act.
The operational lesson is visibility and review
Deadline failures often begin with fragmentation. A date may sit in an email, a personal calendar, a spreadsheet, a case file, or one person's memory. Each location can be useful, but a team that cannot see the whole caseload cannot reliably identify what is becoming urgent.
A practical workflow gives each deadline a clear owner and a second point of verification. It makes the source and due date visible, records changes promptly, and gives someone a reason to review the list daily. Review should focus on what needs attention across the practice, not only within the matter currently open on screen. When a date is uncertain, changed, or approaching without progress, an escalation path creates a prompt to resolve it before the deadline is critical.
These are workflow controls, not legal prescriptions. Every lawyer remains responsible for determining which rules apply, calculating the relevant dates, and supervising work in the particular matter. The useful question is whether the firm's process makes that responsibility easier to carry out consistently.
Where Handled. fits, and where it does not
Handled. is organizational software for litigation practices. It keeps matters, deadlines, appearances, and next steps together, presents deadlines across the caseload ranked by urgency, and shows a countdown for each deadline. Those features can make it easier to conduct a daily review and to notice work that needs attention. For a closer look at the underlying approach, see the deadline-tracking workflow and the Handled. workflow overview.
Its role has limits. Handled. does not automatically calculate legal deadlines. It is organizational software, not legal advice. The responsibility for calculating, entering, monitoring, and verifying every deadline remains with the attorney and legal team. Handled. cannot guarantee that a deadline will never be missed. It is a tool within a reviewed process, not a substitute for professional judgment, supervision, or a firm's own procedures.
The practical takeaway
The Anderson decision is a reminder to examine the system before a late filing turns into a pattern. Pick one place to review active deadlines, assign clear ownership, verify new and changed dates, and escalate uncertainty early. A dependable routine is more valuable than relying on memory or waiting for a court notice to expose a problem.
Handled. is being built for that kind of visibility. If you want to follow its early development, you can join the early-access waitlist. The right workflow will still depend on your practice, your jurisdiction, and the people who carry it out.
Source
See the Iowa Supreme Court opinion, Iowa Supreme Court Attorney Disciplinary Board v. Anderson, No. 24-1894 (Iowa May 16, 2025).