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.