Skip to main content
GullyHR

HR technology and automation · Alteration shops

Policy and Document Centre for Alteration shops

A policy and document centre is the module that holds a company's HR policies, employee handbook, letter formats and forms in one version-controlled place, with access set by role, department or location, a record of which employees have acknowledged which version, and reminders before a document reaches its review or expiry date.

Two colleagues finding a workplace policy on a laptop beside a neatly closed handbook.

The operating context

Publish one approved version to the right employees

An alteration shop shortens, takes in and repairs other people's clothes, to a date for a wedding or a trip. Tailors and counter staff must work accurately, keep garments safe and meet promised pick-up times.

Master tailorTailors and machine operatorsFinishers and pressersCounter and measurement staffDelivery and pick-up staffTrainee tailors
A facility supervisor reviewing deployment with housekeeping and maintenance staff at a client building

The decision to work through

Configure document categories, version owners, audience access and acknowledgements for approved policies. Workforce to consider: Master tailor, Tailors and machine operators, Finishers and pressers.

Records and configuration to test

Version register, publishing roles and acknowledgement report. A workforce issue to consider: Without tags and a log, an order goes missing or reaches the wrong customer.

An exception to test

Replace an outdated policy and verify that users find the current version while authorised owners retain the required history.

Which parts of your business should the scope cover?

The right workforce and approval structure depends on the operations you run. Confirm which of these apply, and whether they share one HR process.

  • Saree blouse and lehenga alterations for weddings
  • Men's suit and trouser fitting
  • School and college uniform alterations
  • Zip, lining and button repair
  • Ethnic wear refitting for festivals
  • Maternity and nursing wear alterations

When to consider this service

  • The policy an employee was shown is not the version HR revised last quarter, and nobody knows how many copies of the old one are still circulating.
  • An employee says they were never told about a rule, and there is no record either way.
  • The same leave application form exists in three slightly different versions on three different laptops.
  • A site-specific rule, such as a shift allowance, is being applied at a location it was never meant to cover.

Businesses this service is designed for

  • Companies whose policies are scattered across email, a shared drive, a printed handbook and one person's memory.
  • Multi-location businesses where some rules apply company-wide and others belong to a single site or state.
  • Businesses that need to show a client, an auditor or a new employee that a policy was issued and acknowledged.
  • Companies revising their HR policies who want the new set version-controlled from the day it is approved.

What the system needs to support

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.

Configure, validate and prepare users

Map the approved process to fields, user roles, permissions and workflow rules. Inspect the source data and identify migration, integration and reporting requirements before configuration.

  1. 01

    Document set review

    We collect what you currently hold, identify what is current, what is superseded, what is duplicated and what is missing, and put the questionable ones to you for a decision.

  2. 02

    Categorisation and mapping

    Documents are organised into categories that match how employees and managers actually look for them, and mapped to the roles, departments or locations they apply to.

  3. 03

    Version control setup

    Version numbering, effective dates, approval and replacement rules are configured so a revision becomes the current document while the previous one is retained as record.

  4. 04

    Acknowledgement setup

    The policies requiring acknowledgement are identified with you, and the acknowledgement and reminder workflow is configured for those documents.

  5. 05

    Access configuration

    Role, department and location-based access is configured so each document reaches the people it applies to and no wider.

  6. 06

    Upload and migration

    The approved current document set is uploaded and organised, and the scattered copies it replaces are identified so they can be withdrawn from circulation.

  7. 07

    User training

    HR administrators are trained on issuing a revision, managing versions and reading acknowledgement reports; managers and employees are shown how to find and acknowledge a document.

  8. 08

    Go-live support

    The centre opens to the agreed user groups, with the acknowledgement campaign for any policy you have chosen to require one on.

  9. 09

    Adoption review

    After the first cycle we look at acknowledgement records, what people could not find, and which access rules turned out to be wrong, and adjust.

Test migrated records, approvals, exceptions and permission boundaries with representative users. Agree acceptance, user training, support ownership and the handling of remaining issues before go-live.

Agreed configuration and handover

  • A categorised, version-controlled policy and document centre inside the GullyHR platform.
  • Your current policies, handbook, letter formats and forms uploaded, with superseded copies identified.
  • A documented view of what is current, what was superseded and where the gaps are.
  • Acknowledgement tracking configured for the policies you require it on.
  • Review and expiry reminders configured on time-bound documents.
  • Role, department and location-based access rules for restricted documents.
  • Training for HR administrators, managers and employees, with a short reference guide.
  • An acknowledgement and document-status report agreed with management.

What your team provides

  • Your current policies, handbook, letter formats and forms, in whatever form they exist today.
  • A decision on which version of each document is the current one.
  • The list of policies that need acknowledgement and who must acknowledge them.
  • Who may see each restricted document, and an owner for every document.

Share personal records only after the scope, access and handling arrangements are agreed.

Responsibilities and approvals

The client owns employee records and approves policies, spending and employment decisions. GullyHR's assigned responsibilities are documented in the engagement.

Establishing the current document set

GullyHR
Collects and reviews what exists, and flags duplicates, superseded versions and gaps.
Your team
Supplies the documents and decides which version of each is current and approved.

Deciding acknowledgement and access rules

GullyHR
Sets out the options and configures the rules agreed.
Your team
Decides which policies require acknowledgement and who may see which documents.

Uploading and organising

GullyHR
Uploads, categorises and version-controls the approved set.
Your team
Approves each document as current before it is published to employees.

Training users

GullyHR
Trains HR administrators on versions and reports, and managers and employees on finding and acknowledging documents.
Your team
Releases staff for training and announces that the centre is now the only source.

Keeping the set current

GullyHR
Remains available to publish approved revisions and adjust access as the structure changes.
Your team
Owns the decision to revise a policy and approves the revision before it replaces the current version.

How we agree that the work is complete

Review these outputs with your process owner and agree the evidence required for sign-off.

  • Every document in scope is uploaded to a category, with one version marked current.
  • Superseded and duplicate copies are identified in a written view, with gaps listed for your decision.
  • Acknowledgement tracking is on for each policy you chose, and a test acknowledgement is recorded correctly.
  • Review or expiry reminders are set on the time-bound documents and reach the named owners.
  • Restricted documents open only for the roles, departments or locations you specified, confirmed with test logins.

Data, configuration and adoption

The document centre sits on the same platform as employee records, so a document can be scoped to the roles, departments and locations it applies to using the same structure the rest of the system already knows, rather than existing as a folder with permissions maintained separately. Version control keeps one current document visible while retaining superseded versions with the dates they applied. Acknowledgements are recorded against the employee and the specific version, and review or expiry reminders come from the date set on the document itself rather than from a parallel tracker somebody maintains. On the limits: an acknowledgement record shows a policy was issued and marked as read, which is useful evidence of communication, but GullyHR is not a legal practice and gives no opinion on whether a policy is enforceable or compliant. Where that assurance is needed, we help you frame the question and coordinate a qualified professional.

Limit access to the records needed for the agreed work. Confirm authorised users, secure sharing, retention and return or deletion arrangements before exchanging personal information.

Read the full policy and document centre service guide →

Agree the engagement before work starts.

Demonstration and configuration

A walkthrough of the centre, followed by review, categorisation and configuration of your own policy and document set.

Policy review or drafting

Where the documents themselves need writing or revising, that is scoped as HR management consulting work before configuration, so you are not version-controlling a policy you have outgrown.

Ongoing support

Publishing approved revisions, adding new documents and adjusting access as departments, locations and policies change.

Scope and exclusions

  • Confirm product fit, licensing and the implementation scope before committing. Custom development, third-party integrations and GullySystem services are separately agreed; they are not automatically included.
  • The policies themselves still need to be written or rewritten, and you expect that to be part of the upload.
  • You want legal review of policy wording, which your own adviser must confirm.
  • You want a document tool that is separate from the rest of the GullyHR platform.
  • You have no one to decide which version of a document is current.
Confidentiality, specialist review and accountability

Limit access to the records needed for the agreed work. Confirm authorised users, secure sharing, retention and return or deletion arrangements before exchanging personal information.

Applicability depends on locations, workforce arrangements and the issue under review. Confirm applicable requirements with your qualified adviser before adopting policies or employment actions; this service is not a legal certification.

Employment-law opinions, statutory filings, professional or clinical standards and safety-critical technical decisions require the appropriate qualified professional; include those dependencies in the scope.

Questions before you decide

For alteration shops, identify who owns these records: version register, publishing roles and acknowledgement report. Start with an anonymised example and the decision you need to make; agree the sample and access before sharing personal data.

Discuss your HR system

Tell us the teams and locations involved, what is happening today and what you want this work to resolve.

Start with your business need

What does your HR team need to solve?

Tell us your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.

  • A free first conversation with an HR practitioner
  • A clear scope and fee before any paid work
  • A practical next step for your business

Let’s start with your business

Share your contact details and the HR challenge on your mind. We’ll help you find the right starting point.

Include your country code, for example +44 or +1. Indian numbers can be 10 digits.

Your details stay private. Privacy policy