> For the complete documentation index, see [llms.txt](https://docs.openetf.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openetf.xyz/how-it-works/risk-controls/mandate.md).

# Mandate (Coming soon)

**A Mandate (Coming soon) is a set of trading limits the Manager publishes, such as permitted assets, leverage, exposure and order types. Managed Execution checks every trade against the Mandate before signing.**

A Mandate is optional; an ETF can open to investors without one. The Manager chooses the limits, and each has explicit units and rules, so free text never becomes a limit. A Mandate shows that trades stayed inside published limits, not that the limits are prudent or the strategy profitable.

## Three states

* **Mandate: Active.** Every normal risk-changing path, whether the Trading Terminal, the OpenETF API or a contract method, is checked against the version in force. Recovery powers are limited to modeled, risk-reducing mechanisms, and any unrestricted contract method, or any upgrade that could take effect before a suspension, keeps the ETF from Active.
* **Mandate: Pending.** A published version is not yet in force.
* **Mandate: None.** The ETF has no Mandate.

## Loosening waits for notice; tightening applies at once

Tightening a limit can take effect at once. Loosening waits for a public notice period, and a notice period alone cannot authorize a material expansion of the risk scope disclosed at issuance. Switching a Mandate off follows the same wait as loosening, and while outside investors hold shares it can happen only through a holder governance path disclosed at issuance. No such path exists yet, so today a Mandate cannot be switched off while outside investors hold shares.

The [Passport](https://docs.openetf.xyz/transparency/passport.md) shows the version in force, its history and each decision made under it.

Next: [Who controls what](https://docs.openetf.xyz/how-it-works/control.md)
