# 3. Create a Publishing Plan

Once your data systems and datasets are inventoried, the publishing priority of each dataset can be calculated. Prioritizing datasets is based on two dimensions:

* **Demand:** How valuable is the data? Do people often request to see or use it either through sunshine requests or informally? The higher the demand, the higher the dataset should be prioritized for publishing.
* **Classification:** Is the data classified as "Public" or are there "Sensitive" or "Protected" items included in it? The lower the classification, the higher the dataset should be prioritized for publishing.

{% hint style="info" %}
Unlike previous inventories, publishing priorities will be **automatically calculated** based on the grid below. You only need to specify a priority if you want to overwrite the decision matrix. For example, you think a "P2" dataset should actually be "P1"
{% endhint %}

### Decision Matrix

Below is a matrix to help decided how datasets should be prioritized.

<figure><img src="https://lh6.googleusercontent.com/tJ1iUdzJw1fc4gJSDKUic6BDXbT8blFOGYBn1rY8jaYllqfdI73_DSOjDkijPvIdzKuW4jgXi-Po9swbtaxK5DeiVZg65T_RLU6CeeoO40PNxW9AvFRuYjDdi-iJLTO5fNmyehE4Iv09oxlQwByKBYyQ5VHfow6WmQ_ke9vv4BBhFqwNFeSGpgLJv-or" alt=""><figcaption></figcaption></figure>

## Add the scores to your datasets

Under the **department priority field** field in the dataset inventory, you can add you new priority to you datasets based on the system listed above. Adding the department priority fulfills the requirement to develop a publishing plan.


---

# Agent Instructions: 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:

```
GET https://sfdigitalservices.gitbook.io/data-inventory-process/how-to-update-your-inventory/3.-create-publishing-plan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.