> For the complete documentation index, see [llms.txt](https://help.tillit.cloud/tillit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tillit.cloud/tillit/planning/data-gathering/materials.md). # Materials **Start with a comprehensive analysis of all the materials involved.** This includes raw materials, finished goods, intermediate materials, and consumables. By documenting each material, you can create a complete inventory of your production inputs, which can be valuable for managing costs and identifying opportunities for optimisation. Once you have recorded each material, group them into Material Groups such as raw materials, semi-finished, finished goods, and packing materials. This provides a more organised structure for tracking and monitoring materials throughout the production process. **As you evaluate each type of material, also record any attributes and tolerances that may be associated with them.** For example, certain raw materials may have specific requirements for temperature, humidity, or storage conditions. By documenting these attributes and tolerances, you can ensure that materials are properly handled and monitored throughout the production process. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.tillit.cloud/tillit/planning/data-gathering/materials.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.