Employee Performance Tracking for Centre Staff
The module records goals agreed with centre staff and the work already logged against them. Reviews are then based on the record for the year and not on recollection.
Reviews built on the record
When a goal is set in April, the January review depends on what each side remembers. One recalls a problem in August. The other recalls two weekends of extra work. The module keeps goals, work counted and notes together, so the review starts from the year’s record.
What the record holds
Where the numbers stop
Writing goals for centre roles
Vague goals produce vague reviews. Each goal needs a thing that can be pointed to later.
A review conversation in three parts
- Look at the record together: goals, counted work, notes.
- Ask the employee what got in the way.
- Agree two goals for the next stretch and a date to check them.
What a manager should avoid
Tracking can turn into pressure if used badly. Keep the purpose clear.
Scoping questions for a staff goals record
A goals record is only useful if the goals fit your centre. Settle these at the demo.
- How many goals does each role carry?
- Who writes the goals, and who signs them off?
- Which counts from the system should be visible to the employee?
- Will reviews happen once a year or each quarter?
- Who sees the notes written about a person?
Near this screen
- Training: the sessions behind a skills gap.
- Employee records: the file a review is kept on.
- Operating reports: tickets, tours and follow-ups, counted across the centre.
Agree the evidence before signing off this part.
Use a representative scenario to decide what this part of the system must show and where review is still needed.
Work no report counts
What does one row mean before totals are combined?
Choose one period in “Work no report counts” and compare it with the source records. Define the date basis and grouping before accepting a total that combines several kinds of entry.
Background reading: Microsoft: reporting grain and relationships
Maintenance
What proves that a planned task was actually completed?
Select an overdue entry in “Maintenance”. Ask which work record closes it and what remains visible when the visit is postponed or only part of the job is done.
Background reading: ERPNext: maintenance plans
Frequently asked questions
Does it score staff automatically?
No. It gathers what happened and shows it beside what was agreed. The judgement is made by the manager in a conversation.
What can we set goals on for a front desk role?
The things the system already records, such as complaints closed within the day, visitor passes logged properly and notices going out on time.
Can an employee add their own note?
Yes. Some managers ask staff to write two lines each quarter on what went well, which gives the review more to work from.
Is this monitoring how long people sit at their desk?
No. There is no screen watching or keystroke counting. It works from the records the job already produces.
How often should reviews happen?
Centres do one formal review a year and a short check each quarter. You decide the rhythm, and the record supports either.
Can it link pay revisions to reviews?
The review and the pay revision are kept on the same file, so you can see them side by side. The pay decision stays with you.
Is it fair to compare two centres?
Only with care. Footfall, floor size and member mix differ. Read each person against their own goals first.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements