> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-administrators/season-switchover-blue-banner/sort-your-staff.md). # Sort your staff Sorting your staff is the final step to close out your current season and begin working in the upcoming season. Check out the video below to see what the staff sort process looks like! {% embed url="" %} {% hint style="warning" %} **Important:** Completing this step will close out your current season, converting it to historical data. The season will still be available to you via the [season selector](/flaik-knowledge-base/for-sups-managers/site-navigation/navigating-between-seasons.md), but past seasons cannot be edited. {% endhint %} Before you proceed, please review this checklist to make sure you're ready to close out your current season: > * [ ] Ski school operations have ended for the season? > * [ ] You no longer need to use Scheduling, Class Management, or Timekeeping until the start of your upcoming season? > * [ ] Training clinics are wrapped up? > * [ ] Evaluations have been completed for all your staff? Has everyone acknowledged their evaluation? Additionally, consider the range of usable dates for your upcoming season. For example, if you're a Northern Hemisphere resort operating in the winter, you will only be able to use dates from July 1st through June 30th the following year. If you end your current season, some features will not be usable in the upcoming season until *July 1st at the earliest.* {% hint style="warning" %} **For example:** Scheduling, Class Management, and Timekeeping are all date-bound and cannot be used earlier than July 1st in this scenario. Check the [table of usable date ranges](https://knowledgebase.flaik.com/flaik-knowledge-base/flaik-admin-settings-setup/season-switchover-blue-banner/set-up-your-new-season#usable-date-ranges) to see which are applicable for your resort. {% endhint %} ### Overview After you have ended your operations for the season, it is important to sort your staff to either Archived People or the Talent Pool in Hiring. Year-round staff will remain in Staff Management and they will still have access to their flaik accounts. {% hint style="info" %} The prompt to sort your staff will only appear after the season ends. This is based on the last day of the season specified in **Admin settings** -> **General settings** -> **Season dates** {% endhint %} The account holder will be the only user that is prompted in this way, but this process can also be done by other users manually in the Staff Management section. If you don’t see a blue banner, you can look up the account holder for your resort in **Admin settings** -> **General settings** -> **Account holder**. ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043132061376/original/bskZ3zKhos6RA71VAxFjJwnaHWQK7XubGw.png?1595975076) By moving the staff, all staff data will be preserved, it is only their access to the site that will be turned off for the season. ### **Step 1: Select your year round staff** Some of your staff work year-round, and will need to keep their access. This first page will allow you to designate who these users are, and will keep their accounts active in Staff Management. ![](https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2Fx3v8VQyT1CbNNTFUAu3W%2F2-1%20Year-round%20staff.png?alt=media\&token=67c371dd-3f47-4946-8cf8-e3476dae47b1) ### **Step 2: Sort your remaining staff** #### Recommended strategy Our recommended strategy is to sort staff based on their hiring recommendation which is completed during the evaluation process. We've included some examples below to explain where your staff should be moved to. | Staff you want to hire again | Staff you don't want to hire again | | ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | Staff with a hiring recommendation of **Hire**, **Conditional hire**, and **Not reviewed** should be moved to **Hiring**. | Staff with a hiring recommendation of **Do not hire should** be moved to **Archive**. | Cross referencing the hiring recommendation that was assigned during staff evaluation, you can move the staff member to the appropriate location. ![](https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FWAt5jmpPowvztTVUy90G%2F2-3%20Staff%20sort.gif?alt=media\&token=742268bd-1d99-4791-be3a-5c286e266f22) {% hint style="success" %} 🔥 Nice one! Now that your staff are sorted, you can jump straight into Hiring to get ready for the upcoming season. {% endhint %} --- # 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://knowledgebase.flaik.com/flaik-knowledge-base/for-administrators/season-switchover-blue-banner/sort-your-staff.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.