GullyHR collects your current policies, handbook, letter formats and forms, flags the duplicates, superseded versions and gaps, then uploads what survives into a categorised, version-controlled document centre, configures who can see which document, sets up acknowledgement tracking on the policies you choose, and puts review or expiry reminders on the documents that need them. You decide which version of each document is the current one, which policies require an acknowledgement, and who is allowed to see what. It is delivered as part of a platform configuration engagement. Where the policies themselves need drafting or revising, that is separate consulting work and is scoped as such rather than folded into the upload.
Every policy has one current version and one place to find it.
Policies are held with a version number and an effective date, so the copy an employee reads is the copy HR last approved, and the question of which version applies stops being a matter of who forwarded what.
The handbook stops being a printed document that ages in a drawer.
The employee handbook lives as a single current document that can be revised in place, so a new joiner reads what the company does now rather than what it did when the handbook was last printed.
Forms and letter formats come from one source instead of somebody's laptop.
Requisition, leave, reimbursement, change-request and other operational forms, along with standard letter formats, are kept current and available to the people who need them, ending the quiet circulation of old versions.
Superseded versions are kept as record rather than lost.
Each revision is tracked, and the previous version is retained with the dates it applied, which matters when a question arises about what the rule was at the time something happened.
You can see who has acknowledged which version of a policy.
Where you require it, employees confirm they have read a policy, and the acknowledgement is recorded against them and that version. It evidences communication; whether a policy is enforceable remains a legal question, not a software one.
A review date surfaces before it passes, not a year afterwards.
Documents that carry a review or renewal date generate a reminder ahead of it, so a policy is revisited on a schedule rather than when somebody notices it has become out of step with practice.
A document reaches only the people it applies to.
Access can be restricted by role, department or location, so a site-specific allowance rule or a manager-only guideline is visible where it applies and nowhere else, which prevents the wrong rule being quoted at the wrong place.
An employee can find the right policy without asking HR.
Documents are organised into categories that match how people actually search, so somebody looking for the travel, leave or exit policy finds the current one rather than sending a message and waiting.
The clean-up happens before the upload, not after it.
Duplicates, superseded copies and drafts nobody approved are identified and put to you for a decision, so the centre opens with a document set you have confirmed rather than the shared drive moved wholesale into a new place.