A school-based services nonprofit pays ten-month staff over twelve months. Its pay spread lived in a fragile spreadsheet until CloudApper added a pay spread engine to UKG Ready that splits school-year earnings evenly across every pay period, recalculates mid-year changes automatically, and keeps summer paychecks predictable for staff.
Every June, a school-based services nonprofit faces the same payroll question. Its counselors, aides and program specialists work inside partner schools, so when classrooms close, their hours stop. Their paychecks are expected to keep coming through July and August. The organization runs time and payroll on UKG Ready. What it needed was a reliable way to take ten months of earnings and pay them out over twelve. CloudApper built that calculation as an extension on top of UKG Ready, and the spreadsheet that used to do the job has been retired.
Why Pay Spreading Lived in a Spreadsheet
Pay spreading sounds simple until you run it for a few hundred people. Each employee’s school-year earnings have to be projected, divided across every pay period in the year, and adjusted whenever something changes: a mid-year hire, a February raise, a leave of absence, a resignation in April. That logic is a custom business rule specific to the school calendar, so the payroll team kept it in a workbook and rebuilt and checked it by hand before every cycle.
As the Payroll Manager at the nonprofit put it, “The workbook was the most important file in our department, and only two of us really understood how it worked.”
Mistakes were expensive. An underpaid employee came up short in summer, and one who left mid-year might have been paid ahead of hours worked.

Building the Pay Spread Engine on Top of UKG Ready
CloudApper connected a custom pay spread engine directly to the organization’s UKG Ready environment using CloudApper AI for UKG Personalization. The engine reads each employee’s school-year earnings from UKG Ready, calculates an even distribution across all pay periods, including the summer months when no hours are recorded, and writes the result back into UKG Ready before payroll runs. UKG Ready stays the system of record, and the payroll team reviews everything in the screens they already use.
“We didn’t want another system to log into. The calculation happens where our payroll already lives, and we review the result the same way we review everything else.”
Director of Human Resources, school-based services nonprofit
CloudApper has used the same pattern for other custom earnings rules, from piecework pay at a large manufacturer to retro pay corrections. The business rule lives in a dedicated engine, and the payroll record stays in UKG.
What Changed for Payroll and for Staff
The workbook is gone. When a rate changes mid-year, the engine recalculates the spread for the remaining periods on its own. Payroll errors tied to the spread dropped, and the team got back the hours it used to spend reconciling before each cycle.
“Summer used to be when we found our mistakes. Now it’s just another pay period.”
Finance Director, school-based services nonprofit
For employees, the result is predictable income. Many school-based staff are hourly or modestly paid, and a short check in August is a real problem for a household budget.

“My team stopped asking whether their summer checks would be right. That question used to come up every spring.”
Program Operations Manager, school-based services nonprofit
The Lesson for Every School-Calendar Employer
School districts, education nonprofits and contractors that place staff in schools all run on the same calendar. Many already use UKG for time tracking across school buildings and regional substitute and absence management. Pay spreading is often the last school-calendar process still running outside the platform.
If that describes your organization, start with three questions. Who owns the spreadsheet today, and what happens if they leave? How does the spread respond to a mid-year rate change? And how are hours outside the base schedule handled? Under the federal overtime rules, overtime generally has to be paid on the regular payday for the period in which it was earned, so any spread logic needs to keep deferrable base pay separate from overtime that has to be paid right away. CloudApper builds that kind of rule into the engine itself, not into a workbook.
If your organization pays school-year staff over twelve months and the math still lives in a spreadsheet, talk to CloudApper about extending UKG Ready to handle it automatically, without changing how your payroll team works.




