> 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/returning-resort-review.md).

# Returning resort review

Getting back up and running for the upcoming season? Use this checklist to ensure all systems are a go as the season approaches.

<figure><img src="https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FkrkVoDEqEinmGeurL4bT%2Funconditional%20surrender.jpg?alt=media&amp;token=ec05cca5-e67e-4a71-9d14-b7d0581f0418" alt=""><figcaption><p>Bill Watterson, January 13, 2015</p></figcaption></figure>

## Goals for revisiting flaik setup

*Wait, I already set flaik up last year! I gotta do it again?!*&#x20;

Well, not quite! But there are some areas we think you should revisit before you kick off your upcoming season. The weeks before your operations start may be the only quiet(ish) time you'll have to refine how your site works.&#x20;

The top three areas we think you should focus on are **Scheduling**, **Class Management**, and **Timekeeping**. These three features are the most impactful to your operation, so it's worth spending a little bit of time to maintain the settings that make these features tick.&#x20;

There's also some features that need to be set up fresh each season, such as Hiring and Availability. We've outlined some action items for those features, too. If you don't use Hiring and Availability, no worries, you can skip over those bits.

{% hint style="info" %}
Has it been a while since you logged in? Check out our [Changelog](/flaik-knowledge-base/welcome/changelog.md) to see what new updates and fixes have been released!
{% endhint %}

#### Why change things, though?

Year-over-year, your configuration in flaik can get bloated, as users tend to add new things without removing unused items. We recommend taking a hard look at the amount of shifts, tasks, and paid activities you're using and think about whether you can make any refinements, merge any like items, or take a more minimalist approach.

You can [use the season switcher](/flaik-knowledge-base/for-sups-managers/site-navigation/navigating-between-seasons.md) to flip back to a past season. This will show you a snapshot of your old config as well as how many times a specific item was used in the past. That last bit is crucial - if you created anything that didn't get used last season, you should consider removing it.&#x20;

## Before you get started

Now is a great time of year to run through your site's config before you start using it. Some things, like shifts and tasks, can only be altered *before* you start applying them to schedules. \
\
To start, we recommend browsing through admin settings (particularly product settings) and taking short notes of the different areas you might want to adjust before you start using flaik again. Once you're ready to start making changes, use the checklists below to stay organized.

## Prerequisites

* [Your upcoming season has been created](/flaik-knowledge-base/for-administrators/season-switchover-blue-banner/set-up-your-new-season.md) by your site's account holder.
* The account holder has [completed the staff sort](/flaik-knowledge-base/for-administrators/season-switchover-blue-banner/sort-your-staff.md) and closed out your previous season.

{% hint style="warning" %}
**Not able to sign in?** Your profile may not be in Staff Management. If your profile was moved into Talent Pool or Archived People, another member of your team will need to move your profile into Staff Management before you can sign in.&#x20;
{% 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/returning-resort-review.md?ask=<question>&goal=<endgoal>
```

`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.