Assessment brief
Capture the use, boundaries, risks, owner, and evidence questions before creating the case.
Download MarkdownWorking references, planning worksheets, and answers for the next step.
Use these editable Markdown worksheets to prepare the question and hand off the evidence.
Capture the use, boundaries, risks, owner, and evidence questions before creating the case.
Download MarkdownWrite the question, source versions, requirements, criteria, and planned evidence.
Download MarkdownKeep the finding, evidence, open gaps, responsibilities, and next review together.
Download MarkdownThe names used throughout the workbench and these guides.
Read a score with its task, reference, and decision rule.
Understand the host, provider, and sharing choices behind the work.
Review diagnostic information before sending or exporting it.
Follow the first-evaluation path for hands-on testing, or the Assessment path when your question is about a system’s use, risks, and decision.
Read the guideManual work does not require one. Connect a provider when you want the assistant to help read context, prepare records, or examine results.
Read the guideA local service or explicit Team host owns Project files and execution. Assistant and prediction API requests go to the providers you configure.
Read the guideYes. Create separate cases for different objectives on the same version. Use a follow-on Assessment when product components or configuration change.
Read the guideKnotest records reviewed coverage of its selected guidance. The decision retains scope, evidence, and gaps; certification and legal judgments require their appropriate process.
Read the guideStart with the task’s recovery action and Troubleshooting. In Settings → About → Diagnostics, review a support report before sending or exporting it.
Read the guide