Capability template for operations and process improvement
Court-order deadline notice preparation
When a court order arrives, the legal assistant has a draft notice ready for the attorney: every directive in the court’s own words, every date copied from the order or proposed under the firm’s own written rule file, and a list for the attorney to confirm. Nothing is calendared or sent until the attorney confirms.
The outcome
The attorney opens one page and sees everything the order asks of anyone: each directive quoted with its page, each date, each hearing set or vacated, each amount. The careful first reading arrives prepared, footnotes included, and the attorney’s time goes to the judgment only an attorney can make.
This is preparation, and it stays preparation. It does not give legal advice and it does not decide when anything is due. A date the order states is copied. A date that has to be counted is a proposed date, counted only by the firm’s own written rule file, with the working shown, on a list the attorney answers line by line. Where the rule file does not cover a count, the capability stops on that line and says so. No date is final until the attorney confirms it.
Who starts the work, and when
A legal assistant or docketing clerk starts it when a signed, entered order arrives on a matter and has been saved to the matter file. The handling attorney confirms. It is not for a proposed order, a letter from the other side, a clerk’s notice with no order in it, or explaining an order to a client.
What they supply
- The order, as text or a PDF with readable text, every page.
- The matter name and case number they expect, and the people on the matter: handling attorney, supervising attorney, paralegal, docketing.
- The firm’s own written deadline rule file, dated and approved by an attorney: which kinds of count the firm lets staff propose, and exactly how each is counted.
- The court-closure list the firm’s docketing keeps for that court, with the period it covers.
The capability template ships no court rules and uses none from memory. A firm without a rule file still gets the directives, the copied dates, the hearings and the amounts; every counted date goes to the attorney.
What comes out
One draft notice, marked as a draft, for the matter team:
- What the court ordered: each directive in the court’s sentence, with page and paragraph, from the discussion and footnotes as well as the numbered list.
- Dates: copied from the order, or proposed under a named rule with the count shown, or marked “Not computed” with the reason.
- Hearings: set, moved and vacated, so docketing can see what must come off the calendar.
- Amounts: the exact figure, who pays, who is paid.
- Attorney to confirm: a line to answer for every proposed date, every copied deadline and every date left for the attorney, then the hearings and whether every directive is listed.
- Check: pages read against the order’s own footer, the rule file and closure list used with their dates, and how the counting was done.
The legal assistant reads the draft against the order and gives it to the handling attorney. The attorney confirms each line or corrects it. Only then does the notice go to the matter team and docketing put dates on the calendar. The notice never goes to the client.
An invented example
Illustrative example with invented data. Tallis Marrow LLP, its people, its client, the Superior Court of Eastmere, the order, the rule file and the court-closure list below are all invented. The rule file is one invented firm’s way of counting for an invented court. It is not any real court’s rule and must not be used for a real deadline.
The legal assistant’s four inputs come first, in full, then what the capability prepares. The request carries the matter name and case number, the people on the matter and, as the day it was sent, today’s date.
Input 1: the request
Sent by Dalia Renner, legal assistant, on Monday 9 November 2026.
Copperline: the order on the discovery dispute came in Friday. It is saved to
the matter file. Please prepare the order notice.
Matter: Copperline Bakery Supply Co. v. Ostrander Freight, Inc.,
case no. LC-CV-26-01873. We act for the plaintiff.
On the matter: Marcus Thibault, handling attorney; Helen Voss, supervising
partner; Joan Abara, paralegal; Petra Lindahl, docketing.
Attached: the order (3 pages), our order deadline rule file, the court-closure
list.
Input 2: the order
ENTERED
November 6, 2026
Clerk of the Superior Court
Linden County
SUPERIOR COURT OF EASTMERE
COUNTY OF LINDEN
COPPERLINE BAKERY SUPPLY CO.,
Plaintiff,
v. Case No. LC-CV-26-01873
OSTRANDER FREIGHT, INC.,
Defendant.
ORDER ON DISCOVERY DISPUTE AND RESETTING CASE MANAGEMENT CONFERENCE
The court heard the parties' discovery dispute on November 3, 2026. Having
read the papers and heard counsel, the court rules as follows.
Plaintiff seeks delivery records responsive to Requests for Production Nos. 7
through 15. Defendant objects that the requests are burdensome. The objection
is overruled. The records are kept in the ordinary course of business, and
defendant has not shown that gathering them would be unduly costly.[1]
[1] Any party seeking a protective order covering the route data shall file
its request within 10 days of entry of this order.
Page 1 of 3
The parties also dispute which employees' delivery logs must be searched. The
record is not developed enough to decide that question today. Counsel shall
meet and confer regarding the delivery-log custodians within 14 days of this
order, and shall file a joint statement of any remaining dispute no later than
5 court days before the conference set below.
Defendant's position on Requests 7 through 15 was not substantially justified,
and an award of expenses is appropriate.
IT IS ORDERED:
1. Defendant shall produce all documents responsive to Requests for Production
Nos. 7 through 15 within 20 days of entry of this order.
2. Defendant shall serve a privilege log no later than December 4, 2026.
3. Defendant shall pay $3,180.00 to plaintiff's counsel within 30 days of
service of this order.
Page 2 of 3
4. The case management conference set for December 10, 2026 is vacated. A
further case management conference is set for January 14, 2027 at 9:00 a.m. in
Department 4.
Dated: November 5, 2026
[signed]
Hon. Mireille Asante
Judge of the Superior Court
Page 3 of 3
Input 3: the firm’s order deadline rule file
Tallis Marrow LLP · Order deadline rule file
Dated: 1 October 2026 Review by: 31 March 2027
Approved by: Helen Voss, partner. Changes go through her.
Covers: civil orders of the Superior Court of Eastmere. No other court.
R-0. A date the order states ("no later than", "on or before", "by", a hearing
date). Copy it. Never recount it.
R-1. A count of calendar days from entry of the order.
Phrases: "within N days of entry of this order", "within N days of entry",
"within N days of this order", "N days after entry".
Start: the date on the court's ENTERED stamp on page 1. Never the date the
judge signed.
Count calendar days. The day of entry is not counted.
If the last day is a Saturday, a Sunday or a day on the court-closure
list, move forward to the next day that is none of these.
Not covered. Staff propose no date for any of these; they go to the handling
attorney:
- a count from service of the order;
- a count backwards from a hearing, a conference or trial;
- a count in court days or business days;
- a count from the date the order was signed;
- a count from an event the order does not date;
- a sentence that holds two kinds of count, even for two different tasks:
neither count gets a proposed date;
- anything this file does not list.
Every proposed date is confirmed by the handling attorney before docketing
calendars it. If the handling attorney is away, the supervising partner
confirms.
Input 4: the court-closure list
Superior Court of Eastmere · days the court is closed
Dated: 1 October 2026. Kept by Petra Lindahl, docketing.
Covers: 1 October 2026 to 31 December 2027. For any later date, ask docketing.
These are the court's closures, not the firm's office holidays.
2026-11-11 Wednesday Veterans Day
2026-11-26 Thursday Thanksgiving Day
2026-11-27 Friday Day after Thanksgiving
2026-12-25 Friday Christmas Day
2027-01-01 Friday New Year's Day
2027-01-18 Monday Eastmere Founders' Day
2027-02-15 Monday Presidents' Day
2027-05-31 Monday Memorial Day
2027-07-05 Monday Independence Day (observed)
2027-09-06 Monday Labor Day
2027-11-11 Thursday Veterans Day
2027-11-25 Thursday Thanksgiving Day
2027-11-26 Friday Day after Thanksgiving
2027-12-24 Friday Christmas Day (observed)
What the capability prepares
A short note to the legal assistant, then the draft.
Dalia, the draft notice for Copperline is below. I read 3 of 3 pages. No stop applied to the whole order. Two dates are proposed under your rule R-1. Three counts are not computed. Your rule file does not cover a count from service (the payment). It does not cover a count in court days or a count backwards from a conference (the joint statement). And the 14 days for the meet and confer sit in the same sentence as that court-day count: your rule file sends a sentence that holds two kinds of count to the attorney, so I have proposed no date for the meet and confer either. Two directives are outside the numbered list: one in footnote 1 on page 1 and one in the discussion on page 2.
Still to do, by people: read the draft against the order, recount the two proposed dates on a calendar, and give the draft to Marcus Thibault to confirm. I have sent nothing and calendared nothing. The notice does not go to the matter team, and docketing calendars nothing, until he confirms.
DRAFT ORDER NOTICE · FOR THE ATTORNEY TO CONFIRM
Proposed dates only. Not legal advice. Nothing has been calendared or sent.
Matter: Copperline Bakery Supply Co. v. Ostrander Freight, Inc.
Case no.: LC-CV-26-01873
Prepared for: Marcus Thibault, handling attorney, to confirm
After confirmation, to: Helen Voss, supervising partner; Joan Abara,
paralegal; Petra Lindahl, docketing. Not to the client.
ORDER
- Court: Superior Court of Eastmere, County of Linden (p. 1)
- Title: Order on Discovery Dispute and Resetting Case Management
Conference (p. 1)
- Signed: November 5, 2026 (p. 3)
- Entered: November 6, 2026 (ENTERED stamp, p. 1)
WHAT THE COURT ORDERED
1. "Any party seeking a protective order covering the route data shall file
its request within 10 days of entry of this order." (p. 1, fn. 1)
2. "Counsel shall meet and confer regarding the delivery-log custodians within
14 days of this order, and shall file a joint statement of any remaining
dispute no later than 5 court days before the conference set below."
(p. 2, para. 1)
3. "Defendant shall produce all documents responsive to Requests for
Production Nos. 7 through 15 within 20 days of entry of this order."
(p. 2, ¶ 1)
4. "Defendant shall serve a privilege log no later than December 4, 2026."
(p. 2, ¶ 2)
5. "Defendant shall pay $3,180.00 to plaintiff's counsel within 30 days of
service of this order." (p. 2, ¶ 3)
6. "The case management conference set for December 10, 2026 is vacated."
(p. 3, ¶ 4)
7. "A further case management conference is set for January 14, 2027 at 9:00
a.m. in Department 4." (p. 3, ¶ 4)
DATES
A. PROPOSED: Monday 16 November 2026. Any party's request for a protective
order covering the route data.
"within 10 days of entry of this order" (p. 1, fn. 1).
Working: entered Friday 6 November 2026 (ENTERED stamp, p. 1); entry day
not counted; calendar days, so Wednesday 11 November (on the closure
list) is counted like any other day; day 10 is Monday 16 November 2026;
not a Saturday or Sunday; not on the closure list; no closed day moved
the last day. Rule R-1.
B. NOT COMPUTED: counsel to meet and confer on the delivery-log custodians.
"within 14 days of this order" (p. 2, para. 1). The rule file does not
cover a sentence that holds two kinds of count: this sentence holds a
count of days from the order and a count in court days backwards from a
conference. Attorney to supply the date.
C. NOT COMPUTED: joint statement of any remaining dispute. "no later than 5
court days before the conference set below" (p. 2, para. 1). The rule file
does not cover a count in court days or a count backwards from a
conference. Attorney to supply the date.
D. PROPOSED: Monday 30 November 2026. Defendant to produce documents
responsive to Requests 7 through 15.
"within 20 days of entry of this order" (p. 2, ¶ 1).
Working: entered Friday 6 November 2026 (ENTERED stamp, p. 1); entry day
not counted; calendar days, so Wednesday 11 November is counted; day 20
is Thursday 26 November 2026, on the closure list (Thanksgiving Day);
Friday 27 November is on the closure list (Day after Thanksgiving); 28
and 29 November are a Saturday and a Sunday; the next day that is none
of these is Monday 30 November 2026. Rule R-1.
E. COPIED: December 4, 2026. Defendant to serve a privilege log. Stated in
the order (p. 2, ¶ 2). Not recounted.
F. NOT COMPUTED: payment of $3,180.00. "within 30 days of service of this
order" (p. 2, ¶ 3). The rule file does not cover a count from service, and
the order does not say when or how it was served. Attorney to supply the
date.
HEARINGS
- VACATED: December 10, 2026, case management conference (p. 3, ¶ 4)
- SET: January 14, 2027, 9:00 a.m., Department 4, further case management
conference (p. 3, ¶ 4)
AMOUNTS
- $3,180.00, paid by defendant to plaintiff's counsel, "within 30 days of
service of this order" (p. 2, ¶ 3)
ATTORNEY TO CONFIRM
[ ] A. Proposed Monday 16 November 2026 (rule R-1). Confirm or correct: ____
[ ] B. Not computed: meet and confer. Your date: ____
[ ] C. Not computed: joint statement. Your date: ____
[ ] D. Proposed Monday 30 November 2026 (rule R-1). Confirm or correct: ____
[ ] E. Copied December 4, 2026 (p. 2). Confirm: ____
[ ] F. Not computed: payment of $3,180.00. Your date: ____
[ ] Hearings: December 10, 2026 VACATED; January 14, 2027 SET. Confirm: ____
[ ] Every directive in the order is listed above. Confirm: ____
CHECK
- Pages: read 3 of 3 (footer: "of 3").
- Directives listed: 7. Dates: 1 copied, 2 proposed, 3 not computed.
Hearings: 2.
- Rule file: Tallis Marrow LLP order deadline rule file, dated 1 October
2026, review by 31 March 2027, covers this court. In date on 9 November 2026.
- Closure list: dated 1 October 2026, covers 1 October 2026 to 31 December
2027. Every proposed date falls inside it.
- Counting: day by day, shown above. Recount on a calendar before the
attorney confirms.
- Every date above appears in the order on the page cited or is a proposed
date with its working. No other date appears.
Confirmed by: ____________ Date: ________
Until this line is signed, this is a draft and no date in it is final.
The meet and confer is the line to notice. Taken alone, "within 14 days of this order" is wording rule R-1 lists. It gets no proposed date because the court put it in one sentence with a count in court days before a conference, and the firm's rule file sends such a sentence to the attorney whole. The capability stops there and says why.
Marcus Thibault confirms or corrects each line and supplies the dates for B, C and F. Only then does Dalia Renner circulate the notice, and only then does Petra Lindahl take the 10 December conference off the calendar and add the confirmed dates.
Where it fits
- Operations and process improvement: the notice is a procedure with an owner, a rule file and a confirmation step, run the same way on every order.
- Law firms, in litigation groups where orders arrive daily and a missed line in a footnote is expensive.
- Established businesses, where one long-serving assistant knows how the firm counts and nobody has written it down.
It follows matter-opening checklist preparation, which records who is on the matter. If the firm’s way of counting lives in one person’s head, SOP exception capture is how to get it written before this capability relies on it.
What has to change for your company
The rule file is yours, and it is the heart of this. A supervising attorney decides which kinds of count staff may propose, which date the firm counts from, what happens when a last day falls on a day the court is closed, and when the file is reviewed. Everything the file leaves out goes to the attorney. Docketing supplies the closure list for each court. You name who confirms when the handling attorney is away, where the confirmation is recorded, and who may circulate the notice afterwards.
We sit with the assistant who writes the notices and the attorney who owns the procedure, write down what is really done, and set it up in the AI product the firm has approved: ChatGPT, Claude, Copilot or Gemini. Your firm keeps control of how the work gets done.
What has been checked
Fully Powered AI wrote this capability template from its own built example for an invented firm. It was editorially reviewed on 9 November 2026. It was tried on its invented example in Claude on 9 November 2026, and the record of that run, which replaced an earlier one from the same day, is published with the template. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your firm means running it on past orders whose dates your attorneys already settled, and comparing: every directive found, every proposed date equal to the attorney’s, every uncovered count left alone, nothing sent. Include an order with a directive in a footnote, one counted from service and one with a page missing. Pilot acceptance-test preparation builds that set, and what we test before we call an AI workflow ready describes the record we keep.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Bring a real piece of this work to a call. We’ll walk through what it takes to fit this capability to your rules, prove it on your work and put it in the hands of the roles that own it.