Editable Word file, 26 pages: 213 requirements across 23 areas, 5-year pricing grid, scoring grid and demo scenarios. Free, no sign-up.
What is an HRIS RFP?
An HRIS request for proposal (RFP) describes your organisation, your needs and your constraints, so that several vendors can propose a solution and a price you can compare. In French-speaking countries it is called a “cahier des charges”; in public procurement it becomes the technical specification of the tender.
It serves three times:
- internally, to get HR, payroll, IT and management to agree on what the system must do;
- during the selection, to get answers you can compare requirement by requirement;
- after the choice, attached to the contract with the vendor’s answer, so that what was promised can be checked.
Before you write: scope the project
An RFP takes two to four weeks to write once the scoping is done. Five decisions shape it:
- Map what you have. Current tools (spreadsheets, payroll software, time clocks, e-signature), the flows between them and the pain points.
- Set the scope. The areas covered (employee records, absences, time, recruitment, reviews…), the countries and legal entities, the populations: salaried, hourly, part-time, apprentices.
- Decide what happens to payroll. Keep your payroll software and feed it, run payroll inside the HRIS, or outsource it: this choice changes the whole selection.
- Build the project team. HR, a payroll specialist, IT, the data protection officer, one or two managers, and an executive sponsor.
- Set the budget and the go-live date. Avoid starting during the year-end payroll close or the review campaign.
The 11 sections of the RFP
The template follows this outline. Delete the sections and areas outside your scope rather than leaving them empty.
| Section | What it contains |
|---|---|
| 1. Your organisation | Business, entities, countries, headcount, collective agreements, HR team |
| 2. The project | Goals, scope, users, timeline, budget |
| 3. Current landscape | Tools in place, flows, volumes, data to migrate |
| 4. Functional requirements | Needs, area by area, each with a priority |
| 5. Multi-country and compliance | Agreements, public holidays, languages, currencies, cross-border workers |
| 6. Technical and security | Hosting, authentication, roles, integrations, availability |
| 7. Data protection | GDPR and Swiss FADP, sub-processors, retention, exit |
| 8. Implementation | Method, configuration, data migration, training, testing |
| 9. Support and roadmap | Hours, response times, documentation, product roadmap |
| 10. Commercial proposal | Pricing grid and 5-year total cost |
| 11. The selection process | Timeline, expected answer, selection criteria |
Appendices: demo scenarios, volumes and a glossary.
Writing useful requirements
A useful requirement describes a need you can verify, not a quality. “The software must be user-friendly” separates no one. “An employee requests leave from their phone and immediately sees their updated balance” can be checked in a demo.
- Describe the need, not today’s tool. Copying your current screens means carrying over their flaws.
- Give each requirement a priority. Must, should or could. If everything is a must, nothing is: keep that level for what would block go-live.
- Impose a response code. Standard, configuration, partner, development or not available. A plain “yes” tells you nothing; a development comes with a price and a date.
- Add scenarios. Your real cases, played out in the demo: a part-time hire, a sick leave, the monthly payroll cut-off.
Requirements people often forget
- Multi-country: collective agreements, public holidays by canton or region, employee languages, currencies, cross-border workers.
- Roles and scopes: what a manager, an HR officer for a single entity or payroll can see; delegation during holidays.
- Data migration: leave balances, contracts, history, documents; who does it and in what format.
- Integrations: payroll software, single sign-on (Microsoft Entra ID…), calendars, e-signature, accounting, time clocks, APIs.
- Exit: getting all data and documents back at the end of the contract, in a usable format, and at what cost.
- Total cost: subscription, implementation, options, training and changes over 3 to 5 years, not just the monthly price.
- Adoption: mobile app, interface in each employee’s language, simplicity for managers.
Personal data and employee representatives
An HRIS processes sensitive data: health, absences, pay, family situation. The RFP should set the rules from the start.
- Data processing agreement. The vendor processes data on your behalf: the GDPR requires a contract setting out its obligations, including security, the use of sub-processors and what happens to the data at the end of the contract (article 28). Ask for the vendor’s data processing agreement (DPA), its list of sub-processors and its hosting countries.
- Impact assessment. Processing likely to result in a high risk to individuals requires a data protection impact assessment (article 35 GDPR, article 22 of the Swiss FADP). The French regulator, the CNIL, lists among them profiling for HR management and the constant monitoring of employee activity. Ask the vendor for the documentation that will help you carry it out.
- Switzerland. The Swiss FADP also regulates processors (article 9) and data transfers abroad (article 16). The European Commission recognises Switzerland as providing an adequate level of protection: data hosted in Switzerland can serve a company in the European Union.
- Works council. In France, in companies with 50 or more employees, the works council (CSE) is consulted, before the decision, on the introduction of new technologies that changes working conditions (article L2312-8 of the Labour Code): an HRIS used by every employee often qualifies. If the HRIS is also used to monitor activity, time tracking for example, employees must be informed beforehand (article L1222-4) and the CSE consulted (article L2312-38). Other countries have their own rules: build the time into your plan.
Running the selection in 10 weeks
A typical timeline, to adapt to your size and go-live date:
| Week | Step |
|---|---|
| 0 | RFP sent to 4 to 6 shortlisted vendors |
| 1 to 2 | Written questions; answers shared with all bidders |
| 4 | Proposals due |
| 5 | Analysis and a shortlist of 2 or 3 vendors |
| 6 to 7 | Demos on your scenarios, with managers and employees |
| 8 to 9 | Trial on your data and technical workshop: security, integrations, migration |
| 10 | Negotiation, decision, contract and data processing agreement |
Comparing the answers
Set the scoring grid before sending the RFP, not after reading the answers. The template suggests these weights:
| Criterion | Weight |
|---|---|
| Functional coverage (requirements and scenarios) | 35% |
| 5-year total cost | 20% |
| Usability and adoption (demo, trial) | 15% |
| Technical, security and data protection | 15% |
| Implementation and support during rollout | 10% |
| Vendor: support, roadmap, sustainability | 5% |
For coverage, score each requirement from 0 to 4 according to its response code and weight it by priority: 3 for must, 2 for should, 1 for could. A must-have marked “not available” rules the proposal out, whatever its score.
Nothing replaces a trial: a demo shows what the vendor prepared, a trial on your own data shows what your teams will live with.
Mistakes to avoid
- Sending a template without sorting it: out-of-scope requirements drown the ones that matter.
- Inviting fifteen vendors: the analysis becomes impossible. Shortlist first.
- Leaving users out of the demos: managers and employees are the ones who will adopt the tool, or not.
- Comparing monthly prices: implementation, options and changes often make the difference.
- Forgetting the exit: reversibility is negotiated before signing, not when you leave.
Download the template
The template puts this whole method into a document ready to fill in:
- instructions for use, to delete before sending;
- the 11 sections, with forms to complete (organisation, headcount, current tools);
- 213 functional and technical requirements across 23 areas, with a suggested priority and a response column for the vendor;
- a 5-year pricing grid and a weighted scoring grid;
- 7 demo scenarios.
Editable Word file, 26 pages: 213 requirements across 23 areas, 5-year pricing grid, scoring grid and demo scenarios. Free, no sign-up.
Your RFP and Illizeo
The template’s requirements follow the areas Illizeo covers in a single platform: employee records and documents, onboarding and offboarding journeys, absences, time and time clocks, payroll preparation and Swiss payroll, expenses, recruitment, reviews, training and reporting, for one or several entities and countries, with data hosted in Switzerland.
To check it against your own scenarios, the 30-day free trial gives you access to the platform, and pricing is public. Our HRIS for Switzerland and HRIS for France pages detail what a system must handle in each country.
FAQ — Frequently asked questions
How long should an HRIS RFP be?
There is no set length. What matters is that every requirement can be verified and has a priority. Delete out-of-scope areas rather than leaving them empty: a shorter but sorted RFP gets more precise answers.
Do you need a consultant to run an HRIS selection?
Not necessarily, when the scope is clear and the project team is available. Outside help makes sense for a group in several countries, complex payroll or a public tender.
How long does choosing an HRIS take?
Allow two to three months between sending the RFP and making a decision, following the typical timeline in this article. Implementation comes after that.
How many vendors should receive the RFP?
Four to six vendors shortlisted on their scope, countries and customer size. Beyond that, analysing the answers properly becomes too heavy.
Is the RFP contractually binding?
Only if you attach it to the contract, together with the vendor’s answer. That is recommended: the response codes (standard, configuration, development) and promised dates then become commitments.
Can you try an HRIS before choosing?
Yes, many vendors offer a trial or a demo environment. Ask for one on your own data and scenarios: it is the surest way to judge usability and real coverage.
30-day free trial, public pricing, data hosted in Switzerland.

