HRMAGIX021Performance, progression and payTimely Submission of Reports
The reporting obligations attached to a role, the expectation of timeliness, and the consequence of persistent delay.
- Companies on HRMagix
- 120+
- Employees managed
- 9,000+
- Integrated modules
- 12
- Free trial, no card
- 14-day
Purpose
This policy sets out the reporting obligations attached to a role, the expectation of timeliness, and what follows from persistent delay.
It exists because reporting deadlines are usually the first obligation to slip and the last to be addressed, and because downstream work, payroll cutoff among it, depends on them.
Who it applies to
Employees in roles carrying a defined reporting obligation.
What you write into it
Progression policies fail on process rather than principle. The template provides the cycle and the sequence; the criteria, the weightings and who decides are the parts that make it yours.
- Which reports are due, from whom, and to whom
- The deadline for each, and how it relates to the payroll cutoff
- How an extension is requested
- What follows from persistent delay
What HRMagix records
A progression decision that cannot be evidenced is difficult to defend later. These are the records that support it.
- Reminders and document deadlines are tracked rather than remembered
- Approval and submission actions leave a dated trail
Where the rules themselves live
No cycle, rating scale or eligibility period appears above. Those are the employer's criteria, and restating them here would create a second version to keep in step with the approved one. Read HRMAGIX021 in full.