> For the complete documentation index, see [llms.txt](https://docs.mathewscompany.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mathewscompany.com/dryer-operations/dryer-operations/maintenance/post-season-maintenance.md).

# Post-Season Maintenance

After the drying season, the following steps are recommended to put your dryer into a condition suitable for an extended period of non-operational time.

1. Disconnect all power and turn off the gas supply.
2. Perform one final cleaning of the dryer inside and out as previously explained in the Seasonal Cleaning section of the manual. Use a power washer on the outer panels if dirt has built up in hard-to-reach areas.
3. Open the plenum access doors and sweep out all foreign material.
4. Visually inspect all bearings to see if there is indication of one in need of replacement. Inspect the drive belts and chains and note if any are in need of replacement or lubrication.
5. Grease all fan motor bearings and fan bearings as recommended in the Lubrication section of the manual.
6. Use a vacuum cleaner to remove any dirt from the control cabinet.


---

# 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.mathewscompany.com/dryer-operations/dryer-operations/maintenance/post-season-maintenance.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.