> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/guardian/workspace/policies/policy-creation.md).

# Policy Creation

Policy creation in Hedera Guardian is the foundation for digitizing sustainability standards. It transforms rules into automated, transparent workflows, ensuring trust, compliance, and scalability in environmental asset management.

**Importance of Policy Creation**

1. **Standardization of Methodologies**
   * Digitizes environmental standards into consistent, enforceable rules.
   * Ensures all participants follow the same verified process.
2. **Transparency & Trust**
   * Anchors policy actions (VCs, approvals, tokens) to Hedera.
   * Creates an immutable, auditable trail of activities.
3. **Automation of Workflows**
   * Replaces manual verification with automated checks and triggers.
   * Reduces errors, costs, and administrative overhead.
4. **Interoperability**
   * Policies use W3C-compliant VCs and schemas, enabling global compatibility across registries, standards bodies, and marketplaces.
5. **Flexibility & Governance**
   * Supports versioning for methodology updates.
   * Allows controlled deprecation of outdated policies.
6. **Scalability**
   * Enables large-scale deployment of sustainability projects (thousands of projects under a single policy template).
7. **Regulatory Compliance**
   * Encodes the requirements of standards bodies into enforceable workflows.
   * Provides verifiable proof of compliance for audits and reporting.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guardian.hedera.com/docs/develop/guardian/workspace/policies/policy-creation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.