> For the complete documentation index, see [llms.txt](https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/vci-help/the-evaluation-summary/saving-an-evaluation-summary/saving-as-a-provisional-interpretation.md).
# Saving as a Provisional Interpretation
### **How to Save as Provisional**
Upon saving a classification and/or changing/updating the Evidence Summary text the ‘Save’ button will change to an ‘Edit’ button and a “Save Interpretation as Provisional” section will appear.
**A.** Click 
to make further edits to the Evaluation Summary
**B. ClinGen Affiliation:** If the curator is curating as part of an Affiliation, this field will display that affiliation. If not curating as part of an Affiliation, it will display "**--**"
**C. Provisional Classification entered by:** Field will auto-populate with curator's name after clicking "Preview Provisional"
**D. Date Reviewed:** Field will auto-populate with current date. Curator may also enter a date manually (MM/DD/YYYY) or select from the calendar. Note: Dates in the future should never be selected!
**E. Additional Comments:** Optional field for capturing additional notes about the review process
**F.** Click 
to initiate the process for Provisionally Saving the Interpretation
### **Provisional Preview**
{% hint style="warning" %}
Once an Interpretation has been Saved as Provisional this action cannot be undone. However additional edits can be saved as a new Provisional snapshot.
{% endhint %}
In preview mode, the curator has three options:
1. **Cancel Provisional** Returns to prior view and cancels the Saving as Provisional process. Any additional comments will be deleted, and the Date reviewed returns to the current date.
2. **Edit** Returns to prior view and allows the curator to go back and correct any errors. Additional comments and date changes are saved.
3. **Submit Provisional** Permanently saves the current Interpretation as a Provisional Interpretation
#### **Current New Provisional**
Upon Saving a new Provisional Interpretation it will appear at the top of the "Saved Provisional and Approved Interpretation(s)". The current Saved Provisional Interpretation will always be marked with a green flag.
#### **New Saved Provisional Interpretations**
Every time a curator updates an Interpretation (e.g. new evidence, new evaluations, etc.) they can choose to Save the updates by clicking the Save button in the Evaluation Summary. They will then be invited to Save that new Interpretation as Provisional.
#### **Archiving Provisional Interpretations**
Upon Saving a New Provisional Interpretation then that will now be the new current Saved Provisional and will appear at the top of the "Saved Provisional and Approved Interpretation(s)" panel and be marked with a green flag. The previous current saved Provisional Interpretation will now become archived, and its green flag will be replaced with a grey archive box.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/vci-help/the-evaluation-summary/saving-an-evaluation-summary/saving-as-a-provisional-interpretation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.