HR Foundation Package for Turnkey construction companies
What this looks like in your business
A turnkey construction firm reaches a point where it has a dozen or more people across design, procurement, site and commissioning, yet HR is a drawer of offer letters and the project director's memory. The HR Foundation Package gives that firm its first working basics: a handbook that speaks to design engineers and site engineers alike, a small set of one-page processes, standard letters and first people records. The owner asks for it when a second project starts, when engineers are being moved between sites without a written note, or when a client asks who is accountable for the team that will hand over the building.
Where a first HR system is missing in construction
In a young turnkey firm the first projects run on the owner's presence. The owner knows who is good at drawings, who can hold a site, and who can be trusted with a client meeting. Then a second project opens, a few engineers are borrowed from the first, a safety officer is hired, and the owner can no longer be in the room for every decision. What was obvious becomes a dispute: whose leave was approved, which allowance applies on a remote site, who decides that the design manager can instruct the site engineer.
The handbook fails here because it is borrowed from an office business. It says nothing about site hours, travel to a project, or what happens to a team when a package closes. Project teams disband fast, and without written steps for release and redeployment the firm loses people in the gaps between projects. Commissioning is the sharpest case: a handful of engineers carry the final stage for every project, and no document says how their time is requested, protected or rewarded. The package exists to fix this with a small, usable set of papers, not a thick binder.
What GullyHR writes and tests first
GullyHR begins with the people actually on your books and the projects they serve. A short baseline list records each role, reporting line and project, and exposes the questions the handbook must answer: who may instruct whom, how site and design hours differ, how travel and site stays are treated, and how a person moves from one project to the next.
The handbook is then written in your firm's voice, with separate short sections where design office and site genuinely differ. Five core processes follow as one-page documents, chosen from the moments that hurt most in this trade: joining onto a project, moving between projects, leave and attendance on site, release at project closure with a handover note, and exit. Each is tested on a real case before handover. For example, the joining page is walked through with the last site engineer you hired, and the release page with the team that just finished.
Standard letters come next: offer, role confirmation for a project post, transfer between projects and release. A first people record and a simple report on a written schedule close the work, so you can see who is on which project.
Suppose a second project opens next month
Suppose a firm with one commercial fit-out under way wins a warehouse build. The owner needs two site engineers and a quality engineer on the new job within weeks, and plans to move one planning engineer across. There is no written transfer step, and the planning engineer has never been told whether her allowance, reporting line or leave balance changes.
With the foundation papers in place, the sequence is short. The project director completes the transfer note, naming the new project, the start date and the person she now reports to. HR issues the standard transfer letter, and the leave balance carries over on the first people record. The two new engineers receive the joining page, which lists what they must receive on day one: role note, safety briefing, site contacts and the handbook sections for site staff. The quality engineer's joining is tested against the page, and the owner finds one missing step, who briefs the engineer on the client's approval routes. That is added before the process is handed over.
The owner then decides whether the allowance rule is acceptable. The package records the choice; it does not make it for you.
Who runs each paper once it is handed over
A foundation is only useful if someone owns each part after handover. In a firm like this, the project director normally owns the transfer and release notes for their project, because they know when a package closes. The design manager owns the role notes for design posts, and the safety officer owns the site joining briefing. Head office, whether that is the owner or an administrator, holds the originals and the first people record.
GullyHR hands over the handbook, the processes, the letters and the record in a form your managers can use without calling for help. The simple report, such as who is on which project and who is leaving in the coming weeks, is sent on the agreed schedule and read by the owner.
What stays with you is judgment. You decide pay levels, allowances for remote sites, how long a commissioning engineer is protected from new assignments, and when a team is released. The finished papers go to your own legal adviser before issue, so that local rules on contracts, working time and site work are confirmed by someone qualified to say so.