> 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-it-specialists/payroll-export-configuration/resort-specific-info/alterra/pre-season-checklist.md).

# Alterra Pre-Season Checklist

Checklist for NEW Pre-Season tasks to complete for Alterra for 22/23 season

### Create Incentives&#x20;

Incentives are used for any pay above the base wage rates. Incentives are created in Admin Settings -> Product Settings -> Incentives&#x20;

* [ ] Create Lesson Incentives (applied to the paid activity)&#x20;
* [ ] Connect Lesson Incentives to Paid Activities in the Paid Activity setup
* [ ] Create Hourly Incentives (applied to the Instructor)&#x20;
* [ ] Connect Hourly Incentives to Paid Activities in Hourly Incentive setup
* [ ] Create Metric Rules \ <mark style="color:red;">\*For those using pay bumps\*</mark>
* [ ] Connect Metric Rules to Hourly Incentives (for those using pay bumps)\ <mark style="color:red;">\*For those using pay bumps\*</mark>

### Connect Paycodes & Business Structures &#x20;

Paycodes and Business Structures can Be Uploaded in Admin Settings -> Product Settings -> Timekeeping&#x20;

* [ ] Review Business Structures each season \ <mark style="color:red;">\*</mark>*<mark style="color:red;">Alterra is asked for new or changes to existing cost centers by finance teams at any time, it's advised you check each season that structures remain accurate\*</mark>*
* [ ] Upload Paycodes <mark style="color:red;">\*Provided by Alterra\*</mark>
* [ ] Upload Business Structures <mark style="color:red;">\*Provided by Alterra\*</mark>
* [ ] Consider whether you need to re-structure Paid Activities to align with Business Structures and Pay Codes offered&#x20;
* [ ] Connect Pay Codes to Paid Activities \ <mark style="color:red;">\*Not needed for external Punch In/Out\*</mark>
* [ ] Connect Business Structure to each Paid Activity
* [ ] Connect Paycodes to each Hourly Incentive
* [ ] Connect Paycodes to each Lesson Incentive&#x20;

### Update Permissions&#x20;

Permission Tiers can be updated in Admin Settings -> General Settings -> Roles and Permissions

Permissions can be updated for Instructors in Admin Settings-> General Settings -> Roles & Permissions, in Staff Management, in Talent Pool, or in the Instructor Profile&#x20;

* [ ] Update/Add Permission Tier for staff requiring access to: \
  1\. Add/remove Hourly Incentives manually \
  2\. View Metric Rules tab \
  3\. Approve/reject Metric Rules once calculated&#x20;
* [ ] Update the assigned Permission Tier for applicable staff&#x20;

### Existing Instructor Profiles in flaik

For existing flaik profiles - pre Workday integration launch

* [ ] Update Wage fields using Bulk Update \
  \*Teaching, Non Teaching, Training, Private Request (same wage as Teaching)\*
* [ ] Update Staff ID (Workday ID) \ <mark style="color:red;">\*flaik/Alterra can assist for existing profiles, contact Alterra for more details\*</mark>
* [ ] Update Wage Position IDs\ <mark style="color:red;">\*Alterra can assist, contact Alterra for more details\*</mark>

### Apply any start-of-season Hourly Incentives to Existing Staff&#x20;

* [ ] Apply starting Hourly Incentives in Staff Management using Add Hourly Incentive \
  \*i.e. any Hourly Private Request Incentive or other Hourly Incentives that start right away. These can be applied to all staff at the same time. If they have already had the incentive applied, no action is taken so it's ok to re-apply.

### New Hire Actions&#x20;

Until the Workday integration is implemented

* [ ] Add new hires to flaik using Add Staff - Add multiple staff template or Add single staff member (In Talent Pool or directly in Staff Management) \ <mark style="color:red;">\*Make sure First, Last, and email match Workday profile\*</mark>
* [ ] Populate Payroll ID field with Workday ID - can use Bulk Update Staff
* [ ] Populate Staff ID field with POS ID - can use Bulk Update Staff&#x20;
* [ ] Add Wage Position IDs \ <mark style="color:red;">\*Alterra can assist, contact Alterra for more details\*</mark>
* [ ] Apply any starting Hourly Incentives in Staff Management using Add Hourly Incentive&#x20;
* [ ] Apply Permission Tier if anything above default/Instructor is required&#x20;
* [ ] Invite staff in Staff Management to flaik to create a password and log into flaik in Staff Management -> Invites \
  \*Staff do not need to be invited to complete Availability\*&#x20;

{% hint style="info" %}

#### Questions?&#x20;

Alterra SRS//HRIS Dat Integration Sharepoint-> <https://alterramtnco.sharepoint.com/sites/SRS-HRIS>\
Workday HR/Payroll Knowledge Base ->\
<https://enterprise.alterra.support/support/solutions>

flaik Application Support -> <resortsupport@flaik.com>
{% 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-it-specialists/payroll-export-configuration/resort-specific-info/alterra/pre-season-checklist.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.
