We would benefit from more merge tags and an easier way to create documents & emails using them. An example is first day of absence.
Joanne Crook
Jun 4, 2026
Request for Enhanced Date Formatting Options in Merge Tags
The current merge‑tag date formatting options are causing challenges for us when producing formal HR and contractual documentation through the system.
At present, the available tags —
[[Current Date]], which outputs a weekday and abbreviated date (e.g., “Thu, 04 Jun 2026”), and
[[Current Date-2]], which outputs DD/MM/YYYY (eg 04/06/2026)— do not provide a format suitable for legally sensitive or professionally presented HR documents)
In employment contracts, formal letters, and policy communications, it is standard practice to use a clear written‑date format such as “29 January 2026”. This style is widely recognised in UK HR, legal, and compliance contexts because it is unambiguous, professional, and consistent with best‑practice drafting conventions.
The current merge‑tag formats unfortunately do not meet this standard. As a result, we are forced either to manually amend dates — which undermines the efficiency of automated document generation — or to issue documents with a date style that does not reflect the level of professionalism expected in formal HR correspondence.
I would be grateful if you could introduce additional date‑format options, or whether this could be considered as a feature enhancement. The ability to generate dates in formats such as “29 January 2026” or “29th January 2026” would significantly improve the quality and compliance of documents produced through PeopleHR.
We use tags for ripple emails in line with triggers for Sickness Absence so would be good to have a rolling 12 month ability rather than just what has been taken in the current calendar year which is what it is currently set at.
I would also like to see the ability to include in the automated email to managers and HR, exactly what Other Event type has been booked from our populated list, as they are all so different in type.
We really appreciate your suggestions and participation in voting. We are completing research involving the documents creator in PeopleHR. Your contribution of just 5 minutes to complete a brief survey would be extremely valuable to us. Please visit the following link to access the questionnaire: https://forms.office.com/e/KyNmVbhBrq
More tags available for Document Template Creator (Ripple Emails)
Merged
If we had more field tags for ripple emails this would make the emails much more user friendly. At the moment each time someone registers an 'Other Event' the best I can write is "[[First Name]] [[Lat Name Name]] has added an Other Leave Event. Pl...
Claire Harrison
over 2 years ago
in AdminAdded to Product Backlog
2
MERGED
Work pattern as mail merge field
Merged
To have the ability to pull through the work pattern into a document (not just the name of the pattern but the actual pattern)
VIctoria Clark
almost 2 years ago
in PlannerAdded to Product Backlog
7
MERGED
New mailmerge field
Merged
Please can future salary be added to mail merge - this would enable us to send out letters to staff about what their salary will be, for example when cost of living is applied, before the effective date of the salary change. Many staff wanted to k...
Guest
about 2 years ago
in IntegrationsAdded to Product Backlog
Request for Enhanced Date Formatting Options in Merge Tags
The current merge‑tag date formatting options are causing challenges for us when producing formal HR and contractual documentation through the system.
At present, the available tags —
[[Current Date]], which outputs a weekday and abbreviated date (e.g., “Thu, 04 Jun 2026”), and
[[Current Date-2]], which outputs DD/MM/YYYY (eg 04/06/2026)— do not provide a format suitable for legally sensitive or professionally presented HR documents)
In employment contracts, formal letters, and policy communications, it is standard practice to use a clear written‑date format such as “29 January 2026”. This style is widely recognised in UK HR, legal, and compliance contexts because it is unambiguous, professional, and consistent with best‑practice drafting conventions.
The current merge‑tag formats unfortunately do not meet this standard. As a result, we are forced either to manually amend dates — which undermines the efficiency of automated document generation — or to issue documents with a date style that does not reflect the level of professionalism expected in formal HR correspondence.
I would be grateful if you could introduce additional date‑format options, or whether this could be considered as a feature enhancement. The ability to generate dates in formats such as “29 January 2026” or “29th January 2026” would significantly improve the quality and compliance of documents produced through PeopleHR.
We use tags for ripple emails in line with triggers for Sickness Absence so would be good to have a rolling 12 month ability rather than just what has been taken in the current calendar year which is what it is currently set at.
I would also like to see the ability to include in the automated email to managers and HR, exactly what Other Event type has been booked from our populated list, as they are all so different in type.
We really appreciate your suggestions and participation in voting. We are completing research involving the documents creator in PeopleHR. Your contribution of just 5 minutes to complete a brief survey would be extremely valuable to us. Please visit the following link to access the questionnaire: https://forms.office.com/e/KyNmVbhBrq
It would be incredibly useful to be able to use merge tags from all fields in the Employment tab' for an employee.
This would be very useful. Being able to pull through things like maternity dates would assist with the production of SMP letters and the like.