ERP Selection for K-12 School Districts (8-Step Process)
On this page
- How to choose an ERP for a K-12 school district (8 steps)
- What is ERP selection for K-12 school districts?
- Signs your district needs a new ERP (or just a better-configured one)
- The three phases of K-12 ERP selection
- Step 1: Build your selection team and governance
- Step 2: Map your current processes before you look at software
- Step 3: Write requirements that actually separate vendors
- Step 4: Build a realistic budget and 10-year total cost of ownership
- Step 5: Pick your procurement path and write the RFP
- Step 6: Score proposals and run scripted demos
- Step 7: Do your due diligence
- Step 8: Negotiate the contract and plan implementation before you sign
- 7 common K-12 ERP selection mistakes
- How long does ERP selection for K-12 take? A realistic 2026 timeline
- Should your district hire an ERP selection consultant?
- Frequently asked questions
- Conclusion
ERP selection for K-12 is mostly a process problem.
Districts that end up happy with their ERP rarely “found the best product.”
They mapped how work really happens, wrote requirements around their own scenarios, made vendors prove it in scripted demos, and wrote those promises into the contract.
Most districts do it backwards. They sit through three polished demos, pick the one that felt easiest, and spend the next two years paying for workarounds.
At KCT, I advise public agencies on ERP selection, and KCT is vendor-neutral. So this guide has no product to push. Its only job is to help you run a selection you won’t regret in 2028.
Nearly every guide ranking for school district ERP software is published by a company that sells it. Frontline and Linq, for example, both publish solid K-12 ERP buyer’s guides, and both steer you toward their own product.
In this post, I’m walking through the exact 8-step process I’d use for ERP for school districts in 2026: who sits on the team, what to map, how to write requirements and RFPs, how to script demos, what to ask references, and which contract terms protect you.
If you’d rather have a vendor-neutral team run that process alongside your staff, that’s exactly what KCT’s ERP selection advisory does.
First, a quick definition, since vendors stretch the term.
How to choose an ERP for a K-12 school district (8 steps)
- Build your team and governance: name a sponsor, a core team, and who actually decides.
- Map your current processes: document hire-to-retire, procure-to-pay, budgeting, grants, and position control before you look at any software.
- Write requirements that separate vendors: fewer checkboxes, more real district scenarios.
- Build a 10-year budget: price the whole project, not just the subscription.
- Pick a procurement path and write the RFP: formal RFP, cooperative contract, or RFI first.
- Score proposals and run scripted demos: you write the script, the vendor follows it.
- Do your due diligence: talk to districts that went live recently, not the vendor’s favorite reference.
- Negotiate the contract and plan go-live before you sign: tie payments to results and time go-live around payroll and fiscal year-end.
What is ERP selection for K-12 school districts?
ERP selection for K-12 is the structured process a school district uses to choose the system that runs its business operations: finance, budgeting, payroll, HR, and purchasing. The process covers forming a team, documenting needs, procuring and evaluating vendors, and negotiating a contract, all before implementation starts.
The key word is process. A solid process with a middling product usually beats the reverse. Plenty of districts have bought well-reviewed software, skipped the prep, and spent their first year after go-live fixing payroll by hand.
What ERP for K-12 actually covers
An ERP (enterprise resource planning) system is the district’s financial and people backbone. It’s separate from your student information system (SIS), which handles enrollment, attendance, grades, and schedules.
A typical K-12 ERP covers these modules:
- Finance and fund accounting: general ledger, the chart of accounts, and fund and grant tracking.
- Budgeting: budget development, position budgeting, and budget transfers.
- Purchasing and accounts payable: requisitions, purchase orders, approvals, and vendor payments.
- Human resources: hiring, onboarding, credentials, and evaluations.
- Payroll: pay runs, deductions, retirement system reporting, and W-2s.
- Position control: tying every funded position to a budget line and a person.
- Benefits and leave: enrollment, absence tracking, and leave balances.
- Inventory and fixed assets: devices, buses, buildings, and equipment.
Some vendors also bundle substitute management, timekeeping, or employee self-service. Others leave those to separate products that need integration.
Why school district ERP software is different
School district ERP software has to handle things a city or a manufacturer rarely deals with. If a vendor’s K-12 story is “we’ll configure it,” press hard on each of these:
- A lot of the money is restricted. Title I, IDEA, state categorical funds, and local levies all come with spending rules, and one purchase can be split across three of them.
- Split-funded positions. A single instructional aide can be paid 60% from Title I and 40% from the general fund, and that split may change mid-year.
- Mixed assignments. One employee can be a teacher, a coach, and a summer school instructor, each with a different pay rate and contract.
- Collective bargaining agreements. Salary schedules, step and lane movement, stipends, and retro pay are set by negotiated contracts.
- State reporting. Every state has its own staff, finance, and retirement reporting formats, and they change often.
- The school-year calendar. Teachers on 10-month contracts paid over 12 months, a fiscal year that starts July 1 in most states, and payroll that can’t miss a cycle.
- SIS integration. Staffing, schedules, and enrollment data flow between your SIS and ERP.
So skip asking vendors whether they support K-12. They’ll all say yes. Ask them to show split funding, retro pay, and your state’s staff report working without custom code.
Signs your district needs a new ERP (or just a better-configured one)
You need a new ERP when your current system can’t be fixed with configuration, training, or a vendor upgrade. Replacing an ERP is a multi-year project, so make sure the problem is the software and not the setup before you start.
The six triggers I see most often
- End of vendor support. Broward County Public Schools is replacing its SAP ECC system because support ends in December 2027 (Citizen Portal). When a sunset date is on the calendar, the selection clock is already running.
- Payroll errors staff can feel. Missed or wrong paychecks destroy trust faster than anything else in a district.
- Audit findings. Repeat findings on grant tracking, capital assets, or segregation of duties often point to system limits.
- Shadow spreadsheets. If position control, budget tracking, or grant balances really live in Excel, the ERP has stopped being the system of record.
- One-person knowledge. The only person who knows how to run fiscal year-end is retiring in 18 months.
- Manual state reporting. Staff rebuild state reports by hand every cycle because the system can’t produce them cleanly.
One trigger alone doesn’t justify a replacement. Three or more, especially with a support deadline, usually does.
Replace, upgrade, or optimize?
Before you commit to a full K-12 ERP selection, answer this honestly. Many districts buy a new system to fix problems that a configuration review or retraining would have solved for a fraction of the cost.
Replace, upgrade, or optimize? Effort grows from top to bottom.
| Option | Choose it when | Typical effort |
|---|---|---|
| Optimize Lowest effort | The product can do what you need, but it was set up poorly or staff were never fully trained. | Weeks to monthsProcess review plus reconfiguration |
| Upgrade Moderate effort | Your vendor has a modern version (often cloud) with a supported migration path. | MonthsSmaller than a full replacement, but not trivial |
| Replace Highest effort | The product is being sunset, can’t support core K-12 needs, or the vendor relationship is broken. | Multi-yearFull selection and implementation |
An honest test: list your top 10 pain points and ask, “Would a different product fix this, or would we carry the same problem over?” If most of the answers are “we’d carry it over,” fix your processes first.
The three phases of K-12 ERP selection
To choose an ERP for a K-12 school district, you prepare internally first, then buy, then commit. The eight steps fall into those three phases:
The eight steps in three phases. Each phase ends with something concrete in hand.
- 1Team and governance
- 2Process mapping
- 3Requirements
- 4Budget and TCO
You walk away withA clear picture of what you need and what you can afford
- 5Procurement and RFP
- 6Scoring and scripted demos
- 7Due diligence
You walk away withOne finalist you’ve tested against your own scenarios
- 8Contract and implementation plan
You walk away withA contract that protects the district and a realistic go-live date
Most districts rush the Prepare phase because it feels like it delays the “real” work. A missing requirement caught in week 6 costs an afternoon. Caught during implementation, it’s a change order.
Step 1: Build your selection team and governance
Start by naming who leads, who does the work, and who makes the final call. When a selection goes wrong, the cause is usually nobody owning the decision, or the people who’d use the system every day getting left out until the demos.
Who belongs on the team
Use three layers:
- Executive sponsor. Usually the CFO, CBO, or an assistant superintendent for business. They clear roadblocks, protect staff time, and carry the recommendation to the superintendent and board.
- Steering committee (5 to 8 people). Department heads from finance, HR, payroll, purchasing, and technology, plus one principal. They set priorities and settle disagreements between departments.
- Core evaluation team (8 to 15 people). The people who do the work every day: an accountant, a payroll specialist, an HR generalist, a buyer, a budget analyst, a school office manager, and someone from IT who knows your integrations.
Don’t skip the school sites. Principals and school secretaries enter requisitions, approve time, and check budgets, and they’ll judge the new system by how fast those tasks feel.
Set decision rights early
Write down, in one page, who does what:
- Who scores proposals and demos (the core team).
- Who recommends a finalist (the steering committee).
- Who approves the contract (the superintendent and board).
- How ties get broken when finance and HR want different vendors.
Put this in writing before you see a single vendor. Once demos start, people form favorites, and rules written after that look like they were designed to pick a winner.
Protect staff time
Your best payroll specialist can’t run payroll full-time and also sit through 40 hours of demos. Plan to backfill key people with temporary help, overtime, or delayed non-urgent projects during the busiest stretch.
Avoid scheduling heavy selection work during fiscal year-end, budget adoption, or the first two weeks of school. Your team has no spare capacity then.
Bring the board and unions in early
Brief the board at kickoff, not at contract approval. A board that understands why ERP for school districts is a multi-year commitment asks better questions and approves faster.
If your district has collective bargaining agreements, let union leadership know what’s changing. They don’t need a vote on the software. They do care about paychecks, timekeeping, and self-service, and early communication heads off rumors.
Before the first meeting, put the goal, sponsor, team, decision rights, and target dates on one page and get the superintendent’s signature on it. That page will settle more arguments than you’d expect.
Step 2: Map your current processes before you look at software
Document how work actually gets done today, including the workarounds, before you talk to a single vendor. If you skip this step, your requirements turn into a wish list, and vendor demos end up defining what “good” looks like for you.
The five K-12 processes to map
Focus on the end-to-end processes that cross departments, because that’s where hand-offs break:
- Hire-to-retire. From posting a position to onboarding, pay changes, leave, and separation. Include how HR and payroll hand off new hires.
- Procure-to-pay. From a teacher’s requisition to approval, the purchase order, receiving, the invoice, and payment. Note every approval level.
- Budget-to-actuals. From budget development to board adoption, transfers, encumbrances, and monthly reporting to principals.
- Grant lifecycle. From award to budget setup, spending, time-and-effort tracking, drawdowns, and closeout.
- Position control. How a funded position is created, filled, split across funding sources, and reconciled to payroll.
For each one, run a 2 to 3 hour workshop with the people who do the work. Capture who does each step, which system or spreadsheet they use, how long it takes, and where it goes wrong.
Separate “how we do it” from “why we do it”
Some steps exist because of a law or board policy. Others exist because the old system couldn’t do something in 2009, and nobody changed the habit.
Tag every step as one of three types:
- Required: law, regulation, audit, or board policy.
- Preference: how staff like to do it.
- Workaround: compensating for the current system.
Only the required steps are true requirements. Preferences are negotiable, and workarounds should disappear.
Key insight: If you write requirements from today’s workarounds, you’ll buy a new system that reproduces your old problems.
Inventory your systems and integrations
List every system that touches business operations, how it connects to your ERP, and who owns it. Typical districts are surprised by how long this list gets:
- Student information system (SIS)
- Timekeeping and time clocks
- Substitute and absence management
- Applicant tracking and onboarding
- Nutrition services and point-of-sale
- Student activity fund software
- Transportation and fleet
- Facilities work orders
- Bank, benefits carrier, and retirement system file feeds
Mark each one: replace with the ERP, keep and integrate, or retire. That list goes straight into your RFP.
Check your data quality now
Data conversion is where a lot of ERP budgets overrun, usually because nobody looked closely at the data until the vendor asked for it. Pull samples of your vendor file, chart of accounts, employee records, and position data.
Look for duplicate vendors, inactive accounts, inconsistent job codes, and missing history. Start cleaning now. The vendor will load your data, but deciding which of your vendor records are duplicates is your team’s job.
By the end of this step you should have five process maps, a ranked list of pain points, a systems inventory, and a short note on data quality. Everything in Step 3 builds on that packet.
Step 3: Write requirements that actually separate vendors
If every vendor can answer “yes” to a requirement, it isn’t helping you choose. The goal is a short, prioritized list that ties back to your process maps and is written in a way vendors can’t answer with a simple checkbox.
Why a 3,000-line checklist works against you
You can buy K-12 requirements templates with thousands of line items. They feel thorough, but they cause three problems:
- Every vendor answers “yes” to 90%+ of them, so scores cluster, and nothing separates.
- Your evaluators drown. Nobody can carefully score 3,000 responses times five vendors.
- The real differentiators get buried, like split-funded payroll or your state’s retirement file, under hundreds of generic items like “system supports PDF export.”
Aim for 300 to 600 well-written requirements, with the critical ones flagged.
The five requirement categories
The five requirement categories. Examples are written the way they’d appear in an RFP.
| Category | What it covers | Example requirement |
|---|---|---|
| Functional | What the system must do | Split one position across up to five funding sources with effective-dated percentages |
| Technical | Hosting, security, and performance | Single sign-on with the district’s identity provider; role-based access to the field level |
| Integration | Data flows to other systems | Nightly staff and section sync with the SIS; positive-pay file to the district’s bank |
| Reporting | State, federal, board, and internal reports | Produces the state’s staff and finance reports in the required format without manual editing |
| Service | Implementation, support, and training | Named support contact; response times for payroll-critical issues during pay week |
Prioritize ruthlessly
Tag every requirement:
- Must-have: Without it, the vendor is disqualified. Keep this to roughly 10 to 15% of the list.
- Important: It carries heavy weight in scoring.
- Nice-to-have: A tiebreaker.
If more than a fifth of your list is marked “must-have,” you haven’t prioritized yet.
Write scenarios, not just checkboxes
For your most important needs, describe a real situation and ask the vendor to explain exactly how their system handles it. For example:
“A paraprofessional is hired on October 15, funded 70% Title I and 30% general fund. In January, the split changes to 50/50 retroactive to December 1. Describe how your system processes the change, the retro adjustment, and the related grant reporting.”
A vendor can’t answer that with “Yes, fully supported.” They have to walk through the retro calculation and the grant charge step by step. Reuse these scenarios later as demo scripts in Step 6.
Treat state reporting as non-negotiable
State reporting is where school district ERP software most often disappoints. Ask every vendor:
- How many districts in your state currently run your product?
- Who on your staff tracks changes to our state’s reporting requirements?
- How quickly have you delivered required state changes in the past two years?
- Are state reports included in the base price or billed as custom work?
A vendor with no live districts in your state isn’t automatically out. Still, they should explain exactly how they’ll build and maintain your state reports, and at whose cost.
Run the draft past every department, then freeze the must-have list. Changing it after release means issuing addenda, and changing it after proposals arrive can invite a protest.
Step 4: Build a realistic budget and 10-year total cost of ownership
Price the whole project. The subscription or license is often the smallest slice of what an ERP costs a district over its lifetime. Implementation, conversion, integrations, and staff time make up the rest.
For scale, Broward County Public Schools presented a conservative, upper-end estimate of about $75 million for the first three years of its ERP replacement (Citizen Portal). Broward is one of the largest districts in the country, so your number will be smaller. What’s useful is how they’re paying for it: mostly capital funds, with some general fund money to backfill staff during the transition.
What belongs in total cost of ownership
What belongs in total cost of ownership. The darker the tag, the more often districts leave that cost out of the budget.
| Cost category | What it includes | Often missed? |
|---|---|---|
| Software | Subscription or license, plus annual maintenance and price increases | No |
| Implementation services | Vendor or partner configuration, project management, and testing support | Sometimes underestimated |
| Data conversion | Extracting, cleaning, mapping, and validating history | Yes |
| Integrations | SIS, timekeeping, bank, benefits, and retirement interfaces | Yes |
| Training | End-user training, train-the-trainer, and materials | Sometimes |
| Internal staff time | Backfill, overtime, and temporary staff during the project | Almost always |
| Independent oversight | Selection advisor, IV&V, and project quality assurance | Often |
| Contingency | I’d reserve 10 to 20% of project cost | Often cut first |
Model all of it over 10 years. A cheap first-year subscription with a 7% annual increase can cost more in year 8 than a pricier option with a 3% cap.
Know your funding sources
Districts typically fund ERP projects from a mix of sources:
- Capital or bond funds for one-time implementation costs, where your state and bond language allow.
- General fund for ongoing subscriptions and backfill staffing.
- Technology levies or dedicated reserves in some states.
Check early with your finance team and bond counsel about which costs qualify for capital funding. Subscriptions and staff backfill often don’t, which changes how you structure the deal.
Get your CFO to sign off on a 10-year cost range before the RFP goes out. A low case and a high case are enough.
Steps 1 through 4 are where most districts underinvest, and they’re the hardest to do objectively from the inside. Some districts bring in outside help for exactly that reason. Tucson Unified School District, for example, issued an RFP in July 2026 for an independent consulting firm to support its ERP planning, procurement, selection, and contracting (RFP summary). If you want that kind of support, KCT’s ERP selection advisory runs the process with your team from a vendor-neutral seat.
Step 5: Pick your procurement path and write the RFP
Choose the procurement route your state law and board policy allow, then write a solicitation that makes vendors compete on your terms. Your procurement path also determines how much leverage you have later in negotiations.
Three common procurement paths
Three common procurement paths. Check which ones your state law and board policy allow.
Formal RFP
Open competitive solicitation, scored by a committee
Best whenYou want the widest competition and the most negotiating leverage
Watch out forTakes longer; needs strong requirements and scoring discipline
Cooperative contract
Buy through a pre-competed purchasing cooperative or state contract
Best whenYour timeline is tight and the co-op covers the vendors you want
Watch out forLess competition; you still need demos, references, and your own SOW
RFI first, then RFP
A short request for information to scan the market before the full RFP
Best whenYou’re unsure what’s available or what it costs
Watch out forAdds one to two months; RFI answers aren’t binding
Cooperative contracts can save months, but they don’t replace the evaluation. They only settle the procurement-law question. You still need scripted demos, reference checks, and a negotiated statement of work.
Software and implementation: together or separate?
You can buy the software and the implementation services from one vendor, or select a separate implementation partner. Each approach has trade-offs:
- Single source (one contract): clear accountability and simpler management. The trade-off is less leverage if the implementation team underperforms.
- Separate partner: you can pick the strongest implementer for your product. The trade-off is that you have to manage the hand-offs, and blame can bounce between parties.
What a strong K-12 ERP selection RFP includes
- District background. Enrollment, staff count, number of schools, budget size, current systems, and why you’re replacing them.
- Scope. Which modules are in, which systems the ERP replaces, and which it must integrate with.
- Requirements matrix with standard response codes, such as: available today, configuration, future release, custom development, third party, or not available.
- Scenario questions from Step 3.
- Implementation approach. Methodology, staffing plan, named key personnel, timeline, and what the district must provide.
- Standardized pricing template. Every vendor fills in the same 10-year cost sheet. Don’t accept free-form pricing.
- References. At least three districts of similar size, ideally in your state, that went live in the last three years.
- Evaluation criteria and weights, published up front.
- Contract terms. Your standard agreement or the key terms you expect, so exceptions show up early.
Key insight: The standardized pricing template is the most underrated part of the RFP. Without it, you’ll spend weeks trying to compare five proposals priced five different ways.
Keep the process clean
Once the RFP is out, route all vendor contact through your purchasing officer. Answer questions in writing to all bidders, and have every evaluator sign a conflict-of-interest statement.
A bid protest can stall a selection for months, and a messy paper trail is what makes protests stick.
Sit down with your purchasing director to pick the path, then draft the RFP section by section using the list above.
Step 6: Score proposals and run scripted demos
Score the written proposals to get down to a shortlist, then make the finalists prove themselves in demos that you script. Scripted demos are the single biggest difference between a disciplined selection and a beauty contest.
Build the scoring rubric before proposals arrive
Publish your weights in the RFP and stick to them. A sample weighting for ERP for K-12:
A sample scoring rubric. Longer bars carry more of the score. Set your own weights before you open proposals.
Adjust the weights to fit your district. Just make sure the adjustments happen before you open any proposals, never after.
Get from long list to shortlist
- Pass/fail screen. Disqualify any proposal that misses a must-have requirement or a mandatory submission item.
- Independent scoring. Each evaluator scores alone first, which avoids groupthink.
- Consensus session. Discuss big scoring gaps, and let evaluators adjust if they missed something.
- Shortlist two to four vendors for demos. Five or more will wear your team out.
Why vendor-led demos mislead you
In a vendor-led demo, the vendor picks the scenarios, uses perfectly prepared data, and skips anything awkward. Every product looks great.
In a scripted demo, you give every finalist the same scenarios and the same sample data a few weeks ahead of time. They show your workflow, in your order, and you score each scenario live.
Six day-in-the-life scenarios every K-12 script should include
- Mid-year split-funded hire. Hire a paraprofessional funded by two sources, process the onboarding, and show the first paycheck and grant charges.
- Title I purchase. A teacher requests supplies charged to Title I, then show the approvals, the budget check, the PO, receiving, and payment, plus how an allowability rule is enforced.
- Retro pay after a settled contract. The board approves a 3% raise retroactive to July 1. Show the calculation, the review, and the payment across many employees.
- Fiscal year-end close. Roll encumbrances, close the year, and open the new budget while payroll keeps running.
- State report submission. Produce one of your required state staff or finance reports and show how errors get corrected.
- Principal budget check. A principal checks remaining building budget on a phone and approves a requisition.
Add two or three scenarios drawn from your top pain points in Step 2.
Run demos so they produce scores, not opinions
- Same day structure for every vendor, ideally on back-to-back days so the comparisons stay fresh.
- Score each scenario right after it ends, on a 1 to 5 scale, using a short rubric.
- Have the people who do the work score their own scenarios. Payroll scores payroll; principals score the principal view.
- Ask “show me” instead of “can it.” If a vendor says “we can configure that,” ask them to show it now or confirm it in writing.
- Track every “future release” and “customization” answer. These become contract issues later.
If a finalist offers a sandbox, have a few staff members spend a day in it. Clicking through a task yourself tells you more than watching a presenter do it.
One practical note: by the third demo of the day, everyone’s tired, and that vendor gets graded harder. If demos run across several days, rotate the order.
Send finalists the scripts and sample data about three weeks before demo day. Give them less time and you’ll likely get a canned demo with your district’s logo pasted on it.
Step 7: Do your due diligence
Before you name a finalist, check what the vendor told you against what other districts actually lived through. Reference checks, peer calls, and a look at the vendor’s stability catch problems that demos can’t show.
Find the references the vendor didn’t give you
Vendors hand over their happiest customers. Those calls are still worth making, but also find two or three districts on your own:
- Search board meeting minutes and agendas in your state for the vendor’s name.
- Ask your state’s school business officials association who runs the product.
- Ask the vendor for a full list of districts in your state, not just their chosen references.
Prioritize districts that went live in the last two years. A district that went live in 2018 implemented a different product version with a different implementation team.
Questions that get honest answers
Ask open-ended questions, and get specific:
- “What happened on your first payroll after go-live?”
- “What do you still do outside the system, in spreadsheets or on paper?”
- “How many change orders did you sign, and why?”
- “Did the implementation team that sold you the project actually do the work?”
- “How long does a typical support ticket take to resolve during pay week?”
- “How did the vendor handle the most recent state reporting change?”
- “If you started over, what would you do differently?”
- “Would you choose this vendor again?” Then wait through the pause.
Talk to the people who use it daily, not only the CBO. A payroll specialist will tell you things a cabinet member won’t.
Visit a live district
If you can, send three or four core team members to a district running the product. Watch staff do real work: entering a requisition, running a payroll preview, pulling a budget report. If they’ll let you, sit with the payroll clerk during a real pay week.
Check the vendor itself
The K-12 software market has seen a lot of acquisitions and ownership changes. Before you commit for 10 years, ask:
- Who owns the company, and has that changed recently? New owners can bring price increases or product consolidation.
- Is the product you’re buying the vendor’s strategic platform, or one they’re maintaining while steering customers somewhere else?
- What’s on the roadmap for the next 24 months, and which roadmap items are you counting on?
- How big is the K-12 support team, and where is it located?
Aim for five reference calls per finalist, at least two with districts you found yourself, and boil each finalist’s calls down to a page for the steering committee.
Step 8: Negotiate the contract and plan implementation before you sign
Negotiate the contract and statement of work so the vendor gets paid when deliverables pass your tests. Lock in your go-live plan before signing, too. Your leverage is highest right before you sign and drops sharply the day after.
Contract terms that protect the district
Contract terms that protect the district. Ask for these before you sign, while your leverage is highest.
| Term | What to ask for | Why it matters |
|---|---|---|
| Detailed statement of work (SOW) | Every deliverable, who does what, and what “done” means | A vague SOW turns into change orders |
| Acceptance criteria | Defined tests the district signs off on before a deliverable counts as complete | Stops vendors from billing for work that doesn’t function |
| Milestone-based payments | Payments tied to accepted deliverables, with part of each payment held back until after stabilization | Keeps the vendor invested through go-live |
| Price increase caps | A fixed annual cap on subscription increases for the full term, including renewals | Stops year-4 price shocks |
| Key personnel | The named project manager and lead consultants can’t be swapped without district approval | Protects you from “A team sells, C team delivers” |
| Data ownership and exit | District owns its data; vendor provides a full export in a usable format at no extra cost when the contract ends | Keeps you from being locked in |
| Service levels | Response and resolution times, with stricter targets during payroll processing | Payroll can’t wait for a 3-day ticket |
| Change order process | Written, priced, and approved before work begins | Keeps scope creep visible |
| Security and privacy | Data location, breach notification, audits, and compliance with student and employee privacy laws | Required for both your board and your auditors |
Write every “yes, it does that” from the demo into the contract or SOW. If a capability depends on a future release, put the delivery date and remedy in writing.
Time go-live around the school calendar
Go-live dates in K-12 aren’t arbitrary. Common patterns:
- Finance at the start of the fiscal year (usually July 1), so you don’t convert a half-year of transactions.
- HR and payroll on January 1, so W-2s come from one system for the whole calendar year.
- Never in August or September, when hiring, onboarding, and the first school-year payrolls hit all at once.
Albuquerque Public Schools follows exactly this pattern as it replaces its Lawson system, which is more than 25 years old. The district planned finance go-live for July 1, 2026, with HR and payroll targeted for January 1, 2028 (Albuquerque Public Schools). Plan for that kind of runway rather than an optimistic 9-month sprint.
Plan the rollout before you sign
Decide these with your finalist during negotiations so they appear in the SOW:
- Phased or big-bang. Phased (finance first, then HR/payroll) lowers risk but means running interfaces between old and new systems for a while.
- Parallel payroll. Run at least two to three payroll cycles in both systems and reconcile every difference before cutover. Don’t let anyone talk you out of this to save time.
- Independent verification and validation (IV&V). An independent party that reviews project health, testing, and readiness, reporting to the district rather than the vendor. Broward’s advisor pointed to IV&V as a key way to reduce implementation risk.
- Change management and training. A named owner, a communication plan, and training scheduled in the few weeks before go-live, while people will still remember it.
- Go/no-go criteria. Clear, written conditions (such as payroll parallels reconciled within a set tolerance) that must be met before cutover.
Key insight: The best contract term you can negotiate is a go/no-go gate the district controls. It gives you a legitimate way to delay a go-live that isn’t ready.
Have legal, purchasing, and your advisor read the contract and SOW in the same room. Don’t sign until the implementation plan, payment milestones, and go/no-go criteria are attached as exhibits.
7 common K-12 ERP selection mistakes
Most K-12 ERP selection mistakes come from rushing the early steps or trusting what you were shown instead of what you tested. Here are the ones I see most often.
- Choosing from the demo. The vendor with the best presenter tends to win. Fix it with scripted demos and scores agreed in advance.
- Letting a vendor shape your requirements. If your requirements read like one product’s feature list, every other vendor is at a disadvantage, and so are you. Write requirements from your process maps.
- Treating payroll as just another module. Payroll is where errors become very visible, very fast. San Francisco Unified is the cautionary example. After its EMPowerSF system launched in January 2022, many teachers and staff were paid incorrectly or not at all, some for months, and the district later moved to replace it (CBS News). Give payroll the most demo time, the most reference questions, and mandatory parallel runs.
- Buying a municipal or corporate ERP without a K-12 fit test. Strong general platforms can work for districts, but split funding, collective bargaining agreements, and state reporting have to show up working in your demo.
- Skipping data cleanup. Bad data moves into the new system and shows up as wrong paychecks and broken reports.
- Underestimating staff time. The vendor can’t configure your system without your experts. If those experts are also running daily operations at full capacity, the project slips.
- No independent oversight. Without someone who reports only to the district, small issues stay hidden until go-live week.
How long does ERP selection for K-12 take? A realistic 2026 timeline
A well-run ERP selection for K-12 typically takes 9 to 15 months from kickoff to signed contract, and implementation adds another 12 to 24 months. Treat them as rough ranges. District size, board calendars, and procurement rules all move the numbers.
A realistic K-12 ERP selection timeline. Typical ranges, not guarantees. Bars use a 0 to 6 month scale.
Broward’s 2026 timeline shows how fast the procurement phase can move once the preparation is done. The district released its RFP on May 1, received proposals on June 11, finished demos, and targeted a vendor recommendation in August with board approval in the fall (Citizen Portal).
Work backward from your target go-live date. If you want HR and payroll live on January 1 two years from now, you’re already on a tight schedule, so start the selection this semester.
Should your district hire an ERP selection consultant?
Hire an ERP selection consultant if your team hasn’t run an ERP selection in the past decade, doesn’t have spare capacity, or needs an independent voice the board will trust. Skip one if you have recent in-house experience and a simple scope.
Vendor-neutral vs. vendor-affiliated
Not every “consultant” is neutral. Before hiring one, ask directly:
- Do you resell, implement, or partner with any ERP vendor?
- Do you receive referral fees, commissions, or marketing funds from vendors?
- What share of your revenue comes from implementing the products you help select?
An implementation partner advising on selection has a built-in conflict. They may be excellent at what they do, but they’re not neutral about which product you pick.
Some districts write that separation into the RFP itself. When the Toronto Catholic District School Board hired ERP strategy and sourcing consultants in 2022, it made the winning firm ineligible to bid on the implementation work that followed (TCDSB tender).
What a good selection advisor actually does
- Runs process-mapping workshops and turns them into requirements.
- Builds the RFP, the pricing template, and the scoring rubric.
- Writes demo scripts and facilitates scoring sessions.
- Pulls market knowledge: which vendors are winning K-12 deals, what fair pricing looks like, and which references to call.
- Reviews the contract and SOW, and flags risky terms.
- Gives the board an independent recommendation it can rely on.
A good advisor won’t make the decision for you, and you shouldn’t want one who would. Your board needs to hear the recommendation from district staff.
When it’s not worth it
A small district with straightforward needs, a recent selection under its belt, or a state-sponsored shared system may not need outside help. Put that budget toward backfilling your own staff instead.
Frequently asked questions
What is the best ERP for K-12 school districts?
The best ERP for K-12 school districts is the one that handles your state reporting, funding rules, and payroll with the least customization. No product wins everywhere, so rank finalists on your scripted scenarios and recent references. For a starting list, see KCT’s ERP Tools Directory.
How much does school district ERP software cost?
School district ERP software costs vary widely with district size, modules, and hosting model. Small districts may spend in the hundreds of thousands over a decade, while the largest districts spend tens of millions. Compare options on 10-year total cost of ownership, including implementation, conversion, integrations, and staff time.
How long does an ERP implementation take for a school district?
An ERP implementation for a school district typically takes 12 to 24 months after the contract is signed. Finance often goes live first at the start of a fiscal year, and HR and payroll on January 1. Larger districts and multi-phase rollouts can run longer.
What’s the difference between an SIS and an ERP?
An SIS (student information system) manages student data: enrollment, attendance, grades, schedules, and student state reporting. An ERP manages the district’s business operations: finance, budgeting, purchasing, HR, and payroll. Some vendors sell both, but they’re separate systems with different users, and they need a reliable integration between them.
Can school districts buy an ERP through a cooperative contract?
School districts can often buy an ERP through a cooperative purchasing contract if state law and board policy allow it. Co-ops save procurement time but reduce competition. You still need scripted demos, reference checks, a negotiated statement of work, and your own contract protections.
What is IV&V in an ERP project?
IV&V (independent verification and validation) is oversight by a third party that reports to the district rather than the vendor. The IV&V team reviews project health, test results, and readiness, and flags risks early. It’s especially valuable on large district projects that include payroll and run for several years.
Does a small district need a formal ERP selection process?
Small districts still need a structured process, just a lighter one. Keep the same eight steps, but scale them down: a smaller team, fewer requirements, two finalists, and shorter demos. Skipping the process is riskier for a small district, because there’s less staff capacity to absorb a bad go-live.
Conclusion
The districts with the smoothest go-lives did the unglamorous work first: mapping real processes, writing requirements around real scenarios, scripting the demos, and putting every promise in the contract. Good ERP selection for K-12 is mainly a way to catch the wrong product before you’ve signed for it.
If your system has a sunset date coming, or your payroll team is already running on spreadsheets, start Step 1 this semester. The procurement can’t move faster than the preparation behind it.
If you want a partner with no stake in which vendor you choose, KCT runs this full process alongside your team, from the first process-mapping workshop to the signed contract. Talk to KCT about ERP selection for your district.