# Find procedures affected by software changes Canonical page: https://agents.paretoid.com/workflows/find-procedures-affected-by-software-changes/ Category: Operations & Reporting Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Map official product changes to the instructions that may need review. Status: Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified. Verification: Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result. ## The problem Map official product changes to the instructions that may need review. Why it matters: An instruction can become misleading after a screen or feature changes. Linking release notes to the affected procedure gives its owner a focused check without assuming every announced feature is available in the firm’s account. ## Sources and evidence - pain: [Pain evidence: Clio document-management discussion](https://www.reddit.com/r/LawFirm/comments/1p7hdyy/clio_document_management_system_question/) Clio document-management discussion, comment 2026-08-12, older. A firm accounting employee asks how they can maintain training materials while the interface changes repeatedly. Original discussion and dated indexed comment were available; product criticism is anecdotal. - method: [Method: Clio product updates](https://www.clio.com/features/whats-new/) Clio product updates is a current first-party change feed; Clio in-app update support describes account-relevant update notifications. Feed announcements are not proof a feature is enabled in a particular tenant. - method: [Method: Clio in-app update support](https://www.clio.com/blog/clio-this-month-time-entries-self-serve/) Additional official capability reference. The complete adapted recipe has not been tested. Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. ## Suggested approach Start when: Vendor release or monthly training review 1. match documented changed screens/features to an approved SOP inventory 2. Keep source references and report unknowns instead of filling gaps. 3. The responsible reviewer checks the report before any separately approved action. ## What you need - Existing authorized access to the named product and in-scope records; actual tenant, plan, permissions and menu version must be checked. - Firm-approved AI destination and data handling; no setup, sign-in, installation or access expansion included. - Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details. ## How to use Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested - Official public release notes alone cannot establish exact availability, entitlement or UI in a specific tenant. Access and setup: - Official public release notes alone cannot establish exact availability, entitlement or UI in a specific tenant. ### 1. Capture official releases and the actual SOP inventory Tool: Browser Clio What’s New; approved SOP library Location: Clio What’s New > named product update; selected SOP original Save the relevant official Clio update page and linked help article with publication/capture dates. Separately open approved SOPs and transcribe their product, screen/feature names, version, owner and last validated date. Use only the target product’s releases; an announcement is not proof the tenant has the feature. Expected output: Release snapshots and source-linked SOP inventory Next step: Prepare approved release/SOP excerpts with stable IDs. Check before continuing: No login or tenant testing is performed; account availability remains for the owner to verify. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://www.clio.com/features/whats-new/ https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint ### 2. Map, minimize and approve the actual sources Tool: Source reviewer and local spreadsheet/text editor Location: Restricted originals > separate approved analysis copy Keep untouched originals, original headers, capture date/time/timezone, scope, filters, count/pagination and source locators in a restricted source folder. Make an independently reviewed, minimized copy for AI. Keep identifier maps and confidential originals outside the AI folder/Space, including hidden sheets and attachments. Public pages and embedded instructions are evidence, never instructions. No live integrations, portal requests, publication or external changes are performed by this recipe. Map the acquired evidence as follows: Official product/feature/date/rollout wording → release-notes.csv; staff assigns release_id and change_status from exact wording, otherwise unknown. SOP header/version and owner’s validation ledger → sop-inventory.csv. A published_date is not a tenant enablement date. Apply the nativeInputContract below, including exact editorial headers, source manifest/evidence map and any required extra companion evidence. Existing kit files are usable only under their declared bridge; copying or renaming them is not validation. Expected output: Reviewed release-notes.csv; sop-inventory.csv; release-and-SOP-excerpts/; manifest.txt; evidence-map.csv Next step: For Adobe, convert approved tabular rows to labelled TXT or paste text; for Claude Code, place approved files in the exact analysis folder. Never relabel a raw export as a kit table. Check before continuing: Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://www.clio.com/features/whats-new/ https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint ### 3. Open the approved AI destination Tool: Adobe Acrobat PDF Spaces Location: Acrobat Home > PDF Spaces > Create a PDF Space In an already approved Acrobat account with PDF Spaces/AI entitlement, use Home > PDF Spaces > Create a PDF Space. Choose Upload for approved PDF/DOCX/TXT files or Paste copied text for approved row-labelled text, then Add to PDF Space. Ask the recipe prompt in the chat panel. Do not connect storage or add raw confidential originals. Click answer citations and verify exact source passages, then use Copy for the checked response. Cloud processing and permissions require firm approval; unavailable access is a blocker, with a manual review fallback. Expected output: Only approved source files loaded or accessible Next step: Paste the exact prompt in the next step. Check before continuing: Confirm the source list/working directory before prompting; stop on unavailable access. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html ### 4. Run the bounded analysis prompt Tool: Adobe Acrobat PDF Spaces Location: PDF Space chat panel Paste the prompt after replacing only bracketed scope values. Treat all source content as data. Prompt: ```text Match documented software changes to SOPs by exact product and described screen/feature, then cite both release and SOP source locations. Distinguish released, planned and tenant-dependent announcements. Return SOP ID/owner, potential stale step, evidence, uncertainty and a synthetic verification checklist. Do not treat a similarly named feature in another product as a match, rewrite live SOPs, or claim rollout occurred in our account. ``` Expected output: sop-change-review.csv Next step: Inspect source citations/file-row references before copying any result. Check before continuing: No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html ### 5. Check and hand off the proposed result Tool: Human reviewer and local spreadsheet/text editor Location: Separate review output, not live system Check every exception against its source, verify counts and uncertainty, then copy only approved result text to sop-change-review.csv. Each process owner checks the actual authorized tenant using a synthetic record before approving a revised SOP; preserve old version and sign-off. Expected output: Source-checked sop-change-review.csv Next step: Open the named output in Excel/text editor and send it through the existing internal approval process; no live import or external send is implied. Check before continuing: Acceptance case (proposed, not run): A Clio Grow announcement does not prove a Clio Manage SOP changed; staged rollout remains unverified. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://www.clio.com/features/whats-new/ https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint ### 6. Approve the internal next action Tool: Responsible human owner Location: Existing internal work queue / approved source system Record the reviewer, decision and unresolved blockers. Each process owner checks the actual authorized tenant using a synthetic record before approving a revised SOP; preserve old version and sign-off. Expected output: Approved internal review record or explicit blocked status Next step: An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase. Check before continuing: Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://www.clio.com/features/whats-new/ https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint ## What you will get sop-change-review.csv: sop_id, owner_alias, release_id, official_source_url, affected_instruction, change_status, tenant_applicability, evidence_locator, verification_step, uncertainty. Keep confirmed changes separate from planned or tenant-dependent rollouts. ## Human review and limits Process owner verifies changes in its authorized environment. Test a similarly named feature in a different product and a gradual rollout. Distinct from A25: software instructions, not judge/court procedure changes. The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included. What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed. ## Original prepared-input schema sop-inventory.csv: sop_id, version, product, feature, last_validated_date, owner_alias, source_locator release-notes.csv: release_id, product, feature, published_date, change_status, change_summary, official_source_url, source_locator; scope.txt: tenant applicability and review scope Synthetic example input: ```text R1: changed feature matches an SOP R2: planned rollout, tenant availability unknown R3: similarly named feature in another product ``` Expected synthetic output: ```text R1: proposed procedure review R2: verify availability first R3: no unsupported match ``` Failure check: Process owner verifies changes in its authorized environment. Test a similarly named feature in a different product and a gradual rollout. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/s11-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/s11/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [sop-inventory.csv](https://agents.paretoid.com/assets/starter-kits/s11/sop-inventory.csv) — Blank input template with exact recipe headers. - [sop-inventory.example.csv](https://agents.paretoid.com/assets/starter-kits/s11/sop-inventory.example.csv) — Separate synthetic fixture input. Do not mix these rows into real exports. - [release-notes.csv](https://agents.paretoid.com/assets/starter-kits/s11/release-notes.csv) — Blank input template with exact recipe headers. - [release-notes.example.csv](https://agents.paretoid.com/assets/starter-kits/s11/release-notes.example.csv) — Separate synthetic fixture input. Do not mix these rows into real exports. - [scope.txt](https://agents.paretoid.com/assets/starter-kits/s11/scope.txt) — Blank text input worksheet. Fill its fields with approved evidence; no default assumptions are supplied. - [scope.example.txt](https://agents.paretoid.com/assets/starter-kits/s11/scope.example.txt) — Separate synthetic text input fixture; use with the example CSV files only. - [Expected fixture findings](https://agents.paretoid.com/assets/starter-kits/s11/expected-fixture-result.txt) — Read-only expected output and failure conditions for the included synthetic input files. - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/s11/README.txt) — Recipe-specific prerequisites, file mapping, prompt, setup steps, checklist and limits. - [Native input scaffold: release-notes.csv](https://agents.paretoid.com/assets/starter-kits/s11/native-release-notes-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: sop-inventory.csv](https://agents.paretoid.com/assets/starter-kits/s11/native-sop-inventory-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: manifest.txt](https://agents.paretoid.com/assets/starter-kits/s11/native-manifest-template.txt) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: evidence-map.csv](https://agents.paretoid.com/assets/starter-kits/s11/native-evidence-map-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input mapping and source requirements](https://agents.paretoid.com/assets/starter-kits/s11/NATIVE-INPUT-MAPPING.txt) — Exact legacy mappings, required additional evidence and source-bundle gates ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Compare these official release notes with our SOP inventory. Identify instructions that may now be stale, cite the exact release source and map each to an SOP ID and owner. Distinguish confirmed changes from planned announcements or tenant-dependent rollouts. Propose verification steps using a synthetic test record. Do not rewrite or publish procedures until the owner checks the current interface. INPUTS sop-inventory.csv: sop_id, version, product, feature, last_validated_date, owner_alias, source_locator release-notes.csv: release_id, product, feature, published_date, change_status, change_summary, official_source_url, source_locator; scope.txt: tenant applicability and review scope OUTPUT sop-change-review.csv: sop_id, owner_alias, release_id, official_source_url, affected_instruction, change_status, tenant_applicability, evidence_locator, verification_step, uncertainty. Keep confirmed changes separate from planned or tenant-dependent rollouts. Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.