Core employment model
The workforce types, working patterns, locations, benefits and management practices the documents genuinely need to support.
Contracts and employee handbook setup
Build one employment system—not a folder of unrelated templates.
For a growing employer, the real value is not the number of documents. It is knowing which promises are contractual, which rules are policies, how they connect and how managers should use them.
The useful starting point
Document architecture is an operating decision.
A contract should hold the durable individual terms. A handbook should make shared expectations and procedures easy to find and update. Starter forms should support the same process. When those layers are designed together, managers can explain them and future changes are less likely to create contradictions.
This route may fit when
Start here if any of this sounds familiar.
- 01Your business has grown beyond informal founder-led arrangements.
- 02Contracts, policies and starter documents have been collected from different sources.
- 03Managers cannot tell which rules are contractual or where the current version lives.
- 04You need a proportionate core handbook rather than dozens of unused policies.
- 05You want a stable foundation before recruitment or headcount accelerates.
What I examine
The decisions behind the document.
A useful contract service joins the wording to the operating reality. These are the questions that make the document usable.
Contractual layer
The durable individual terms, appropriate flexibility and the references that connect each contract to shared organisational documents.
Policy layer
A proportionate core handbook covering the procedures and standards people need, without turning every operational choice into a contractual promise.
Implementation layer
Version control, issue records, acknowledgement, onboarding prompts and simple ownership so the documents remain usable after handover.
What you receive
Something you can actually implement.
Exact deliverables are confirmed in writing so the boundary is visible before you instruct me.
- A tailored core employment contract
- A proportionate core employee handbook
- Agreed starter and acknowledgement documents
- An onboarding and implementation checklist
- A document map showing ownership, status and review points
Important boundary
The package creates a foundation, not permanent outsourced maintenance.
Documents are current at issue. Future legal updates, policy ownership, case advice, consultation and manager training are separate unless they are expressly included in the scope. That boundary keeps the initial package honest and the price visible.
Practical questions
Straight answers before you enquire.
How many policies are included?+
The aim is a coherent core handbook, not an impressive page count. The exact policy set follows the workforce, sector and agreed risks. Additional specialist policies can be scoped where they genuinely earn their place.
Are handbook policies contractual?+
Usually the architecture is designed to keep most shared policies non-contractual, while the contract clearly identifies the binding individual terms. Existing wording and practice still need checking before documents are replaced.
Does the package include future updates?+
No automatic lifetime promise. The documents are version-current when issued. A future review or maintenance arrangement can be agreed separately if that is useful.
Not sure which route fits?
Tell me the situation, not the legal label.
I'll point you to the sensible next step.
Describe the real situation without including names, health information or other sensitive employee details. I’ll tell you the proportionate next step before any paid work begins.