# BUCP Template

## Template: BUCP&#x20;

Use this Word document to draft your BUCPs. If needed, we will periodically update this based on feedback and include version notes.

{% file src="<https://266674908-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MiYc4Za0iAb9abALgXj%2Fuploads%2FlV65PG7qml52TtPE5Kmz%2FBUCP-Template-V1.0.docx?alt=media&token=787bee95-4967-4d3e-abc3-1b05a873a085>" %}

{% hint style="info" %}
Remember when you complete your BUCP to [submit to the Statewide Chief Data Officer](https://airtable.com/shrUMjZghIK1aAQqR)
{% endhint %}

## Template: Data Field Definitions Template

One of the best ways to improve data use is to provide data that is well-documented. The data field definitions table below will help both the Data Provider and Recipient develop a shared understanding of the data to be exchanged.

| **Field**     | **Description**                                                                                                                                                                                                                                                     |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Field Name    | What is a brief human readable name for the field? This should be unique and stated in the singular. Don't use abbreviations or acronyms.                                                                                                                           |
| Type          | What is the format of the data? Numeric, text, data and time, currency, boolean, coordinates, other.                                                                                                                                                                |
| Definition    | Define the field. State it as a descriptive phrase or sentence. Be precise, unambiguous and concise. Make it unique and state it in the singular. State what it is, not what it is not. Can it stand alone? Define units of measure (e.g. miles or meters or feet). |
| Required      | Yes or No. Is this field required or optional?                                                                                                                                                                                                                      |
| Valid inputs  | For categories, what is the list of allowable values? For date and numbers, what is the allowable range?                                                                                                                                                            |
| Source        | Defines how the data enters the system.                                                                                                                                                                                                                             |
| Notes         | Describe any known data quality issues or concerns.                                                                                                                                                                                                                 |
| Guide for use | Provide advice on how the field can be used.                                                                                                                                                                                                                        |

##


---

# 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://docs.data.ca.gov/interagency-data-exchange-idea-guidebook/resources-and-references/bucp-template.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.
