<?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/e457496c73fb4ec183f8e323035fb233&quot; frameborder=&quot;0&quot; width=&quot;1246&quot; height=&quot;934&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>934</height><width>1246</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>934</thumbnail_height><thumbnail_width>1246</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/e457496c73fb4ec183f8e323035fb233-d18a5d137f281408.gif</thumbnail_url><duration>187.561</duration><title>Using Playbooks to help with drafting language</title><description>This Loom demonstrates using playbooks with an independent contractor agreement to manage limitations of liability. The author shows a risk rule that evaluates whether the contract includes a cap on damages and flags it as low, medium, or high risk, noting that the example document had no limitation of liability clause and was therefore high risk. Since the risk playbook does not allow editing, they switch to an assistant prompt to draft a limitation of liability clause with a $10,000 cap on damages, then apply the inserted language where the system indicates it should go. They also mention an alternate rule type that can provide text for direct redlining and includes explanations and items to consider.</description></oembed>