How to run your practice on CaseOps.

CaseOps is a workspace for running a legal practice end to end — matters, documents, notices, drafting, hearings, contracts, outside counsel, billing, and the audit trail that ties them together. After sign in, use the left navigation to open the Home dashboard, Today queue, matters, import activity, research, or the workspace administration surfaces your role permits.

1. 1
   Create a workspace. Visit /sign-in, pick New workspace, and enter your firm or company name. You become the workspace Owner.
2. 2
   Recover access. Use /account/forgot-password from the sign-in page to request a single-use reset link. The request message is intentionally generic so it never confirms whether a workspace or email exists.
3. 3
   Add colleagues. Open Admin → Employees and assign an Owner-managed built-in or custom role. The available actions remain capability-gated by the API.
4. 4
   Verify the brand. Add your firm logo and a default contact email so draft dispatches and invoices carry them.
5. 5
   Secure your account. Open Account security to enrol MFA, save recovery codes, and complete recent MFA step-up before protected actions when policy requires it.
6. 6
   Open your first matter. Continue through daily operations, roles, and optional conflict review before opening or working an active file.

Public CaseOps claims use six labels. Live means the capability is available in the product. Review-first means the system proposes or drafts, but a human must approve the substantive result. Provider-gated means CaseOps has internal readiness but needs external provider credentials, consent, or UAT evidence. Founder-only means the surface is restricted to the platform super-admin. Disabled until UAT means code and evidence scaffolding exist but production activation is intentionally blocked. Planned means the public claim is roadmap/readiness only.

Start routine work at Today. It brings together hearings and deadlines in the next seven days, overdue or due-soon tasks, drafts pending review, and overdue invoices across the matters you can see.

• Act from the source. Each Today item links back to its matter, hearing, draft, or billing surface. Today is a prioritised feed; the underlying list remains the source of truth.
• Know when a stream is capped. A note appears when a stream reaches its server-side limit. Open the relevant list view to see the complete set.
• Use Calendar for date work. Calendar combines visible legal filing deadlines, internal targets, hearings/listings, renewals, and task dates with distinct labels. IP legal dates link back to their docket. Provider sync conflicts stay reviewable rather than overwriting manually protected dates.
• Inspect an IP deadline before relying on it. In the IP workspace, open calculation provenance to see the stored trigger, rule, working calendar, approved extension input, override, and predecessor chain. An extension application alone does not move the legal date.
• Use Portfolio for the roll-up. Portfolio groups matters by lifecycle status, forum, and practice area and calls out work that needs attention.

Every workspace is an isolated tenant. Data never crosses tenant boundaries — the query layer, storage layer and audit trail all filter by tenant id. Users inside a workspace see what their role permits, and matter-level access restrictions can further narrow visibility.

Roles at a glance

• Owner. Workspace owner with the broadest built-in access, including ownership-sensitive employee administration.
• Admin. Manages employees, roles, teams, workspace settings, provider operations, billing configuration, and audit tools according to assigned capabilities.
• Partner. Runs matters and can receive approval and conflict-resolution capabilities without becoming a workspace owner.
• Member. The standard fee-earner or legal-team role for day-to-day matter work.
• Paralegal. A narrower operational role for permitted matter, document, task, and hearing work.
• Viewer. Read-oriented access where the capability grid permits it. Custom roles can be configured from Admin → Roles.

Use Intake for inbound business requests before they become matters. Users with the relevant capabilities can submit, triage, assign, update, reject, complete, or promote a request once its scope is clear.

1. 1
   Capture the request, requester, business context, priority, target date, and proposed matter code where known.
2. 2
   Triage through New, Triaging, and In progress; reject or complete requests with a recorded reason when appropriate.
3. 3
   Promote an approved request to a matter. Client records live in Clients for users with client capabilities.
4. 4
   On the matter Overview, run Conflict check against workspace clients and matters, including the opposing and related parties entered for the scan.
5. 5
   A partner or admin reviews candidate overlaps and records Cleared, Conflicted, or an explicit Waiver with a note. The result is auditable review evidence, not a precondition for creating or activating the matter.

A new matter takes about a minute to open and is the anchor for every other workflow. Create the shell with enough identifying detail to support conflict review, then add parties, documents, dates, and work from the cockpit.

1. 1
   Go to Matters → New matter. Give it a clear plain-English title (e.g. Arbitral award challenge — Acme v. Kappa).
2. 2
   Enter a unique matter code, practice area, client, and opposing party. These fields make lists and conflict review more useful.
3. 3
   Add the case number or CNR when available and select the structured court/forum. If the catalog is unavailable, use the explicit uncatalogued fallback instead of saving stale forum metadata.
4. 4
   New Matter starts Active by default. If your team chooses to keep a pre-engagement file in Intake while its conflict check is pending, it can still move to Active. Conflict review remains optional and available before or after that change.
5. 5
   Add a concise description, create the matter, then attach the first batch of documents. See section 7 for indexing and OCR.

Bulk upload matters

Owners, Admins, and users with a delegated Matter Manager capability can select Bulk upload matters from the Matter portfolio. Download the canonical 21-column XLSX template for status, forum, date, people, and team guidance; CSV is also available for migration tooling. Court stores the name, while Court Forum Number separately stores an optional court, bench, room, or forum reference.

1. Enter one matter per row. Matter Title, Matter Code, Practice Area, and Forum are required. Client Name is optional. Leave Matter Status blank to create the matter as Active.
2. Upload a CSV/XLSX file of at most 500 non-empty rows and 2 MB, then select Validate data before import. Validation does not create matters. CSV accepts UTF-8, BOM-marked UTF-16, or Windows-1252 with comma, semicolon, tab, or pipe separators. Quote any field that contains the selected separator.
3. CaseOps accepts the documented client-register heading aliases and can find a header below report-title rows or an import table on a later XLSX worksheet. Status and Forum ignore case and presentation separators: for example, On Hold and on_hold match.
4. A valid non-catalog Practice Area is preserved. Normal business punctuation is supported in applicable text and reference fields. Client Email is limited to a valid 254-character address. Common ISO, Indian day-first, month-name, and fractional Excel dates are accepted; an XLSX workbook's 1900/1904 date system is honored and its time-of-day fraction is discarded.
5. Review every row error. CaseOps checks required/type rules, duplicates, dates, email and phone formats, status/forum values, active users and teams, tenant boundaries, team scoping, and unsafe formulas.
6. Confirm the job to create every row that remains valid. Invalid rows are retained for correction, so a mixed file may complete with both successful and failed counts.
7. Download the error CSV and use Import History to search by file or uploader and review upload date, status, totals, imported, and failed counts.

Import activity across the workspace

Open Import activity to review accessible trademark, matter, and employee import jobs in one status view. Filter by workflow, inspect the input manifest, download a normalized row-error report, or follow the row action back to the canonical import screen. The activity view is read-only: matter and employee history stays in its existing owner and is never copied or rewritten. Older employee jobs may show checksum not recorded because that legacy workflow did not persist one.

Trademark files continue through Trademark portfolio import, matter files through Bulk upload matters, and employee files through Admin → Employees. Access to each history and its manifest/error report follows the same capability and tenant boundary as its canonical workflow.

The matter cockpit

Opening any matter puts you in the cockpit. The top bar shows parties, forum and next hearing. The live tabs are Overview, Timeline, Tasks & Deadlines, Documents, Notices, Drafts, Hearings, AI Recommendations, Strategy Plan, Predictive Intelligence, Intelligence Review, Knowledge Graph, Statutes, Communications, Billing, and Matter Audit.

• Timeline. Review hearings, orders, documents, deadlines, tasks, and material activity together; filter by event type and sort oldest- or newest-first.
• Tasks & Deadlines. Keep operational work and legal dates on the matter. Source-backed compliance and notice workflows may create linked deadlines; review their source before changing status.
• Status. Active matters use the normal lifecycle states. A completed matter is marked Dispose in the UI and is stored by the API as disposed. Older integrations that still submit closed are normalized todisposed during the compatibility window.
• Next hearing. The header shows the date plus its source: manual, case tracking, court sync, proceeding intelligence, cause list, or unknown. A manually locked date is never overwritten. An exact, verified provider match updates an unlocked date directly; ambiguous or mismatched provider results are rejected.
• History. Every next-hearing change records old date, new date, actor or system source, reason, source reference, timestamp, and whether the manual lock was active.

Every document uploaded to a matter is queued for extraction and embedding so you can search it semantically alongside the CaseOps public corpus. Expect PDFs, DOCX, emails (EML) and scanned pages. Scanned pages run through OCR before indexing.

• Upload. Drag and drop onto the Documents tab, or paste a file list. Files above 50 MB are rejected at the edge.
• Status pills. Queued → Indexed. OCR pending appears on scans and typically clears in a few minutes.
• Retry. A failed extraction shows a Retry button. Re-indexing a document does not duplicate chunks.
• Private by matter. Documents inherit the matter's server-side access restrictions. They are never pooled across tenants or used for cross-tenant training.

Court-order uploads

Manual court orders can be uploaded from the matter or hearings view as PDF, DOC, DOCX, or image files within the configured file-size limit. Extraction starts only after the file-safety gate passes. If text is not available immediately, the order shows OCR pending; failed OCR or extraction shows a redacted error and a Retry action.

Manual trademark applications

In IP docket, select New trademark to create the docket, trademark asset, application, class scope, representation, parties, and any application number as one controlled operation. A draft or pre-filing record does not require an application number. A filed record requires either a confirmed application number or an explicit registry-source statement that allocation is pending.

• Application, registration, opposition, rectification, cancellation, non-use removal, appeal, and court identifiers retain separate labels and legal owners. An opposition or post-registration proceeding number is never displayed or stored as the trademark application number.
• Punctuation and spacing variants are normalized for matching while the source form remains visible. A possible duplicate is saved for review and cannot silently merge records or enter filed phase.
• Duplicate review shows the accessible candidates and blocking reasons before a decision. Confirming a separate filing or superseding a number requires a current preview and a written reason; supersession does not delete or merge either docket.
• Correcting a number creates a new identifier version. The prior source value, effective range, correction reason, and audit evidence remain in history.

Registry reconciliation

Open Registry reconciliation to connect an application or proceeding to one IP-office identifier. Record the office, jurisdiction, identifier type, source URL, and match evidence, then confirm or reject the match with a written reason before adding source snapshots.

• Manual intake stores both the source JSON and normalized register JSON with retrieval time, parser version, attribution, and SHA-256 hashes. A correction supersedes its predecessor with a reason; source snapshots cannot be edited or deleted.
• Every changed field remains a candidate until it is accepted, rejected, mapped, or deferred. Proprietor, status, deadline, refusal, opposition, cancellation, registration, and renewal fields are high risk and require IP approval. Mapping a provider field to one of those canonical paths applies the same approval rule.
• Accepting a change records candidate and reconciled IP docket events. A deadline field also queues a durable calculation proposal; CaseOps does not invent or confirm a legal deadline without an approved rule and calendar version.
• The unresolved queue is paginated independently from bounded evidence history, so an older pending review remains reachable. If accepted state changed after a diff was created, CaseOps rejects the stale decision and requires a fresh snapshot.
• A no-change check still updates freshness and attempt history. Authentication, rate-limit, parsing, outage, configuration, or policy failures preserve the last successful snapshot and accepted legal state.
• Court or CNR proceedings reference the existing Matter bookmark and TrackedCase. Court status, provider snapshots, and updates stay with case tracking and are never copied into the IP registry record.
• IP India live automation remains disabled until an approved provider contract, licensing basis, credentials, and verified legal coverage exist. The current workspace supports sourced manual evidence without claiming a provider call.

Madrid international registrations

Open Madrid portfolio to docket an outbound Indian basic-mark filing, an international registration, or each designated member as a separate controlled record. The international registration retains WIPO status; every designation retains its own national status, local agent, deadlines, documents, fees, and source history.

• Outbound intake requires an eligible Indian trademark application, office of origin, MM2 or applicable form, classes and goods/services. Original and subsequent designations remain distinguishable and link to the same parent registration without sharing legal status.
• Record forms, fees, certification, irregularities, WIPO notification, national examination, provisional refusal, response, publication, opposition, grant or refusal statements, changes, renewals, and local-agent instructions as versioned transactions. Link the canonical deadline, document, or cost evidence used for the transaction.
• A WIPO or national-office snapshot is always a source candidate. Counsel opens the linked source and explicitly accepts, keeps separate, or rejects it before CaseOps changes the authority-owned status. A stale version is rejected and must be reviewed again.
• Basic-mark dependency and central-attack reviews record affected registrations, designations, deadlines, documents, and recommended work. They do not automatically cancel, narrow, or otherwise change legal status.
• WIPO live search, document retrieval, and polling remain disabled until an approved provider contract, licensing basis, credentials, verified legal coverage, and activation decision exist. The current workspace is manual, source-linked docketing and makes no provider call.

Post-registration recordals and title

Open Post-registration for assignment, transmission, registered-user, licence, name/address, association, division, limitation, disclaimer, certified-copy and well-known-mark work. Renewal and restoration remain in Trademark renewals; cancellation, rectification and non-use remain separate proceedings.

• Select the affected application or registration, whole-right or partial-class scope, parties, execution/effective dates, legal basis, form, docket-linked instruments and cost items. Every party cites a selected canonical instrument.
• An authorized reviewer approves the package before filing. Record the acknowledgement, defect, corrected instrument, rejection, withdrawal or Registry acceptance as a separate transaction; prior attempts remain in history.
• Registry acceptance requires a confirmed affected application or registration link, immutable snapshot, exact source, acceptance evidence, Registry-recorded date and IP approval. Source links open from evidence and history.
• The dated title view separates Registry-recorded ownership from effective, pending and beneficial interests. It surfaces overlapping title, partial scope, unavailable or restricted source documents, effective-but-unrecorded interests, title gaps and related-right cycles without changing another family member.
• Download the date-specific title report for the supported chain and its unresolved issues. The report is based only on records and sources visible to the signed-in user and remains subject to lawyer review.

Foreign-associate filings

Open Foreign associates for application- or search-led instructions to approved local counsel.

• Select the target jurisdiction, approved Matter assignment, client authority, scoped docket data, docket-linked documents, estimate, currency, tax evidence, budget policy, responsible lawyer and response deadline.
• Privileged or internal documents remain excluded unless selected explicitly by an IP approver. The selected source version opens from the instruction workspace.
• Record connector-backed or external dispatch separately from delivery and independent associate acknowledgement. Schedule idempotent in-app or email acknowledgement reminders with a named escalation owner.
• Preserve associate queries and lawyer-approved responses, approve later fee, tax or exchange-rate estimates, and reassign a refused instruction without deleting its correspondence or version history.
• A filing report remains unverified until independent evidence is recorded. Completion also requires the paid associate invoice, actual docket cost and matched client-billing reconciliation.

Trademark journal watch

Open Journal watch to define docket-specific word, phonetic, device, class, proprietor, and jurisdiction criteria. Every profile records its check frequency, notification recipients, provider, and cost ceiling. A cost ceiling or unavailable provider visibly pauses the profile instead of silently skipping a check.

• Manual journal intake records the journal and application numbers, published mark, classes and goods, proprietor, publication scope, source URL and page, retrieval time, attribution, and parser version. The source record is append-only and an idempotency key can replay only its original payload and exact results.
• Each hit shows the compared profile, candidate mark, class and goods overlap, similarity-method evidence, publication date, and official source link. AI and device-similarity signals are advisory; an attorney must independently verify the source and record a reasoned disposition.
• Final source-dependent decisions and action handoffs are blocked while the source is unavailable or unconfirmed. Authorized recipients receive a durable in-app notification when a new accessible hit is recorded.
• A confirmed relevant hit can create an opposition proceeding, enforcement Matter, task, operational deadline, or client-report evidence item without re-entering the source and reviewer decision. The receiving Matter or IP owner remains canonical.
• Corrections and re-advertisements link to the prior publication and hit. Prior evidence remains unchanged, partial published scope remains visible, delayed intake raises a stale alert, and an earlier deadline state is superseded only after the successor source is reviewed and confirmed.
• Live journal-provider polling remains paused until the provider contract, source licence, credentials, cost policy, and legal coverage are approved. The current workflow supports sourced manual evidence and makes no external call when those controls are absent.

Rectification, cancellation, and non-use proceedings

Open the post-registration workspace in the IP docket to create a claimant- or respondent-side proceeding against the exact application. Keep its proceeding number, profile, challenged classes, grounds, forum, form, fee, service, rule map, and source records distinct from opposition.

• A rule applied mutatis mutandis requires counsel to record the source rule, mapped provisions, excluded provisions, and confirmation. An opposition template cannot be silently reused.
• Link a parallel court or Registry proceeding without merging either record. Record sourced stays and lift orders before proposing a legal disposition.
• Settlement, withdrawal, and closure require the legal effect, effective date, evidence, and authorized confirmation. Candidate outcomes are limited to the proceeding type and require a separate review.
• Approval records the reviewed candidate but never changes the trademark registration automatically. Any authoritative register update remains a separate sourced, authorized action.

IP and Matter relationships

An IP docket can reference more than one accessible Matter. Open the docket's Matter relationships panel to add an operational, litigation, advisory, appeal, enforcement, billing, or other role with a written reason. Creating an IP docket with a Matter creates its operational relationship automatically.

• Each relationship keeps an effective date and retirement history. Retire a relationship instead of deleting it; retiring the operational role also clears the compatibility Matter pointer.
• The relationship panel shows the Matter and IP lifecycle states side by side. Disposing or reopening a Matter does not archive, close, or reopen the IP docket, and an IP lifecycle change does not change the Matter status.
• Accessible IP legal events appear in the linked Matter timeline by reference and open the source IP record. CaseOps does not create a duplicate Matter activity for the event.
• If the two records have different access policies, authorized users see a warning. A user who cannot access both sides sees no relationship metadata, count, or hidden record identity.

Applicant opposition docketing

In the opposition workspace, confirm the applicant profile and source notice first. A pending Registry opposition number remains visible and must be recorded separately from the application number before stage progression.

1. 1
   Select the exact active applicant-side rule and working calendar, enter the trigger date and certainty, then propose the counterstatement deadline.
2. 2
   Confirm the calculated deadline with distinct primary and backup membership owners. The linked operational Matter is required before confirmation.
3. 3
   At the counterstatement stage, record the TM-O filing reference, final signed document, filing evidence, signatory, authority, verification place/date, paragraph ranges, and knowledge basis.
4. 4
   Record service separately. At the applicant-evidence stage, propose and confirm the Rule 46 deadline and explicitly choose either filed evidence or reliance on pleaded facts; no action is never treated as an election.

Opponent opposition docketing

Select the opponent side when the firm is preparing the notice of opposition. Keep the application number and Registry opposition number separate; pending opposition-number allocation remains visible until the Registry number is recorded.

1. 1
   Confirm the sourced opponent profile, relied-on rights, client instruction, and limitation date. A watch hit can be closed with evidence without marking an opposition filed; missing instruction is escalated through an urgent shared task before limitation.
2. 2
   Propose and confirm the notice deadline from the exact active opponent rule and working calendar with distinct primary and backup owners. Record the signed TM-O notice, filing receipt, verification, source, and lawyer reason.
3. 3
   If the Registry rejects the filing, record the rejection evidence and corrective due date. CaseOps opens a corrective task and keeps the filed stage blocked until an accepted corrected notice is recorded.
4. 4
   Record notice service separately. At the evidence stages, confirm the governed deadlines and make explicit Rule 45 and Rule 47 elections; filed-evidence elections require final document and filing evidence references.

Trademark pleading review and filing

Open Trademark pleadings inside an opposition proceeding. The available notice, counterstatement, and evidence templates follow the represented side, current stage, and Registry jurisdiction.

1. 1
   Generate from the confirmed application and opposition identifiers, current proceeding, linked immutable document versions, and retrieved authorities. Conflicting required identifiers block generation.
2. 2
   Save every lawyer change as a new revision and open the revision comparison before review. The original generated and previously filed bodies remain available unchanged.
3. 3
   Clear every blocker before approval: unresolved placeholders, changed proceeding context or deadlines, lost authorities, missing or changed source hashes, and unmapped exhibit references fail closed. Warnings remain visible for lawyer resolution.
4. 4
   Finalize the approved revision and download the filing bundle. The Registry-formatted DOCX is separated from the internal generation manifest and filing checklist inside the ZIP.
5. 5
   Record filing, Registry rejection, corrected revision, and service as separate human actions with references. A rejected filing reopens drafting without rewriting the originally filed version.

Shared evidence, hearing, order, and appeal work

1. 1
   Record the filed Rule 45, Rule 46, or Rule 47 affidavit package with its exhibits, index, verification, relied-on documents, filing receipt, and service evidence. Further evidence stays blocked until the matching leave or order is recorded.
2. 2
   Schedule the canonical shared hearing with responsible attendance and reminders. Link the cause list, issue checklist, evidence bundle, authorities, written submissions, and post-hearing note to that hearing.
3. 3
   Record an authorized deadline extension as a replacement of the confirmed legal deadline. The original calculation and responsibility history remain available; the replacement receives fresh ownership and reminders.
4. 4
   Record the operative order, affected application and opposition, costs, compliance directions, appeal review, and final order document. A later appeal must link that order to a separate appeal proceeding and appeal identifier, or to an accessible Matter.
5. 5
   Use the evidence-backed stage transition for withdrawal, settlement closure, waiver, abandonment, or other exceptional outcomes. Closing an opposition does not close its linked Matter.

Trademark renewals

Open Trademark renewals for the portfolio-wide due, instructed, filing, accepted, grace, and overdue register. Each term shows the confirmed legal deadline, rule citation, source version, grace date, recorded state, and any date-derived state that still needs an explicit workflow transition.

1. 1
   Select a term and schedule instruction notifications. Active primary and backup deadline owners receive an immediate in-app request plus the future reminder offsets; repeating the action does not duplicate them.
2. 2
   Record the client decision, scope, authority, channel, and evidence reference. Receiving an instruction cancels queued no-instruction reminders. A reviewer then accepts, rejects, or requests clarification.
3. 3
   Record filing initiation with its provider reference. This state is not Filed, Registry accepted, or Completed.
4. 4
   Link the confirmed filing event, then the separate registry-acceptance event. Completion requires an accepted certificate document and a confirmed next-term deadline calculated from that acceptance event.

IP reports

Open IP reports for internal portfolio register, application status, opposition status, deadline control, renewal, watch, workload, data-quality, and integration-freshness snapshots. Every result shows its generated time, applied scope, audience, confidentiality, source freshness, row limit, and snapshot hash.

• Application and opposition reports retain their separate registry identifiers and use the same permission-filtered portfolio reader.
• Workload, deadline, renewal, and integration results are read from their existing operational owners; generating a report does not create a second docket, deadline, renewal, export, or connector record.
• Sources that are stale, unavailable, or not activated appear as such. Restricted records outside the user's access are omitted without a count.

IP client portal

Open IP client portal to grant a named client selected dockets, identifier/status visibility, event and date categories, approved document categories, an expiry, and instruction rights. The same workspace lists active and historical grants, approved-document publication, delivery state, and client instructions.

1. 1
   Grant only the required IP docket and categories, with an expiry when appropriate.
2. 2
   Generate and review an Internal report, select the client's active grants, then publish now or schedule delivery.
3. 3
   Publish only an approved, non-privileged internal document version whose taxonomy category and docket are granted.
4. 4
   Review each client instruction and accept, reject, or request clarification. A client instruction never changes legal state before firm acknowledgement.
5. 5
   Revoke access with a reason. Active sessions are invalidated and queued publication delivery is cancelled.

IP document workflow

When the IP workspace is enabled for your firm, open IP docket to classify, name, version, and link portfolio documents without forcing them into a synthetic Matter. Original bytes, filename, hash, processing result, and every immutable version remain available separately from the controlled display name.

1. 1
   Choose an accessible docket, file, classification, naming details, document date, confidentiality, and privilege label.
2. 2
   Select Preview controlled name. Review the proposed name and filing state. Any changed input requires a new preview.
3. 3
   Upload the reviewed document. CaseOps scans before storage, hashes the bytes, and uses the shared extraction/OCR job. A duplicate hash plus matching metadata offers a reusable link instead of another file.
4. 4
   Move the current version through review. Approved and Filed actions require the approval capability and lock the exact version, actor, and time. Uploading replacement bytes creates a new version and supersedes the prior one.
5. 5
   Document managers preview bulk classification/name changes before apply. Taxonomy administrators preview supplied law-firm aliases before import.

Open Notices from the main navigation to manage incoming and outgoing notices across the workspace. A notice can be standalone, linked to one matter, or linked to several matters. Existing matter attachment notices also appear in this register with a clear read-only legacy label.

1. 1
   Open Notices, choose New notice, and set the direction to Received or Sent.
2. 2
   Record the subject, date, type, authority or counterparty, department, optional owner, summary, status, and received-notice reply due details where relevant.
3. 3
   Optionally select any number of accessible matters. Leave every matter clear when the notice is not yet associated with a case.
4. 4
   Optionally attach the primary notice file. CaseOps saves the notice record before uploading the file, so a file error cannot erase or duplicate the notice itself.
5. 5
   Track work from the register by changing an editable notice's status or owner. Use linked matter chips to return to the relevant matter workspace.

• Dashboard. Received, sent, replies-due, and overdue counters summarize the tenant-safe register.
• Filters. Use received and sent tabs, full-text search, status, matter, owner, and reply-due date filters.
• Permissions. documents:upload enables creation and first-file upload; documents:manage enables metadata updates. Linked matter visibility remains server-enforced.

Use a matter's Communications tab to review platform messages, imported email, attachment references, internal notes, and client- or outside-counsel-visible updates in chronological order. Permitted users can log phone, meeting, note, SMS, or email activity and send a template email when an approved delivery provider is configured.

• Mailbox. Mailbox is a Gmail and Outlook metadata review queue. Link safe metadata to a matter, request content import, or ignore a candidate. The queue does not import raw bodies or attachment bytes by default.
• Drive. Drive reviews Google Drive and OneDrive/SharePoint candidates. Link metadata, explicitly import a file through the document safety pipeline, retry failures, or ignore the candidate.
• Notification preferences. Preferences controls in-app, email, SMS, and WhatsApp choices. An external channel remains disabled unless its provider and delivery controls are ready.
• Client and outside-counsel portals. External users request a 30-minute one-time link at Portal sign in. Clients see only explicitly granted matters. Outside counsel is routed to its assigned-matter portal for permitted work product, time, and invoice submission; cross-counsel visibility is off unless enabled.

The Drafting Studio produces a first draft from the matter's own record — parties, stage, documents, focus note — grounded in statutes and judgments retrieved from the CaseOps corpus and your internal precedents. Every inline citation resolves to a named authority. Every fact gap renders as a placeholder the reviewer fills in, not as a fabricated number.

1. 1
   In a matter, open Drafts → New draft and pick a template (bail application, §34 petition, reply to summons, quashing, etc.).
2. 2
   Add a focus note — one or two lines of what this draft must argue. This is the single most load-bearing field.
3. 3
   Press Generate. The first pass finishes in 30–90s; the draft opens with inline citation pills and a grounding panel on the right.
4. 4
   Review for: fact placeholders to resolve, citations to verify, and statute attribution. The reviewer findings block at the foot of the draft calls these out.
5. 5
   Request approval from a partner. Approval is recorded in the audit trail alongside the draft version.

The Hearings tab shows manual hearings, tracked case updates, and cause-list entries linked to the matter. Open the next hearing and press Compile pack. CaseOps stitches a pack in under a minute, from the matter record and the authority corpus:

In an IP docket, record an exact time, a named session, or time not published. CaseOps keeps date-based reminders active for an unpublished time and asks for the published time later; it never inserts a default hearing time. Rescheduling or confirming the time preserves the cancelled reminder generation and labels the current replacement, so the team can inspect what changed before relying on it.

• A chronology built from the matter's documents and activity — no manual entry.
• The last order and its operative portion extracted and pinned.
• A short oral points list — the arguments you actually want to make, keyed to the matter record.
• Source-backed bench context with sample size, linked sources, and limitation notes where the corpus supports it.
• The source list — every piece of content in the pack is traceable back to a matter document or a named authority.

Case tracking uses the configured, approved provider. Active matters with a reliable CNR or exact case-number-plus-court identity are linked in a bounded backfill, while user-created bookmarks remain supported. Closed, Disposed, ambiguous, mismatched, and unsupported records are not updated.

• Daily window. Scheduled production runs start at 6 PM IST, inside the 6 PM–8 PM execution window. No new provider calls start after 8 PM IST unless an operator uses an explicit force or local override.
• Backlog. Unfinished work persists and resumes on the next five-minute continuation inside the execution window. Batches are fair across tenants so one tenant cannot consume the entire window. A queued provider refresh is checked for completion before another refresh is purchased.
• Provider safety. Disabled or misconfigured providers make no external calls. The run records skipped or blocked state instead of failing silently.
• Operations view. Admins can review attempted, refreshed, changed, skipped, blocked, provider-call, error, window, started, ended, partial, and backlog counts in provider operations.
• Freshness and cost. Each bookmarked case shows its provider, last attempt, last good result, next scheduled refresh, freshness, response class, redacted current error, and recorded refresh cost. Stale data remains visible and is labelled stale for lawyer and AI review.
• Verified hearing identity. CNR is the primary exact identifier. Without it, matching requires the court and a public case or filing number with year, corroborated by the supplied case details. Missing, conflicting, multiple or incomplete matches do not update a Matter. Party names alone never identify a case. A verified result updates Next Hearing with the nearest upcoming date; it never reopens a closed or disposed Matter.
• Summary processing. Eligible new order summaries are processed asynchronously under the workspace AI policy. A model failure does not undo the saved provider update. Current access, source identity and Matter lifecycle are checked again before a summary is published.
• Workspace provider budget. Live human searches, refreshes, scheduled eligible refreshes and source downloads count toward one shared Indian Kanoon and eCourts account budget. The default is INR 1,000 per month; Admin > Billing > Usage separates provider contribution from total budget use, limit, remaining amount, and any explicit unlimited policy.
• Scheduled eligibility. Configured credentials do not guarantee that a workspace is eligible for unattended refresh. Provider status reports the current scheduled policy separately from live-human access. Automated tests and configured persistent QA workspaces cannot consume paid provider credits.
• Manual fallback. Manual refresh is rate-limited, cost-attributed, and disabled when provider health is red or the row is quarantined. Existing evidence remains available and the page directs the user to manual docketing while the connector is degraded.
• Replay and quarantine. Admin replay is previewed, tenant-scoped, limited to 25 rows, step-up protected where MFA policy applies, and executed by the next bounded poll. A poison record can be quarantined without stopping other cases. Rate limits, timeouts and temporary outages use bounded automatic recovery, not permanent quarantine or mandatory manual replay. Incident closure requires a successful canary plus root-cause and prevention evidence.
• Disconnect. Calendar, Gmail, and Drive disconnects use recent security step-up where required, revoke stored access, recompute health immediately, stop future connector work, and preserve prior evidence for audit and manual fallback.

Court orders can produce compliance items, tasks, and deadlines, but the default workflow is review-first. Deterministic proceeding extraction runs before AI. AI extraction runs only when the tenant AI policy allows it, and the output must pass JSON schema validation before it creates review-required compliance items.

• Source-backed fields. Each item shows description, responsible party, due date if supported, timeline text, filing requirement, court direction, next action, source order or attachment, snippet, page or paragraph, confidence label, status, review status, generated task or deadline link, and dedupe key.
• Deadline caution. Calendar-day calculations use the default convention shown in the item. Court holidays are not assumed unless a court calendar exists. Ambiguous phrases such as "from today", "within two weeks", "next date", or a missing order date stay review-required. CaseOps never invents a due date.
• Activation. Generated tasks and deadlines stay draft or review-linked unless a tenant/admin setting allows auto-activation. A lawyer confirms, edits, assigns, rejects, waives, completes, or retries items from the matter-level compliance panel.
• Rejections. Rejected items do not appear as active compliance, and every confirm, reject, waive, complete, and retry action is audited.

The cause-list workspace at /app/cause-list creates a printable date-wise list from hearings, imported cause-list entries, or both. Use it for daily court preparation, team allocation, and court clerk handoff.

• Filters. Pick date or date range, court, practice area, matter status, include/exclude disposed matters, source, and sort order. Sorting includes date, court, or lawyer.
• Required columns. Serial number, file number, court name, case number, case title, judge name, court number, item number, lawyers appearing, and hearing date. Missing data appears asNot available or a preview warning instead of a blank cell.
• Fix source data first. The page has no per-row override editor. If preview data is incomplete, update the underlying matter, hearing, or imported cause-list entry and run the preview again.
• PDF audit. Each download records filters, row count, actor, timestamp, checksum, and file name.

Litigation Intelligence is the matter-level workspace for source-backed preparation and review. It pulls together proceeding sheets, affidavits, mock-hearing sessions, predictive context, legal-source readiness, a matter knowledge graph, and transcript-first coaching without changing the rule that a lawyer reviews substantive output.

• Proceeding Sheet Intelligence. Court orders and order sheets are parsed from raw order text only. Next hearing dates, compliance directions, affidavit deadlines, and generated tasks keep the source order, snippet, confidence, and review-required status.
• Affidavit Intelligence. Mark a document as an affidavit, chief affidavit, or counter-affidavit to extract key statements, dates, figures, entities, annexures, gaps, contradictions, and source-grounded cross-examination questions.
• Mock Hearing and Coach. The simulator is typed-text only and uses LI affidavit question banks. The coach requires a session acknowledgement and scores observable preparation markers such as whether the question was answered, whether a source reference was used, and whether unsupported assertions were added.
• Predictive and bench context. Predictive Intelligence shows observed historical patterns only when indexed source evidence exists. Supported signals display sample size, confidence band, source links, snapshot references, and limitation notes.
• Review queue and knowledge graph. The Litigation Intelligence review page groups pending review items and lets permitted users accept, reject, mark reviewed, or edit notes. The knowledge graph materializes matter-scoped nodes and edges from source-backed LI records with bounded snippets.
• Strategy Plan. The matter strategy surface lays out current posture, primary and alternative routes, forum sequence, recommended draft pack, missing facts, risks, authorities, and a lawyer-review workflow. It remains decision support, not an automatic filing instruction.

When you generate an appeal_memorandum draft for a matter that has an upcoming listing, CaseOps doesn't just pull authorities from the court at large — it pulls authorities authored by the specific bench scheduled to hear the appeal and prefers ones that align with the matter's practice area. The advocate-bias selection is editorial: the system surfaces the citations that support your grounds. Adverse-authority duties to the court remain yours.

• Career timeline on every judge profile — /app/courts/judges/{id} shows every court the judge has served on, with source-attributed evidence.
• Bench resolver on the matter hearings tab — "Justice X & Justice Y" renders as clickable links to each judge's profile.
• Appeal Strength panel on the appeal stepper flags per-ground citation coverage and weak-evidence paths.

Judge profiles use canonical judge-to-judgment mappings rather than a free-text name coincidence. Each mapped judgment shows the court, citation, date, source action, mapping confidence, and retained source evidence. Filters and bounded pagination keep longer decision histories usable without scanning the authority corpus in the browser.

• Coverage is explicit. The profile distinguishes a court with no mapped corpus from a mapped court with no judgments for the selected judge, and separately labels filters with no matches.
• Analytics fail closed. Low-confidence mappings remain visible for review but do not enter descriptive analytics. Counts carry sample and coverage limitations and never become judge scores or outcome forecasts.
• Curator controls. Staff can resolve each collision evidence slot, add sourced judge or bench aliases, merge duplicate identities with record versions, and reprocess an authority. Every write remains capability-gated and audited.
• Research handoff. A judge profile can start a research query constrained by the canonical judge and court, while every listed judgment retains its own source action.

Visit /app/statutes to browse the structured catalog of central Indian Acts. The live catalog separates catalogued provisions from verified selectable provisions, including the Constitution, BNSS, BNS, BSA, CrPC, IPC, CPC, major commercial and regulatory Acts, and source links to indiacode.nic.in — the Government of India's official Acts repository.

• Attach to a matter. The Statutes sub-tab on the matter cockpit lets you mark which sections this matter cites, opposes, or holds in context.
• Fed into drafting. When you generate an appeal-memorandum draft, the prompt receives the bare text of each attached section. The LLM is instructed to quote verbatim instead of paraphrasing.
• BNSS vs BNS unambiguous. The structured reference makes the act explicit, so "Section 483 BNSS" (bail) is never confused with "Section 483 BNS".
• Catalog visibility. An Act page lists every catalogued section, including pending, quarantined, and retired rows, with its available source and trust state. Only fully verified sections can be attached or used for drafting and AI grounding.

Open /app/research from the left navigation to run open-ended queries without tying the query to a specific draft. Choose the CaseOps corpus or, where your workspace has completed every provider gate, the licensed Indian Kanoon API.

• Query. Natural language works best — phrase the issue, not a keyword. Example: triple test for anticipatory bail under BNSS s.482.
• Results. Authority cards show the available title, citation, publisher, court/date metadata, extract, and source action. Licensed results also show required attribution, cache freshness, provider cost, and unreviewed authority/binding status.
• Save. Saving a result creates a tenant-private entry in the workspace research notebook. It is not automatically attached to the matter currently open in another tab.
• Intelligent review. Save a frozen report, then choose Start intelligent review from Saved research. Select one permitted Matter or IP docket, state the issue, record facts and conflicting values, reference existing documents, and confirm the authority set. The asynchronous review separates relevant facts, applicable provisions, supporting and contrary passages, factual analogies, gaps, unresolved contradictions, and lawyer checks. Every authority retains its citation, court, date, passage, relevance, source URL, content hash, and source version. A link containing the server-owned review ID opens that exact permission-visible review even when it is outside the bounded history list; access is rechecked by the review API before any detail is shown.
• Lawyer gate. An authorized lawyer can include or exclude authorities and add notes. Removing any citation behind an assertion makes the review visibly incomplete and blocks finalization. A finalized review can be published only into the existing Draft lifecycle, where the approved Draft remains separate from generated analysis and follows the normal review and finalization controls. An IP-docket review can be finalized as analysis, but publishing it into the trademark pleading workspace also requires a selected opposition proceeding from that docket.
• Ask this Workspace. Open /app/assistant, search for the permitted client, matter, docket, IP right, proceeding, or document records you want to include, and apply that explicit scope. Answers show exact record citations and source links. The assistant abstains when permitted verified evidence is insufficient and routes legal-proposition research back here. It can suggest navigation, searches, drafts, tasks, or field updates, but it does not execute a write without the separate preview-and-confirm workflow. Conversations can be exported, archived, or cleared; destructive deletion remains blocked until legal-hold-aware retention is implemented.
• Licensed source. Indian Kanoon is available to authenticated human users when contract, terms, server-only credentials, permitted uses, retention, legal coverage, and a positive verified INR cost profile all pass. By default, Indian Kanoon and eCourts share one INR 1,000 monthly account limit; Billing > Usage publishes each provider's contribution, total budget use, and remaining budget. CaseOps never scrapes Indian Kanoon public pages.
• Automation is nonbillable. Automated verification may read CaseOps readiness and recorded balances, but it cannot execute a paid search, detail, refresh, retrieval, or download request. A test-looking workspace name does not block a normal human request.

Contracts live in the top-level Contracts workspace. A contract record can hold its document, extracted clauses, playbook comparison, obligations, and a parsed redline view.

• Upload. Drop the contract (.docx or .pdf). CaseOps extracts parties, effective dates, key covenants and payment terms.
• Playbook compare. Pick a playbook; the system flags clauses that deviate from it and suggests an edit per deviation.
• Obligations. Payment, reporting, consent and termination obligations lift into the Obligations list with due dates and owners.
• Redlines. Upload a DOCX with tracked changes to parse and review additions/deletions in CaseOps. The current surface does not export a newly tracked Word document or claim version lineage.

CaseOps produces explainable recommendations — forum choice, supporting authorities, next best action — with rationale, assumptions, missing facts and a confidence label. Recommendations must show the source trail and limitation note before anyone accepts them.

1. Rationale. Two to four sentences, grounded in named authorities and the matter record.
2. Assumptions. Facts the system took as given. Wrong assumptions are your signal to reject the recommendation.
3. Missing facts. Fields the system flagged as absent or too thin. Filling these in and re-running sharpens the output.
4. Confidence. High / Medium / Low. Low-confidence recommendations are deliberately surfaced, not hidden.

General Counsel teams run Outside counsel from the top-level navigation. The live directory records counsel and firm profiles, contacts, jurisdictions, practice areas, panel status, and notes. A matter can carry one or more counsel assignments.

• Profiles. Add and maintain the panel identity, contact information, jurisdiction, and practice-area coverage used when selecting counsel.
• Assignments. From a matter's Outside Counsel surface, assign a panel record and record the fee arrangement, budget, scope, dates, and assignment status supported by the form.
• Spend and payment state. Record assignment-level spend and payment status where available. The current UI does not promise rate cards, outcome history, generated brief packets, budget alert enforcement, realization, or aging roll-ups.

Matter billing is separate from CaseOps SaaS subscription billing. Tenant admins configure law-firm billing at/app/admin/matter-billing, then users generate invoices from unbilled matter work, expenses, fixed fees, milestones, retainers, advance adjustments, and manual line items.

• Profiles. Store firm legal name, address, GSTIN, PAN, invoice prefix and sequence, default currency, payment terms, default SAC/HSN or service classification, footer/note, and logo or header where tenant branding supports it.
• Rates and arrangements. Resolve hourly rates by user, role, practice area, or default. Fixed-fee matters, milestone templates, retainers or advances, expense/reimbursement categories, and manual line items can be added where applicable.
• Tax and adjustments. Tax is calculated server-side from invoice data: client billing name/address/GSTIN where available, place of supply, taxable value, CGST/SGST/IGST split, totals, grand total, amount paid, outstanding amount, and TDS deduction/payment adjustment fields where recorded.
• Double-billing guard. Time entries already attached to an invoice cannot be billed again unless the original invoice path is voided or adjusted under the tenant's audit rules.
• PDF export. Downloadable invoice PDFs are rendered server-side from stored invoice data. Invoice downloads and billing profile or rate changes are audited. External payment links are used only when a tenant has explicitly configured an approved provider.

Admins run the workspace from /app/admin. The important subsections are Employees, Roles, Teams, AI policy, provider and connector operations, Audit export, and Matter billing. CaseOps SaaS subscription billing stays separate from matter/client billing.

• Employees and roles. Add employees, assign built-in or custom roles, update employment state, and review per-employee matter access. Prior activity remains attributed after deactivation.
• Teams. Organize employees for practice and operational workflows; continue to enforce permissions and matter access through the server-side capability model.
• AI policy. Cap the providers, models and context shapes the workspace is allowed to use. AI actions outside the policy are blocked before any token is spent.
• Provider operations. Review scheduled case-tracking runs, blocked/skipped reasons, provider-disabled states, last attempt, last good state, response class, freshness, partial backlog, refresh window, and per-tenant batching metrics. Replayable rows require a short-lived scope-and-cost preview before an audited confirmation; enrolled MFA also requires recent step-up.
• Provider spend. Billing > Usage publishes this workspace's Indian Kanoon and eCourts spend independently, including the monthly limit, remaining amount, currency, and unlimited state.
• Matter billing. Manage billing profiles, rate cards, invoice numbering, tax split settings, expense categories, and invoice templates for law-firm matter billing.
• Audit export. JSONL or CSV for any date range. Large exports run as background jobs; download when complete.

Security is not a tab — it is the way every other tab is built. The short version:

• Tenant-private data isolation at query and storage boundaries. Shared public authority records remain deliberately separate from tenant-owned records and embeddings.
• Matter access restrictions are enforced server-side in addition to the workspace role and capability grid.
• Audit on material and sensitive events — including administrative changes, exports, AI runs and review decisions, recommendation decisions, document activity, and payment state changes where implemented.
• Provider and AI data minimisation. Tenant-facing screens do not expose provider tokens, raw provider payloads, raw prompts, raw LLM responses, internal costs, or tenant-private data to unauthorized users.
• Notification safety. Scheduled job failures, compliance review events, and provider-blocked states create durable in-app notification intents. Email, SMS, and WhatsApp delivery are not sent unless an approved provider is explicitly configured.
• No cross-tenant training. Your documents and matter activity are not pooled into model training without an explicit opt-in.
• Encryption in transit and at rest, signed URLs for document downloads, and short-lived session tokens.
• Hardened browser headers — CSP, HSTS, X-Frame DENY, strict Permissions-Policy — reduce client-side exposure.

A document won't index

Check the status pill in Documents. Most failures are OCR timeouts on very large scans — press Retry. Persistent failures usually mean the PDF has no extractable text and no OCR layer; convert to DOCX or re-scan at a higher DPI.

Citations in my draft look wrong

Use the grounding panel on the right side of the Drafting Studio — every inline citation has a source. If an authority is wrong for the point, open it, remove it from the shortlist, and regenerate. The reviewer findings block at the foot of the draft also flags likely mismatches.

Research returned 0 results

The query may be too generic (bail) or the indexed corpus may not cover that jurisdiction and year. Rewrite with the issue, statute, forum, and date range rather than assuming the system will narrow it.

A colleague cannot see a matter I opened

Ask an owner or admin to review the employee's built-in/custom role, capabilities, active status, and matter access under Admin → Employees. The dedicated ethical-walls UI is not yet a live self-service remedy.

A tracked case was skipped

Open provider operations. Skipped and blocked runs show the reason: outside the 6 PM-8 PM IST window, provider disabled, missing configuration, source blocked, tenant batch limit, or backlog carried forward. Disabled providers make no external calls. A configured connector with no recent successful check is shown as unhealthy, never as healthy merely because it is enabled. Preview any replay, review its bounded scope and cost basis, then confirm and monitor the durable job.

A compliance due date is missing

Check the source snippet and confidence label. Ambiguous text, missing order date, missing court calendar, or phrases like "next date" keep the item review-required. Add the date manually only after lawyer review; CaseOps will not invent one.

A rejected compliance item still appears active

Refresh the matter compliance panel and inspect the review status. A rejected item should not appear as active compliance. If it does, export the audit trail for the matter and contact support with the item ID.

A notice reply deadline is missing or still open

Confirm the record is a primary received notice, Reply requiredis enabled, and a reply due date is present. To complete the linked deadline, upload via Reply document or use Mark reply sent; a supporting document alone does not change reply status.

A cause-list PDF has missing fields

The preview must show Not available or a warning for missing serial number, file number, court, case number, title, judge, court number, item number, lawyers appearing, or hearing date. Correct the underlying matter, hearing, or imported cause-list record, then preview again before downloading; the page has no per-row override editor.

Matter graph

The connected record of everything that belongs to one matter — parties, documents, drafts, hearings, invoices, activity, audit.

Cockpit

The single-page view of a matter. Every tab inside it is a lens on the same graph.

Corpus

The public pool of statutes, judgments and regulatory material CaseOps retrieves against. Tenant documents are separate and tenant-private.

Matter access restriction

Server-enforced visibility below the workspace role/capability layer. Employee matter access is live; the dedicated ethical-walls admin UI remains status-gated.

Grounding

The link between an AI output and the source it came from (a judgment, statute, or matter document). A CaseOps output without a grounding is a bug.

Recall@10 / MRR

Retrieval quality metrics. Recall@10 is the fraction of queries whose correct answer appears in the top-10 results. MRR (mean reciprocal rank) averages 1/rank across queries — higher means the correct hit sits closer to the top.

Hearing pack

The bundle a lawyer takes into court — chronology, last order, oral points, bench brief, source list — compiled from the matter record and authority corpus.

Disposed

The canonical backend status for a completed matter. The UI action is Dispose; API responses emit disposed.

Tracked case

A matter-linked or explicitly bookmarked case eligible for the bounded 6 PM IST refresh. Automatic links require a reliable CNR or exact case-number-plus-court identity.

Compliance review item

A source-backed court-order direction that requires lawyer review before it becomes active compliance, a task, or a deadline.

Next-hearing suggestion

A non-authoritative intelligence-derived date that conflicts with the current matter header. It must be accepted before replacing the displayed next hearing.

Cause-list PDF

A black-and-white, date-wise court table generated from hearings and cause-list entries, with missing-field warnings and audited downloads.

TDS adjustment

A recorded deduction or payment adjustment against a matter invoice. It is tracked as invoice data and does not change the rule that tax calculations are server-side.

Playbook

A named set of preferred contract positions. CaseOps compares any inbound contract against the playbook and surfaces deviations.

Open Patent intake to maintain restricted invention families and separate application records. Application, publication and grant identifiers retain their source form; an application number may be explicitly recorded as pending allocation.

1. 1
   Record the disclosure. Select the client, enter the disclosure date and narrative, then retain the source document in the family Documents area. Family membership does not establish priority.
2. 2
   Add separate applications. Record the application type, jurisdiction, office, dates, identifiers and exact source versions. Applications keep their own record lifecycle and correction history.
3. 3
   Record parties. Use Parties for inventor, applicant, proprietor, agent and licensee facts. Pin the address and source version; replace an incorrect fact with a reason instead of overwriting history.
4. 4
   Record priority and parents. Open an application's Priorities area, select an authorized parent application and the relationship type, then record the priority date and source. A parent may belong to another family without moving either application. The family Relationships area shows the recorded links.
5. 5
   Correct or withdraw a record. Corrections and withdrawals append new evidence and preserve the original source. A withdrawal here withdraws the recorded link, not the patent application. Historical evidence for a closed parent remains readable; a new link requires an active parent and an active child.
6. 6
   Review and close explicitly. Inspect recorded review notes, download the exact retained source version, and use Lifecycle for an authorized closure with an impact preview. Source edits and relationship changes do not reopen closed records.

These are intake and evidence records. They do not confirm legal priority, grant, ownership or filing, calculate patent deadlines, or complete a prosecution or maintenance action. Verify the governing source and the domain availability shown in the workspace before relying on automation.