What should a public-sector HRIS RFP include?
A public-sector HRIS request for proposal (RFP) should include six things: a plain description of who you employ and how they are paid, the documents that govern their pay, a requirements list sorted into must-have and nice-to-have, a pricing form that forces one all-in number, an implementation section that asks what you will have to do, and a scoring method you publish before bids arrive. An HRIS is a human resources information system, the software that holds employee records and usually connects to payroll.
Most of the weak RFPs I read fail on the first two. They list 300 features and never say how many employees there are, how often they are paid, or which agreement sets their overtime. A vendor can only answer what you ask. If you leave out the hard parts, you get polished answers about the easy ones.
The rest of this post goes through each piece in the order I would write it. A checklist sits near the end if you want to skip ahead. If you are also comparing vendors by demo, the HRIS demo questions pair well with it.
What goes in the scope?
Start with facts a vendor cannot guess. Head count, in total and by group. How many are full-time, part-time, seasonal or casual. How often each group is paid. How many pay groups you run, and how many locations. Whether payroll is part of this purchase or you only want HR, time or scheduling.
Then say what you are replacing. "Three spreadsheets, a paper leave form and a payroll system we have outgrown" tells a vendor more than any feature list. Name the systems that must keep running and the ones that will switch off.
Be honest about scope in both directions. If you only need time off and timekeeping, say so. Vendors treat a single-module RFP as a real bid, and it keeps your evaluation clean. If you want HR and payroll on one record, say that too, and say why. It changes how a vendor prices and how they plan the work.
Finally, attach every document the RFP depends on. A collective agreement, a pay policy, a classification chart, a council resolution. If the RFP names a document, the document goes in the package. A bid written against rules the vendor has never seen is a guess, and the gap between that guess and your real rules shows up after you sign, usually at the first pay run.
How do you write the requirements?
Write requirements as things you need to be able to do, not features you hope exist. "Approve a leave request and see the balance change before the pay run closes" is testable. "Full leave management capability" is not.
Sort every line into must-have, should-have and nice-to-have. If everything is mandatory, nothing is. A good sorting test is to ask whether you would still award the contract to a vendor who missed the line. If yes, it is not a must-have.
Ask vendors to answer each line with a short code, such as available now, available with configuration, available through a workaround, or not available. Then ask for one sentence of explanation on every line that is not "available now". The honest vendors will use all four answers. The ones who answer "yes" to everything are telling you something too.
Pay rules deserve special care. If your employees are covered by a collective agreement, do not ask whether the software is "compliant with" it. No vendor can honestly promise to read and interpret your agreement for you. Instead, list the specific rules you need applied, such as how vacation accrues, how overtime is premium-paid, how seniority is counted, and ask each vendor how those would be set up. In practice you tell the vendor the rules, they configure them as far as the product supports, and they tell you about any rule that needs a workaround. Ask each vendor to describe that process in writing.
The same goes for accrual rules that depend on hours or days worked rather than a date. Name them. They are the ones that surprise people.
Payroll needs its own paragraph in the requirements. Say which provinces you pay in, which statutory deductions and year-end slips you must produce, and who files. Ask each vendor what the software prepares and what your team still reviews and submits. The CRA's payroll page for employers is the official starting point for the deductions, contributions and remittances your requirements need to name.
How should you price it?
Give vendors a form, and make every vendor fill in the same one. Free-form pricing makes comparison impossible.
Ask for a single all-in annual number for your head count, then ask them to break it out. The questions that matter are whether implementation, data migration, training and ongoing support are included or charged separately, whether there are monthly or annual minimums, what happens to the price if your head count changes, and what currency you will be billed in. Ask what a second-year price looks like, and what it costs to add a module later.
Price per employee is the easiest model to compare, because you can multiply it against your own roster. Ask each vendor to state the per-employee rate and what is included in it. Seasonal workforces need a sentence of their own. If your head count swings between a quiet winter and a busy summer, ask how the bill follows it.
Ask about contract length too. Some vendors require multi-year terms and some run month to month. Neither is wrong, but you should see it side by side before you score.
What should you ask about implementation?
This is where public-sector projects go sideways, so spend your words here.
Ask for a plan, not a promise. A vendor who puts a fixed number of weeks in a bid without knowing your data, your pay groups or your decision-makers is guessing. Real timelines depend on things like how clean your employee data export is, how clear your organization structure is, how fast your team makes workflow decisions, and whether a payroll parallel run is part of the plan. Ask each vendor to list those dependencies and say who owns each one. The HR software implementation guide covers the same ground from the buyer's side. Then compare the lists. The vendor with the longest list is often the one who has done this before.
Ask who from your side is needed and for how many hours a week. Be ready to answer the same question yourself. Municipal and First Nation teams are usually small, and an HR lead who is also running payroll cannot give 15 hours a week to a project. Say so in the RFP and see who adjusts.
Ask who will do the work and whether the same people will support you after go-live. Ask what training covers, and whether it is built to train your own trainers so you are not dependent on the vendor forever. Ask how a pay run is tested before it goes live, and what happens if a result does not match.
Ask about data too. Where will it be hosted, who can access it, and what happens to it if you leave. Public bodies often have privacy obligations that apply to the contract, so state them and ask for the vendor's written response.
How do you score the bids?
Publish your scoring before bids come in. Weight the sections, for example requirements fit, implementation approach, price and references, and say what the weights are. Check your own procurement policy and any trade agreements that apply to your organization for rules on how bids must be evaluated. Those rules vary by organization and by purchase size, so your procurement team owns that part.
Ask for references from organizations of your size and type, and call them. Ask what went slower than expected. That question is worth more than any demo.
Run scripted demos. Hand each vendor the same three or four scenarios from your real work, such as a leave request through manager approval to pay, a mid-period pay change, a new hire in a seasonal group, and let them show it live. Marketing demos show what a product does well. Your scenarios show what it does for you.
A short checklist
| Part of the RFP | What it must state |
|---|---|
| Scope | Head count by employee group, pay frequency, pay groups and locations stated. |
| Current systems | The systems being replaced, and any that must stay. |
| Governing documents | Every governing document attached, including collective agreements and pay policies. |
| Requirements | Requirements sorted into must-have, should-have and nice-to-have, each written as something you need to do. |
| Response codes | A response code on every line, with one sentence of explanation for anything not "available now". |
| Pay rules | The specific pay rules you need, listed by rule, not by agreement name. |
| Payroll scope | Payroll scope stated, including provinces, deductions, year-end slips and who files. |
| Pricing form | A standard pricing form with an all-in number, minimums, inclusions and second-year pricing. |
| Implementation | Implementation dependencies listed by owner, with your own team's hours stated. |
| Data terms | Data hosting, access and exit terms requested in writing. |
| Scoring | Scoring weights published, scripted demos planned and references checked. |
Where Workzoom fits
I answer these RFPs for a living, so I will say plainly where we come in. Workzoom is a Canadian-owned HRIS and payroll platform for organizations with 50 to 5,000 employees. Pricing is $4 per employee per month per suite, or $16 for all four, with implementation, migration, training and support included, so the pricing form above is an easy one for us to fill in. See pricing and the Payroll page for detail. Payroll runs live in Canada, the United States and the Bahamas.
Public bodies we work with include the County of Renfrew in Ontario, which has over 900 employees on one platform. The county phased its rollout, starting with the highest-impact work, and onboarded 32 new hires in three months without adding HR headcount, according to its case study.
If you are writing your first one, send me your draft before it goes out. I will tell you where a vendor could answer it too easily, whether or not you ever bid us in.
How useful was this page?
What should we improve?
Questions about writing an HRIS RFP
Workzoom handles HR, payroll, workforce, and talent on one employee record. Book a Walkthrough.
Get started
Built around your org. See it run live.
Explore your suite options, pricing and fit in a 15 to 60 minute working session. For organizations with 50 or more employees. See our minimums.












