HR Year End Procedures Checklist

Navigation: HR Setup & Maintenance > Setup Tables (Databases) > Location > Change

These are the times that the system uses when an employee’s schedule references AMS, AME, PMS, or PME).

The Location Clerk field can be used as a selection/filtering criterion on the following reports:

• Authorization Report

• Absence Costing Report

Use this option to narrow report results based on the assigned location clerk.

This field identifies the location’s Principal and is used in any product that supports task routing. It also appears in Attendance Management Web, where the Principal’s name is displayed at the top of the screen.

These fields are used to support automated communication in several areas:

• Attendance Management Web reminders

• Morning Absence Reports sent via email

• Manual Intervention Emails sent directly to schools (when not routed through a central dispatcher)

Ensure these fields are completed to enable proper delivery of system-generated notifications.

Update block times as needed if you are using the profile listed below:

• Related Setting: Substitute/Casual Dispatch Parameters Profile > Page 4 > Field: Location Break Times Category List

This setting works in conjunction with the Location Break Times defined in the system. To understand how this functionality works or to verify your setup, review the Location Database Maintenance page.

Purpose: If the district has new schools, add the school using the code obtained by the district’s finance department.

Additional Considerations when adding a location code.

Purpose: Use this process when a school or location has been closed and should no longer be active in the system. Soft-deleting keeps the location in the system for historical reference while preventing it from being used in future transactions.

Guidance:

1. Change the Status:

   • Navigate to the location record.

   • Set Status to “S” (Soft-Deleted).

2. Update the Location Code Type:

   • Change the Type to “*” (Do Not Use).

   • This prevents the location from being included in processes like Authorization Week creation.

Navigation: Assignments > Assignment Reports > Ending Assignment Report

Purpose: This report identifies employees whose assignments are ending within a specified date range and who do not have any future assignments scheduled in the system.

Key Uses:

• Helps track employees whose assignments are ending without a follow-up assignment.

• Ensures timely action—either by terminating the employee or by creating a new assignment.

Additional Feature:

• Recall Date Filter: Allows you to filter the report by employees who are on or off the recall list, providing more targeted results.

Purpose: To ensure that reports reflect the correct school year and avoid manual updates in the future.

Steps:

1. Review any reports that contain hardcoded start or end dates for the school year.

2. Update those dates to reflect the new year if necessary.

3. Whenever possible, replace exact dates with date keywords to make reports more flexible and reduce the need for yearly updates.

Navigation: Tools > Security & Setup > User Profile Maint - Tabbed > HRW, FRW, and PRW tabs.

Purpose: To ensure that reports using date keywords reflect the correct school year.

Steps:

1. Open the User Profile Maintenance screen.

2. Go to the HRW, FRW, and PRW tabs.

3. Update the school year dates used in the date keyword fields to match the new academic year.

Navigation: Tools > Security & Setup > User Profile Maint - Tabbed > Insights tab.

Purpose: To ensure that the "My Absences" and "Employee Absences" Power Tiles on the Insights dashboard reflect the correct school year when users select "Current School Year to Date."

Steps:

1. Open the User Profile Maintenance screen.

2. Go to the Insights tab.

3. Update the Start and End of School Year Month and Day fields to match the new school year.

Navigation: HR Setup & Maintenance > Profiles > User Specific Parameter Profile

The following fields are used in GL validation:

• Page 1, Field: Current Absence Year 

Enter the current school year. This value is used in the Absence and Leave application subsystems to determine which entitlement record to reference. It also serves as the default year on various screens and reports, and is used in GL validation during absence and dispatch costing.

• Page 3, GL Validation Year 

Enter the year currently used by Payroll. This year is used specifically for validating GL account numbers.

Navigation: HR Setup & Maintenance > Setup Tables (Databases) > Experience Year > Add

Navigation: HR Setup & Maintenance > Setup Tables (Databases) > Non Instruction Calendar > Change

Purpose: Set up or update calendars to reflect key dates for the school year. This ensures accurate processing in areas such as absence entry, dispatch costing, and seniority calculations.

Calendar Types to Review and Update:

• Statutory holidays

• District Professional Development

• Location Professional Development

• Teaching holidays

• Position Calendar

Important Notes:

• Calendars can be updated at any time once they are board-approved.

• While it’s not necessary to wait until year-end, it’s important to review and confirm accuracy during year-end processing.

Navigation: Dispatches > Automated Dispatch Profiles > ADS Profiles > ADS Absence Parameter Profile Menu > Parameter Changes

• Page 3 – Field: ADS Web Absence Entry – Number of Days in Past to Allow
  This field controls how far back users can enter absences. You can either:

  • Enter a number of days (e.g., 10) to allow entries that many days in the past, or

  • Enter a specific date in the format YYYYMMDD (e.g., 20240901) to restrict entries before that date.

  For example, to prevent teachers from entering absences before September 1 of the current school year, enter 20240901.

Navigation: Dispatches > Automated Dispatch Profiles > ADS Profiles > ADS Absence Parameter Profile Menu > Parameter Changes

• Page 3 – Field: ADS Web Absence Entry – Number of Days in Future to Allow
  This field sets how far into the future users can enter absences. You can either:

  • Enter a number of days (e.g., 30) to allow entries up to that many days ahead, or

  • Enter a specific date in the format YYYYMMDD (e.g., 20250630) to block entries beyond that date.

  For example, to prevent teachers from entering absences past June 30 of the current school year, enter 20250630.

You will know you have AMS if your school administrators have access to the core Atrieve system and they may have the ability to add/change/delete/authorize. Or, depending on the setup, they might just have authorize. This isn’t done from the web portal, but from the Atrieve client.

Navigation: Absences > Attendance Authorization (AMS) > Authorization Creation Process

Purpose: Use this process to create authorization weeks, which are required for absence entry and dispatch processing.

Guidance:

• If you're unsure where to start, choose a past date that you know has already been created (e.g., June 1). This helps ensure there are no gaps in your week-ending dates.

• As long as you don’t change the day of the week for the week-ending date (e.g., always use Sunday), the system will not create duplicates.

Troubleshooting Tip:

You may have missed this step if:

• A school reports an error like: “Invalid week ending date, not in authorization file.”

• Users using the binoculars lookup don’t see the expected week-ending date available for selection.

Purpose: Ensure that all users have the correct access to Atrieve, especially for tasks like weekly absence authorization.

Actions:

1. Submit Support Requests for Account Updates:

   • If existing users (e.g., principals, vice-principals, admin assistants) have moved to a new school, submit a request to update their location security in AMS.

   • Requests must come from management.

2. Request New Accounts:

   • For any new employees who require Atrieve access (e.g., for weekly authorization), submit a request as early as possible.

   • You will be asked to complete a form. If you already have a copy, you may reuse it—but be prepared to receive an updated version if the form has changed.

If your school administrators are using Attendance Management Web, they will access it from the web and see a screen like this. Instead of being able to manipulate the absences/dispatches, they must submit comments instead.

Navigation: Absences > Attendance Authorization (AMS) > Authorization Creation Process

Purpose: Use this process to create authorization weeks, which are required for absence entry and dispatch processing.

Guidance:

• If you're unsure where to start, choose a past date that you know has already been created (e.g., June 1). This helps ensure there are no gaps in your week-ending dates.

• As long as you don’t change the day of the week for the week-ending date (e.g., always use Sunday), the system will not create duplicates.

Troubleshooting Tip:

You may have missed this step if:

• A school reports they are seeing “no dates” in the date drop-down menus.

Navigation: Absences > Attendance Authorization (AMS) > Daily Absence/Dispatch Review Record Creation

Purpose: This process creates daily records used for reviewing absences and dispatches. These records are essential for proper functioning of Attendance Management Web.

Guidance:

• If you're unsure where to start, choose a past date that you know has already been created (e.g., June 1).

• The system will not create duplicates if you select dates that already exist.

• This helps ensure there are no gaps in your week-ending dates.

Troubleshooting Tip:

You may have missed this step if:

• A school reports they are seeing “no dates” in the date drop-down menus.

Navigation: Absences > Attendance Authorization (AMS) > Daily Absence/Dispatch Review Record Mass Update

Purpose: Use this process to automatically mark specific days (e.g., weekends or stat holidays) as reviewed, so schools don’t have to manually review them.

Steps:

1. After creating your Daily Review Records, run the Mass Update Review Status process.

2. In the Day Type to Update field, choose one of the following options:

   • S – Stat holidays only

   • W – Weekends only

   • B – Both weekends and stat holidays

   • A – All days (not recommended, as it marks every day as reviewed)

Tip: Avoid using option A unless you are certain all days should be marked as reviewed.

Navigation: Dispatches > Automated Dispatch Profiles > Automated Dispatch Profiles > ADS Profiles > ADS Group Profile Report
(Use this report to identify your dispatch groups, then go to ADS Group Profile to make changes.)

Purpose: Temporarily disable automated dispatching during the summer months.

Steps:

1. Identify the relevant dispatch groups using the ADS Group Profile Report.

2. In the ADS Group Profile, update the callout times for each group you want to pause:

   • Set Callout Start Time and End Time to 2400–2400.

   • This effectively disables callouts without affecting callbacks or other settings.

Navigation: Dispatches > Automated Dispatch Utilities > Maintenance Utilities > Name Recording Status Update

Purpose: Refresh the system flag that indicates whether an employee has recorded their name in ADS.

Why it Matters:

• This status is displayed on the following reports:

  • Replacement Employee Availability Report

  • Substitute/Casual Call Out Report

• Keeping this information up to date ensures accurate reporting and helps identify employees who still need to complete their name recording.

Tip: Run this utility periodically, especially before the start of a new school year or major dispatch cycle.

Navigation: Dispatches > Refusals > Refusal Count Reset Process

Each time a replacement refuses an assignment; their refusal count is increased by one. The system uses this count to determine when a replacement should be marked as inactive.

The refusal limit is set in the ADS Group Profile. To review or update this setting:

1. Go to Dispatches > Automated Dispatch Profiles > Automated Dispatch Profiles > ADS Profiles.

2. Run the ADS Group Profile Report to identify the relevant groups.

3. When ready to make changes, open the ADS Group Profile.

4. On Page 1, locate the field labeled “Number of Refusals Before Rep Employee Becomes Inactive” and update as needed.

Navigation: Dispatches > Substitute/Casual Preferences > Preference Report

Purpose: Ensure that replacement employees (e.g., substitutes or casual staff) have up-to-date preferences and qualifications in the system.

Actions:

• Run the Preference Report to review current settings.

• Make any necessary updates using:

  • Quick Entry Screen, or

  • Preference Changes screen.

Efficiency Tips:

• Consider creating a dashboard report to share with replacement employees, showing their current preferences and qualifications.

• You can also allow employees to update their own preferences using HR Workflows, with approval routing if required.

Navigation: Dispatches > Automated dispatch Profiles > Search Parameters > Search Phases > Phase One and Two Maintenance

Purpose: Ensure that only appropriate employees are prioritized in Phase 1 and Phase 2 of the dispatch process.

Actions:

• Review both Phase 1 and Phase 2 lists.

• Remove any employees who should no longer receive priority dispatching.

Important: Your Phase 1 list might be generated automatically based on seniority.
If you know this is the case or if you see a large number of employees listed, do not make any changes without first consulting PowerSchool Support.

Navigation: Dispatches > Employee search Criteria > Criteria Changes

Purpose: To ensure that permanent preferred replacement lists are accurate and up to date.

Optional Actions:

• Create a report using HR Report Writer to review existing data using the PERM_EMP_SEARCH_CRITERIA table and REQUESTED_EMP_##_NAME fields. Use the SECURITY_EMPLOYEE_NO from NAME_AND_SIN table in selection fields to secure by employee

• Place the report on employee dashboards so they can review their own lists and make requests for changes if needed.

Efficiency Tip:

• If you use HR Workflows, allow employees to update their own preferred substitute list, with optional approval if needed.

Navigation: HR Setup & Maintenance > E-Forms > Routing Authorizer Codes

Purpose: Ensure that task routing remains accurate by reviewing and updating authorizer assignments, especially those tied to specific employees.

Key Points:

• Some authorizers may be linked to a specific employee number rather than a position code.

• If any of those employees change roles or leave the district, the authorizer setup must be updated to avoid routing issues.

Recommended Reports:

There are a couple of reports available on the PowerSchool Community -  to help with this process. 

1. Review Task Authorizers – Year End Process

   • Identifies authorizers set up by employee number.

2. Routing Detail – Year End Process

   • Shows which form types or products (e.g., Leave Management, HR Workflows) are using each authorizer code.

   • Use this report to determine if a code is shared across multiple products and coordinate changes with the appropriate teams.

Navigation: HR Setup & Maintenance > E-Forms > Location Authorizers

Purpose: Ensure that location-based authorizers are still valid, especially if they are tied to specific employee numbers.

Key Points:

• In addition to general authorizer codes, your district may have location-specific authorizers assigned by employee number.

• This setup is most commonly used in Schedule Entry Web.

• If any of these employees have changed roles or left the district, the authorizer records should be reviewed and updated accordingly.

Navigation: HR > Reporting > HR Report Writer (New) > Task Reports > Supervisor Report

Purpose: Ensure that all employees have a correctly assigned supervisor for the new school year. This is critical for task routing, such as leave approvals and expense approvals.

When to Run: After all new year assignments have been entered.

What to Check:

• Each employee has a calculated supervisor.

• The correct supervisor is assigned based on their current assignment.

Tip: Verifying this now helps prevent routing errors in systems that rely on supervisor relationships.

Navigation: HR Setup & Maintenance > Setup Tables(Databases) > Posting Segment 02 (or whichever segment number you use for school year) > Add

Purpose: To create a new school year entry in the Posting Segment database so it can be selected when adding job postings.

Steps:

1. In the Posting Segment database code, create a new entry for the upcoming school year.

2. Use the lookup feature to review how previous years were formatted.

3. Follow the same format to maintain consistency across years.

Navigation: HR Setup & Maintenance > System Setup > Web Application Setup > Web Screen Changes

Purpose: To update the default school year that appears on the web application for job postings.

Steps:

1. Update the B1, B2, and B3 web screens if applicable. These correspond to Teaching, Support, and Other application types.

2. In each screen, update the Posting Number Segment 2 Year field to reflect the new default year you want to appear on the web.

Navigation: HR Setup & Maintenance > Setup Tables (Databases) > Posting Segments > Change > select the segment associated with school year (e.g. Segment 02)

Purpose: To set the default school year that will automatically appear when adding new job postings.

Steps:

1. In the selected segment, locate the field labeled Default Value.

2. Enter the appropriate year in this field.

3. This value will automatically populate when using Job Posting Additions.

Navigation: HR Setup & Maintenance > E-Forms > Form Initiation Code > Form Initiation Code Changes

Purpose: To update the prefix used in automatically generated job posting numbers for the new school year.

Steps:

1. Select the E-Form type labeled STAFF REQ.

2. Go to Page 5 of the form setup.

3. In the field for Posting Auto Number Prefix, update the year portion to reflect the new school year.

4. Keep the letter portion of the prefix unchanged. For example, if the current prefix is T2425, update only the numbers and keep the T.

Navigation: HR Setup & Maintenance > E-Forms > Form Initiation Code > Form Initiation Code Changes

Purpose: To update the default posting and closing dates that appear when initiating a staffing requisition.

Steps:

1. Select the E-Form type labeled STAFF REQ.

2. Go to Page 5 of the form setup.

3. Update the default posting and closing dates as needed.

4. These fields may be left blank if no default dates are required.

Navigation: Demographics > Certifications and Training > Certificates > Certification Report

Purpose: This report allows you to extract certification records based on expiry date (e.g., August 31, 2025), helping you identify employees with upcoming expirations.

Alternative Options:

• Use HR Report Writer to create a custom report.

• Use the Insights – Certificates Expiring Power Tile for a quick visual overview.

Navigation: Demographics > Evaluations and Discipline > Evaluation Supervisor Mass Update

or: Demographics > Evaluations and Discipline > Evaluation Changes to manually change evaluation supervisors.

Purpose: This module allows you to replace a specific supervisor with another across all incomplete evaluations. You can run the process in preliminary (preview) mode to review the changes before applying them.

Navigation: HR Setup & Maintenance > Profiles > User Specific Parameter Profile

• Page 1 – Field: Current Absence Year
  Enter the current school year (e.g., 2024). This field is used by the Absence and Leave application subsystems to determine which entitlement record to reference. It also serves as the default year on many screens and reports, and is used in GL validation during absence and dispatch costing.

Additional Guidance:

• Complete this field if you are using Entitlements or FTE Allocation.

• There is no harm in filling it out annually, even if you're not using these features.

• The Allocation module uses this year as a default when running reports in Atrieve or during the FTE Allocation Import process. This value can be overridden if needed.

Important Notes:

• If you are not using PRM absence entitlements, you can update this field when you're ready to load or report on new allocations.

• If you are using PRM entitlements, do not update this field until you're ready to begin using the next year's absence entitlements.

Navigation: Assignments > FTE Allocation > Year To Year Copy

Make changes as needed.

Navigation: HR Setup & Maintenance > Profiles > User Specific Parameter Profile

• Page 1 – Field: Current Absence Year

Purpose:

• This value is used by the Absence and Leave application subsystems to determine which entitlement record to reference. It also serves as the default year on many screens and reports. Additionally, this year is used during GL validation for absence and dispatch costing.

• Action
  Enter the current school year (e.g., 2025).

Navigation: Absences > Entitlements > Entitlement Creation Process

Steps:

1. Run the Load Used Process to capture used entitlement amounts.

2. Run the Carry Over Load Process to transfer remaining entitlement balances into the new year.

Navigation: HR Setup & Maintenance > Profiles Menu > User Specific Parameter Profile

• Page 2 – Field: Employee Transfer Request Year
  Complete this field if your organization uses the Employee Transfer Request Menu.

  This year value is automatically applied when adding, changing, or deleting transfer requests for the selected year. To work with a different year in these programs, you must update this field in the profile.

Navigation: HR Setup & Maintenance > Profiles Menu > User Specific Parameter Profile

Page 1, Field: Current School Draw Time Year

Fill in if the Location Draw time menu if you are using the draw time module to track additional allocated time for non-teaching staff.

Navigation: HR Setup & Maintenance > Setup Tables (Databases) > Location Draw Time Maintenance > Add