Performance Management Form: Fields, Scales and Templates

If your performance management form only gets opened once a year, after the work it was meant to guide is already finished, what is it managing? Most forms fail at that point. They record a rating, but they don't connect objectives, evidence, development and follow-up into a record that managers and employees can use throughout the cycle.

I would design the form as a configurable record, not a fixed template. That means clear field groups, rating definitions you can copy into policy, and separate records for developmental conversations and formal decisions. In a Microsoft-based system, those choices affect your Dataverse tables, Power Apps layout, security roles and reporting from day one.

Table of Contents

• Core Blocks of a Performance Management Form
• Field-Level Guidance for Objectives and Evidence
  • Fields to configure for each objective
  • Evidence fields that make ratings defensible
• Rating Scales and Outcome Definitions
  • What each rating level must define
• Competency Sections and Behavioural Evidence
  • A structure managers can use consistently
• Goal Alignment Fields and Review Cadence
  • Keep check-ins shorter than the formal form
• Separating Records and Protecting Employee Data
  • Five areas to separate
  • Privacy, access and retention controls
  • Automated input and AI-assisted summaries
• How to Configure Forms and Workflows in Microsoft Systems
  • Standard capability versus configured extension
• Frequently Asked Questions
  • Is a performance management form a legal requirement in the UK
  • How long should completed forms be kept
  • What changes for EU organisations
  • Can one form serve both pay and development
  • Does Microsoft or HRManagement365 make a form compliant
• Speak to an HRManagement365 specialist

Core Blocks of a Performance Management Form

A UK performance management form needs eight core blocks: objectives, evidence, competencies, development, overall rating, comments, follow-up actions and sign-off. Treat each block as its own section or related table in Dataverse, with Power Apps controlling the layout. That structure lets you report on incomplete objectives or overdue actions without opening every review.

Eight blocks sounds like a lot, but each answers a different question. Objectives and evidence record what was agreed and what happened. Competencies and development record how the work was done and what support is needed. Rating, comments, follow-up actions and sign-off close the cycle by capturing the formal outcome, both parties' input and the commitments that carry into the next period.

Ownership matters as much as the field list. Employees should add evidence and comments, managers should record ratings and rationale, and HR should control templates, access and reporting. Acas recommends written records of discussions with a copy shared with the employee, so sign-off should capture acceptance and date, not just a submitted status. In practice that means sign-off is a two-party field pair: employee acceptance with date, manager confirmation with date, so an unsigned review is visible rather than left pending.

Your first decision is whether you need one record per employee or linked records per cycle. A single record is simpler to build and search, but linked objective, check-in and action records give you history and an audit trail across cycles. The same prioritisation question arises in other functions, including which procurement workflows to automate first, where teams have to sequence structure before automation. HRManagement365 typically configures this structure to organisational policy rather than assuming one standard layout, and you can group blocks differently for developmental and administrative use.

Field-Level Guidance for Objectives and Evidence

Objectives carry the most weight in the record, so they need the tightest field design. A text box labelled "goals" won't support fair assessment, interim updates or reporting. Acas guidance on performance management recommends regular reviews, at least annual formal reviews, written records and a copy shared with the employee, with objectives that are specific, measurable, achievable, relevant and time-bound.

Fields to configure for each objective

Create one child record per objective rather than listing several objectives in one field. I would start with these fields.

• Objective name and description: A short title plus a measurable description of the result expected.
• Success measure: The number, milestone or observable output that shows the objective has been met.
• Owner and due date: The employee accountable and the date by which the result is due.
• Weighting: Used only where your policy aggregates objective scores, expressed as a percentage.
• Status: Not started, in progress, achieved or revised, so changes stay visible during the year.

Add fields for strengths, improvement areas, support or training required, career objectives, employee comments, manager comments and agreed follow-up actions at review level. That mirrors the Acas model without forcing every objective to carry development notes that belong elsewhere.

Evidence fields that make ratings defensible

Evidence should be a linked record, not an attachment dumped into a notes field. Give each item a type, source, date, attachment or link, and a short statement of what it shows. Types might include a project output, customer feedback, training record or performance log.

Practical rule: If a manager cannot point to dated evidence for a rating, the rating isn't ready to save.

Version history is essential. When an objective changes, record the previous wording, who changed it, when and why. Overwriting the original target makes year-end assessment unfair, because nobody can tell whether the employee missed the target or the business moved it.

Say a sales employee has an objective to produce 12 accepted proposals per quarter, weighted at 30%. The evidence record links to a CRM export dated at quarter end. After a territory change, the status moves from in progress to revised, the measure is updated, and the change reason is logged. The final rating can then reflect the revised commitment, not the obsolete one.

In Power Apps, use Dataverse business rules to make objective name, measure, owner and due date mandatory, and block submission if weightings total more than 100%. Make evidence type, source and date mandatory before a manager can enter a final rating. For more detail on writing measures, see our guide to performance management objectives.

Rating Scales and Outcome Definitions

Choose your scale as a policy decision before you build the form. The scale determines your field type, aggregation logic, calibration process and reporting. Changing it after reviews have started creates inconsistent history.

The illustration below contrasts the main scale approaches managers will see on the form.

The Lincolnshire performance and development appraisal guidance specifies 3 to 6 SMART objectives, a six-month review and a 12-month review, with each objective rated on a 1 to 5 scale. That model works, but only if each number has an observable definition.

What each rating level must define

For every level, publish four things: the label, numerical value if used, evidence expected, and threshold that triggers a development plan. A four-point scale forces a judgement and avoids midpoint drift. A five-point scale gives more range, but managers often overuse the middle value to avoid difficult conversations.

If you aggregate scores, show the calculation to the employee. For example, weight each objective rating by its percentage weighting, then round only at the final stage under a documented rule. Hidden rounding damages trust quickly, especially where pay or progression is linked to the result.

The video below is useful for checking how rating language translates into manager behaviour during the conversation itself.

Define evidence per level in plain language. A rating of 4 out of 5 on a customer service objective might require two items, such as a customer survey result and a written service review. Test the scale against a sample of past reviews before launch. If almost everyone lands on one value, your definitions aren't discriminating.

Competency Sections and Behavioural Evidence

Objectives assess what was achieved. Competencies assess how the work was done. Mixing the two in one rating hides the underlying issue. An employee can hit a sales target while damaging collaboration, or behave exactly as required while external factors block the result.

A structure managers can use consistently

Build each competency as a reference record with four parts: competency name, link to an organisational value, three to five behavioural indicators, and a rating with an evidence field. Store the framework centrally so the same definitions appear on every form. When a competency changes, version it rather than editing history.

Observable wording is the difference between a useful section and a vague one. For a competency called collaboration:

• Observable: Shares draft work with the team before the deadline so others can comment.
• Not observable: Is a good team player.

The first indicator can be evidenced from a shared document, project update or colleague feedback. The second invites opinion, recency bias and inconsistent standards between managers. If an employee challenges the rating, you need examples of behaviour, not personality labels. Structured input from colleagues can help here, which is why many organisations connect competency evidence to 360 feedback questionnaires rather than relying only on manager recall.

Don't automatically sum competency ratings with objective ratings unless policy states the rule and employees can see it. I would keep them as separate subtotals first. That lets HR analyse whether low outcomes stem from targets, capability, workload or behaviour.

You can also record a development need against a competency without turning it into a poor rating. For example, "needs support presenting to senior stakeholders" can create a development action while the competency still meets the expected standard for the current role. Pilot two or three competencies with a small manager group, check whether they interpret the indicators the same way, and rewrite any indicator that produces debate about wording rather than evidence.

Goal Alignment Fields and Review Cadence

An objective without context becomes a personal task list. Alignment fields show why the work matters and make it easier to revise priorities when team plans change. I recommend three fields on every objective record.

• Parent team objective: The team target this objective supports.
• Organisational priority: The service, department or company priority it contributes to.
• Changed-target note: What changed, when, and who agreed the revision.

The Vale of Glamorgan Council 2024 Performance Management Framework specifies quarterly meetings, including two half-yearly formal meetings, and links individual performance to team and service plans. That is a practical cadence to copy, even if your formal rating stays annual.

Keep check-ins shorter than the formal form

Create a separate check-in record with fields for progress since last review, obstacles, support needed, wellbeing or workload concerns where appropriate, development actions and employee comments. Keep it short. If a quarterly check-in looks like a full appraisal, managers will skip it or copy text forward.

A short record completed four times a year gives you better evidence than a long form completed once from memory.

Say a customer onboarding objective slips because a supplier delays system access. In the quarterly check-in, the manager records the obstacle, re-dates the milestone, updates the changed-target note and links the objective to the revised team plan. The year-end review then shows a managed change rather than unexplained under-delivery.

Report alignment directly from these fields. Useful Power BI views include the percentage of objectives linked to a team plan by department, objectives with no parent priority, and check-ins overdue by manager. HRManagement365 can configure review records, reminders and approvals in the Microsoft Power Platform, with customer-specific extensions where your cadence doesn't fit the configured process. Don't assume a quarterly pattern is universal. Set the cadence in policy first, then configure it.

Separating Records and Protecting Employee Data

Keep developmental reflection separate from administrative decisions where possible. Developmental conversations work when employees can discuss gaps, support needs and career goals openly. Pay, promotion and capability decisions need a formal rating, tighter access and a documented rationale. If employees believe every development note will feed a pay decision, they'll stop being candid.

The comparison below shows why those two record types need different fields, visibility and approval routes.

Five areas to separate

• Developmental reflection and support: Coaching notes, strengths, learning needs and future goals.
• Objective and competency evidence: Dated facts that support assessment.
• Formal rating: The manager's assessed outcome and rationale.
• Reward or progression recommendation: Pay or promotion input, normally routed for approval.
• Capability or conduct escalation: A restricted HR-led record where concerns may lead to formal action.

The CIPD evidence review on what works in performance management reports that 48% of employees reported at least basic performance management in 2023, while only 28% reported systematic performance management comprising objectives, monitoring, feedback and accountability. It also notes that developmental and administrative appraisals should be separated where possible because they use different judgement processes and can produce different rating patterns.

That separation also protects decision quality. Specific, challenging goals suit relatively straightforward work, but they're less suitable for complex roles involving adaptation and new learning. Feedback and perceived fairness matter. A form that forces one rating conversation to cover coaching, pay and capability will usually do all three badly.

In a Microsoft-based system, use separate Dataverse tables or column-level secured sections. Route reward recommendations through a Power Automate approval. A developmental note on presentation skills might be visible to the employee and manager only, while a capability escalation is visible to HR and triggers a documented review. Don't rely on managers remembering what not to share. Build the boundary into security roles.

Privacy, access and retention controls

Appraisal records contain personal data, so document the purpose, lawful basis, employee transparency information, access permissions, retention period and correction route. Employees should know who can see the record, how long you'll keep it and how they can challenge inaccuracies. Your retention schedule should distinguish final signed records from drafts, superseded objectives and informal check-in notes. Our guidance on employee records retention covers how to set those periods by record type.

Automated input and AI-assisted summaries

Treat automation as evidence handling, not just workflow convenience. Prettys guidance on AI in employment decisions and UK GDPR states that UK GDPR rules apply when personal data is processed in employment decisions, including performance reviews, and employees should be informed when AI is involved, given an understandable explanation and provided with a genuine route to human review.

An automated summary, sentiment score or absence-based flag can embed bias or strip away context. Low message activity might reflect focused work, caring responsibilities or a system outage, not underperformance. Label automated input clearly, store its source, and require the manager to record a final human rationale before it affects a rating.

Governance test: If you cannot explain an automated flag to the employee in plain English, don't use it in the rating.

For EU operations, don't copy a UK design without local checks. GDPR applies across EU Member States, but employment rules and works council consultation requirements differ by country. Agree at design stage which decisions need HR approval, which records employees can see, and which automated tools are prohibited from feeding formal outcomes. HRManagement365 can support those processes through configurable security and workflows, but policy and legal advice must define the rules.

How to Configure Forms and Workflows in Microsoft Systems

Configure in policy order, not screen order. A form built before the rating scale, retention period and approval route are agreed usually gets rebuilt, because the fields, validation and permissions all depend on those decisions. I would run the build in this sequence.

1. Confirm the policy: review cycle, rating scale, competency list, separation rules and retention.
2. Model the data in Dataverse: tables for review cycles, objectives, evidence, competencies, check-ins and actions.
3. Build forms in Power Apps: sections matched to employee, manager and HR tasks.
4. Add business rules: required fields, weighting totals and mandatory rationale before submission.
5. Create Power Automate flows: reminders, review submission, sign-off and reward recommendation approvals.
6. Set role-based security: employees, managers, HR and approvers see only the records they need.
7. Build Power BI reports: completion rates, overdue check-ins and rating distribution by team.
8. Test and retire old versions: use sample reviews, test permissions, then archive superseded templates.

The sequence keeps the record configurable across the cycle: an objective created in step 3 can carry evidence at check-in, feed a rating with a stored rationale, and close into actions without copying data between files.

Standard capability versus configured extension

Be precise about what Microsoft provides and what your implementation adds. Dataverse, Power Apps, Power Automate and Power BI are platform capabilities. The performance tables, validation logic, templates and dashboards are configuration or extension work shaped by policy.

HR Management 365 configures and extends Microsoft Power Platform and Dynamics 365 with custom workflows, integrations and HR applications where standard configuration doesn't meet the process. That can mean a custom calibration view, a separate capability escalation app, or links into Dynamics 365 data. Review meetings also need practical scheduling discipline, especially where managers need to coordinate team schedules across calendar accounts before check-ins are booked.

Don't promise capability before checking licences, environments and security design. Access through Teams, Outlook or mobile depends on your set-up. Confirm the exact scope with a specialist, then test with real manager scenarios, including a disputed rating and a mid-year objective change.

Frequently Asked Questions

Is a performance management form a legal requirement in the UK

No single statute requires one specific form. Acas recommends regular reviews, written records and a copy shared with the employee. Once you process personal data in reviews, UK data protection law applies.

How long should completed forms be kept

Set retention in policy by record type and document it. Keep final signed reviews for your defined period, and delete unfinalised drafts on a set schedule. Don't retain developmental notes indefinitely just because storage is available.

What changes for EU organisations

GDPR applies across EU Member States, but employment and consultation rules vary locally. In Germany, for example, works councils have co-determination rights over appraisal guidelines, so check national requirements before launch.

Can one form serve both pay and development

It can, but I wouldn't use one undifferentiated record. Keep developmental sections, formal ratings and reward recommendations separate, with different visibility and approval routes.

Does Microsoft or HRManagement365 make a form compliant

No platform guarantees compliance. Technology can support compliance processes through access control, audit trails and retention rules. Your policy, manager training and legal advice determine whether the process is compliant.

Speak to an HRManagement365 specialist

Start with the record, not the screen. Bring your current template, one completed review and the rating definitions managers use, then test whether each block can be captured as a field with an owner, an approval route and a retention rule. If a prompt cannot be stored, evidenced or reported on, it is still a document rather than a configurable performance record.

HRManagement365 is a Microsoft Power Platform HR provider with UK-based implementation, configuration and support. The platform covers objectives, reviews and continuous feedback, with employee and manager self-service through Teams, Outlook, browser and mobile. Forms, fields, workflows, approvals and reporting can be configured without heavy custom code, and Power BI can show completion and rating patterns from live HR data.

Because the system is modular, performance can be configured first and expanded later into leave, time and attendance, training or recruitment without re-platforming. A useful next step is a configuration review: map your sections to fields, split developmental comments from formal ratings and reward recommendations, then agree who can draft, view, approve and audit each record. Visit HR Management 365 to discuss how your performance management form and workflows should be set up.

Chris Pickles Director | Dynamics 365, Power Platform & HR Solutions Architect

I help HR leaders get off the admin hamster wheel with a Dynamics-based HR Management solution built on Hubdrive. HRManagement365 gives organisations a flexible HR platform within the Microsoft ecosystem that can be easily customised around the way they already work — rather than forcing teams into rigid, one-size-fits-all processes. It can be tailored to your HR workflows, integrated with Microsoft Dynamics 365 Business Central (BC) and Finance & Operations (F&O), and extended with Microsoft Power Platform to automate processes and connect HR more closely with the wider business. For employees, the experience stays familiar. They can interact with HR processes through the Microsoft tools they already know and use every day, including Teams, Outlook, Word and Power BI, helping drive adoption without introducing another unfamiliar system. The goal is simple: less manual admin, better-connected processes and an HR solution that fits your organisation. If you’re using Microsoft Dynamics and want HR to work as part of the same ecosystem, ask me about HRManagement365.

See Full Bio

Digital Transformation Microsoft Power Platform Power Apps Power Automate Power BI Dynamics 365 HR / HR Systems Business Process Automation Hubdrive HR