> ## Documentation Index
> Fetch the complete documentation index at: https://docs.snaplabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set contract defaults

> Give AI your house rules for deletes, history, duplicates, late-arriving rows, money, time zones, the business calendar and the load schedule once, for every contract in a project.

## What you're building

Most teams answer the same questions on every table. What happens to a row deleted at the source? Do dimensions keep every version of a changed row? Which row wins when two share a key? Contract defaults let you answer each of these once for the whole project. When AI [writes a contract](https://docs.snaplabs.ai/guides/draft-and-approve-a-data-contract.md), it follows them, so you stop answering the same question table after table.

Defaults are house rules, not locks. You can still decide differently for one table.

## Set the defaults

1. Open a project, then click **Settings** at the bottom of the sidebar.
2. Click **Contract defaults**. It is unavailable until a project is open.
3. In **Contract defaults**, choose a value for each rule you want to set. Leave the rest on **Not set**.
4. Click **Save**. You see **Contract defaults saved**.

You can also open the same window from a new contract. The **Project defaults:** row has an **Edit** link. When none are set, click **Set defaults** beside **No project defaults set.**

**Save** stays unavailable until you change something, and **Cancel** closes the window without saving. If the saved defaults cannot be loaded, the window closes and you see **Failed to load contract defaults. Please try again.** so you cannot save an empty form over them.

Every row can take an optional note under **Add a note (optional)**, up to 500 characters. AI reads it along with your choice, so use it for the detail the choice cannot carry. A note that is too long shows **Keep the note under 500 characters.**

## The eight defaults

| Default | What it decides | Choices |
| - | - | - |
| **Deletes** | What happens to a row when it is deleted at the source. | **Ignore deletes**: the row stays as last loaded. **Mark as deleted**: the row is kept and flagged as deleted. **Remove the row**: the row is removed. |
| **Dimension history** | How dimension tables handle changed values. | **Overwrite with the latest value**, or **Keep every version** of a changed row. |
| **Duplicate tie-breaker** | Which row wins when several rows share the same key. | **Latest source change**, **Latest load**, or **Described in the note**. |
| **Late-arriving rows** | What a row points to when the row it looks up has not arrived yet. | **Unknown member**, with an **Unknown member key** such as `-1`. Or **Inferred member**, a placeholder row that is completed when the real one arrives. |
| **Money** | How amounts and currencies are stored. | **Keep the source currency**, or **Convert to a reporting currency**, with its **Currency** such as `USD`. Either can set **Decimal places**, from 0 to 8. |
| **Time zones** | Which time zone timestamps are stored in. | **UTC**, **Source time zone**, or **A named time zone**, with its **Time zone** such as `Europe/London`. |
| **Business calendar** | When weeks and fiscal years start, for date and fiscal columns. | **Weeks start on Monday** or **Weeks start on Sunday**, with an optional **Fiscal year starts in month**, a number from 1 to 12. Left empty, the fiscal year is the calendar year. Business days are Monday to Friday, and no day is a holiday unless a source holds a holiday calendar. |
| **Load schedule** | How often every table is loaded. | **Every hour**, **Every day** or **Every week**. The hand-off prompt asks the agent to schedule the loads. |

Some choices need one more value, and the window shows it only when that choice is picked:

* **Duplicate tie-breaker** set to **Described in the note** needs the note to say which row wins. Without it you see **Describe which row wins.**
* **Unknown member** needs a key. You see **Enter the key unknown members use, such as -1.** until you give one.
* **Convert to a reporting currency** needs a three-letter code: **Enter a three-letter currency code such as USD.** A decimal places value outside 0 to 8 shows **Use a whole number from 0 to 8.**
* **A named time zone** needs a real zone name: **Enter a time zone such as Europe/London.**
* **Fiscal year starts in month** takes a month number: **Use a month number from 1 to 12.**

If a row has an error, nothing is saved. You see **Please fix the highlighted defaults and try again.** and each row that needs attention says why. Picking **Not set** on a row removes its default.

## How a contract follows your defaults

Defaults apply to each project on its own and reach every contract in it.

* **AI follows them.** When it writes a table, the defaults you set are part of what it is given. On the table, a line that follows a default reads **Your house rule** under it.
* **Deletes and Dimension history are always kept.** AI cannot write a table that contradicts them. For history, that applies to dimension tables. If a draft would, AI writes it again until it fits.
* **The other six guide the wording.** **Duplicate tie-breaker**, **Late-arriving rows**, **Money**, **Time zones**, **Business calendar** and **Load schedule** shape what AI writes, but they are not checked line by line, so read those lines as you would any other.
* **A row left on Not set is up to AI.** It decides from the sources and asks you a question when it cannot tell.

## Override a default for one table

A default never stops you. To do something different on one table:

1. Open the table in the contract and find the line, for example **If a source row is deleted** on a dimension.
2. Click **Change** to change it yourself, or **Ask AI instead** in the editor and say what should change. See [Change a line](https://docs.snaplabs.ai/guides/draft-and-approve-a-data-contract.md#change-a-line) and [Ask AI to change a line](https://docs.snaplabs.ai/guides/draft-and-approve-a-data-contract.md#ask-ai-to-change-a-line).

The line then reads **You changed this** and keeps your choice for that table. Other tables still follow the default.

## When you change a default later

Defaults are read when a contract is written, so changing them does not rewrite a contract by itself. Open the contract and the status bar says the contract's inputs changed, with **Update contract**. Click it. **What changed** then lists **Changed the Contract defaults.** and the lines the new defaults affect are written again. Your own changes are kept. An approved version stays as it was until you approve again. See [Update a data contract](https://docs.snaplabs.ai/guides/update-a-data-contract.md).

## What's next

* [Draft and approve a data contract](https://docs.snaplabs.ai/guides/draft-and-approve-a-data-contract.md)
* [Update a data contract](https://docs.snaplabs.ai/guides/update-a-data-contract.md)
* [Create an artifact](https://docs.snaplabs.ai/guides/create-artifact.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.