<?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/cdf139e1d52d44cca993d3e2fa086d8a&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/cdf139e1d52d44cca993d3e2fa086d8a-a2b8860019c2c969.gif</thumbnail_url><duration>160.087</duration><title>Mastering Flags: Your Guide to QA/QC in Pirros</title><description>In this video, I discuss the process of flagging details for issues that affect multiple projects or firm standards, such as typos or constructability problems. If you encounter a project-specific issue, please use stashes and markups instead. I walk you through how to create a flag, add actionable notes, and include supporting context like field photos or marked-up PDFs. Remember to submit the flag so that anyone who has downloaded the detail in the last six months will be automatically notified. It&apos;s a straightforward process designed to help our team stay informed and address issues promptly.</description></oembed>