This is a watchlist process for changes that may affect the chamber later. It helps decide what deserves investigation; it is not a product ranking or a prediction that every announced feature will arrive.
Keep a dated evidence log
For each proposed change, record the announcement, issuing organisation, date, scope and source link. Separate a proposal, pilot, release and mandatory requirement. If the source is a vendor, label its description as the provider's claim rather than independent testing.
Identify what would change in your practice
Name the affected task, document or court workflow. Record who would need access or training, which existing process might change and whether the relevant court or recipient has issued directions. Avoid treating a national announcement as proof that every local forum uses the same process.
Assign a review trigger
Choose an event that justifies another look: published rules, availability for your account, a supported export, or a completed trial. Record the owner and review date. Archive claims that remain unverified instead of repeating them in client-facing guidance.
Move a verified change into the right process
Use vendor due diligence for procurement, the AI adoption policy for internal permissions and training, and the relevant court's official directions for filing changes. Keep the watchlist separate from the record of what the chamber has actually adopted.