Repository: validmind/documentation
Pull request #687: User guide updates for attestation
Author: login: nrichers
Labels: name: documentation
description: Improvements or additions to documentation
name: highlight
description: Feature to be curated in the release notes
Created: 2025-04-07T14:37:04Z | Merged: 2025-04-11T00:25:18Z

## Internal Notes for Reviewers

This PR includes:

- A new "Attestation" section in our user guide with topics for:
   - "Working with attestations" — overview topic 
   - "Set up attestations" — for admins
   - "Complete attestation questionnaires" — for model owners
   - "Review attestation questionnaires" — for validators
- New attestation glossary entries
- Minimal CSS to style mermaid diagrams
- Some "Guides" cleanup to remove extraneous navigation

[**LIVE PREVIEW**](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/guide/attestation/working-with-attestations.html)

![Capto_ 2025-04-07_07-40-33_am](https://github.com/user-attachments/assets/fc92a023-a488-4321-890b-e98c56a071e9)

<!--
PR instructions for release notes:

1. Pick at least one label:

- `internal` (skip Step 2, no release notes required)
- `highlight`
- `enhancement`
- `breaking-change`
- `deprecation`
- `bug`
- `documentation`

2. In the next section, describe the changes so that an external user can understand them. Keep it simple and link to the docs with [Learn more ...](<relative-link>), if available.
-->

## External Release Notes

Model attestation is now available.

Attestation allows model owners and validators to formally review and certify key details about a model at a specific point in time. This helps support internal governance and compliance with external requirements. Progress for the attestation process is tracked through clear status updates and role-specific tasks. 

[Working with attestations](/guide/attestation/working-with-attestations.qmd)


Diff:
diff --git a/site/_quarto.yml b/site/_quarto.yml
index 315500556b..b884dbb182 100644
--- a/site/_quarto.yml
+++ b/site/_quarto.yml
@@ -325,6 +325,13 @@ website:
           - guide/monitoring/review-monitoring-results.qmd
           - text: "Metrics over time"
             file: guide/monitoring/work-with-metrics-over-time.qmd
+        - text: "---"
+        - text: "Attestation"
+        - file: guide/attestation/working-with-attestations.qmd
+          contents:
+          - guide/attestation/set-up-attestations.qmd
+          - guide/attestation/complete-attestation-questionnaires.qmd
+          - guide/attestation/review-attestation-questionnaires.qmd
 
     - title: "Support"
       contents:
diff --git a/site/about/fine-print/data-privacy-policy.qmd b/site/about/fine-print/data-privacy-policy.qmd
index 0c357ebcec..ae5a3d0d2d 100644
--- a/site/about/fine-print/data-privacy-policy.qmd
+++ b/site/about/fine-print/data-privacy-policy.qmd
@@ -45,7 +45,7 @@ Access is available through AWS PrivateLink, Azure Private Link, or GCP Private
 
 When you generate documentation or run tests, {{< var vm.product >}} imports the following artifacts into the documentation via our {{< var validmind.api >}} endpoint integration:
 
-![Artifacts imported into the docuemntation via our {{< var vm.api >}}](overview-api-integration.jpg){width=80% fig-alt="A representation of artifacts imported into the documentation via our Python API"}
+![Artifacts imported into the documentation via our {{< var vm.api >}}](overview-api-integration.jpg){width=80% fig-alt="A representation of artifacts imported into the documentation via our Python API"}
 
 - Metadata about datasets and models, used to look up programmatic documentation content, such as the stored definition for _common logistic regression limitations_ when a logistic regression model has been passed to the {{< var vm.product >}} test suite to be run.
 - Quality and performance metrics collected from datasets and models.
diff --git a/site/about/glossary/_attestation.qmd b/site/about/glossary/_attestation.qmd
new file mode 100644
index 0000000000..52c1866985
--- /dev/null
+++ b/site/about/glossary/_attestation.qmd
@@ -0,0 +1,17 @@
+attestation 
+: A formal process where model owners certify key model information at a specific time. Reviewed by the second line of defense, typically a validator, attestation is part of your audit trail and confirms that governance, documentation, and control requirements are met.
+
+attestation instance
+: The invocation of the attestation process on the {{< var validmind.platform >}}. Created when the attestation is triggered by the schedule you set up, it includes a snapshot with model activity and findings, questionnaire responses and review status, forming a full record of the review and approval process. 
+
+attestation period  
+: The time window during which attestation is active, with fixed start and end dates. Each period creates an unchanging model snapshot. Periods are usually scheduled quarterly or annually and can align with regulatory or internal cycles.
+
+attestation questionnaire  
+: A structured form that model owners use to confirm model status, documentation and compliance. It supports formatted inputs like checkboxes and text fields, serving as both a compliance check and formal review record.
+
+execution schedule  
+: The mechanism, manual or automated, that starts the attestation process based on set periods. It creates attestation instances, triggers snapshots and begins the workflow for model owners and validators.
+
+snapshot  
+: A fixed capture of model data at a specific time. It includes optional custom fields and related findings and stays unchanged throughout the attestation, ensuring historical accuracy.
\ No newline at end of file
diff --git a/site/about/glossary/glossary.qmd b/site/about/glossary/glossary.qmd
index e51f787313..2ecac3b0ef 100644
--- a/site/about/glossary/glossary.qmd
+++ b/site/about/glossary/glossary.qmd
@@ -16,6 +16,7 @@ This glossary of terms provides short definitions for technical terms you find c
 - [Model documentation](#model-documentation)
 - [Validation reports](#validation-reports)
 - [Ongoing monitoring](#ongoing-monitoring)
+- [Attestations](#attestations)
 - [Developer tools](#developer-tools)
 - [Artificial intelligence](#artificial-intelligence)
 
@@ -41,6 +42,10 @@ This glossary of terms provides short definitions for technical terms you find c
 
 {{< include _monitoring.qmd >}}
 
+## Attestations
+
+{{< include _attestation.qmd >}}
+
 ## Developer tools
 
 {{< include _developer-tools.qmd >}}
diff --git a/site/guide/attestation/attestation-banner.png b/site/guide/attestation/attestation-banner.png
new file mode 100644
index 0000000000..b4991ce445
Binary files /dev/null and b/site/guide/attestation/attestation-banner.png differ
diff --git a/site/guide/attestation/complete-attestation-questionnaires.qmd b/site/guide/attestation/complete-attestation-questionnaires.qmd
new file mode 100644
index 0000000000..a8872a87dc
--- /dev/null
+++ b/site/guide/attestation/complete-attestation-questionnaires.qmd
@@ -0,0 +1,75 @@
+---
+title: "Complete attestation questionnaires"
+date: last-modified
+---
+
+Certify the accuracy of key model information at a point in time by completing the attestation questionnaire.
+
+As a model owner, this process is part of the audit trail for your model's information, supporting accountability across its lifecycle. Attestation typically includes details about ownership, usage, performance, controls, and documentation.
+ 
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Not Started]{.bubble} state.
+- [x] You are a model owner.[^3]
+
+:::
+
+## Steps
+
+When prompted on your dashboard:
+
+::: {.column-margin .mt6}
+![Start attestation](start-attestation.png){fig-alt="Prompt to start the attestation process with a button labelled 'Open Attestations'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. In the right sidebar:
+
+   - If shown, click an attestation instance in the [**{{< fa clipboard-check >}} Not Started**]{.bubble} state.
+   - Click **Start Attestation**.
+
+3. Document the status change to [**{{< fa clipboard-check >}} In Progress**]{.bubble} in the [**notes**]{.small-caps} field and click **Confirm**.
+
+   After you confirm the status change to [**{{< fa clipboard-check >}} In Progress**]{.bubble}, the attestation questionnaire is ready to be completed in the right sidebar.
+
+4. Complete the attestation questionnaire, including:
+
+   - Checking all applicable boxes
+   - Answering each question 
+   - Adding relevant comments
+
+   ::: {.callout}
+   Refer to the model snapshot to ensure the attestation questionnaire is accurate:
+
+   - **{{< fa cubes >}} Inventory** — Shows model information and recent activity such as comments, status changes, updates and test results.
+   - **{{< fa triangle-exclamation >}} Findings** — Shows model findings with details like title, severity, status, and due date.
+   :::
+
+5. Verify that your answers are complete and click **Submit for Review**.
+
+6. Document the status change in the [**notes**]{.small-caps} field for your reviewer and click **Confirm**.
+
+After you confirm the status change, the attestation questionnaire is sent to your reviewer to be completed, typically someone with the [{{< fa circle-check >}} Validator]{.bubble} role or another role with sufficient permissions.
+
+If your reviewer rejects your attestation questionnaire, you will need to revise your responses and resubmit for review. The platform maintains a history of all status changes and notes.
+
+<!-- FOOTNOTES -->
+
+[^1]: [Register models in the inventory](/guide/model-inventory/register-models-in-inventory.qmd)
+
+[^2]: [Set up attestations](/guide/attestation/set-up-attestations.qmd)
+
+[^3]: [Manage permissions](/guide/configuration/manage-permissions.qmd) 
\ No newline at end of file
diff --git a/site/guide/attestation/edit-questionnaire-template.gif b/site/guide/attestation/edit-questionnaire-template.gif
new file mode 100644
index 0000000000..e74bababd5
Binary files /dev/null and b/site/guide/attestation/edit-questionnaire-template.gif differ
diff --git a/site/guide/attestation/review-attestation-questionnaires.qmd b/site/guide/attestation/review-attestation-questionnaires.qmd
new file mode 100644
index 0000000000..896ec2f090
--- /dev/null
+++ b/site/guide/attestation/review-attestation-questionnaires.qmd
@@ -0,0 +1,118 @@
+---
+title: "Review attestation questionnaires"
+date: last-modified
+---
+
+Review and sign off on attestation questionnaires to verify the accuracy of key model information at a point in time.
+
+As a validator, you assess the model owner's attestation, including ownership, usage, performance, controls, and documentation. You can provide feedback, request changes, and formally sign off to support a traceable and accountable audit trail.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Ready For Review]{.bubble} state.[^3]
+- [x] You are a [{{< fa circle-check >}} Validator]{.bubble} or assigned another role with sufficient permissions.[^4]
+
+:::
+
+## Review attestation questionnaires
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state, to be completed by a person who holds [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps 
+
+When prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation review](review-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Accept'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. If shown in the right sidebar, click an attestation instance in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state.
+
+   The attestation questionnaire is now ready to be reviewed in the right sidebar.
+
+3. Optional: Click **{{< fa signal-stream >}} See Activity** to review:
+
+   - Who completed the different status changes for the attestation.
+   - When the attestation status changed.
+   - Notes that were provided to document the process.
+
+      If you previously rejected an attestation questionnaire, review the model owner’s response on resubmission. 
+
+4. Review the attestation questionnaire:
+
+   - Check all applicable boxes have been checked.
+   - Check the answers to each question.
+   - Check the comments for accuracy and relevance.
+
+   ::: {.callout}
+   Refer to the model snapshot to ensure the attestation questionnaire is accurate:
+
+   - **{{< fa cubes >}} Inventory** — Shows model information and recent activity such as comments, status changes, updates and test results.
+   - **{{< fa triangle-exclamation >}} Findings** — Shows model findings with details like title, severity, status, and due date.
+   :::
+
+5. Accept or reject the attestation questionnaire:
+
+   - Click **Accept** to record the status change to [**{{< fa clipboard-check >}} Reviewed**]{.bubble} in the [**notes**]{.small-caps} field, then click **Confirm**.
+   - Click **Reject** to record the status change back to [**{{< fa clipboard-check >}} In progress**]{.bubble} in the [**notes**]{.small-caps} field, detail the requested changes, then click **Confirm**.
+
+      If you reject an attestation questionnaire, the model owner is prompted to revise the questionnaire and resubmit it. The platform maintains a history of all status changes and notes.
+
+6. If you approved: [Sign off on the attestation](#sign-off-attestations).
+
+
+## Sign off attestations
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Reviewed**]{.bubble} state, to be completed by a person who holds the [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps
+
+Following your [review of an attestation questionnaire](#review-attestation-questionnaires) or when prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation sign-off](sign-off-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Sign Off'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**.
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. In the right sidebar:
+
+   - If shown, click an attestation instance in the [**{{< fa clipboard-check >}} Reviewed**]{.bubble} state.
+   - Click **Sign Off**.
+
+4. Document the status change to [**{{< fa clipboard-check >}} Signed Off**]{.bubble} in the [**notes**]{.small-caps} field and click **Confirm**.
+
+After you sign off, the attestation is recorded in the model’s history. Attestation sign-offs are permanent and cannot be changed.
+
+<!-- FOOTNOTES -->
+
+[^1]: [Register models in the inventory](/guide/model-inventory/register-models-in-inventory.qmd)
+
+[^2]: [Set up attestations](/guide/attestation/set-up-attestations.qmd)
+
+[^3]: [Complete attestation questionnaires](/guide/attestation/complete-attestation-questionnaires.qmd)
+
+[^4]: [Manage permissions](/guide/configuration/manage-permissions.qmd) 
\ No newline at end of file
diff --git a/site/guide/attestation/review-attestation.png b/site/guide/attestation/review-attestation.png
new file mode 100644
index 0000000000..0b75fecae0
Binary files /dev/null and b/site/guide/attestation/review-attestation.png differ
diff --git a/site/guide/attestation/set-up-attestations.qmd b/site/guide/attestation/set-up-attestations.qmd
new file mode 100644
index 0000000000..ae484a477e
--- /dev/null
+++ b/site/guide/attestation/set-up-attestations.qmd
@@ -0,0 +1,197 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings**.
+
+2. Under Workspace Settings, select **{{< fa clipboard-check >}} Attestations**.
+
+3. Click **{{< fa plus >}} Add New Attestation**.
+
+4. Enter a name for the attestation.
+
+5. Enter a description.
+
+6. Click **Add Attestation**.
+
+7. [Configure the attestation](#configure-attestations).
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. In the left sidebar, click **{{< fa gear >}} Settings**.
+
+2. Under Workspace Settings, select **{{< fa clipboard-check >}} Attestations** and then click an attestation to configure.
+
+3. Click **{{< fa plus >}} Add Attestation Period**.
+
+4. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+5. Set the start date for the attestation period.
+
+6. Set the end date when the attestation period ends.
+
+7. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
+
+### Add attestation fields
+
+By default, attestations include the model name. Add additional model inventory fields as needed:
+
+1. In the left sidebar, click **{{< fa gear >}} Settings**.
+
+2. Under Workspace Settings, select **{{< fa clipboard-check >}} Attestations** and then click an attestation to configure.
+
+3. Under **Relevant Attestation Fields**, drag model inventory fields between columns:
+
+   - **Model Inventory Fields** — Available fields from the model inventory
+   - **Relevant Attestation Fields** — Selected fields to display in model snapshots
+
+3. Optional: Reorder the fields to change how they display in the attestation.
+
+### Edit questionnaire templates
+
+Attestation questionnaires should confirm that key controls, governance processes, and documentation requirements have been followed. 
+
+::: {.column-margin .callout}
+
+### Tip
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+___ 
+
+[How do I create meaningful attestation questionnaires?](/guide/attestation/working-with-attestations.qmd#how-do-i-create-meaningful-attestation-questionnaires)
+:::
+
+1. In the left sidebar, click **{{< fa gear >}} Settings**.
+
+2. Under Workspace Settings, select **{{< fa clipboard-check >}} Attestations** and then click the attestation you want to configure.
+
+3. Under **Questionnaire Template**, click the template area to edit. You can add rich text fields such as:
+
+   - Instructions 
+   - Links to guidelines
+   - Checkboxes
+   - Lists 
+   - Other custom elements
+
+   ![A screenshot of the questionnaire template editor](edit-questionnaire-template.gif){width=100% fig-alt="An animation of the questionnaire template editor showing the process of adding a question about documentation of compliance to the template with the instructions to confirm that required documentation, such as model documentation, validation reports, and change logs, has been completed." .screenshot}
+
+4. After you complete your edits, click **Save**.
+
+The attestation questionnaire is now ready to be be used in future attestation instances, to be completed by model owners and reviewed and signed off by validators.
+
+## Test attestation schedules
+
+::: {.callout-important title="Not normally required"}
+These steps are optional and not required to set up attestation — **perform only under the direction of ValidMind**.
+:::
+
+For testing purposes only, you can trigger the attestation process: 
+
+1. In the left sidebar, click **{{< fa gear >}} Settings**.
+
+2. Under Workspace Settings, select **{{< fa clipboard-check >}} Attestations** and then click the attestation to test.
+
+3. Under **Scheduling**, hover over an attestation period.
+
+4. When **{{< fa ellipsis-vertical >}}** appears, select **{{< fa play >}} Execute Schedule**.
+
+5. Click **Confirm**.
+
+After executing the schedule, the dashboard of the model owner displays a banner notification that the attestation is ready to be completed.
+
+## Edit attestation periods
+
+1. In the left sidebar, click **{{< fa gear >}} Settings**.
+
+2. Under Workspace Settings, select **{{< fa clipboard-check >}} Attestations** and then click the attestation period to edit.
+
+3. Under **Scheduling**, hover over an attestation period.
+
+4. When **{{< fa ellipsis-vertical >}}** appears, select **{{< fa pencil >}} Edit**.
+
+5. Make changes to one of the following:
+
+   - Name
+   - Start date
+   - End date
+
+6. Click **Save Period**.
+
+Edits to an attestation period will be effective for future occurrences but do not affect previous or in-progress attestation periods.
+
+## Remove attestation periods
+
+1. In the left sidebar, click **{{< fa gear >}} Settings**.
+
+2. Under Workspace Settings, select **{{< fa clipboard-check >}} Attestations** and then click the attestation to remove.
+
+3. Under **Scheduling**, hover over an attestation period.
+
+4. When **{{< fa ellipsis-vertical >}}** appears, select [**{{< fa trash >}} Remove**]{.red}.
+
+5. Click **Delete** to confirm the removal.
+
+<!-- TO DO Confirm with Steven that this is correct -->
+::: {.callout-important title="Removing an attestation period is permanent"}
+This action cannot be undone and prevents the attestation period from being triggered in the future. The history of previous attestation periods is unaffected by this action.
+:::
+
+<!-- FOOTNOTES -->
+
+[^1]: [Register models in the inventory](/guide/model-inventory/register-models-in-inventory.qmd)
+
+[^2]: [Manage permissions](/guide/configuration/manage-permissions.qmd)
diff --git a/site/guide/attestation/sign-off-attestation.png b/site/guide/attestation/sign-off-attestation.png
new file mode 100644
index 0000000000..aa7cf3fbfd
Binary files /dev/null and b/site/guide/attestation/sign-off-attestation.png differ
diff --git a/site/guide/attestation/start-attestation.png b/site/guide/attestation/start-attestation.png
new file mode 100644
index 0000000000..6e1107f85d
Binary files /dev/null and b/site/guide/attestation/start-attestation.png differ
diff --git a/site/guide/attestation/working-with-attestations.qmd b/site/guide/attestation/working-with-attestations.qmd
new file mode 100644
index 0000000000..121d3d7c98
--- /dev/null
+++ b/site/guide/attestation/working-with-attestations.qmd
@@ -0,0 +1,107 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.platform >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+Responsibilities for the attestation process are shared:
+
+::: {.tc}
+```{mermaid}
+graph LR
+    subgraph Model Owner
+        A["**Not Started**"] --> B["**In Progress**"]
+        B --> C["**Ready for Review**"]
+    end
+    
+    subgraph Validator
+        C --> D["**Reviewed**"]
+        D --> E["**Signed Off**"]
+        D -.-> B
+    end
+```
+
+[The attestation process — Model owner and validator responsibilities]{.silver .small}
+:::
+
+::: {.column-margin .callout title="Attestation is collaborative"}
+A validator can request changes from the model owner by rejecting the attestation questionnaire. 
+
+___
+
+The platform maintains a history of all status changes and notes.
+:::
+
+The model owner is responsible for completing the questionnaire and addressing change requests from their reviewer. In turn, the validator is responsible for reviewing the questionnaire, requesting any necessary changes, and signing off.
+
+Plan your attestation periods ahead of time to ensure they can be completed on time. The start date must be today or a future date, and you cannot set a date in the past to trigger attestation retroactively.
+
+## How do I create meaningful attestation questionnaires?
+
+Attestation questionnaires are typically used in model risk management to confirm that key controls, governance processes and documentation requirements have been followed throughout a model's lifecycle. These questionnaires are part of a broader effort to ensure accountability and regulatory compliance. 
+
+Areas typically covered in the questionnaire:
+
+- **Verification of responsibilities** — Attests that model owners, developers and validators have performed their roles in accordance with internal policies and procedures.
+
+- **Documentation of compliance** — Confirms that required documentation — such as model documentation, validation reports and change logs — has been completed and properly archived.
+
+- **Evidence of control operation** — Serves as formal evidence that key controls (for example: backtesting, performance monitoring, version control) are in place and functioning as intended.
+
+- **Governance checkpoints** — Used as checkpoints at critical stages, such as model approval, annual reviews or retirement, to ensure all required steps have been completed before proceeding.
+
+- **Regulatory reporting** — In regulated environments, provides a documented trail that can be reviewed during internal audits or by external regulators.
+
+- **Risk ownership and accountability** — By signing off on questionnaires, individuals acknowledge their responsibilities and support a strong control culture.
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+## What's next
+
+::: {#attestation-listing}
+:::
+
+<!-- FOOTNOTES -->
+
+[^1]: [Register models in the inventory](/guide/model-inventory/register-models-in-inventory.qmd)
+
+[^2]: [Working with model findings](/guide/model-validation/working-with-model-findings.qmd)
+
+[^3]: [Manage permissions](/guide/configuration/manage-permissions.qmd) 
\ No newline at end of file
diff --git a/site/guide/guides.qmd b/site/guide/guides.qmd
index c497735145..6b1286829b 100644
--- a/site/guide/guides.qmd
+++ b/site/guide/guides.qmd
@@ -83,16 +83,16 @@ listing:
     max-description-length: 250
     sort: false
     fields: [title, description]
+  - id: guides-attestation
+    contents:
+    - attestation/working-with-attestations.qmd
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
 ---
 
-Our guides offer step-by-step instructions for frequent tasks you perform within the {{< var validmind.platform >}}, organized by category:
-
-- [Onboarding](#onboarding)
-- [Model workflows](#model-workflows)
-- [Model inventory](#model-inventory)
-- [Model documentation](#model-documentation)
-- [Model validation](#model-validation)
-- [Monitoring](#monitoring)
+Our guides offer step-by-step instructions for frequent tasks you perform within the {{< var validmind.platform >}}, organized by category.
 
 ::: {.callout-important collapse="true" appearance="minimal"}
 ## {{< fa building-columns >}} Key {{< var vm.product >}} concepts
@@ -152,6 +152,7 @@ Set up validation guidelines and prepare validation reports, work with findings
 :::{#guides-model-validation}
 :::
 
+### Reporting
 
 Review reports or export your documentation for external records:
 
@@ -164,3 +165,10 @@ Regularly evaluate the ongoing accuracy, robustness, and stability of a model af
 
 :::{#guides-monitoring}
 :::
+
+## Attestation
+
+Document and certify model attributes at specific points in time, supporting compliance and governance processes:
+
+:::{#guides-attestation}
+:::
diff --git a/site/theme.scss b/site/theme.scss
index 6bf87cdf7a..8b0da24f2e 100644
--- a/site/theme.scss
+++ b/site/theme.scss
@@ -12,14 +12,52 @@ $sidebar-hl: #de257e;
 
 $toc-active-border: #de257e;
 
-$mermaid-fg-color: de257e;
-$mermaid-edge-color: #373a3c;
-$mermaid-node-bg-color: #f7e4ee;
-$mermaid-node-fg-color: #373a3c;
-$mermaid-fg-color--lighter: lighten($body-color, 30%);
-$mermaid-fg-color--lightest: lighten($body-color, 40%);
-$mermaid-label-bg-color: #f7e4ee;
-$mermaid-label-fg-color: #373a3c;
+// Mermaid theme variables
+$mermaid-node-bg-color: #FAFBFB;
+$mermaid-node-fg-color: #083E44;
+$mermaid-edge-color: #083E44;
+$mermaid-fg-color: #36454F;
+$mermaid-fg-color--lighter: #083E44;
+$mermaid-fg-color--lightest: #FAFBFB;
+$mermaid-label-bg-color: #FAFBFB;
+$mermaid-label-fg-color: #36454F;
+
+:root {
+  --mermaid-node-radius: 5px;
+}
+
+/* Target all Mermaid diagram nodes */
+.node rect {
+  rx: var(--mermaid-node-radius) !important;
+  ry: var(--mermaid-node-radius) !important;
+}
+
+/* Additional selectors to ensure all node types are covered */
+.node .basic.label-container {
+  rx: var(--mermaid-node-radius) !important;
+  ry: var(--mermaid-node-radius) !important;
+}
+
+/* Target cluster rectangles */
+.cluster rect {
+  rx: var(--mermaid-node-radius) !important;
+  ry: var(--mermaid-node-radius) !important;
+}
+
+/* Target all rectangles in Mermaid diagrams */
+#mermaid-1 rect, 
+#mermaid-2 rect, 
+#mermaid-3 rect, 
+#mermaid-4 rect, 
+#mermaid-5 rect, 
+#mermaid-6 rect, 
+#mermaid-7 rect, 
+#mermaid-8 rect, 
+#mermaid-9 rect, 
+#mermaid-10 rect {
+  rx: var(--mermaid-node-radius) !important;
+  ry: var(--mermaid-node-radius) !important;
+}
 
 .termsfeed-com---palette-light .cc-nb-okagree,
 .termsfeed-com---palette-light .cc-nb-reject,


Reviews:
user: login: validbeck
body: Overall very solid foundation! I tested out some of the instructions and have some comments about clarity/cleaning up styling. I wasn't able to fully test the "execute" and "review" situations since my development platform doesn't seem to be behaving...
state: CHANGES_REQUESTED
author_association: COLLABORATOR
submitted_at: 2025-04-08T22:49:26Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-09T16:57:44Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-09T16:59:52Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-09T17:02:58Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-09T17:03:39Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-09T17:12:28Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-09T17:18:50Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-09T17:29:57Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-09T17:30:33Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-09T17:44:55Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-09T17:50:20Z
user: login: validbeck
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T20:07:08Z
user: login: validbeck
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T20:08:22Z
user: login: validbeck
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T20:08:46Z
user: login: validbeck
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T20:09:33Z
user: login: validbeck
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T20:10:00Z
user: login: validbeck
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T20:11:19Z
user: login: validbeck
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T20:11:28Z
user: login: validbeck
body: There were a bunch of missed comments (probably because they were hidden by GH), but I resovled the ones that were dealt with!
state: CHANGES_REQUESTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T20:12:27Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T22:25:45Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T22:34:58Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T22:46:57Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T22:52:11Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T22:58:15Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T23:04:48Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T23:14:56Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T23:16:32Z
user: login: validbeck
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T23:36:23Z
user: login: validbeck
body: I'll approve this as it looks much better (thank you for making all the changes!). But one more request, as I think the hover is an important step that is missed here:

https://github.com/validmind/documentation/pull/687#discussion_r2034127265
state: APPROVED
author_association: COLLABORATOR
submitted_at: 2025-04-10T23:38:14Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-10T23:42:10Z
user: login: nrichers
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-11T00:01:51Z

Review comments:
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
path: site/guide/attestation/working-with-attestations.qmd
user: login: validbeck
body: In other parts of the site where we are defining glossary terms and NOT the UI, we do not capitalise the term so let's keep that convention here.

Refer to: [Glossary](https://docs.validmind.ai/about/glossary/glossary.html), [Working with model findings — Key concepts](https://docs.validmind.ai/guide/model-validation/working-with-model-findings.html)
created_at: 2025-04-08T22:20:21Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+The process tracks progress from questionnaire assignment to final sign-off. Responsibilities are shared — the model owner completes the questionnaire and the validator reviews, requests changes if needed, and signs off:
+
+::: {.tc}
path: site/guide/attestation/working-with-attestations.qmd
user: login: validbeck
body: Ohhhhh this light CSS is nice! I infer it automatically applies to other places that have Mermaid charts? 
created_at: 2025-04-08T22:22:08Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
path: site/guide/attestation/working-with-attestations.qmd
user: login: validbeck
body: Pretty sure this should just be the "ValidMind Platform" variable and NOT the full "AI risk platform" variable as all of the attestation work is tracked in the platform and none of it is accessible via the library.
created_at: 2025-04-08T22:25:09Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
path: site/guide/attestation/working-with-attestations.qmd
user: login: validbeck
body: ```suggestion
Attestation on the {{< var validmind.platform >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
```
created_at: 2025-04-08T22:25:17Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+The process tracks progress from questionnaire assignment to final sign-off. Responsibilities are shared — the model owner completes the questionnaire and the validator reviews, requests changes if needed, and signs off:
+
+::: {.tc}
+```{mermaid}
+graph LR
+    subgraph Model Owner
+        A["**Not Started**"] --> B["**In Progress**"]
+        B --> C["**Ready for Review**"]
+    end
+    
+    subgraph Validator
+        C --> D["**Reviewed**"]
+        D --> E["**Signed Off**"]
+        D -.-> B
+    end
+```
+
+[The attestation process — Model owner and validator responsibilities]{.silver .small}
+:::
+
+::: {.column-margin .callout title="Attestation is collaborative"}
+A validator can request changes from the model owner by rejecting the attestation questionnaire. 
+
+___
+
+The platform maintains a history of all status changes and notes.
+:::
+
+**Model owners** are responsible for moving the questionnaire through these states:
path: site/guide/attestation/working-with-attestations.qmd
user: login: validbeck
body: Let's use the role bubbles here as well I think, to keep things consistent on the page — there's also a lot of bolding here that could be broken up.
created_at: 2025-04-08T22:26:13Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+The process tracks progress from questionnaire assignment to final sign-off. Responsibilities are shared — the model owner completes the questionnaire and the validator reviews, requests changes if needed, and signs off:
+
+::: {.tc}
+```{mermaid}
+graph LR
+    subgraph Model Owner
+        A["**Not Started**"] --> B["**In Progress**"]
+        B --> C["**Ready for Review**"]
+    end
+    
+    subgraph Validator
+        C --> D["**Reviewed**"]
+        D --> E["**Signed Off**"]
+        D -.-> B
+    end
+```
+
+[The attestation process — Model owner and validator responsibilities]{.silver .small}
+:::
+
+::: {.column-margin .callout title="Attestation is collaborative"}
+A validator can request changes from the model owner by rejecting the attestation questionnaire. 
+
+___
+
+The platform maintains a history of all status changes and notes.
+:::
+
+**Model owners** are responsible for moving the questionnaire through these states:
+
+- **Not Started** — When attestation is first assigned to the model owner
+- **In Progress** — While the model owner completes the questionnaire or addresses change requests
+- **Ready for Review** — When the model owner has submitted the completed questionnaire
+
+**Validators** are responsible for moving the questionnaire through these states:
+
+- **Reviewed** — When a validator has reviewed the questionnaire
+- **Signed Off** — Final state after a validator has signed off
+
+## How do I create meaningful attestation questionnaires?
+
+Attestation questionnaires are typically used in model risk management to confirm that key controls, governance processes and documentation requirements have been followed throughout a model's lifecycle. These questionnaires are part of a broader effort to ensure accountability and regulatory compliance. 
+
+Areas typically covered in the questionnaire:
+
+- **Verification of responsibilities** — Attests that model owners, developers and validators have performed their roles in accordance with internal policies and procedures.
+
+- **Documentation of compliance** — Confirms that required documentation — such as model documentation, validation reports and change logs — has been completed and properly archived.
+
+- **Evidence of control operation** — Serves as formal evidence that key controls (e.g. backtesting, performance monitoring, version control) are in place and functioning as intended.
path: site/guide/attestation/working-with-attestations.qmd
user: login: validbeck
body: A very smart human (I believe his name was NIk...) once told me that latin initialisms were opaque, and we should instead use the more accessible common name instead. ;)
created_at: 2025-04-08T22:27:49Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+The process tracks progress from questionnaire assignment to final sign-off. Responsibilities are shared — the model owner completes the questionnaire and the validator reviews, requests changes if needed, and signs off:
+
+::: {.tc}
+```{mermaid}
+graph LR
+    subgraph Model Owner
+        A["**Not Started**"] --> B["**In Progress**"]
+        B --> C["**Ready for Review**"]
+    end
+    
+    subgraph Validator
+        C --> D["**Reviewed**"]
+        D --> E["**Signed Off**"]
+        D -.-> B
+    end
+```
+
+[The attestation process — Model owner and validator responsibilities]{.silver .small}
+:::
+
+::: {.column-margin .callout title="Attestation is collaborative"}
+A validator can request changes from the model owner by rejecting the attestation questionnaire. 
+
+___
+
+The platform maintains a history of all status changes and notes.
+:::
+
+**Model owners** are responsible for moving the questionnaire through these states:
+
+- **Not Started** — When attestation is first assigned to the model owner
+- **In Progress** — While the model owner completes the questionnaire or addresses change requests
+- **Ready for Review** — When the model owner has submitted the completed questionnaire
+
+**Validators** are responsible for moving the questionnaire through these states:
+
+- **Reviewed** — When a validator has reviewed the questionnaire
+- **Signed Off** — Final state after a validator has signed off
+
+## How do I create meaningful attestation questionnaires?
+
+Attestation questionnaires are typically used in model risk management to confirm that key controls, governance processes and documentation requirements have been followed throughout a model's lifecycle. These questionnaires are part of a broader effort to ensure accountability and regulatory compliance. 
+
+Areas typically covered in the questionnaire:
+
+- **Verification of responsibilities** — Attests that model owners, developers and validators have performed their roles in accordance with internal policies and procedures.
+
+- **Documentation of compliance** — Confirms that required documentation — such as model documentation, validation reports and change logs — has been completed and properly archived.
+
+- **Evidence of control operation** — Serves as formal evidence that key controls (e.g. backtesting, performance monitoring, version control) are in place and functioning as intended.
path: site/guide/attestation/working-with-attestations.qmd
user: login: validbeck
body: ```suggestion
- **Evidence of control operation** — Serves as formal evidence that key controls (for example: backtesting, performance monitoring, version control) are in place and functioning as intended.
```
created_at: 2025-04-08T22:27:58Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: GLOBAL COMMENT: Settings has more than one section to navigate to, and finding the correct settings page after landing on Settings should be a separate step for clarity. Here is the convention we have been following for Settings pages, directing users to the section first:

`Under {section}, select {option}.`

Example: 

<img width="922" alt="Screenshot 2025-04-08 at 3 30 17 PM" src="https://github.com/user-attachments/assets/40336080-7d3e-4bb1-a634-9907722f0f4c" />

created_at: 2025-04-08T22:31:07Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: A callout is a bit busy here, and not necessary. For the complex workflow docs I simply added the step at the very end that was just `0. Configure the workflow.` that was a direct link to the configuration instructions — users SHOULD be taken out of context to that next section at that stage, after all. 

Example:

<img width="683" alt="Screenshot 2025-04-08 at 3 33 22 PM" src="https://github.com/user-attachments/assets/ceeb7528-fb9e-4596-b51a-a25f65b94d89" />

created_at: 2025-04-08T22:33:34Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: Here you may want to add a note that attestation periods cannot be set *retroactively* — as I'm sure some orgs will no doubt try to do that for some reason or another.
created_at: 2025-04-08T22:35:03Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
+
+### Add attestation fields
+
+By default, attestations include the model name. Add additional model inventory fields as needed:
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Under **Relevant Attestation Fields**, drag model inventory fields between columns:
+
+   - **Model Inventory Fields** — Available fields from the model inventory
+   - **Relevant Attestation Fields** — Selected fields to display in model snapshots
+
+3. Optional: Reorder the fields to change how they display in the attestation.
+
+### Edit questionnaire templates
+
+Attestation questionnaires should confirm that key controls, governance processes, and documentation requirements have been followed. 
+
+::: {.column-margin .callout}
+
+### Tip
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+___ 
+
+[How do I create meaningful attestation questionnaires?](/guide/attestation/working-with-attestations.qmd#how-do-i-create-meaningful-attestation-questionnaires)
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation you want to configure.
+
+2. Under **Questionnaire Template**, click the template area to edit. You can add rich text fields such as:
+
+   - Instructions 
+   - Links to guidelines
+   - Checkboxes
+   - Lists 
+   - Other custom elements
+
+   ![A screenshot of the questionnaire template editor](edit-questionnaire-template.gif){width=100% fig-alt="An animation of the questionnaire template editor showing the process of adding a question about documentation of compliance to the template with the instructions to confirm that required documentation, such as model documentation, validation reports, and change logs, has been completed." .screenshot}
+
+3. After you complete your edits, click **Save**.
+
+The attestation questionnaire is now ready to be be used in future attestation instances, to be completed by model owners and reviewed and signed off by validators.
+
+## Test attestation schedules
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: I followed the instructions in this section and I can't seem to trigger the dashboard message. Hm. 🤔 
created_at: 2025-04-08T22:37:15Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
+
+### Add attestation fields
+
+By default, attestations include the model name. Add additional model inventory fields as needed:
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Under **Relevant Attestation Fields**, drag model inventory fields between columns:
+
+   - **Model Inventory Fields** — Available fields from the model inventory
+   - **Relevant Attestation Fields** — Selected fields to display in model snapshots
+
+3. Optional: Reorder the fields to change how they display in the attestation.
+
+### Edit questionnaire templates
+
+Attestation questionnaires should confirm that key controls, governance processes, and documentation requirements have been followed. 
+
+::: {.column-margin .callout}
+
+### Tip
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+___ 
+
+[How do I create meaningful attestation questionnaires?](/guide/attestation/working-with-attestations.qmd#how-do-i-create-meaningful-attestation-questionnaires)
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation you want to configure.
+
+2. Under **Questionnaire Template**, click the template area to edit. You can add rich text fields such as:
+
+   - Instructions 
+   - Links to guidelines
+   - Checkboxes
+   - Lists 
+   - Other custom elements
+
+   ![A screenshot of the questionnaire template editor](edit-questionnaire-template.gif){width=100% fig-alt="An animation of the questionnaire template editor showing the process of adding a question about documentation of compliance to the template with the instructions to confirm that required documentation, such as model documentation, validation reports, and change logs, has been completed." .screenshot}
+
+3. After you complete your edits, click **Save**.
+
+The attestation questionnaire is now ready to be be used in future attestation instances, to be completed by model owners and reviewed and signed off by validators.
+
+## Test attestation schedules
+
+::: {.callout-important title="Not normally required"}
+These steps are optional and not required to set up attestation — **perform only under the direction of ValidMind**.
+:::
+
+For testing purposes only, you can trigger the attestation process: 
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to test.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Execute Schedule**.
+
+3. Click **Confirm**.
+
+After executing the schedule, the dashboard of the model owner displays a banner notification that the attestation is ready to be completed.
+
+## Edit attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation period to edit.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Edit**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: There's an additional sub-step here: You have to hover until the ellipsis appears first. Let's not assume users can find things that are invisible without interaction!
created_at: 2025-04-08T22:38:55Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
+
+### Add attestation fields
+
+By default, attestations include the model name. Add additional model inventory fields as needed:
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Under **Relevant Attestation Fields**, drag model inventory fields between columns:
+
+   - **Model Inventory Fields** — Available fields from the model inventory
+   - **Relevant Attestation Fields** — Selected fields to display in model snapshots
+
+3. Optional: Reorder the fields to change how they display in the attestation.
+
+### Edit questionnaire templates
+
+Attestation questionnaires should confirm that key controls, governance processes, and documentation requirements have been followed. 
+
+::: {.column-margin .callout}
+
+### Tip
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+___ 
+
+[How do I create meaningful attestation questionnaires?](/guide/attestation/working-with-attestations.qmd#how-do-i-create-meaningful-attestation-questionnaires)
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation you want to configure.
+
+2. Under **Questionnaire Template**, click the template area to edit. You can add rich text fields such as:
+
+   - Instructions 
+   - Links to guidelines
+   - Checkboxes
+   - Lists 
+   - Other custom elements
+
+   ![A screenshot of the questionnaire template editor](edit-questionnaire-template.gif){width=100% fig-alt="An animation of the questionnaire template editor showing the process of adding a question about documentation of compliance to the template with the instructions to confirm that required documentation, such as model documentation, validation reports, and change logs, has been completed." .screenshot}
+
+3. After you complete your edits, click **Save**.
+
+The attestation questionnaire is now ready to be be used in future attestation instances, to be completed by model owners and reviewed and signed off by validators.
+
+## Test attestation schedules
+
+::: {.callout-important title="Not normally required"}
+These steps are optional and not required to set up attestation — **perform only under the direction of ValidMind**.
+:::
+
+For testing purposes only, you can trigger the attestation process: 
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to test.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Execute Schedule**.
+
+3. Click **Confirm**.
+
+After executing the schedule, the dashboard of the model owner displays a banner notification that the attestation is ready to be completed.
+
+## Edit attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation period to edit.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Edit**.
+
+3. Make changes to one of the following:
+
+   - Name
+   - Start date
+   - End date
+
+4. Click **Save Period**.
+
+Edits to an attestation period will be effective for future occurrences but do not affect previous or in-progress attestation periods.
+
+## Remove attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to remove.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Remove**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: GLOBAL COMMENT: We have a red class to signify red UI elements to try to make the docs match the interface: 

https://github.com/validmind/documentation/blob/5a873618b108f686a6461a8e89db2f6db0c3dbf4/site/styles.css#L606

Example:

<img width="928" alt="Screenshot 2025-04-08 at 3 41 16 PM" src="https://github.com/user-attachments/assets/55aafa50-5726-41c7-8338-ecd4c1f4b7e9" />


Also, this could use the lil trash can icon!
created_at: 2025-04-08T22:42:24Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,77 @@
+---
+title: "Complete attestation questionnaires"
+date: last-modified
+---
+
+Certify the accuracy of key model information at a point in time by completing the attestation questionnaire.
+
+As a model owner, this process is part of the audit trail for your model's information, supporting accountability across its lifecycle. Attestation typically includes details about ownership, usage, performance, controls, and documentation.
+ 
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Not Started]{.bubble} state.
+- [x] You are a model owner.[^3]
+
+:::
+
+## Steps
+
+When prompted on your dashboard:
+
+::: {.column-margin .mt6}
+![Start attestation](start-attestation.png){fig-alt="Prompt to start the attestation process with a button labelled 'Open Attestations'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. In the right sidebar:
+
+   - If shown, click an attestation instance in the [**{{< fa clipboard-check >}} Not Started**]{.bubble} state.
+   - Click **Start Attestation**.
+
+3. Document the status change to [**{{< fa clipboard-check >}} In Progress**]{.bubble} in the [**notes**]{.small-caps} field and click **Confirm**.
+
+   After you confirm the status change to [**{{< fa clipboard-check >}} In Progress**]{.bubble}, the attestation questionnaire is ready to be completed in the right sidebar.
+
+4. Complete the attestation questionnaire, including:
+
+   - Checking all applicable boxes
+   - Answering each question 
+   - Adding relevant comments
+
+   ::: {.callout}
path: site/guide/attestation/complete-attestation-questionnaires.qmd
user: login: validbeck
body: Too many callouts too close together on this page — can we remove this one?
created_at: 2025-04-08T22:44:33Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,77 @@
+---
+title: "Complete attestation questionnaires"
+date: last-modified
+---
+
+Certify the accuracy of key model information at a point in time by completing the attestation questionnaire.
+
+As a model owner, this process is part of the audit trail for your model's information, supporting accountability across its lifecycle. Attestation typically includes details about ownership, usage, performance, controls, and documentation.
+ 
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Not Started]{.bubble} state.
+- [x] You are a model owner.[^3]
+
+:::
+
+## Steps
+
+When prompted on your dashboard:
+
+::: {.column-margin .mt6}
+![Start attestation](start-attestation.png){fig-alt="Prompt to start the attestation process with a button labelled 'Open Attestations'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. In the right sidebar:
+
+   - If shown, click an attestation instance in the [**{{< fa clipboard-check >}} Not Started**]{.bubble} state.
+   - Click **Start Attestation**.
+
+3. Document the status change to [**{{< fa clipboard-check >}} In Progress**]{.bubble} in the [**notes**]{.small-caps} field and click **Confirm**.
+
+   After you confirm the status change to [**{{< fa clipboard-check >}} In Progress**]{.bubble}, the attestation questionnaire is ready to be completed in the right sidebar.
+
+4. Complete the attestation questionnaire, including:
+
+   - Checking all applicable boxes
+   - Answering each question 
+   - Adding relevant comments
+
+   ::: {.callout}
+   Refer to the model snapshot to ensure the attestation questionnaire is accurate:
+
+   - **{{< fa cubes >}} Inventory** — Shows model information and recent activity such as comments, status changes, updates and test results.
+   - **{{< fa triangle-exclamation >}} Findings** — Shows model findings with details like title, severity, status, and due date.
+   :::
+
+5. Click **Submit for Review**.
path: site/guide/attestation/complete-attestation-questionnaires.qmd
user: login: validbeck
body: I think the language for this step should imply a bit more agency like we do in other places —  maybe something like "Confirm that the attestation questionnaire was saved correctly, then click ..."

I tried out these steps and honestly the UI flow is a bit confusing as to what happened, but that's not something docs can fix, but we can at least change the language to be more affirming. 
created_at: 2025-04-08T22:46:03Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,125 @@
+---
+title: "Review attestation questionnaires"
+date: last-modified
+---
+
+Review and sign off on attestation questionnaires to verify the accuracy of key model information at a point in time.
+
+As a validator, you assess the model owner's attestation, including ownership, usage, performance, controls, and documentation. You can provide feedback, request changes, and formally sign off to support a traceable and accountable audit trail.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Ready For Review]{.bubble} state.[^3]
+- [x] You are a [{{< fa circle-check >}} Validator]{.bubble} or assigned another role with sufficient permissions.[^4]
+
+:::
+
+## Review attestation questionnaires
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state, to be completed by a person who holds [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps 
+
+When prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation review](review-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Accept'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. If shown in the right sidebar, click an attestation instance in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state.
+
+   The attestation questionnaire is now ready to be reviewed in the right sidebar.
+
+3. Optional: Click **{{< fa signal-stream >}} See Activity** to review:
+   - Who completed the different status changes for the attestation.
+   - When the attestation status changed.
+   - Notes that were provided to document the process.
+
+4. Review the attestation questionnaire:
+
+   - Check all applicable boxes have been checked.
+   - Check the answers to each question.
+   - Check the comments for accuracy and relevance.
+
+   ::: {.callout}
path: site/guide/attestation/review-attestation-questionnaires.qmd
user: login: validbeck
body: Again, too many callouts on this page!! This one should go.
created_at: 2025-04-08T22:47:19Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,125 @@
+---
+title: "Review attestation questionnaires"
+date: last-modified
+---
+
+Review and sign off on attestation questionnaires to verify the accuracy of key model information at a point in time.
+
+As a validator, you assess the model owner's attestation, including ownership, usage, performance, controls, and documentation. You can provide feedback, request changes, and formally sign off to support a traceable and accountable audit trail.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Ready For Review]{.bubble} state.[^3]
+- [x] You are a [{{< fa circle-check >}} Validator]{.bubble} or assigned another role with sufficient permissions.[^4]
+
+:::
+
+## Review attestation questionnaires
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state, to be completed by a person who holds [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps 
+
+When prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation review](review-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Accept'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. If shown in the right sidebar, click an attestation instance in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state.
+
+   The attestation questionnaire is now ready to be reviewed in the right sidebar.
+
+3. Optional: Click **{{< fa signal-stream >}} See Activity** to review:
+   - Who completed the different status changes for the attestation.
+   - When the attestation status changed.
+   - Notes that were provided to document the process.
+
+4. Review the attestation questionnaire:
+
+   - Check all applicable boxes have been checked.
+   - Check the answers to each question.
+   - Check the comments for accuracy and relevance.
+
+   ::: {.callout}
+   Refer to the model snapshot to ensure the attestation questionnaire is accurate:
+
+   - **{{< fa cubes >}} Inventory** — Shows model information and recent activity such as comments, status changes, updates and test results.
+   - **{{< fa triangle-exclamation >}} Findings** — Shows model findings with details like title, severity, status, and due date.
+   :::
+
+5. Accept or reject the attestation questionnaire:
+
+   - Click **Accept** to record the status change to [**{{< fa clipboard-check >}} Reviewed**]{.bubble} in the [**notes**]{.small-caps} field, then click **Confirm**.
+
+   ::: {.callout}
+   **Next {{< fa arrow-right >}}** [Sign off on the attestation](#sign-off-attestations)
path: site/guide/attestation/review-attestation-questionnaires.qmd
user: login: validbeck
body: Same comment here, this could just be a final step linking to the subsequent instructions instead.
created_at: 2025-04-08T22:47:52Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,125 @@
+---
+title: "Review attestation questionnaires"
+date: last-modified
+---
+
+Review and sign off on attestation questionnaires to verify the accuracy of key model information at a point in time.
+
+As a validator, you assess the model owner's attestation, including ownership, usage, performance, controls, and documentation. You can provide feedback, request changes, and formally sign off to support a traceable and accountable audit trail.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Ready For Review]{.bubble} state.[^3]
+- [x] You are a [{{< fa circle-check >}} Validator]{.bubble} or assigned another role with sufficient permissions.[^4]
+
+:::
+
+## Review attestation questionnaires
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state, to be completed by a person who holds [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps 
+
+When prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation review](review-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Accept'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. If shown in the right sidebar, click an attestation instance in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state.
+
+   The attestation questionnaire is now ready to be reviewed in the right sidebar.
+
+3. Optional: Click **{{< fa signal-stream >}} See Activity** to review:
+   - Who completed the different status changes for the attestation.
+   - When the attestation status changed.
+   - Notes that were provided to document the process.
+
+4. Review the attestation questionnaire:
+
+   - Check all applicable boxes have been checked.
+   - Check the answers to each question.
+   - Check the comments for accuracy and relevance.
+
+   ::: {.callout}
+   Refer to the model snapshot to ensure the attestation questionnaire is accurate:
+
+   - **{{< fa cubes >}} Inventory** — Shows model information and recent activity such as comments, status changes, updates and test results.
+   - **{{< fa triangle-exclamation >}} Findings** — Shows model findings with details like title, severity, status, and due date.
+   :::
+
+5. Accept or reject the attestation questionnaire:
+
+   - Click **Accept** to record the status change to [**{{< fa clipboard-check >}} Reviewed**]{.bubble} in the [**notes**]{.small-caps} field, then click **Confirm**.
+
+   ::: {.callout}
+   **Next {{< fa arrow-right >}}** [Sign off on the attestation](#sign-off-attestations)
+   ::: 
+
+   - Click **Reject** to record the status change back to [**{{< fa clipboard-check >}} In progress**]{.bubble} in the [**notes**]{.small-caps} field, then click **Confirm**.
+
+   ::: {.callout-important title="How to request changes"}
+   If you reject an attestation questionnaire, the model owner is prompted to revise the questionnaire and resubmit it. The platform maintains a history of all status changes and notes.
+   :::
+
+   ::: {.column-margin .callout title="Tip"}
path: site/guide/attestation/review-attestation-questionnaires.qmd
user: login: validbeck
body: I think this can just be a regular footnote... WAY too much visual clutter on this page. 😆 How did we swap visual preferences? LOL
created_at: 2025-04-08T22:48:22Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
path: site/guide/attestation/working-with-attestations.qmd
user: login: nrichers
body: Great catch, fixed! 
created_at: 2025-04-09T16:57:44Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
path: site/guide/attestation/working-with-attestations.qmd
user: login: nrichers
body: Switched to ` {{< var validmind.platform >}}` as requested.
created_at: 2025-04-09T16:59:52Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+The process tracks progress from questionnaire assignment to final sign-off. Responsibilities are shared — the model owner completes the questionnaire and the validator reviews, requests changes if needed, and signs off:
+
+::: {.tc}
path: site/guide/attestation/working-with-attestations.qmd
user: login: nrichers
body: Yes, the CSS applies generally. I'm glad you agree — mermaid diagrams are an inexpensive way to add some visuals but the styling always really bugged me. 
created_at: 2025-04-09T17:02:58Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
path: site/guide/attestation/working-with-attestations.qmd
user: login: nrichers
body: Applied suggestion manually before I saw this comment — thank you all the same! 
created_at: 2025-04-09T17:03:38Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,77 @@
+---
+title: "Complete attestation questionnaires"
+date: last-modified
+---
+
+Certify the accuracy of key model information at a point in time by completing the attestation questionnaire.
+
+As a model owner, this process is part of the audit trail for your model's information, supporting accountability across its lifecycle. Attestation typically includes details about ownership, usage, performance, controls, and documentation.
+ 
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Not Started]{.bubble} state.
+- [x] You are a model owner.[^3]
+
+:::
+
+## Steps
+
+When prompted on your dashboard:
+
+::: {.column-margin .mt6}
+![Start attestation](start-attestation.png){fig-alt="Prompt to start the attestation process with a button labelled 'Open Attestations'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. In the right sidebar:
+
+   - If shown, click an attestation instance in the [**{{< fa clipboard-check >}} Not Started**]{.bubble} state.
+   - Click **Start Attestation**.
+
+3. Document the status change to [**{{< fa clipboard-check >}} In Progress**]{.bubble} in the [**notes**]{.small-caps} field and click **Confirm**.
+
+   After you confirm the status change to [**{{< fa clipboard-check >}} In Progress**]{.bubble}, the attestation questionnaire is ready to be completed in the right sidebar.
+
+4. Complete the attestation questionnaire, including:
+
+   - Checking all applicable boxes
+   - Answering each question 
+   - Adding relevant comments
+
+   ::: {.callout}
path: site/guide/attestation/complete-attestation-questionnaires.qmd
user: login: nrichers
body: You ARE turning into me, Beck  😂 ... this callout feels important as it provides the sum total of guidance on what to consult for filling out the attestation questionnaire. The notion of the model snapshot is also not readily gleaned from the UI and so it feels worth highlighting here that there are specific things you should look at. 

There are only two callouts on this page, this one and the one about rejected questionnaires. I'll leave this comment open for now but if I removed the OTHER ONE in 318f4c658.
created_at: 2025-04-09T17:12:28Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,77 @@
+---
+title: "Complete attestation questionnaires"
+date: last-modified
+---
+
+Certify the accuracy of key model information at a point in time by completing the attestation questionnaire.
+
+As a model owner, this process is part of the audit trail for your model's information, supporting accountability across its lifecycle. Attestation typically includes details about ownership, usage, performance, controls, and documentation.
+ 
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Not Started]{.bubble} state.
+- [x] You are a model owner.[^3]
+
+:::
+
+## Steps
+
+When prompted on your dashboard:
+
+::: {.column-margin .mt6}
+![Start attestation](start-attestation.png){fig-alt="Prompt to start the attestation process with a button labelled 'Open Attestations'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. In the right sidebar:
+
+   - If shown, click an attestation instance in the [**{{< fa clipboard-check >}} Not Started**]{.bubble} state.
+   - Click **Start Attestation**.
+
+3. Document the status change to [**{{< fa clipboard-check >}} In Progress**]{.bubble} in the [**notes**]{.small-caps} field and click **Confirm**.
+
+   After you confirm the status change to [**{{< fa clipboard-check >}} In Progress**]{.bubble}, the attestation questionnaire is ready to be completed in the right sidebar.
+
+4. Complete the attestation questionnaire, including:
+
+   - Checking all applicable boxes
+   - Answering each question 
+   - Adding relevant comments
+
+   ::: {.callout}
+   Refer to the model snapshot to ensure the attestation questionnaire is accurate:
+
+   - **{{< fa cubes >}} Inventory** — Shows model information and recent activity such as comments, status changes, updates and test results.
+   - **{{< fa triangle-exclamation >}} Findings** — Shows model findings with details like title, severity, status, and due date.
+   :::
+
+5. Click **Submit for Review**.
path: site/guide/attestation/complete-attestation-questionnaires.qmd
user: login: nrichers
body: Agreed, the UI flow could be improved, but there is no _saving_ in the workflow, I just retested to be sure. You fill in the details by editing the questionnaire and then go straight to **Submit for Review**.

In 63d69f5a7, I modified this to read: `5. Verify that your answers are complete and click **Submit for Review**.`

created_at: 2025-04-09T17:18:50Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,125 @@
+---
+title: "Review attestation questionnaires"
+date: last-modified
+---
+
+Review and sign off on attestation questionnaires to verify the accuracy of key model information at a point in time.
+
+As a validator, you assess the model owner's attestation, including ownership, usage, performance, controls, and documentation. You can provide feedback, request changes, and formally sign off to support a traceable and accountable audit trail.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Ready For Review]{.bubble} state.[^3]
+- [x] You are a [{{< fa circle-check >}} Validator]{.bubble} or assigned another role with sufficient permissions.[^4]
+
+:::
+
+## Review attestation questionnaires
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state, to be completed by a person who holds [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps 
+
+When prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation review](review-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Accept'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. If shown in the right sidebar, click an attestation instance in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state.
+
+   The attestation questionnaire is now ready to be reviewed in the right sidebar.
+
+3. Optional: Click **{{< fa signal-stream >}} See Activity** to review:
+   - Who completed the different status changes for the attestation.
+   - When the attestation status changed.
+   - Notes that were provided to document the process.
+
+4. Review the attestation questionnaire:
+
+   - Check all applicable boxes have been checked.
+   - Check the answers to each question.
+   - Check the comments for accuracy and relevance.
+
+   ::: {.callout}
path: site/guide/attestation/review-attestation-questionnaires.qmd
user: login: nrichers
body: Same comment, this callout matters more than others, as it's the sum total of instructions for reviewing the questionnaire, and the concept of the model snapshot matters here. 

In 3027f992210654271ea920c84ef210370f69553e, I turned the other two callouts on this page into body text, so that there's now only a SINGLE callout on the page, this one. I'll leave this comment open for now but this change should address the spirit of your 'there are too many callouts' comment. 
created_at: 2025-04-09T17:29:57Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,125 @@
+---
+title: "Review attestation questionnaires"
+date: last-modified
+---
+
+Review and sign off on attestation questionnaires to verify the accuracy of key model information at a point in time.
+
+As a validator, you assess the model owner's attestation, including ownership, usage, performance, controls, and documentation. You can provide feedback, request changes, and formally sign off to support a traceable and accountable audit trail.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Ready For Review]{.bubble} state.[^3]
+- [x] You are a [{{< fa circle-check >}} Validator]{.bubble} or assigned another role with sufficient permissions.[^4]
+
+:::
+
+## Review attestation questionnaires
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state, to be completed by a person who holds [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps 
+
+When prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation review](review-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Accept'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. If shown in the right sidebar, click an attestation instance in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state.
+
+   The attestation questionnaire is now ready to be reviewed in the right sidebar.
+
+3. Optional: Click **{{< fa signal-stream >}} See Activity** to review:
+   - Who completed the different status changes for the attestation.
+   - When the attestation status changed.
+   - Notes that were provided to document the process.
+
+4. Review the attestation questionnaire:
+
+   - Check all applicable boxes have been checked.
+   - Check the answers to each question.
+   - Check the comments for accuracy and relevance.
+
+   ::: {.callout}
+   Refer to the model snapshot to ensure the attestation questionnaire is accurate:
+
+   - **{{< fa cubes >}} Inventory** — Shows model information and recent activity such as comments, status changes, updates and test results.
+   - **{{< fa triangle-exclamation >}} Findings** — Shows model findings with details like title, severity, status, and due date.
+   :::
+
+5. Accept or reject the attestation questionnaire:
+
+   - Click **Accept** to record the status change to [**{{< fa clipboard-check >}} Reviewed**]{.bubble} in the [**notes**]{.small-caps} field, then click **Confirm**.
+
+   ::: {.callout}
+   **Next {{< fa arrow-right >}}** [Sign off on the attestation](#sign-off-attestations)
path: site/guide/attestation/review-attestation-questionnaires.qmd
user: login: nrichers
body: Great suggestion, implemented in 3027f9922.
created_at: 2025-04-09T17:30:33Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,125 @@
+---
+title: "Review attestation questionnaires"
+date: last-modified
+---
+
+Review and sign off on attestation questionnaires to verify the accuracy of key model information at a point in time.
+
+As a validator, you assess the model owner's attestation, including ownership, usage, performance, controls, and documentation. You can provide feedback, request changes, and formally sign off to support a traceable and accountable audit trail.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Ready For Review]{.bubble} state.[^3]
+- [x] You are a [{{< fa circle-check >}} Validator]{.bubble} or assigned another role with sufficient permissions.[^4]
+
+:::
+
+## Review attestation questionnaires
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state, to be completed by a person who holds [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps 
+
+When prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation review](review-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Accept'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. If shown in the right sidebar, click an attestation instance in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state.
+
+   The attestation questionnaire is now ready to be reviewed in the right sidebar.
+
+3. Optional: Click **{{< fa signal-stream >}} See Activity** to review:
+   - Who completed the different status changes for the attestation.
+   - When the attestation status changed.
+   - Notes that were provided to document the process.
+
+4. Review the attestation questionnaire:
+
+   - Check all applicable boxes have been checked.
+   - Check the answers to each question.
+   - Check the comments for accuracy and relevance.
+
+   ::: {.callout}
+   Refer to the model snapshot to ensure the attestation questionnaire is accurate:
+
+   - **{{< fa cubes >}} Inventory** — Shows model information and recent activity such as comments, status changes, updates and test results.
+   - **{{< fa triangle-exclamation >}} Findings** — Shows model findings with details like title, severity, status, and due date.
+   :::
+
+5. Accept or reject the attestation questionnaire:
+
+   - Click **Accept** to record the status change to [**{{< fa clipboard-check >}} Reviewed**]{.bubble} in the [**notes**]{.small-caps} field, then click **Confirm**.
+
+   ::: {.callout}
+   **Next {{< fa arrow-right >}}** [Sign off on the attestation](#sign-off-attestations)
+   ::: 
+
+   - Click **Reject** to record the status change back to [**{{< fa clipboard-check >}} In progress**]{.bubble} in the [**notes**]{.small-caps} field, then click **Confirm**.
+
+   ::: {.callout-important title="How to request changes"}
+   If you reject an attestation questionnaire, the model owner is prompted to revise the questionnaire and resubmit it. The platform maintains a history of all status changes and notes.
+   :::
+
+   ::: {.column-margin .callout title="Tip"}
path: site/guide/attestation/review-attestation-questionnaires.qmd
user: login: nrichers
body: In 9807cfbd6 I turned the tip into body text. Agreed, less visual clutter is more here. 

> How did we swap visual preferences? LOL

It's CLEARLY your fault since I avoided highlighting like the plague before you came along, @validbeck ... 😂 

The original motivation for a callout here was to highlight that notes are how model owners and validators communicate — but the UI itself could provide more guidance. Let's not patch that with more highlighting. 
created_at: 2025-04-09T17:44:55Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+The process tracks progress from questionnaire assignment to final sign-off. Responsibilities are shared — the model owner completes the questionnaire and the validator reviews, requests changes if needed, and signs off:
+
+::: {.tc}
+```{mermaid}
+graph LR
+    subgraph Model Owner
+        A["**Not Started**"] --> B["**In Progress**"]
+        B --> C["**Ready for Review**"]
+    end
+    
+    subgraph Validator
+        C --> D["**Reviewed**"]
+        D --> E["**Signed Off**"]
+        D -.-> B
+    end
+```
+
+[The attestation process — Model owner and validator responsibilities]{.silver .small}
+:::
+
+::: {.column-margin .callout title="Attestation is collaborative"}
+A validator can request changes from the model owner by rejecting the attestation questionnaire. 
+
+___
+
+The platform maintains a history of all status changes and notes.
+:::
+
+**Model owners** are responsible for moving the questionnaire through these states:
path: site/guide/attestation/working-with-attestations.qmd
user: login: nrichers
body: Technically, there is no bubble for model owners in the UI ... I snuck one in for the prerequisites only for consistency. 

The bubbles are a UI concept and it feels extraneous to repeat them in this section — there's already some visual clutter due to bolding. Let me experiment with simplifying the bolding but I'll leave this comment open for now. 
created_at: 2025-04-09T17:50:20Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+The process tracks progress from questionnaire assignment to final sign-off. Responsibilities are shared — the model owner completes the questionnaire and the validator reviews, requests changes if needed, and signs off:
+
+::: {.tc}
+```{mermaid}
+graph LR
+    subgraph Model Owner
+        A["**Not Started**"] --> B["**In Progress**"]
+        B --> C["**Ready for Review**"]
+    end
+    
+    subgraph Validator
+        C --> D["**Reviewed**"]
+        D --> E["**Signed Off**"]
+        D -.-> B
+    end
+```
+
+[The attestation process — Model owner and validator responsibilities]{.silver .small}
+:::
+
+::: {.column-margin .callout title="Attestation is collaborative"}
+A validator can request changes from the model owner by rejecting the attestation questionnaire. 
+
+___
+
+The platform maintains a history of all status changes and notes.
+:::
+
+**Model owners** are responsible for moving the questionnaire through these states:
path: site/guide/attestation/working-with-attestations.qmd
user: login: validbeck
body: Can we use the `.smallcaps` instead perhaps? The rolet tiles in the UI are actually displayed that way!
created_at: 2025-04-10T20:07:07Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+The process tracks progress from questionnaire assignment to final sign-off. Responsibilities are shared — the model owner completes the questionnaire and the validator reviews, requests changes if needed, and signs off:
+
+::: {.tc}
+```{mermaid}
+graph LR
+    subgraph Model Owner
+        A["**Not Started**"] --> B["**In Progress**"]
+        B --> C["**Ready for Review**"]
+    end
+    
+    subgraph Validator
+        C --> D["**Reviewed**"]
+        D --> E["**Signed Off**"]
+        D -.-> B
+    end
+```
+
+[The attestation process — Model owner and validator responsibilities]{.silver .small}
+:::
+
+::: {.column-margin .callout title="Attestation is collaborative"}
+A validator can request changes from the model owner by rejecting the attestation questionnaire. 
+
+___
+
+The platform maintains a history of all status changes and notes.
+:::
+
+**Model owners** are responsible for moving the questionnaire through these states:
+
+- **Not Started** — When attestation is first assigned to the model owner
+- **In Progress** — While the model owner completes the questionnaire or addresses change requests
+- **Ready for Review** — When the model owner has submitted the completed questionnaire
+
+**Validators** are responsible for moving the questionnaire through these states:
+
+- **Reviewed** — When a validator has reviewed the questionnaire
+- **Signed Off** — Final state after a validator has signed off
+
+## How do I create meaningful attestation questionnaires?
+
+Attestation questionnaires are typically used in model risk management to confirm that key controls, governance processes and documentation requirements have been followed throughout a model's lifecycle. These questionnaires are part of a broader effort to ensure accountability and regulatory compliance. 
+
+Areas typically covered in the questionnaire:
+
+- **Verification of responsibilities** — Attests that model owners, developers and validators have performed their roles in accordance with internal policies and procedures.
+
+- **Documentation of compliance** — Confirms that required documentation — such as model documentation, validation reports and change logs — has been completed and properly archived.
+
+- **Evidence of control operation** — Serves as formal evidence that key controls (e.g. backtesting, performance monitoring, version control) are in place and functioning as intended.
path: site/guide/attestation/working-with-attestations.qmd
user: login: validbeck
body: @nrichers I don't see this committed — were you working on it? Seems like some comments weren't addressed yet (GitHub DOES like to hide them...)
created_at: 2025-04-10T20:08:22Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: @nrichers These haven't been address either, looks like? 
created_at: 2025-04-10T20:08:46Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: @nrichers This comment as well.
created_at: 2025-04-10T20:09:33Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
+
+### Add attestation fields
+
+By default, attestations include the model name. Add additional model inventory fields as needed:
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Under **Relevant Attestation Fields**, drag model inventory fields between columns:
+
+   - **Model Inventory Fields** — Available fields from the model inventory
+   - **Relevant Attestation Fields** — Selected fields to display in model snapshots
+
+3. Optional: Reorder the fields to change how they display in the attestation.
+
+### Edit questionnaire templates
+
+Attestation questionnaires should confirm that key controls, governance processes, and documentation requirements have been followed. 
+
+::: {.column-margin .callout}
+
+### Tip
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+___ 
+
+[How do I create meaningful attestation questionnaires?](/guide/attestation/working-with-attestations.qmd#how-do-i-create-meaningful-attestation-questionnaires)
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation you want to configure.
+
+2. Under **Questionnaire Template**, click the template area to edit. You can add rich text fields such as:
+
+   - Instructions 
+   - Links to guidelines
+   - Checkboxes
+   - Lists 
+   - Other custom elements
+
+   ![A screenshot of the questionnaire template editor](edit-questionnaire-template.gif){width=100% fig-alt="An animation of the questionnaire template editor showing the process of adding a question about documentation of compliance to the template with the instructions to confirm that required documentation, such as model documentation, validation reports, and change logs, has been completed." .screenshot}
+
+3. After you complete your edits, click **Save**.
+
+The attestation questionnaire is now ready to be be used in future attestation instances, to be completed by model owners and reviewed and signed off by validators.
+
+## Test attestation schedules
+
+::: {.callout-important title="Not normally required"}
+These steps are optional and not required to set up attestation — **perform only under the direction of ValidMind**.
+:::
+
+For testing purposes only, you can trigger the attestation process: 
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to test.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Execute Schedule**.
+
+3. Click **Confirm**.
+
+After executing the schedule, the dashboard of the model owner displays a banner notification that the attestation is ready to be completed.
+
+## Edit attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation period to edit.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Edit**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: @nrichers More hidden GH comments, no doubt ...
created_at: 2025-04-10T20:10:00Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,125 @@
+---
+title: "Review attestation questionnaires"
+date: last-modified
+---
+
+Review and sign off on attestation questionnaires to verify the accuracy of key model information at a point in time.
+
+As a validator, you assess the model owner's attestation, including ownership, usage, performance, controls, and documentation. You can provide feedback, request changes, and formally sign off to support a traceable and accountable audit trail.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Ready For Review]{.bubble} state.[^3]
+- [x] You are a [{{< fa circle-check >}} Validator]{.bubble} or assigned another role with sufficient permissions.[^4]
+
+:::
+
+## Review attestation questionnaires
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state, to be completed by a person who holds [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps 
+
+When prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation review](review-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Accept'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. If shown in the right sidebar, click an attestation instance in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state.
+
+   The attestation questionnaire is now ready to be reviewed in the right sidebar.
+
+3. Optional: Click **{{< fa signal-stream >}} See Activity** to review:
+   - Who completed the different status changes for the attestation.
+   - When the attestation status changed.
+   - Notes that were provided to document the process.
+
+4. Review the attestation questionnaire:
+
+   - Check all applicable boxes have been checked.
+   - Check the answers to each question.
+   - Check the comments for accuracy and relevance.
+
+   ::: {.callout}
path: site/guide/attestation/review-attestation-questionnaires.qmd
user: login: validbeck
body: @nrichers I think the tip really doesn't need to be a callout either, it's way to close to the other imporant info. Can we just change it to a regular footnote please? 🙏🏻 
created_at: 2025-04-10T20:11:18Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
+
+### Add attestation fields
+
+By default, attestations include the model name. Add additional model inventory fields as needed:
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Under **Relevant Attestation Fields**, drag model inventory fields between columns:
+
+   - **Model Inventory Fields** — Available fields from the model inventory
+   - **Relevant Attestation Fields** — Selected fields to display in model snapshots
+
+3. Optional: Reorder the fields to change how they display in the attestation.
+
+### Edit questionnaire templates
+
+Attestation questionnaires should confirm that key controls, governance processes, and documentation requirements have been followed. 
+
+::: {.column-margin .callout}
+
+### Tip
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+___ 
+
+[How do I create meaningful attestation questionnaires?](/guide/attestation/working-with-attestations.qmd#how-do-i-create-meaningful-attestation-questionnaires)
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation you want to configure.
+
+2. Under **Questionnaire Template**, click the template area to edit. You can add rich text fields such as:
+
+   - Instructions 
+   - Links to guidelines
+   - Checkboxes
+   - Lists 
+   - Other custom elements
+
+   ![A screenshot of the questionnaire template editor](edit-questionnaire-template.gif){width=100% fig-alt="An animation of the questionnaire template editor showing the process of adding a question about documentation of compliance to the template with the instructions to confirm that required documentation, such as model documentation, validation reports, and change logs, has been completed." .screenshot}
+
+3. After you complete your edits, click **Save**.
+
+The attestation questionnaire is now ready to be be used in future attestation instances, to be completed by model owners and reviewed and signed off by validators.
+
+## Test attestation schedules
+
+::: {.callout-important title="Not normally required"}
+These steps are optional and not required to set up attestation — **perform only under the direction of ValidMind**.
+:::
+
+For testing purposes only, you can trigger the attestation process: 
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to test.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Execute Schedule**.
+
+3. Click **Confirm**.
+
+After executing the schedule, the dashboard of the model owner displays a banner notification that the attestation is ready to be completed.
+
+## Edit attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation period to edit.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Edit**.
+
+3. Make changes to one of the following:
+
+   - Name
+   - Start date
+   - End date
+
+4. Click **Save Period**.
+
+Edits to an attestation period will be effective for future occurrences but do not affect previous or in-progress attestation periods.
+
+## Remove attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to remove.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Remove**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: @nrichers Last missed comment, I think?
created_at: 2025-04-10T20:11:28Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+The process tracks progress from questionnaire assignment to final sign-off. Responsibilities are shared — the model owner completes the questionnaire and the validator reviews, requests changes if needed, and signs off:
+
+::: {.tc}
+```{mermaid}
+graph LR
+    subgraph Model Owner
+        A["**Not Started**"] --> B["**In Progress**"]
+        B --> C["**Ready for Review**"]
+    end
+    
+    subgraph Validator
+        C --> D["**Reviewed**"]
+        D --> E["**Signed Off**"]
+        D -.-> B
+    end
+```
+
+[The attestation process — Model owner and validator responsibilities]{.silver .small}
+:::
+
+::: {.column-margin .callout title="Attestation is collaborative"}
+A validator can request changes from the model owner by rejecting the attestation questionnaire. 
+
+___
+
+The platform maintains a history of all status changes and notes.
+:::
+
+**Model owners** are responsible for moving the questionnaire through these states:
path: site/guide/attestation/working-with-attestations.qmd
user: login: nrichers
body: I tried `.smallcaps` and for this to work well, you'd also need to apply this formatting to the Mermaid diagram, but it doesn't support Quarto formatting directives. 

Less is more here — I think plain text fine. 
created_at: 2025-04-10T22:25:45Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,125 @@
+---
+title: "Review attestation questionnaires"
+date: last-modified
+---
+
+Review and sign off on attestation questionnaires to verify the accuracy of key model information at a point in time.
+
+As a validator, you assess the model owner's attestation, including ownership, usage, performance, controls, and documentation. You can provide feedback, request changes, and formally sign off to support a traceable and accountable audit trail.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Ready For Review]{.bubble} state.[^3]
+- [x] You are a [{{< fa circle-check >}} Validator]{.bubble} or assigned another role with sufficient permissions.[^4]
+
+:::
+
+## Review attestation questionnaires
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state, to be completed by a person who holds [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps 
+
+When prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation review](review-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Accept'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. If shown in the right sidebar, click an attestation instance in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state.
+
+   The attestation questionnaire is now ready to be reviewed in the right sidebar.
+
+3. Optional: Click **{{< fa signal-stream >}} See Activity** to review:
+   - Who completed the different status changes for the attestation.
+   - When the attestation status changed.
+   - Notes that were provided to document the process.
+
+4. Review the attestation questionnaire:
+
+   - Check all applicable boxes have been checked.
+   - Check the answers to each question.
+   - Check the comments for accuracy and relevance.
+
+   ::: {.callout}
path: site/guide/attestation/review-attestation-questionnaires.qmd
user: login: nrichers
body: I think we’ll have to agree to disagree:

- The way we communicate available model info is fragmented across multiple locations
- This info is important for model owners and validators to complete their tasks
- Ideally, the UI would consolidate the info but in the meantime this callout is necessary
 
This callout is what I would look for as someone trying to understand the feature — I found the presentation of model info confusing myself. I’ve already removed other callouts on this and related pages to align with the spirit of your request. Let's just leave it at that, please? 
created_at: 2025-04-10T22:34:58Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: nrichers
body: Fixed globally in f37bcee1530a05aac3f2c13807c097b45f3ab562 — thank you for pointing out that this comment had not been addressed, yet.
created_at: 2025-04-10T22:46:57Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
path: site/guide/attestation/set-up-attestations.qmd
user: login: nrichers
body: I don't think this info is required here, as the UI prevents you from even trying ... You cannot select an attestation start before today's date, the option is unavailable:

![Capto_ 2025-04-10_03-48-31_pm](https://github.com/user-attachments/assets/a4d24a3d-bd35-4175-bfd5-c934ed0e2120)

That said, it might be useful to include this in the overview as a consideration for when you are planning your attestation periods. I'll see where I can weave that in.

created_at: 2025-04-10T22:52:11Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
path: site/guide/attestation/set-up-attestations.qmd
user: login: nrichers
body: 4f87bc3260596ed7a19d1549b7b28c86c2b9aafe adds a short paragraph in the context where the process is explained. I think that is the best solution for your comment. 
created_at: 2025-04-10T22:58:14Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
+
+### Add attestation fields
+
+By default, attestations include the model name. Add additional model inventory fields as needed:
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Under **Relevant Attestation Fields**, drag model inventory fields between columns:
+
+   - **Model Inventory Fields** — Available fields from the model inventory
+   - **Relevant Attestation Fields** — Selected fields to display in model snapshots
+
+3. Optional: Reorder the fields to change how they display in the attestation.
+
+### Edit questionnaire templates
+
+Attestation questionnaires should confirm that key controls, governance processes, and documentation requirements have been followed. 
+
+::: {.column-margin .callout}
+
+### Tip
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+___ 
+
+[How do I create meaningful attestation questionnaires?](/guide/attestation/working-with-attestations.qmd#how-do-i-create-meaningful-attestation-questionnaires)
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation you want to configure.
+
+2. Under **Questionnaire Template**, click the template area to edit. You can add rich text fields such as:
+
+   - Instructions 
+   - Links to guidelines
+   - Checkboxes
+   - Lists 
+   - Other custom elements
+
+   ![A screenshot of the questionnaire template editor](edit-questionnaire-template.gif){width=100% fig-alt="An animation of the questionnaire template editor showing the process of adding a question about documentation of compliance to the template with the instructions to confirm that required documentation, such as model documentation, validation reports, and change logs, has been completed." .screenshot}
+
+3. After you complete your edits, click **Save**.
+
+The attestation questionnaire is now ready to be be used in future attestation instances, to be completed by model owners and reviewed and signed off by validators.
+
+## Test attestation schedules
+
+::: {.callout-important title="Not normally required"}
+These steps are optional and not required to set up attestation — **perform only under the direction of ValidMind**.
+:::
+
+For testing purposes only, you can trigger the attestation process: 
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to test.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Execute Schedule**.
+
+3. Click **Confirm**.
+
+After executing the schedule, the dashboard of the model owner displays a banner notification that the attestation is ready to be completed.
+
+## Edit attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation period to edit.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Edit**.
+
+3. Make changes to one of the following:
+
+   - Name
+   - Start date
+   - End date
+
+4. Click **Save Period**.
+
+Edits to an attestation period will be effective for future occurrences but do not affect previous or in-progress attestation periods.
+
+## Remove attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to remove.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Remove**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: nrichers
body: Fixed two icons on this page in 0e803134dee9eaaa369d2f33fc4fcdb4cc37ef32 and added `.red` where applicable. 
created_at: 2025-04-10T23:04:48Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,114 @@
+---
+title: "Working with attestations"
+date: last-modified
+listing:
+  - id: attestation-listing
+    type: grid
+    max-description-length: 250
+    sort: false
+    fields: [title, description]
+    contents:
+      - set-up-attestations.qmd
+      - complete-attestation-questionnaires.qmd
+      - review-attestation-questionnaires.qmd
+---
+
+Attestation enables model owners and validators to formally certify, review, and sign off on model attributes at specific points in time, supporting compliance and governance processes. 
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] If applicable, model findings have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Model owner]{.bubble} — Completes attestation questionnaires
+   - [{{< fa circle-check >}} Validator]{.bubble}  — Reviews and signs off on attestation questionnaires
+
+:::
+
+## Key concepts
+
+{{< include /about/glossary/_attestation.qmd >}}
+
+### How does the attestation process work?
+
+Attestation on the {{< var validmind.product >}} begins at the start of the attestation period after the process has been set up initially. The platform captures a snapshot of each model and its findings, preserving the state at that point in time. Changes made after the process starts do not affect the historical record.
+
+Model owners and validators each see a banner on their dashboard when an attestation requires action. The banner links directly to their active respective attestation tasks, also known as _attestation instances_:
+
+![Dashboard prompt for attestations](attestation-banner.png){width="80%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+The process tracks progress from questionnaire assignment to final sign-off. Responsibilities are shared — the model owner completes the questionnaire and the validator reviews, requests changes if needed, and signs off:
+
+::: {.tc}
+```{mermaid}
+graph LR
+    subgraph Model Owner
+        A["**Not Started**"] --> B["**In Progress**"]
+        B --> C["**Ready for Review**"]
+    end
+    
+    subgraph Validator
+        C --> D["**Reviewed**"]
+        D --> E["**Signed Off**"]
+        D -.-> B
+    end
+```
+
+[The attestation process — Model owner and validator responsibilities]{.silver .small}
+:::
+
+::: {.column-margin .callout title="Attestation is collaborative"}
+A validator can request changes from the model owner by rejecting the attestation questionnaire. 
+
+___
+
+The platform maintains a history of all status changes and notes.
+:::
+
+**Model owners** are responsible for moving the questionnaire through these states:
+
+- **Not Started** — When attestation is first assigned to the model owner
+- **In Progress** — While the model owner completes the questionnaire or addresses change requests
+- **Ready for Review** — When the model owner has submitted the completed questionnaire
+
+**Validators** are responsible for moving the questionnaire through these states:
+
+- **Reviewed** — When a validator has reviewed the questionnaire
+- **Signed Off** — Final state after a validator has signed off
+
+## How do I create meaningful attestation questionnaires?
+
+Attestation questionnaires are typically used in model risk management to confirm that key controls, governance processes and documentation requirements have been followed throughout a model's lifecycle. These questionnaires are part of a broader effort to ensure accountability and regulatory compliance. 
+
+Areas typically covered in the questionnaire:
+
+- **Verification of responsibilities** — Attests that model owners, developers and validators have performed their roles in accordance with internal policies and procedures.
+
+- **Documentation of compliance** — Confirms that required documentation — such as model documentation, validation reports and change logs — has been completed and properly archived.
+
+- **Evidence of control operation** — Serves as formal evidence that key controls (e.g. backtesting, performance monitoring, version control) are in place and functioning as intended.
path: site/guide/attestation/working-with-attestations.qmd
user: login: nrichers
body: Very true, and I am guilty here. Fixed! 
created_at: 2025-04-10T23:14:56Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,125 @@
+---
+title: "Review attestation questionnaires"
+date: last-modified
+---
+
+Review and sign off on attestation questionnaires to verify the accuracy of key model information at a point in time.
+
+As a validator, you assess the model owner's attestation, including ownership, usage, performance, controls, and documentation. You can provide feedback, request changes, and formally sign off to support a traceable and accountable audit trail.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation.[^1]
+- [x] Attestation has been set up.[^2]
+- [x] An attestation instance is in the [{{< fa clipboard-check >}} Ready For Review]{.bubble} state.[^3]
+- [x] You are a [{{< fa circle-check >}} Validator]{.bubble} or assigned another role with sufficient permissions.[^4]
+
+:::
+
+## Review attestation questionnaires
+
+### Before you begin
+
+These steps apply to attestations that are in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state, to be completed by a person who holds [**{{< fa circle-check >}} Validator**]{.bubble} role at the time the attestation snapshot was taken.
+
+### Steps 
+
+When prompted on your dashboard:
+
+::: {.column-margin}
+![Attestation review](review-attestation.png){fig-alt="Prompt to review the attestation with a button labelled 'Accept'" .screenshot}
+:::
+
+1. Click **Open Attestations {{< fa arrow-right >}}**:
+
+   ![Dashboard prompt for attestations](attestation-banner.png){width="90%" fig-alt="Attestation prompt with a link to the attestation labelled 'Open Attestations'" .screenshot}
+
+   Alternatively, you can access attestations pending your action by clicking **{{< fa clipboard-check >}} Attestations** in these pages:
+
+   - **{{< fa cubes >}} Inventory**
+   - **{{< fa triangle-exclamation >}} Findings**
+
+2. If shown in the right sidebar, click an attestation instance in the [**{{< fa clipboard-check >}} Ready For Review**]{.bubble} state.
+
+   The attestation questionnaire is now ready to be reviewed in the right sidebar.
+
+3. Optional: Click **{{< fa signal-stream >}} See Activity** to review:
+   - Who completed the different status changes for the attestation.
+   - When the attestation status changed.
+   - Notes that were provided to document the process.
+
+4. Review the attestation questionnaire:
+
+   - Check all applicable boxes have been checked.
+   - Check the answers to each question.
+   - Check the comments for accuracy and relevance.
+
+   ::: {.callout}
path: site/guide/attestation/review-attestation-questionnaires.qmd
user: login: nrichers
body: Discussed — you meant a different callout than the one mentioned here. You will take a look and see which one it was. 
created_at: 2025-04-10T23:16:32Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
+
+### Add attestation fields
+
+By default, attestations include the model name. Add additional model inventory fields as needed:
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Under **Relevant Attestation Fields**, drag model inventory fields between columns:
+
+   - **Model Inventory Fields** — Available fields from the model inventory
+   - **Relevant Attestation Fields** — Selected fields to display in model snapshots
+
+3. Optional: Reorder the fields to change how they display in the attestation.
+
+### Edit questionnaire templates
+
+Attestation questionnaires should confirm that key controls, governance processes, and documentation requirements have been followed. 
+
+::: {.column-margin .callout}
+
+### Tip
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+___ 
+
+[How do I create meaningful attestation questionnaires?](/guide/attestation/working-with-attestations.qmd#how-do-i-create-meaningful-attestation-questionnaires)
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation you want to configure.
+
+2. Under **Questionnaire Template**, click the template area to edit. You can add rich text fields such as:
+
+   - Instructions 
+   - Links to guidelines
+   - Checkboxes
+   - Lists 
+   - Other custom elements
+
+   ![A screenshot of the questionnaire template editor](edit-questionnaire-template.gif){width=100% fig-alt="An animation of the questionnaire template editor showing the process of adding a question about documentation of compliance to the template with the instructions to confirm that required documentation, such as model documentation, validation reports, and change logs, has been completed." .screenshot}
+
+3. After you complete your edits, click **Save**.
+
+The attestation questionnaire is now ready to be be used in future attestation instances, to be completed by model owners and reviewed and signed off by validators.
+
+## Test attestation schedules
+
+::: {.callout-important title="Not normally required"}
+These steps are optional and not required to set up attestation — **perform only under the direction of ValidMind**.
+:::
+
+For testing purposes only, you can trigger the attestation process: 
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to test.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Execute Schedule**.
+
+3. Click **Confirm**.
+
+After executing the schedule, the dashboard of the model owner displays a banner notification that the attestation is ready to be completed.
+
+## Edit attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation period to edit.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Edit**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: validbeck
body: @nrichers This one still seems to be missing!
created_at: 2025-04-10T23:36:23Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
+
+### Add attestation fields
+
+By default, attestations include the model name. Add additional model inventory fields as needed:
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Under **Relevant Attestation Fields**, drag model inventory fields between columns:
+
+   - **Model Inventory Fields** — Available fields from the model inventory
+   - **Relevant Attestation Fields** — Selected fields to display in model snapshots
+
+3. Optional: Reorder the fields to change how they display in the attestation.
+
+### Edit questionnaire templates
+
+Attestation questionnaires should confirm that key controls, governance processes, and documentation requirements have been followed. 
+
+::: {.column-margin .callout}
+
+### Tip
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+___ 
+
+[How do I create meaningful attestation questionnaires?](/guide/attestation/working-with-attestations.qmd#how-do-i-create-meaningful-attestation-questionnaires)
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation you want to configure.
+
+2. Under **Questionnaire Template**, click the template area to edit. You can add rich text fields such as:
+
+   - Instructions 
+   - Links to guidelines
+   - Checkboxes
+   - Lists 
+   - Other custom elements
+
+   ![A screenshot of the questionnaire template editor](edit-questionnaire-template.gif){width=100% fig-alt="An animation of the questionnaire template editor showing the process of adding a question about documentation of compliance to the template with the instructions to confirm that required documentation, such as model documentation, validation reports, and change logs, has been completed." .screenshot}
+
+3. After you complete your edits, click **Save**.
+
+The attestation questionnaire is now ready to be be used in future attestation instances, to be completed by model owners and reviewed and signed off by validators.
+
+## Test attestation schedules
+
+::: {.callout-important title="Not normally required"}
+These steps are optional and not required to set up attestation — **perform only under the direction of ValidMind**.
+:::
+
+For testing purposes only, you can trigger the attestation process: 
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to test.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Execute Schedule**.
+
+3. Click **Confirm**.
+
+After executing the schedule, the dashboard of the model owner displays a banner notification that the attestation is ready to be completed.
+
+## Edit attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation period to edit.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Edit**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: nrichers
body: Thank you! I have no idea how this comment was not visible; and it needs to be fixed GLOBALLY in several places. On it ...
created_at: 2025-04-10T23:42:10Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,179 @@
+---
+title: "Set up attestations"
+date: last-modified
+---
+
+Enable model owners and validators to step through the attestation process required by your organization. 
+
+::: {.tc}
+```{mermaid}
+flowchart LR
+    A["**Add attestation**"] --> B["**Configure**<br>• Attestation period<br>• Custom fields<br>• Questionnaire template"]
+    
+    O["**Optional**<br>• Test<br>• Edit<br>• Remove"]
+    B -.-> O
+    
+    click A "#add-attestations" "Go to Add attestations section"
+    click B "#configure-attestations" "Go to Configure attestations section"
+    click O "#test-attestation-schedules" "Go to Test attestation schedules section"
+```
+
+[The steps required to set up attestation]{.silver .small}
+:::
+
+Setting up attestations involves adding an attestation, configuring the attestation period, adding custom fields, and editing the questionnaire template. Optionally, you can also execute the attestation schedule to test the process, and edit or remove attestation periods.
+
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Models registered in the inventory require attestation. [^1]
+- [x] You are a [{{< fa hand >}} Customer Admin]{.bubble} or assigned another role with sufficient permissions to set up attestations.[^2]
+
+:::
+
+## Add attestations
+
+1. In the left sidebar, click **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**.
+
+2. Click **{{< fa plus >}} Add New Attestation**.
+
+3. Enter a name for the attestation.
+
+4. Enter a description.
+
+5. Click **Add Attestation**.
+
+::: {.callout}
+**Next {{< fa arrow-right >}}** [Configure the attestation](#configure-attestations)
+:::
+
+## Configure attestations
+
+### Add attestation periods
+
+Attestation periods are typically scheduled quarterly or annually and should be configured to align with regulatory or internal review cycles: 
+
+::: {.column-margin .callout}
+
+### Tips
+
+- **Avoid overlap** — Only one attestation period can be active at a time.
+- **Schedule individually** — You cannot schedule recurring attestation periods.
+
+___
+
+<!-- TO DO: Confirm with Steven -->
+Attestation periods reflect the time zone of the user setting up attestation and they trigger in the time zone of the model owner. 
+
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Click **{{< fa plus >}} Add Attestation Period**.
+
+3. Enter a name for the attestation period, such as `Quarterly attestation`.
+
+4. Set the start date for the attestation period.
+
+5. Set the end date when the attestation period ends.
+
+6. Click **Add Period**.
+
+ When the attestation period begins, the system triggers the process automatically. Model owners are then notified via a banner on their dashboard prompting them to complete the attestation questionnaire.
+
+### Add attestation fields
+
+By default, attestations include the model name. Add additional model inventory fields as needed:
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click an attestation to configure.
+
+2. Under **Relevant Attestation Fields**, drag model inventory fields between columns:
+
+   - **Model Inventory Fields** — Available fields from the model inventory
+   - **Relevant Attestation Fields** — Selected fields to display in model snapshots
+
+3. Optional: Reorder the fields to change how they display in the attestation.
+
+### Edit questionnaire templates
+
+Attestation questionnaires should confirm that key controls, governance processes, and documentation requirements have been followed. 
+
+::: {.column-margin .callout}
+
+### Tip
+
+Work with your model risk management team to create a template that accurately reflects your organization's attestation requirements.
+
+___ 
+
+[How do I create meaningful attestation questionnaires?](/guide/attestation/working-with-attestations.qmd#how-do-i-create-meaningful-attestation-questionnaires)
+:::
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation you want to configure.
+
+2. Under **Questionnaire Template**, click the template area to edit. You can add rich text fields such as:
+
+   - Instructions 
+   - Links to guidelines
+   - Checkboxes
+   - Lists 
+   - Other custom elements
+
+   ![A screenshot of the questionnaire template editor](edit-questionnaire-template.gif){width=100% fig-alt="An animation of the questionnaire template editor showing the process of adding a question about documentation of compliance to the template with the instructions to confirm that required documentation, such as model documentation, validation reports, and change logs, has been completed." .screenshot}
+
+3. After you complete your edits, click **Save**.
+
+The attestation questionnaire is now ready to be be used in future attestation instances, to be completed by model owners and reviewed and signed off by validators.
+
+## Test attestation schedules
+
+::: {.callout-important title="Not normally required"}
+These steps are optional and not required to set up attestation — **perform only under the direction of ValidMind**.
+:::
+
+For testing purposes only, you can trigger the attestation process: 
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation to test.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Execute Schedule**.
+
+3. Click **Confirm**.
+
+After executing the schedule, the dashboard of the model owner displays a banner notification that the attestation is ready to be completed.
+
+## Edit attestation periods
+
+1. Under **{{< fa gear >}} Settings** > **{{< fa clipboard-check >}}  Attestations**, click the attestation period to edit.
+
+2. Under **Scheduling**, click **{{< fa ellipsis-vertical >}}** and select **Edit**.
path: site/guide/attestation/set-up-attestations.qmd
user: login: nrichers
body: OK, fixed in b294b5245f65ae6742e8ef6968485a4cecba7d47! I also found another missing icon, now fixed as well. 
created_at: 2025-04-11T00:01:51Z
author_association: COLLABORATOR

PR comments:
user: login: github-actions[bot]
created_at: 2025-04-07T16:15:21Z
body: # PR Summary
This pull request introduces a new feature for managing attestations within the platform. The changes include the addition of new documentation files and updates to existing ones to support the attestation process. Key functional changes include:

- **Attestation Documentation**: New guides and glossary entries have been added to explain the attestation process, including setting up attestations, completing questionnaires, and reviewing them. This includes detailed steps for model owners and validators to follow during the attestation process.
- **Glossary Update**: A new glossary entry for 'Attestation' has been added to provide definitions and context for terms related to the attestation process.
- **Mermaid Diagram Styling**: Updates to the theme styling for Mermaid diagrams, including changes to node and edge colors, and the addition of rounded corners for nodes.
- **Guide Organization**: The guides have been reorganized to include a new section specifically for attestation, making it easier for users to find relevant information.

These changes aim to enhance the platform's compliance and governance capabilities by providing a structured process for model attestation.

## Test Suggestions
- Verify that the new attestation guides are accessible from the platform's documentation section.
- Test the attestation process by following the steps outlined in the new documentation to ensure clarity and completeness.
- Check the glossary to ensure the new 'Attestation' entry is correctly linked and displayed.
- Review the Mermaid diagrams in the documentation to confirm that the new styling is applied correctly.
- Ensure that the new attestation section in the guides is correctly organized and all links are functional.
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-09T17:10:17Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-09T17:17:11Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-09T17:28:38Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-09T17:34:30Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-09T17:48:05Z
body: # PR Summary
This pull request introduces a new feature for managing attestations within the platform. The changes include the addition of new documentation files and updates to existing ones to support the attestation process. Key functional changes include:

- **Attestation Documentation**: New guides and glossary entries have been added to explain the attestation process, including setting up attestations, completing questionnaires, and reviewing them. This includes detailed steps for model owners and validators to follow during the attestation process.
- **Glossary Update**: A new glossary entry for 'Attestation' has been added to provide definitions and context for terms related to the attestation process.
- **Mermaid Diagram Styling**: Updates to the theme styling for Mermaid diagrams, including changes to node and edge colors, and the introduction of rounded corners for nodes.
- **Guide Organization**: The guides have been reorganized to include a new section specifically for attestation, making it easier for users to find relevant information.

These changes aim to enhance the platform's compliance and governance capabilities by providing a structured process for model certification and review.

## Test Suggestions
- Verify that the new attestation guides are accessible from the platform's documentation section.
- Test the attestation setup process to ensure it aligns with the documented steps.
- Check the functionality of completing and reviewing attestation questionnaires as described in the documentation.
- Ensure that the glossary entry for 'Attestation' is correctly linked and displays the expected content.
- Validate the visual appearance of Mermaid diagrams to confirm that the new styling is applied correctly.
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-09T17:50:26Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR
user: login: nrichers
created_at: 2025-04-09T18:09:14Z
body: @validbeck related to your https://github.com/validmind/documentation/pull/687#discussion_r2034116432, how about this simplified version?

| Original                                                                                                     | Simplified                                                                                  |
|--------|--------|
| ![Capto_ 2025-04-09_10-55-47_am](https://github.com/user-attachments/assets/7a625eee-662a-4e82-b388-bd9fa3254256) | ![Capto_ 2025-04-09_11-05-02_am](https://github.com/user-attachments/assets/2cf88ba4-7156-47be-bf1c-c756821728d2)  |



author_association: COLLABORATOR
user: login: validbeck
created_at: 2025-04-10T20:13:59Z
body: > @validbeck related to your [#687 (comment)](https://github.com/validmind/documentation/pull/687#discussion_r2034116432), how about this simplified version?
> 
> Original	Simplified
> ![Capto_ 2025-04-09_10-55-47_am](https://private-user-images.githubusercontent.com/15148011/431971197-7a625eee-662a-4e82-b388-bd9fa3254256.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDQzMTYyNjksIm5iZiI6MTc0NDMxNTk2OSwicGF0aCI6Ii8xNTE0ODAxMS80MzE5NzExOTctN2E2MjVlZWUtNjYyYS00ZTgyLWIzODgtYmQ5ZmEzMjU0MjU2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA0MTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNDEwVDIwMTI0OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTIxM2Q3YjQzOGQzYjk1MTliZjViYjc2YWY4Y2NhYWRhYzBjYzAzZjMwZjBlODMxMzI5ODNjMjQ5ZGI3ODhiMGUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.eUs8s2k22L8L2XUP9WqkKSJbG_8Mc1b9azJq7MWLzF0)	![Capto_ 2025-04-09_11-05-02_am](https://private-user-images.githubusercontent.com/15148011/431971132-2cf88ba4-7156-47be-bf1c-c756821728d2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDQzMTYyNjksIm5iZiI6MTc0NDMxNTk2OSwicGF0aCI6Ii8xNTE0ODAxMS80MzE5NzExMzItMmNmODhiYTQtNzE1Ni00N2JlLWJmMWMtYzc1NjgyMTcyOGQyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA0MTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNDEwVDIwMTI0OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ1NjU2YjVlODYxMjhmYmMzODI4MzU1ZTVjYmUyMzAwMDFkMjEzOWNlYTZjOTVlZGQwOWJkYWU2ODI0YzBiMjkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.4eNPft2iBYUY7UVtaNe53OOwCCOrKG8_xFJ6kcltPn0)

The simplified one is definitely better I think! We can even keep the two bullet points honestly, and bold the role names only that way.
author_association: COLLABORATOR
user: login: validbeck
created_at: 2025-04-10T20:15:08Z
body: Hm, it looks like the online preview is being fussy due to the merge conflict — might be why I didn't see some of the changes. I'll preview locally and review again.

**EDIT:** Nope, missed comments still apply. Sorry. 😆 
author_association: COLLABORATOR
user: login: github-actions[bot]
created_at: 2025-04-10T21:09:21Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR
user: login: nrichers
created_at: 2025-04-10T22:35:47Z
body: > **EDIT:** Nope, missed comments still apply. Sorry. 😆

Yup, I see the missed comment. Addressing them now, with an apology! 
author_association: COLLABORATOR
user: login: github-actions[bot]
created_at: 2025-04-10T22:44:05Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-10T23:03:21Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-10T23:14:09Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-10T23:20:53Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-10T23:38:15Z
body: # PR Summary
This pull request introduces a new feature related to attestations in the documentation. The changes include:

1. **New Attestation Section**: A new section for attestation has been added to the documentation, which includes guides on setting up attestations, completing attestation questionnaires, and reviewing attestation questionnaires.
   - **Glossary Update**: Added definitions related to attestation in the glossary.
   - **Guide Updates**: New guides have been added to explain the attestation process, including setting up attestations, completing questionnaires, and reviewing them.
   - **Mermaid Diagrams**: Updated the theme for Mermaid diagrams to enhance the visual representation of processes.

2. **Documentation Enhancements**: The documentation now includes detailed steps and prerequisites for each part of the attestation process, ensuring that users can follow along and implement the attestation feature effectively.

3. **Visual Assets**: Added new images and GIFs to support the attestation documentation, providing visual guidance for users.

These changes aim to provide a comprehensive guide for users to understand and implement the attestation process within the platform, supporting compliance and governance processes.

## Test Suggestions
- Verify that all new attestation guides are accessible from the documentation index.
- Check that the glossary includes the new attestation terms and definitions.
- Ensure that all links within the attestation documentation are functional and lead to the correct sections.
- Test the visual appearance of the Mermaid diagrams to confirm that the new theme is applied correctly.
- Review the images and GIFs to ensure they are correctly displayed and relevant to the content.
- Conduct a usability test with a user unfamiliar with the attestation process to ensure the documentation is clear and comprehensive.
author_association: CONTRIBUTOR
user: login: github-actions[bot]
created_at: 2025-04-11T00:17:58Z
body: A PR preview is available: [Preview URL](https://docs-demo.vm.validmind.ai/pr_previews/nrichers/sc-8587/explaining-attestation-to-our-users-initial/index.html)
author_association: CONTRIBUTOR