Key takeaways
- Review the whole period against agreed responsibilities.
- Check evidence gaps and access to opportunities.
- Leave with clear actions, support and a follow-up date.
Make the review about the work
A hybrid performance review should let manager and employee discuss the same evidence, whether they usually meet in person or remotely. Start with the responsibilities agreed for the role, the work delivered and the support needed next. Office visibility is not a substitute for that preparation.
This guide focuses on preparing and holding a review. It complements the separate guide to results-based management, which explains what to measure. Sources were checked on 27 September 2026. The examples below are suggested working practices, not FLYDESK customer results or a universal employee rating system.
Agree the scope before collecting evidence
Define the period being reviewed, the responsibilities in scope and any changes to priorities or role. Tell the employee how to contribute their own account. The manager should prepare too: a self-review is not a transfer of responsibility for noticing and understanding someone's work.
Acas describes reviews as a discussion of achievements, improvement, support and development. It also recommends regular feedback alongside formal reviews. Its UK guidance provides a useful starting point for the conversation; it is not a global employment procedure.
For a hybrid team, agree a format that allows both participants to concentrate and consult the same material. If the meeting is remote, share the agenda in advance and check that the chosen setting is suitable for a private conversation. Avoid making attendance at an office social event an unspoken condition of a good review.
Build a small, representative evidence record

Choose examples from across the review period rather than only the latest project. For each, connect the agreed expectation, the work done and its effect. Include quality, service and collaboration where relevant, not only the number of tasks completed. Explain what is observed and what remains uncertain.
A suggested record for a project handover might include the approved deliverable, feedback from the receiving team and any unresolved issue. If a dependency changed the deadline, record the change and the response to it. This makes the discussion more useful than a bare label such as unreliable or highly committed.
- What was expected, and did the expectation change?
- What evidence shows the contribution and its quality?
- What did the employee control, and what depended on others?
- What support or follow-up would improve the next cycle?
Check for gaps in visibility and opportunity
Before forming a judgement, ask whether you have comparable evidence for people doing comparable work. A colleague you see daily may be easier to remember than someone whose contribution arrives in a shared document. Seek relevant examples of work instead of treating familiarity as evidence.
Check whether access to assignments, information and feedback differed. Compare people with the expectations of their role rather than ranking unrelated jobs by a single task count. If peer input is useful, ask for a specific collaboration example; do not turn popularity or the number of comments into a performance score.
Hold a two-way conversation
Start by checking that both participants understand the evidence and the context. Discuss strengths as well as work that needs attention. Ask how the employee understood the original expectation and whether resources or priorities changed. Give space to correct a factual mistake before finalising the record.
Discuss development as an action, not just a label. For example, if a handover lacked information, agree what a complete handover should contain, how to practise it and who can review the next one. This is a proposed coaching example, not a guarantee of improvement or a substitute for your organisation's formal processes.
Leave with a usable written follow-up
Write down the conclusions, any unresolved differences and the next actions. Identify who will provide support and when the next conversation will happen. Keep the record accessible to the relevant participants within your organisation's established process, without circulating personal appraisal details as general team updates.
Acas publishes appraisal templates that can help structure a record. Adapt a form to the role and purpose rather than collecting fields merely because the template contains them.
Keep coordination data in its proper role
Review whether the process helped the employee understand expectations and obtain support. If the discussion relied on attendance, message volume or booking history instead of work evidence, revisit the measures before the next cycle. A more detailed dashboard does not automatically produce a better judgement.
FLYDESK supports team scheduling and shared workspace coordination. Those practical arrangements can make it easier to plan an in-person conversation or a team working day. Keep the performance assessment in the agreed management process; a location plan or reservation is not a performance rating.