Skip to main content
GullyHR

HR process design · Warehouse developers

HR Foundation Package for Warehouse developers

The HR Foundation Package is a fixed-scope engagement for a business with no real HR system yet. On a schedule agreed in writing, GullyHR writes, tests and hands over an agreed set of basics: an employee handbook, five core processes, standard letters, first HR records and a simple report. Scope and fee are agreed in writing before the work starts.

Colleagues organising HR folders and reviewing a setup plan.

HR Foundation Package for Warehouse developers

What this looks like in your business

Warehouse developers grow from a land deal and a handful of engineers into a company with a leasing team, a construction programme and a park that must run through every night. The people side is still held together by phone calls and one trusted manager. The HR Foundation Package gives that company its first written basics: a handbook, five core processes, standard letters and a first set of records. Owners reach for it when a second park opens, when guard and technician shifts are arranged by message, or when a tenant asks for something in writing and there is nothing to hand over.

Why a growing developer has nothing written down yet

A warehouse developer rarely starts with HR. It starts with land, approvals and a construction schedule, and people are added as each need appears: a project manager here, a site engineer there, then a leasing manager once the first building is nearly ready. When the first park opens, security and facility teams arrive almost overnight, and they work in a pattern the head office has never had to manage, with gate shifts around the clock and technicians covering pumps, power and dock equipment. Nobody sat down to write what happens when a guard misses a shift, who may approve a swap, or what a site engineer is owed when a delay turns a weekend into working time. Each manager has an answer, and the answers differ between the head office, the construction sites and the parks. Staff notice the differences before the owner does. The foundation package exists for this moment, when the business has outgrown memory and goodwill but has not yet built an HR function. It sets one version of the basics so that every site, shift and manager starts from the same page.

What gets written first and in which order

GullyHR begins with a baseline of what already exists: appointment letters, the guard roster, any message that works as a rule, and the way a joiner reaches a site today. From this we set the order of work around the people you actually have. The employee handbook comes first, written in your own terms for head office staff, site teams and park staff, with a clear section for shift workers. Five core processes follow as one-page documents. For a developer these are likely to be joining before the first day, leave and cover, shift and attendance at the park, handling a complaint, and exit with return of keys, access cards and tools. Each process is tested with a real case before handover, such as a new guard starting at a park. Standard letters come next, so a project manager or park operations manager can issue an offer or a warning without waiting for head office. Last, we set up first HR records and a simple report on a schedule agreed in writing, kept separate from any ongoing transaction handling.

Suppose a second park opens with a rushed security team

Suppose a developer has one working park and a second nearing handover. The park operations manager has two weeks to bring in security supervisors, guards and two facility technicians, some on the developer's own books and some supplied by a contractor. Today she would ring a few people and agree dates by message. With the foundation set in place, the joining process says what must be on file before a guard stands at the gate: the signed letter, the induction record, the site pass, and a named supervisor. The leave and cover process says a technician who knows the fire pump cannot take leave while the other is away. The standard letter for fixed-term gate staff is ready, and the handbook explains the shift pattern in plain words. The owner makes the real decisions: what notice a guard owes, whether night allowance is stated in the handbook, and who may approve a swap. GullyHR writes those choices down once they are made, and the manager uses the document, not a memory, on joining day.

Settling owners, records and what stays with you

Before handover, a few roles must be named, and the package is built so they are not left vague. Someone at head office owns the handbook and any change to it. Each park operations manager owns the joining and exit steps for the park. Project managers own the site engineers' attendance and cover. Tenant coordination staff should know which written rules apply to them and which belong to the tenant's own site. Records are kept in one place with a short list of what every employee file contains, so a missing induction record is visible at once. The simple report shows joiners, exits and open cover gaps on the schedule you agreed. What stays with you is the content of the decisions: pay, notice, shift allowances and the rules themselves. GullyHR writes and tests the documents, but your own legal adviser should review the handbook and letters before issue, because local rules differ. Ongoing handling of joiners and leavers is a separate service and not part of this fixed-scope engagement.

The first weeks

  1. 01

    Hold the free first conversation, then agree the fixed scope in writing, naming the sites, parks and staff groups the handbook must cover.

  2. 02

    Gather existing appointment letters, the current gate guard roster, and any messages or notes that managers treat as rules.

  3. 03

    Interview the park operations manager, a project manager and a leasing manager to find where shift, cover and joining practice differ.

  4. 04

    Draft the handbook and the five core processes, then test the joining process on one real or planned guard or technician joiner.

  5. 05

    Hand over standard letters, the first employee records and the simple report, and train each manager to use them without outside help.

The operating context

Build the minimum HR structure in a usable sequence

A warehouse developer builds and leases large storage and logistics space, with a small head office and teams for land, construction and park operations. This is how to run people when tenants expect a warehouse that works from day one.

Land acquisition and project managersLeasing and business development managersSite and quality engineersPark operations managersSecurity supervisors and guardsFacility and maintenance technicians
Construction supervisors and an HR coordinator reviewing crew deployment in a site office

The decision to work through

Prioritise employee records, essential policies, role ownership and recurring processes around the starting workforce. Workforce to consider: Land acquisition and project managers, Leasing and business development managers, Site and quality engineers.

Records to prepare

Baseline inventory, implementation plan and accepted foundation documents. A workforce issue to consider: A handful of managers handle several land parcels, build sites and parks, and none has a deputy.

An exception to test

Check which missing decisions block the next step and separate setup work from ongoing transaction handling.

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.

  • Third-party logistics providers
  • E-commerce and quick-commerce operators
  • FMCG and consumer goods companies
  • Automotive and engineering supply chains
  • Pharma and cold chain operators
  • Retail chains with a regional distribution centre

When to consider this service

  • Each manager joins, approves leave and confirms probation in their own way, and you only hear about the difference when two employees compare notes.
  • The appointment letter is a file copied from a former employer, and nobody is sure which version is current.
  • Month-end payroll starts with a scramble to find who joined, who left and who took unpaid leave.
  • You have no handbook, so every question about notice, holidays or conduct is answered from memory and sometimes answered differently.

Businesses this service is designed for

  • Founder-led businesses of roughly 20 to 100 people where HR has so far been handled by the founder, an admin manager or an accountant.
  • Companies that have grown past the point where one person's memory can carry hiring, leave and payroll inputs.
  • Businesses preparing to hire a first HR manager, who want a working base for that person to inherit.
  • Companies with several managers who each handle people matters in their own way and want one consistent method.

What we design

GullyHR does the drafting, testing and handover; you decide how your business wants to run. We start from what you do today, write the agreed basics in plain language, try each one on real cases from your own team, and correct it before it is handed over. You give us access to your people, current documents and decisions on policy. The work is a defined package with a scope agreed in writing, a mid-point review and a handover session. It is not open-ended consulting, and anything outside the agreed list is scoped separately. Where a document touches employment law, we flag it for review by a qualified professional rather than giving a legal opinion.

An employee handbook written for your business, not copied from another.

Working hours, holidays, leave, conduct, notice and the everyday rules are set down in plain language, using the decisions you make with us. Points that depend on law are marked for confirmation with a qualified professional.

Five core processes written as one-page documents.

Joining, attendance and leave, monthly payroll input, probation and confirmation, and exit. Each page shows the steps, who does each one, what gets recorded and when the document will next be reviewed.

Each process is tested before it is handed over.

We run every process on real or recent cases from your team, such as a recent joiner or a leave request, and see where it breaks. The page is corrected after the test, not before it.

Standard letters and templates your managers can use unaided.

Appointment, confirmation, warning, relieving and the other letters you actually send are drafted once, in a consistent form, with clear fields to fill. Legal wording is flagged for professional review.

A first set of HR records and a simple report on a schedule agreed in writing.

An employee master, a leave record, an exit record and a probation tracker are set up, along with a short monthly set of figures such as headcount, joiners, leavers and open confirmations.

From current practice to a working process

Walk through the present process with the people who run it. Identify the trigger, missing information, decisions and exceptions before drafting the future workflow.

  1. 01

    Weeks 1 and 2: baseline

    We agree the scope in writing, collect your current documents and speak to the people who do the work. We write down how each of the five processes runs today and list what is missing, so the starting point is clear to everyone.

  2. 02

    Weeks 3 to 5: decisions and first drafts

    We bring you a short list of policy decisions to make, such as leave types, notice and probation length. Once you decide, the first drafts of the handbook, process pages and letters are written.

  3. 03

    Weeks 6 and 7: testing on real cases

    Each process is run on recent or live cases with the people who will use it. We note every point where it hesitates, a missing step or an unclear owner, and fix it.

  4. 04

    Week 7 or 8: mid-point review

    A review with you on what is written, what has been tested, what is slipping and what has changed. Scope changes, if any, are agreed in writing at this point rather than assumed.

  5. 05

    Weeks 8 to 10: records and reporting

    The first HR records are set up and filled from your existing information, and the recurring reporting set is built and run once on real data, so the first report is seen before handover.

  6. 06

    Weeks 11 and 12: manager briefing and refinement

    The people who will run each process are briefed on their part. We make final corrections from what they find and from the first live use of the documents.

  7. 07

    Week 13: handover

    A handover session covers each document, who owns it and when it is next reviewed. You receive everything in editable form, with a short note on what to look at in the next quarter.

Test normal and exception cases with the process owner, record changes, and agree acceptance before handing responsibility to the internal team.

The tools your team takes over

  • An employee handbook written for your business, with law-dependent points marked for professional confirmation.
  • Five one-page process documents covering joining, attendance and leave, monthly payroll input, probation and confirmation, and exit, each with an owner and a review date.
  • A record of the test run for each process, showing what was tried and what was corrected.
  • A set of standard letters and templates for the stages you actually use.
  • A first set of HR records: employee master, leave record, probation tracker and exit record.
  • A simple reporting set with a short note on how to read and use it.
  • A responsibility sheet showing who in your business owns each document and each step.
  • A handover session with the people who will run the processes.

What your team provides

  • Access to the people who run joining, leave, payroll input, probation and exit today, for short conversations.
  • Your current documents, letters and records, even where they are rough or incomplete.
  • Decisions on policy points that only you can take, such as notice terms and leave entitlements.
  • Real cases from your own team to test each process against, shared in confidence.

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.

Scope and plan

GullyHR
Proposes the scope, the 90-day plan and the dates for the mid-point review and handover, and records them in writing.
Your team
Confirms the scope, names one point of contact and keeps the review dates in the diary.

Policy decisions

GullyHR
Lists each decision needed, sets out the options and says what other businesses of your size commonly do.
Your team
Makes the decisions promptly, since drafting waits on them.

Drafting

GullyHR
Writes the handbook, process pages, letters and templates in plain language.
Your team
Reviews drafts, corrects facts about how the business really works and approves the final versions.

Testing on real cases

GullyHR
Runs each process on live or recent cases and records what needed to change.
Your team
Provides cases, makes the managers and staff involved available and shares the records needed.

Records and a report on an agreed schedule

GullyHR
Sets up the first records, loads your existing information and builds the report format.
Your team
Supplies employee information, confirms its accuracy and keeps the records updated after handover.

Employment law points

GullyHR
Marks every point that depends on law and coordinates review by a qualified professional where you ask for it.
Your team
Engages its own legal adviser, or asks GullyHR to arrange the coordination, and decides what to adopt.

Measures to agree before work starts

These are measures to track against your baseline, not promised results. Agree definitions, record sources and review dates at the start.

  • Processes written and tested
  • Processes with a named owner
  • Processes with a review date
  • Letters and templates in use
  • Employee records complete
  • Report produced on the agreed schedule
  • Handover session completed

Tools and implementation dependencies

The records and the report can be kept in a spreadsheet you already own, and that is a perfectly sound way to start. If you want them held in software, the employee master, leave record and attendance data can be set up in GullyHR's HRMS software, because the process pages already name the fields, owners and approvals the software needs. That decision is yours and is made after the processes are settled, not before. Nothing in the package requires you to buy software.

Read the full HR foundation package service guide →

Agree the engagement before work starts.

The standard package

The full set described on this page, run over about 90 days against a scope and fee agreed in writing before work begins.

Package with a software follow-on

After handover, the records and processes are set up in HR software as a separately scoped piece of work, built from the pages already written.

Package with ongoing support

After handover, a light monthly arrangement through fractional HR management to run, review and refresh the documents as the business changes.

Package after a process review

For businesses that have already seen a process audit, the package starts from its findings instead of repeating the baseline.

Scope and exclusions

  • The written scope defines the process, templates, testing and handover included. Continuing transaction handling and additional systems work are agreed separately.
  • You already have written processes and want them reviewed rather than rebuilt; the HR Process Audit rates what exists.
  • You need one process fixed, not five; a single process design project is smaller and quicker.
  • You are a very small team not yet hiring regularly; a sector starter pack gives you the basics without the 90-day programme.
  • You want someone to run HR for you rather than hand it over; outsourced HR management does that.
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

One handbook is the aim, with clearly marked sections for staff who work shifts at a park and for site teams on a project. GullyHR writes it around the groups you have, not a copied template. Where site, park and head office rules must differ, we state the difference once, in plain words, and your own legal adviser reviews the draft before it is issued.

Discuss this process

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