Regulatory Readiness

What does regulatory readiness cover?

Regulatory readiness covers the work of knowing which rules apply, documenting how the organization meets them, and communicating accurately about it. It combines legal analysis, technical records and clear external messages. Communications teams support the parts that involve public statements, notices to customers and responses to questions from media or regulators.

Which AI rules are in play?

AI rules differ by region and are changing quickly. The table lists several developments reported by law firm summaries as of late 2026. It is illustrative and incomplete, and dates and scope should be confirmed against the current texts.

Rule	What it generally covers	Reported timing
EU AI Act, Article 50	Transparency for AI interactions and AI-generated content	Applies from August 2, 2026, with a grace period to December 2, 2026 for marking by generative systems already on the market
EU AI Act, high-risk obligations	Duties for high-risk systems	Delayed by the Digital Omnibus (Regulation (EU) 2026/1744): December 2, 2027 for Annex III systems and August 2, 2028 for Annex I products
California AI Transparency Act (SB 942 and AB 853)	Disclosure and detection duties for large generative AI providers	Operative August 2, 2026, with later duties in 2027 and 2028
California AB 2013 and SB 53	Training-data disclosure and frontier model rules	Reported in force from January 1, 2026
Other US state laws	Examples include Texas and Illinois laws, including AI in employment	Reported in force from January 1, 2026

Legal commentary has also noted possible federal challenges to state AI laws, so the picture may shift. See AI disclosure for the transparency rules in more detail.

What is the communications role?

Communications teams help turn legal requirements into clear, accurate public information. Typical tasks are:

• Writing notices and labels, such as those for AI-generated content or AI interactions.
• Preparing statements about how the organization uses AI, checked against what is actually done.
• Keeping a record of public claims about AI so they can be verified.
• Preparing a response plan for regulator inquiries and media questions.
• Training spokespeople on what can and cannot be said.
• Coordinating with legal, product, security and public affairs teams.

How do you build readiness?

1. Inventory where AI is used, including tools from vendors, and who owns each use.
2. Identify which rules apply in each market, with counsel.
3. Document the policies, testing and oversight in place, and fix gaps.
4. Draft the required notices and public statements, and have legal review them.
5. Assign owners, set a review schedule and track rule changes.
6. Test the response plan with a short exercise.

Illustrative readiness log columns (example only)

• AI use case, owner and vendor
• Rules that may apply and the market
• Evidence on file and the date reviewed
• Public statement or notice, and who approved it

What mistakes are common?

• Public statements about AI that the organization cannot support.
• Treating readiness as a one-time project when rules keep changing.
• Leaving communications out until after the legal analysis is done.
• Missing AI that arrives through vendors and default settings.
• Assuming a single country's rules cover every market.

Readiness reduces surprises but does not guarantee compliance or any regulatory outcome. Counsel should review the rules that apply.