> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/user-guide/workflows/moisture/initial-conditions.md).
# Initial Conditions
## Start Month
Select the Start Month as wither Winter (May 1st) or as a Custom Start Month.
## Initial Temperature
Configure initial moisture content, Defaults to 20°C.
## **Initial Moisture**
Configure initial moisture of materials at beginning of assessment.
### Relative Humidity
Configure Relative Humidity % of all materials at beginning of assessment.
### Water Content
Configure Water Content kg/m³ of all materials at beginning of assessment.
### Saturation Ratio
Configure Saturation Ratio %, the fraction of the maximum water content (w\_max), of all materials at beginning of assessment.
### Equilibrium Water Content
Configure Equilibrium Water Content, referencing relative humidity of the equilibrium moisture content (adsorption reference), of all materials at beginning of assessment at EMC 80 or 90% against multipliers.
## Detailed Initial Moisture
Configure Detailed Initial Moisture content of any material.
---
# 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://docs.betterbuilding.io/user-guide/workflows/moisture/initial-conditions.md?ask=&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.
