WEBVTT

00:00:00.900 --> 00:00:06.252
A supplier review brings several people into one decision: the project sponsor,

00:00:06.350 --> 00:00:08.715
procurement, and technical reviewers.

00:00:08.988 --> 00:00:12.978
Start by agreeing the intended workflow and information involved.

00:00:13.238 --> 00:00:16.402
Then organize the questions that each reviewer needs answered.

00:00:17.640 --> 00:00:23.255
Ask who needs access, where information is handled, how long records are retained, and

00:00:23.255 --> 00:00:25.168
what an export or exit would involve.

00:00:25.428 --> 00:00:29.580
Add your organization's accessibility and support requirements.

00:00:29.840 --> 00:00:32.968
These are questions to confirm for the proposed engagement.

00:00:34.188 --> 00:00:38.115
In the Trust Center, browse or search the document library.

00:00:38.363 --> 00:00:40.552
Check the status and update date.

00:00:40.812 --> 00:00:46.390
A published policy, an agreement available on request, and a draft under review have

00:00:46.390 --> 00:00:47.340
different purposes.

00:00:48.560 --> 00:00:54.250
If AI assistance is part of the proposed workflow, discuss the feature, information

00:00:54.250 --> 00:00:57.175
involved, and provider arrangement before activation.

00:00:57.435 --> 00:01:00.288
Confirm who reviews generated suggestions.

00:01:00.548 --> 00:01:05.875
Keep those questions separate from deterministic calculations and authorized decisions.

00:01:07.080 --> 00:01:08.870
Bring your questionnaire to the team.

00:01:09.168 --> 00:01:15.220
For each open item, record the requested evidence, responsible person, and agreed

00:01:15.220 --> 00:01:15.920
disposition.

00:01:16.180 --> 00:01:21.182
Confirm the applicable signed agreements and requirements with your reviewers before

00:01:21.182 --> 00:01:22.532
sharing project information.

00:01:23.760 --> 00:01:26.050
The goal is a review that everyone can follow.

00:01:26.310 --> 00:01:31.762
Use the Trust Center to prepare, bring your organization specific questions, and agree

00:01:31.762 --> 00:01:32.575
the next steps.

00:01:32.860 --> 00:01:37.188
Public information supports that conversation; it does not replace your team's

00:01:37.188 --> 00:01:38.388
acceptance process.