Matter opening memo for the file
Turns intake notes into a one-page opening memo that anchors the matter file. Use it the day you open a new matter, while engagement details are fresh.
Libraries · attorney · practice-ops
Billing narratives, deadlines, and file management: the back office a solo carries alone.
Turns intake notes into a one-page opening memo that anchors the matter file. Use it the day you open a new matter, while engagement details are fresh.
Converts your scattered notes since the last file memo into a dated status memo for the matter file. Use it monthly or at any major development, so the file tells the story without your memory.
Drafts the final memo that closes a matter file: outcome, loose ends, retention, and post-closing obligations. Use it before you archive the file, so a reopened file or a bar inquiry answers itself.
Rewrites vague time entries ("attention to file," "review documents") into specific, defensible billing narratives without inflating the work. Use it on draft entries before they reach the pre-bill.
## Context
You are a billing editor for a solo law practice. The time entries below were written in a hurry. Vague narratives draw client pushback, e-billing rejections, and reductions in fee petitions. Your job is to make each narrative specific enough to justify the time — describing only work the original entry supports.
Matter type: [MATTER TYPE]
Client billing guidelines, if any: [BILLING GUIDELINES OR "NONE"]
Raw entries (date, hours, narrative): [RAW TIME ENTRIES]
## Task
Rewrite each narrative. Output a table: Date | Hours | Original | Revised | Attorney input needed.
## Standards
- Start each revised narrative with a past-tense action verb: drafted, reviewed, revised, conferred, analyzed, prepared.
- Name the document, issue, or party where the original supports it. Where it does not, insert a bracketed placeholder — [WHICH AGREEMENT?], [WHO ATTENDED?] — and repeat the placeholder in the Attorney input needed column.
- Never invent specifics. A narrative that claims work not performed is a fraudulent bill, not a clean one.
- Do not change any hours value. Do not merge or split entries.
- One entry, one description of the actual task. Cut filler verbs ("attend to," "work on," "handle").
- Keep narratives factual about the task, not strategy. Assume the client, an auditor, or a fee-petition judge will read every line.
- No abbreviations a client would not recognize.
If an original entry is so bare you cannot tell what the task was, do not guess — put the whole entry in the Attorney input needed column and move on. Sample output — AI-generated from sample inputs:
| Date | Hours | Original | Revised | Attorney input needed |
|---|---|---|---|---|
| 6/9 | 1.5 | review documents | Reviewed Calloway Freight's responses to first set of interrogatories and noted deficiencies in responses 4, 7, and 11 [CONFIRM: which responses were deficient?] | Confirm deficient response numbers |
| 6/9 | 0.3 | call w client | Conferred with client by telephone about [TOPIC?] | Topic of call |
| 6/10 | 2.1 | work on motion | Drafted motion to compel discovery responses, including statement of facts and good-faith conference certification | None, if this matches the work |
| 6/11 | 0.2 | attention to file | — | Entry too bare to rewrite. What was the task? |
Note: hours unchanged. Three entries need your input before billing. For insurance defense, add the carrier's task-code and staffing rules to [BILLING GUIDELINES] — the rewrite will then track UTBMS phrasing. Flat-fee practices can use this on internal time records to track matter profitability instead of invoicing. For fee-shifting cases, tighten the standard: narratives must survive a lodestar challenge, so resolve every placeholder against contemporaneous records.
Splits a block-billed time entry into discrete task entries that total the same hours. Use it when a client guideline, e-billing system, or fee petition requires task-level entries and you billed the day as one lump.
Checks draft time entries against a client's outside counsel guidelines and flags entries that will be rejected or cut. Use it before submitting bills to insurers and corporate clients with e-billing rules.
Reads a draft pre-bill the way a skeptical client would and flags entries likely to draw objections, with proposed fixes. Use it as the last pass before invoices go out.
Turns a raw unbilled-time report into a one-page memo: totals by matter, anomalies, and billing actions. Use it at month-end before you generate invoices, to catch leaks across the whole practice.
Converts your end-of-day scratch notes into formatted, billable time entries assigned to the right matters. Use it daily, before memory fades and tenths of hours evaporate.
Rebuilds draft time entries for days you never recorded, working from calendar, sent email, and document activity. Use it for the missed week — with every entry flagged as an estimate until you confirm it.
Summarizes proposed write-downs from a pre-bill review into a short decision memo: what gets cut, what it costs, and why. Use it when flagged entries pile up and you need to decide once, on paper, instead of agonizing line by line.
All 152 prompts in this library are free with a VetsLearn account: every prompt, every checklist, synced to your account.
Unlock free with an account →Turns raw CLE notes into a one-page memo for your knowledge file and staff. Run it within a day of the program, while you can still fill gaps from memory.
Turns a CLE summary into a checklist of edits to your templates, forms, and calendar rules. Use it when a program changes how you must practice, not only what you know.
Drafts a plain-language FAQ about a practice area for your website or new-client packet. Use it to answer the ten questions you repeat in every consult.
Writes a stage-by-stage "what to expect" handout for one matter type. Hand it to new clients at engagement to cut status-check calls.
Drafts a billing FAQ that matches your engagement letter. Use it to head off the fee conversations that sour client relationships.
Turns the intake process that lives in your head into a written procedure a new hire can follow. Reach for it before you hire, not after.
Writes a file-closing procedure covering final billing, client property, the disengagement letter, and retention. Files closed wrong become bar complaints; this makes the steps repeatable.
Converts a recorded walkthrough or interview of how a task gets done into a written SOP. Use it to capture procedures that live in one person's head.
Pulls every date, deadline, and undated obligation out of a scheduling order into a calendaring table. First pass only — every date gets verified against the order before it touches your calendar.
## Context
You are a litigation calendaring assistant for a solo attorney in [JURISDICTION]. Below is the text of a scheduling order in [CASE_NAME_OR_MATTER_ID]. Identifying details may be redacted.
Order text:
[SCHEDULING_ORDER_TEXT]
## Task
Extract every date and deadline into a table with these columns:
1. Date, exactly as stated in the order
2. Event or deadline
3. Exact quote from the order
4. Type — fixed date, or relative ("30 days before trial")
5. Suggested reminder dates at [REMINDER_LEAD_TIMES]
After the table, list separately:
- Relative deadlines the order defines but does not date. Do not compute these dates. State the formula and the trigger event.
- Obligations without dates: meet-and-confer duties, page limits, pretrial filing requirements, incorporated standing orders.
## Standards
- Extraction only. Never calculate a date the order does not state. Date arithmetic depends on counting rules, weekends, and court holidays you cannot verify.
- Quote the order exactly in column 3. No paraphrase.
- If two provisions conflict, flag both. Do not pick one.
- Flag any deadline that local rules commonly modify, with a note to check local rules and the judge's standing order.
- If the order text is cut off or a date is unreadable, ask. Do not fill gaps. Sample output — AI-generated from sample inputs:
Meridian Supply Co. v. Calloway Freight, LLC — extraction from scheduling order dated May 12, 2026.
| Date | Event | Order language | Type |
|---|---|---|---|
| Aug 14, 2026 | Amend pleadings / add parties | "Motions to amend the pleadings or add parties shall be filed by August 14, 2026." | Fixed |
| Oct 15, 2026 | Fact discovery closes | "All fact discovery shall be completed by October 15, 2026." | Fixed |
| Nov 6, 2026 | Plaintiff expert disclosures | "Plaintiff shall serve expert disclosures by November 6, 2026." | Fixed |
Relative deadlines — NOT computed; verify under the applicable counting rules:
- Dispositive motions: "no later than 45 days after the close of fact discovery." Trigger: Oct 15, 2026 fact discovery close.
- Daubert motions: "filed with dispositive motions." Trigger: dispositive motion deadline.
Obligations without dates:
- "Counsel shall meet and confer before filing any discovery motion." No date — calendar a standing reminder.
- Pretrial submissions governed by the court's standing order, incorporated by reference. Obtain and review the standing order; it is not in this text. Works the same for state court case management orders and arbitration scheduling orders — adjust [JURISDICTION] and have the right counting rule at hand. Add a column mapped to your calendaring software's import fields if you bulk-enter dates. When the court amends the order, rerun the extraction on the amended text and compare it against your existing calendar line by line; amended orders are where deadlines get dropped.
Turns a raw deadline export from your practice management system into a Monday-morning digest with prep-start dates and conflict flags.
All 152 prompts in this library are free with a VetsLearn account: every prompt, every checklist, synced to your account.
Unlock free with an account →No prompts match your search. Try a different word.