What an RFP should say about school HR and payroll

Define the RFP’s operational case

An RFP should explain the problem and outcome: reliable employee and contract records, timely approvals, accurate payroll, reconciled payments, understandable payslips, controlled access, useful reporting, resilient operations, or lower processing effort.

State employees, positions, contracts, time, leave, absence, pay elements, campuses, entities, locations, currencies, banks, benefits, periods, reports, integrations, local requirements, retention, and exit.

Make requirements testable

For each requirement, include user, scenario, input, expected output, calculation, approval, permission, audit event, evidence, acceptance test, owner, support route, limitation, and priority.

Require normal payroll and new starter, leaver, changed hours, contract change, unpaid leave, absence, overtime, allowance, deduction, retroactive change, bank change, reversal, failed payment, correction, and off-cycle scenarios.

Request evidence and responsibility

Ask suppliers to label answers available, configurable, dependent, manual, roadmap, unsupported, or not evidenced. Require implementation, migration, integration, training, support, privacy, security, records, accessibility, backup, recovery, and exit details.

Separate vendor capability from school responsibility, local employment or tax advice, policy, professional judgement, bank relationship, employee communication, and legal review.

Evaluate after award

Keep assumptions, evidence, costs, limitations, risks, acceptance, owner, and review date. At 30, 60, and 90 days, compare delivered behaviour with payroll variance, correction time, approval delay, employee questions, processing effort, support demand, access exceptions, and outcome.

The U.S. Department of Education checklist offers governance prompts around quality, access, security, lifecycle, sharing, disposal, and monitoring, not a universal payroll certification.

Make the next improvement testable

Use this guidance to improve one bounded part of what an RFP should say about school HR and payroll software. Name the owner, workforce record, evidence, correction route, and review date so staff can apply it consistently.

Check an ordinary payroll case and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, validation rule, permission, approval, training note, or support route.

Record what changed, what remains manual, and who reviews the result before the next HR, payroll, payment, or reporting cycle.

Keep the decision beside its evidence so the next HR or payroll colleague can understand the rule without relying on informal memory.

Use the review to decide whether the change should be expanded, repaired, narrowed, consolidated, or held.

Recheck the boundary when an employee group, contract, pay element, entity, location, bank, benefit, integration, calendar, or local requirement changes.