<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/916a7447ced349f3aa65142149a01f42&quot; frameborder=&quot;0&quot; width=&quot;1728&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1728</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1728</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/916a7447ced349f3aa65142149a01f42-7e7fbb5986bac998.gif</thumbnail_url><duration>363.863</duration><title>Automating Federal Comment Response Workflow 🚀</title><description>Every year agencies get millions of public comments, and they must respond to every substantial ban or the rule gets thrown out. PolicyWare compresses that whole workflow into two hours, versus months and millions in attorney fees, including examples like 26,000 comments for the FTC non-compete rule and 4.3 million for the EPA Clean Power Plan, with up to 1.6 million in drafting time. I demoed an ML plus legal drafting pipeline that ingests regulations.gov and the Federal Register, clusters comments, predicts response risk, maps each comment to CFR sections, and drafts APA compliant response language with live case references. There was no action requested from viewers in this Loom.</description></oembed>