# Working with Planned Documents

Vault can create _Planned_ state documents in several ways, but it does so most often when you create a binder from a template that includes documents. Vault automatically assigns these documents to the _Planned_ lifecycle state, rather than the lifecycle's _Starting_ state. Planned documents differ from other documents in two ways: they do not have a source file and you are not always required to populate required fields for them.

Depending on your Vault's configuration, certain documents may begin in <a href="/en/gr/14560/#planned_starting">_Planned_ state</a>, rather than the lifecycle's _Starting_ state.

## Available User Actions

Most actions that are available for documents in other states are also available for _Planned_ state documents. Admins can configure user actions in the _Planned_ lifecycle state to start workflows or move the document to a new state, as they can for other states. The following actions are available:

  * Edit Document Fields
  * Edit Sharing Settings
  * Make a Copy
  * Delete Renditions
  * View Audit Trail
  * Access Where Used View
  * Download Source File
  * Change Coordinator
  * Delete Document

Some actions (mostly related to the source file) are not available for _Planned_ state documents:

  * Check Out
  * Check In
  * Upload New Version
  * Create Draft
  * Edit through Collaborative Authoring
  * Re-render Document
  * Reclassify
  * Annotate

### Planned State with Document Role Permissions

Note that some actions are not available for _Planned_ state documents, regardless of whether or not you have the correct <a href="/en/gr/2572/">document role permissions</a>. Unavailable actions include:

<table class="wbord" style="width: 660px;">
  <tr>
    <td style="width: 428px;">
      <strong>Actions</strong>
    </td>
    <td style="width: 240px;">
      <strong>Document Role Permission</strong>
    </td>
  </tr>
  <tr>
    <td style="width: 428px;">
      <ul>
        <li>
          Create a new draft of the document
        </li>
      </ul>
    </td>
    <td style="width: 240px;">
      Version
    </td>
  </tr>
  <tr>
    <td style="width: 428px;">
      <ul>
        <li>
          Annotate document
        </li>
      </ul>
    </td>
    <td style="width: 240px;">
      Annotate
    </td>
  </tr>
  <tr>
    <td style="width: 428px;">
      <ul>
        <li>
          Check document in or out
        </li>
        <li>
          Upload a new version
        </li>
      </ul>
    </td>
    <td style="width: 240px;">
      Edit Document
    </td>
  </tr>
  <tr>
    <td style="width: 428px;">
      <ul>
        <li>
          Delete viewable rendition
        </li>
        <li>
          Re-render document to create viewable rendition
        </li>
        <li>
          Upload viewable rendition
        </li>
      </ul>
    </td>
    <td style="width: 240px;">
      Manage Viewable Rendition
    </td>
  </tr>
  <tr>
    <td style="width: 428px;">
      <ul>
        <li>
          Modify the type, subtype, and classification of the document
        </li>
      </ul>
    </td>
    <td style="width: 240px;">
      Reclassify
    </td>
  </tr>
  <tr>
    <td style="width: 428px;">
      <ul>
        <li>
          Change the user assigned to the document owner role
        </li>
      </ul>
    </td>
    <td style="width: 240px;">
      Change Owner
    </td>
  </tr>
</table>

## Required Fields

The _Planned_ state has special behavior for fields that are normally required for a document type. When Vault creates _Planned_ state documents automatically during binder creation, there are no required fields.

However, when creating a single document in _Planned_ state or when editing fields for an existing document, Vault uses these rules:

  * If the field is required because of the document type configuration, you can skip it.
  * If the field is required because of field dependency rules, you must enter a value.

You don't need to know which rule applies to each required field. Vault ensures that you populate any required fields on a _Planned_ document before saving.

## Auto-Populated Fields for Binder Documents

Planned documents created from a binder template automatically inherit values for certain document fields from their binder. For example, if a binder has the study _CC-938_, product _CholeCap_, and the review date (custom field) _3/1/2015_, planned component documents will have the same values for the **Study**, **Product**, and **Review Date** fields.

Fields auto-populate if:

  * The field is either a standard object-type field or a custom field.
  * The field applies to both the binder's document type and the document's.
  * The field is not blank on the binder.
  * The user has the _Edit_ permission for the field. If the user does not have the _Edit_ permission, the field is blank in the created planned document.

If a <a href="/en/gr/592/">field configuration</a> includes a default value, Vault uses the binder's value, rather than the default.

## Moving to Starting State

To change the state from _Planned_ to a different state, an Admin must configure one or more user actions that you can access from the **Actions** menu. Terminology in the menu may vary depending on your Vault's settings.

When you move a document out of _Planned_ state, the document must fulfill all entry criteria for the new state (required fields, etc.) or Vault will prompt you to do so.

## Deleting Planned Documents

Many documents in the _Planned_ state belong to at least one binder. In order to delete these documents, you must have **Edit Document** permission for every binder that includes the document.