<?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/15b580f7aff0424197cddab830f21a86&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/15b580f7aff0424197cddab830f21a86-e37ddf3c993009f7.gif</thumbnail_url><duration>209.1272</duration><title>Scope Assignment Guidance</title><description>In this video, I&apos;ve shared our draft report, which is currently awaiting the data collection process to begin. I&apos;ve outlined a three-step flow for setting up data collection, emphasizing that the first two steps—assigning scopes and activities—are optional and tailored to your project needs. If you know certain scope categories won&apos;t be relevant for your entities, you can unassign them to streamline the reporting process. I&apos;ve provided an example of unassigning specific scope categories under scope three, along with the option to include justifications for transparency. Please review these steps and consider how they might fit into your reporting strategy.</description></oembed>