Free BARS Performance Review Template | Excel with Auto-Calculations & Behavioral Anchors
Free BARS Performance Review Template | Excel with Auto-Calculations & Behavioral Anchors
A performance management software RFP template turns a vague buying wish into a scored, comparable decision. A complete template covers eight things: a module-by-module requirements checklist, integration and security specs, works-council and data-protection questions, a weighted scoring matrix, a structured demo script, a data-migration plan, total cost of ownership, and vendor due-diligence questions. Use the free version below — no form, no email.
Most RFPs for performance management software fail in one of two ways. Either they list features nobody weighted, so every vendor scores "yes" on everything and the shortlist tells you nothing. Or they skip the parts that actually block go-live in the DACH region — the works council and data protection — and the project stalls three weeks before launch. This template fixes both. It is built for HR and People Ops buyers who are already in a formal procurement process and want a document they can send today, not another buyer's guide. For the strategy behind the shortlist itself, pair it with our guide on how to choose enterprise performance management software.
What belongs in a performance management software RFP?
An RFP (Request for Proposal) is the document you send to vendors so they answer the same questions in the same structure — which is the only way to compare them fairly. For performance management specifically, a strong RFP has nine building blocks. Copy this list into your document as the table of contents.
- Context & objectives — company size, headcount, current process, what "better" means (adoption, calibration quality, manager time saved).
- Requirements checklist by module — the functional core, split into must-have / nice-to-have / not needed.
- Integration & security requirements — HRIS, SSO, data residency, DSGVO/GDPR, processing agreement.
- Works council & co-determination questions — the DACH-specific block most templates miss (details below).
- Scoring matrix — the weights you will use to rank answers, disclosed up front.
- Demo script — the exact scenarios each vendor must run live, so you compare like for like.
- Data migration plan — what moves over, in what format, who owns it.
- Total cost of ownership — licence, implementation, integration, admin time, exit.
- Vendor due diligence — company stability, references, roadmap, support SLAs.
Requirements checklist by module
Do not ask "does it have performance reviews?" — every tool says yes. Ask module by module, and force each requirement into one of three buckets. The discipline of marking things "not needed" is what keeps the project scoped and the price honest.
| Module | What to specify in the RFP | Typical priority |
|---|---|---|
| 1:1s & check-ins | Templates, agenda sharing, talking points, history per employee, manager and employee visibility | Must-have |
| Review cycles | Configurable cycle types (annual, quarterly, probation), custom forms, weighting, sign-off workflow | Must-have |
| Calibration | Session support, rating-distribution views, bias flags, audit trail of who changed what | Must-have (mid/enterprise) |
| 360° feedback | Peer/upward/external raters, anonymity thresholds, request routing | Nice-to-have |
| Goals & OKRs | Cascading goals, alignment views, progress check-ins, weighting into the review | Must-have |
| Skills & competencies | Skill framework, self- and manager-assessment, gap analysis, link to development | Nice-to-have → must-have if skills-led |
| Career pathing | Role profiles, growth paths, readiness indicators | Nice-to-have |
| Analytics & reporting | Completion tracking, distribution, exportable data, role-based dashboards | Must-have |
| AI assistant | Draft support, summarisation, bias flagging — and the boundaries around each (see vendor questions) | Evaluate carefully |
If skills and competencies are central to your model, spell that out in the RFP rather than treating it as an add-on — a bolted-on skills tab behaves very differently from a system built around a skill framework. Our guide to successful skill management and the skills and competency management category help you write those requirements precisely.
Integration and security requirements
This is where deals quietly die after signing. Ask for specifics, not a "yes, we integrate."
| Requirement | Question for the vendor |
|---|---|
| HRIS integration | Native connector or API? Which HRIS specifically? Real-time sync or batch? Who maintains it after go-live? |
| Single sign-on | SAML 2.0 / OIDC? SCIM provisioning for joiners and leavers? |
| Adjacent systems | ATS, LMS, payroll — read-only or write-back? Documented API with rate limits? |
| Data residency | EU/EEA hosting available? Which cloud region? Any sub-processors outside the EU? |
| GDPR / DSGVO | Data-processing agreement per Art. 28 GDPR, deletion concept, records of processing, purpose limitation for performance data |
| Security posture | ISO 27001 or SOC 2? Penetration-test cadence? Encryption at rest and in transit? |
For DACH buyers, EU/EEA data residency and a signed data-processing agreement (Auftragsverarbeitungsvertrag) under Art. 28 GDPR are usually non-negotiable — make them pass/fail criteria, not scored ones. A vendor that cannot commit to EU hosting should not reach your shortlist.
Works council and co-determination: the questions most RFPs miss
This is the section that separates a real DACH-ready RFP from a translated US template — and the reason performance-management projects stall late. In Germany, performance management software counts as a "technical system designed to monitor the behaviour or performance of employees" the moment it can theoretically track individual output. That triggers a genuine co-determination right of the works council under § 87 Abs. 1 Nr. 6 BetrVG: you cannot introduce or operate the system without the works council's agreement, and unilateral roll-out is legally void.
Performance dashboards, rating distributions, calibration analytics and AI-scored reviews all fall squarely inside this. On top of that, the criteria you evaluate people against can engage § 94 BetrVG (assessment guidelines and personnel questionnaires), which also require the works council's consent. So the works council is not a compliance footnote — it is a stakeholder whose requirements belong inside the RFP, so vendors can prove up front whether their product can be configured to satisfy a Betriebsvereinbarung (works agreement).
Put these questions to every vendor:
- Can reporting be restricted to anonymised or aggregated views, with a configurable minimum group size before any breakdown is shown?
- Can individual-level tracking and scoring be switched off per module, and is that setting auditable?
- Which analytics can be disabled or scoped to comply with a works agreement, without losing the rest of the product?
- Is there an audit log of who viewed or changed performance data, that can be shared with the works council?
- For any AI feature: what data trains or feeds it, and can the works council be shown exactly what it evaluates and how?
- Will the vendor support the works-council approval process with documentation (data-flow diagrams, a processing description) rather than leaving it entirely to HR?
A vendor that answers these crisply saves you months. One that is surprised by the questions is telling you it has never sold into a co-determined workplace — which is a risk you want on the record before you sign.
Scoring matrix: weighting what actually matters
The point of a scoring matrix is to decide your weights before you see the demos, so you rank on your priorities rather than on whoever gave the slickest presentation. Score each requirement 1–5, multiply by the weight, and sum. Treat the weights below as a starting point and adjust them to your context — a skills-led mid-market company and a compliance-driven enterprise should not use the same split.
| Criteria group | SMB (<250) | Mid-market (250–2,000) | Enterprise (2,000+) |
|---|---|---|---|
| Core functionality (modules) | 35% | 30% | 25% |
| Integration & data | 15% | 20% | 20% |
| Security, GDPR & co-determination fit | 15% | 20% | 25% |
| Usability & adoption | 20% | 15% | 10% |
| Total cost of ownership | 10% | 10% | 10% |
| Vendor stability & support | 5% | 5% | 10% |
One rule that saves shortlists: make security, GDPR and works-council fit a gate, not just a weighted line. If a vendor scores below your minimum there, it is out regardless of how good the features are — because a product the works council will not approve cannot go live.
Demo script and data migration checklist
Never let a vendor drive the demo. Send a scripted set of scenarios and require them to run those, live, in their tool. This is the single most reliable way to see past a polished sales deck.
| Demo scenario to require | What you are really testing |
|---|---|
| Build a review cycle from scratch, on screen | Configurability without vendor services |
| Run a calibration session with sample data | Real calibration support vs. a spreadsheet export |
| Show the exact reports a works council could veto | Whether anonymisation is real or theoretical |
| Complete a review as a mobile-only frontline employee | Fit for non-desk workforces, common in DACH industry and retail |
| Export all performance data for one employee | Data portability and your exit path |
For migration, specify what moves and who owns it: historic reviews, goals, org structure, rating history. Ask for the import format, a test-migration step, and a named owner on the vendor side. "We'll handle it during onboarding" is not an answer — get it into the RFP.
Total cost of ownership
Licence price is the smallest number in the deal. Ask every vendor to price the full picture so the cheap-looking option does not become the expensive one.
| Cost component | What to request in the RFP |
|---|---|
| Licensing | Per-user or tiered? Minimum seats? Price at your 3-year headcount, not today's |
| Implementation | One-off setup, configuration, mandatory professional services |
| Integration | Connector fees, API costs, internal engineering time |
| Ongoing admin | Internal hours to run cycles and reporting each year |
| Training & change | Admin training, manager enablement, works-council documentation effort |
| Exit | Data export cost and format when you leave — ask before you sign |
In our work with HR teams, the most common post-purchase regret is underestimating internal admin time and change management — not the licence. Ask vendors to name a comparable customer and the real effort that customer spent in year one.
Vendor due diligence questions
The product can be right and the vendor still wrong. Cover stability, references and roadmap — and add one forward-looking question about AI that increasingly decides these deals.
- Stability: How long in market? Ownership, funding, profitability? Recent or planned acquisitions?
- References: Two customers of our size, in our region, that we can call — not just logos on a slide.
- Support: Response-time SLAs, support language (German?), named CSM or ticket queue?
- Roadmap: What shipped in the last 12 months? What is committed for the next 12?
- AI boundaries: Does the AI assistant only summarise, or can it draft review content and flag calibration bias — and what stops it from writing an assessment no human checked?
- AI governance: Under the EU AI Act, AI used to evaluate employee performance is treated as high-risk employment AI, and staff working with it need adequate AI literacy under Art. 4 of the EU AI Act. Ask what documentation and training the vendor provides.
Assembling your RFP pack and winning internal buy-in
Package the sections above into one document, add a response deadline and a scoring rubric, and send it to a shortlist of three to five vendors — more than that wastes everyone's time. Internally, get three people aligned before you send: the HR/People Ops owner, IT/security, and a works-council contact. Aligning those three up front is what prevents the late-stage veto that kills so many performance-management projects.
A realistic timeline from RFP-out to signature is six to twelve weeks for mid-market, longer for enterprise where security review and works-council negotiation run in parallel. Build that into your plan rather than promising leadership a go-live date you cannot control.
Frequently asked questions
What should a performance management software RFP include?
Nine blocks: context and objectives, a module-by-module requirements checklist, integration and security requirements, works-council and data-protection questions, a weighted scoring matrix, a demo script, a data-migration plan, total cost of ownership, and vendor due-diligence questions. The template above gives you all nine.
How long does performance management software procurement take?
From sending the RFP to signing, expect roughly six to twelve weeks for mid-market and longer for enterprise. Security review, data-processing agreements and works-council negotiation often run in parallel and set the real pace — not the vendor demos.
Does the works council need to approve performance management software?
In Germany, yes. Because the software can monitor individual performance, it falls under § 87 Abs. 1 Nr. 6 BetrVG, giving the works council a co-determination right. You need a works agreement in place; a unilateral roll-out is legally void. Involve the works council before, not after, you shortlist.
What is a good scoring-weight split for enterprise versus SMB?
Enterprises weight security, GDPR and co-determination fit higher (around 25%) and usability lower; smaller companies weight core functionality and usability higher because they have less admin capacity. Use the matrix above as a starting point and adjust to your priorities — the weights matter less than agreeing them before the demos.
Should the RFP be gated behind a form or shared openly?
Share it openly with your shortlisted vendors. Gating slows responses and signals distrust. The template here is deliberately free and un-gated so you can copy it straight into your own document.
Next step
Copy the nine blocks into your RFP, set your weights, gate on security and co-determination, and send it to three to five vendors. If you want the reasoning behind building the shortlist in the first place, read our guide on choosing enterprise performance management software before you send.
Jürgen Ulbrich
Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.
