# Create and Finalize Documents

Source: https://sites.veevavault.help/gr/sitevault/eisf-ebinder/create-finalize/

This page will guide you to the Study eBinder uploading and approving steps, as well as provide an overview on the SiteVault tools that manage study document progress.

## Upload and Approve Documents in the Study eBinder

- To **upload OR upload and approve** documents in the Study eBinder, see [Upload, Approve, and Initiate Workflows on Documents](/gr/sitevault/eisf-ebinder/upload-final-wf/), located on the [eISF](/gr/sitevault/eisf-ebinder/) help tab.

## Approve Uploaded Documents in the Study eBinder

- To **approve uploaded documents** in the Study eBinder, see [Approve/Finalize Documents after Upload](/gr/sitevault/eisf-ebinder/finalize/), located on the [eISF](/gr/sitevault/eisf-ebinder/) help tab.

## Document Lifecycles, Workflows, and State Changes

The process of approving (finalizing) a document is accomplished by progressing the document from its _starting state_ (Draft) to its _steady state_ (Current, Final, etc.). SiteVault uses lifecycles, workflows, and state changes to complete this process.

- A document is assigned a lifecycle based on the **document type** that was assigned during upload.
- Documents move through a series of **lifecycle states** based on user actions (workflows, state changes, etc.).
- A workflow can include several steps, while a state change is a direct state-to-state action.
- **Draft** state typically require additional reviews, updates, or approvals.
- **Approved/finalized** documents (in steady state) are considered official study records, available for monitor reviews.
- Documents can be moved to a **Superseded** state when a newer version of the document has been finalized. This happens automatically when you stack document versions.

**Note:** If you need to add an updated version of a document that already exists in SiteVault, [upversion the document instead](/gr/sitevault/eisf-ebinder/version-stacking/).