Briard video demo transcript

Watch the narrated video. Recorded September 14, 2026, using fictional sample data. Microsoft connection and discovery are simulated. No customer account is connected and no real approval, upload, subscription, or support message is sent.

00:00:00 — Start with one clear next step

Welcome to Briard! If you manage compliance or security, you probably spend a lot of time asking the same questions. Which AI tools are people using? Who is responsible? And what still needs a decision? Let's see how Briard brings that work together. You don't need a technical background to follow along. We're using a fictional company and sample information throughout this demonstration. Here on Home, Jane sees one clear next step: provide proof for an AI tool. The explanation tells her why it matters, and the button takes her straight to the work. Start here each day, check the place you're reviewing, and focus on the next useful action.

00:00:46 — Know which AI tools you have

First, let's open My AI tools. This is your shared list of the AI tools your organization has recorded. Choose a tool on the left to see its record. In this sample, we have tools used in a secure project, the main work environment, and clinical operations. That context matters. A tool used for everyday office work may need a different review from one used with sensitive information. The guided view keeps the next question easy to find. When you need more detail, open See full record. You can review the profile, answers, supporting proof, and things still to fix. Your team has one place to return to, instead of rebuilding the story from emails and spreadsheets.

00:01:33 — Add a tool in four short steps

What if a tool isn't on the list yet? Open More, then Add an AI tool. We'll add a fictional Contract Review Copilot. First, enter the name and provider. Next, explain its planned use in everyday language. Here, it helps draft contract summaries, and a person reviews the result. Then identify the kinds of information involved. You don't need to paste in a contract or share someone's private details. Finally, review the summary and create the record. That's the starting point: a named tool, a clear purpose, and a record your team can work on together. Adding the record doesn't automatically approve the tool. It gives you a practical place to complete the review.

00:02:21 — Separate an answer from its proof

Now let's look at an existing tool that needs attention. Briard asks one question at a time, and it gives you a useful option when you don't have the answer yet. You can say you're not sure. That keeps uncertainty visible, so the next person doesn't mistake a guess for a confirmed fact. This sample asks whether we have proof for an answer. An answer and its supporting evidence are different things. The Add proof page is where an authorized person can provide the supporting file or reference in their own workspace. Uploads are disabled in this public sample. For your daily work, the idea is simple: record what you know, identify what needs checking, and keep the supporting material with the right tool.

00:03:08 — Let approved discovery help with the list

You can also reduce some of the manual work. Under More, open Connect work tools. Briard guides you through choosing a supported source, such as Microsoft 365. The connection page explains what it can see and what it never collects. This discovery step looks for approved information about tools and usage; it doesn't read employees' messages, files, or prompts. If you aren't the administrator, there's a clear way to ask your IT person for help. Here, we'll use the explicitly labeled sample consent. The demonstration finds likely AI services and separates a new record from existing matches. In your organization, an authorized administrator must approve the real connection. You then review what was found and add anything discovery couldn't see.

00:04:01 — See what needs your attention

Once the records are in place, What needs me helps you decide where to spend your time. Choose the part of the organization you're reviewing, then read the next action and its explanation. You don't have to work through every detail on every visit. Start with the item that needs a person, follow the button, and bring back the answer or evidence that's missing. This is especially helpful when you're new to the platform: the next step is connected to the record it belongs to. Briard helps organize the follow-through, while your team stays responsible for the decisions.

00:04:40 — Build a policy people can understand

Next, let's open My AI policy. This brings policy work into the same workspace as your AI records. At the top, you can see the draft's status and the next action. Review my answers takes you through straightforward questions, such as the organization name, who owns the policy, and what information employees must not put into an AI tool. The draft is organized into sections, so you can review one topic at a time. Here are the rules for acceptable and prohibited use, followed by a short employee guide. That makes the policy easier to discuss with the people who will actually use it. You can also set a review schedule. The aim is a policy your team can maintain, rather than a document that's written once and forgotten.

00:05:30 — Keep review, approval, and sharing clear

A draft is only the beginning. Approve and publish shows who needs to review the policy before it becomes the approved version. In a signed-in workspace, you choose eligible reviewers and the required roles. This sample doesn't send approval requests. Keeping the draft and published version separate lets your team work on changes while the current approved policy remains in place. Share and track is the next stage, where the approved policy can be distributed and acknowledgments recorded. You can see who has responded without treating a response as proof that someone has learned everything. For a compliance manager, the benefit is visibility: what is being edited, what needs approval, and which version people should be using.

00:06:19 — Prepare a package for a reviewer

When someone asks for an update, open Make a review package. Start with who it's for: a customer, advisor, insurer, or your leadership team. We'll choose Leadership, select the relevant AI tool, and make the package. The new executive package appears in the recent list, with a download available. You're bringing recorded information together for a specific review, rather than starting from an empty document each time. Check the package and any open items before sharing it outside your team. A package helps organize the evidence; it doesn't turn missing proof into approval. The same habit applies whenever a colleague asks about a tool: open the current record, review what's supported, and share the appropriate information.

00:07:09 — Know where incident review begins

One quick note about alerts. Home also shows AI incident alerts, with a review priority and a link into KAIDAN. An alert means something needs checking; it isn't proof that harm occurred. KAIDAN supports the deeper incident investigation. We'll cover that in a separate walkthrough. For now, you know where to start when an alert needs attention.

00:07:36 — Find help as you go

You don't have to remember every step from this video. Learn Briard provides short guided lessons for common tasks, including adding a tool, answering questions, and preparing a package. Open a lesson when you're ready to do that work. The Help page also explains common questions and gives you a route to support. In your signed-in workspace, you can ask for help and follow your request. This sample won't send a message. If you're just getting started, keep your first session small: record one AI tool, answer the first question, and identify the person who can provide any missing proof. You can build from there as your team gets comfortable.

00:08:20 — Take your next step with Briard

That's a practical first day with Briard: see your AI tools, understand what needs attention, keep your policy current, and prepare information for the people who need to review it. You don't need to become a technical specialist to keep that work moving. Ready to begin? Visit briard dot A I and choose Start thirty days free, or sign in to your existing workspace. If you'd like help choosing your first steps, contact our team at support at briard dash A I dot app. Tell us what your team is trying to manage, and we'll help you get started. Start with one tool and one clear next action.