Guide
HR Records Built to Answer the Question That Arrives Months Later
A record earns its keep months later, when someone asks what happened and why. We design HR records for that question from the first day, so the answer is already written down.
4-minute read4 November 2026
In Brief
- A completion tick shows a module was finished. The later question is harder: what was taught, which policy applied, who approved and on what basis. Without a record, you rebuild the answer from inboxes.
- We see four design choices that answer it: keep the version that was in force, record every decision with its approver, date every acknowledgement, and hold it all in one place your team can search.
- Thinqmesh fits HRKit, the system that runs our own HR, to your teams and policies, with a record of who asked, who approved and when.
Most HR systems are built for the question asked this week: who has not completed the module, whose review is overdue, how many people are on the payroll. The question that matters more arrives later, from someone outside the organisation, about a person who may have left and a manager who may have moved on. We design HR records for that second question from the first day.
A Record Is Worth What It Can Answer Months Later
A later reader wants to know what the employee was told, what the policy said on that date, who decided and on what basis. A system that holds only activity, such as a ticked box or a completion date, cannot answer. The gap shows itself when it is too late to repair.
The cost is felt in time and in standing. Reconstructing an approval from inboxes and chat threads takes days, and the reconstruction rarely carries the weight of a record made at the time. Leadership meets the same gap in a gentler form when a simple question about headcount or leave takes an afternoon. One record, written when the decision was made, answers both.
Four Choices That Make an HR Record Answer the Later Question
Each is inexpensive when made at the start and slow to add afterwards, and each improves the everyday work of HR as well.
Keep the Version That Was in Force
A policy, a letter or a module is stored as it stood on the day, so a new version never overwrites the old one.
When someone asks what an employee was told, the answer is the wording in force on that date. We keep every version with its effective dates, so the question can be answered from the record and without memory. Your staff also see which rule applied to them at the time.
Get started
- List the five documents most often quoted in HR disputes.
- Check whether you can produce each one as it read a year ago.
Record Every Decision With Its Approver
For leave, pay, promotion and disciplinary matters, the record names who asked, who approved and when.
An approval given in a message thread is hard to find and harder to rely on. We set up approval chains that match how your teams really decide, so the decision, its approver and its date are captured at the moment it is made. A note written at the time carries more weight than one written afterwards.
Get started
- Pick one approval that happens on messaging today.
- Write down who may approve it and what the approver should see first.
Date Every Acknowledgement
When a person reads, accepts or completes something, the date and the version go on their record.
A tick without a date or a version proves little. We attach the acknowledgement to the exact version the person saw, so a later reader can tell what they knew and since when. The same entry tells a manager at a glance who is still outstanding.
Get started
- Choose one policy that every joiner must accept.
- Check that your records show which version each person accepted.
Hold It All in One Place People Can Search
Joining details, leave and approvals sit in one system, so a simple question takes a minute.
Records scattered over spreadsheets and inboxes answer questions only when one particular person is available. We bring your existing staff records into a single system and check them, so headcount, leave balances and approvals can be read by anyone with the right access.
Get started
- Time how long it takes to answer a headcount question today.
- List every place a leave decision is currently recorded.
How Thinqmesh Solves This
We fit HRKit to your teams, your policies and your data, and your records are assessed in the first week, because issues found early protect the date.
- Week 1
HRKit on Your Data, Records Assessed
HRKit is configured on your data and we assess your existing staff records at once, so that anything awkward is found while there is time to deal with it.
- Week 2
Teams, Roles and Approval Chains
Your teams, roles and approval chains are set up as you decide things, and leave rules, holidays and carry-over are set to your policy.
- Week 3
Your Staff Records Moved Across and Checked
Existing records are migrated and checked against the originals, with access levels that match who does what.
- Week 4
Your HR Running on Your Own System
Your HR runs on your own system with your branding, and payroll figures are exported in your provider's format. Reviews and hiring follow as separate steps.
You finish with HR running on your own system and a record of who asked, who approved and when, ready for the question that arrives later.
