HR Policy Packages for ERP software providers
What this looks like in your business
Policies in an ERP firm have to describe work that most office policies never meet: a consultant living at a client's premises, a cut-over weekend that runs through the night, client credentials held by developers, a support rota that covers a client's month-end. Owners reach for a policy package when a go-live argument about time off, or a client complaint about how a consultant handled data, shows that nothing is written down. GullyHR drafts the package in one structure, with an employee FAQ, a workflow and forms for each policy, and your own legal adviser reviews it before issue.
Which policies a project firm needs first
Policy gaps in an ERP business show up at the points where delivery meets people. A working hours and go-live policy decides how a cut-over weekend is planned, what time off follows and who approves it. A client-site deployment policy covers travel, accommodation, conduct on a client's premises and how long an assignment lasts before it is reviewed. A confidentiality and client data policy covers the production data a data migration specialist handles, the credentials a support engineer holds and what happens to both on exit. An intellectual property policy settles who owns the reports, scripts and add-ons a developer writes. A support rota and on-call policy sets how cover is shared and recognised. Leave, notice and handover policies then fill in the basics. Starter, Core and Complete packages differ in the number of policies they contain, and GullyHR helps you choose the smallest set that settles the disputes you actually have. A founder who has just lost a consultant mid-project may want notice and handover first; one with a support backlog may want the rota policy.
What is settled before any drafting
A policy is a set of decisions written down, so the decisions come first. Before drafting, GullyHR takes you through the choices that only management can make. For go-live weekends: is time off in lieu offered, within what window, and does the client's billing affect it? For client sites: who pays travel and lodging, and what notice does a consultant get before a move? For confidentiality: may a developer keep a copy of a report they wrote, and who can hold a client's login? For the rota: is cover paid, rotated or traded? GullyHR also reads your existing documents, such as offer letters, past emails announcing rules, and any handbook, to find conflicts, for example a letter that promises one leave entitlement and a policy that says another. Once the choices are made, each policy is written in the same structure, with an employee FAQ in plain language, a workflow that shows who does what, and the forms a manager or consultant would complete. Drafts go to your legal adviser before they are issued to anyone.
Take the cut-over weekend policy
Take a provider that has argued about time off after every go-live. The founder, the delivery head and GullyHR meet once to settle the choices. They agree that a cut-over weekend is planned at least a set number of days ahead, that the project manager names who works and for how long, and that time off in lieu is taken within an agreed window after the client signs off. GullyHR drafts the policy with a one-page workflow: the project manager completes a weekend effort form, the delivery head approves, HR records the time off, and the line manager confirms it was taken. The employee FAQ answers the questions a tired consultant asks on Monday: whether travel home counts, what happens if the client extends the cut-over, and who to speak to if the rule is not followed. In review, the delivery head notices the draft says nothing about data migration specialists who start before the weekend, and a line is added. The founder then sends the draft to her adviser, who confirms what is needed for her country before it is issued.
Owners, records and what you still decide
A policy that nobody owns slowly stops being followed. For each policy GullyHR proposes a named owner: the delivery head for go-live and deployment policies, the support lead for the rota policy, the founder or office manager for leave, notice and confidentiality. Each policy has a record that shows it is working, such as the weekend effort form, the assignment register, the signed confidentiality acknowledgement or the rota log. Handovers are written into the policy itself: how a consultant's client knowledge is left behind, how a developer's access is removed at exit, and how a support rota passes cover at month-end. Packages can grow with the company, so a Starter set can be extended to Core once you have the next ten consultants. What stays with you: every choice inside a policy, the decision to adopt it, how strictly it is applied, and confirmation from your own legal adviser that it suits the rules of your country. GullyHR drafts and explains; it does not give legal advice. Policies you outgrow are revised in the same structure, not replaced.