HR Foundation Package for Architecture firms
What this looks like in your business
For an architecture firm that has grown past the principals knowing everyone, the HR Foundation Package puts the basics on paper in one fixed engagement. A studio of project architects, draughtspeople, visualisers and interns reaches for it when intern terms live in an email, leave in a diary and the route to project architect in the principals' heads. GullyHR writes a handbook in the studio's own language, five core processes as one-page documents, standard letters, first HR records and a simple report. Each piece is tested with your people before handover, and the scope and fee are agreed in writing before work starts.
Why a growing studio needs written basics
A studio of ten can run on goodwill. A studio of thirty cannot, and the break arrives during a submission crunch, when nobody can say whether late weeks earn time back, who approves leave while a project architect is on site, or what an intern is expected to draw. Interns draw most of the sheets, so the absence of written terms hits the youngest people first. Project architects hold more threads than they can follow and settle HR questions on the fly, each in their own way, which means two teams in one firm follow different rules. Pay trails other careers, so every rise becomes a private negotiation with a principal and the firm has no band to point to. Site and studio stop talking about people as well as drawings: a site architect on leave, or a visualiser on a deadline, is known only to whoever happens to ask. The package exists to replace these habits with a small set of documents that every project architect and every newcomer can read in one sitting.
What GullyHR sets up first in the studio
GullyHR begins by listing what the firm already has: offer letters, the intern agreement if one exists, the leave diary, any overtime notes and the titles on the pay sheet. From this it chooses the five processes the studio will lean on most. For an architecture firm these are likely to be joining a junior or intern, recording leave and late working across a submission, agreeing a pay change, moving someone from junior architect to project architect, and leaving the firm with a clean handover of drawing and model files. Each process is written as a single page with the owner named, the steps in order and the record that proves it was done. The handbook follows, written around studio hours, crunch weeks, site visits, software use and confidentiality of client drawings. Letters come last: offer, confirmation, a change of role and an exit note, each with blanks a project architect can fill in without asking a principal. The aim is a small set that a new project architect can use on the first morning without asking a principal.
A worked example from a hospitality practice
Suppose a hospitality architecture practice has three principals, six project architects, a BIM team of four and a changing group of interns. Before the package, a project architect leaving for a competitor handed over nothing in writing, and the model folders were found half organised weeks later. GullyHR drafts the exit process first. It lists the steps: the leaver's project architect lists live drawings and model folders, the BIM lead confirms the latest file versions, a principal signs the handover, and the administration lead closes access. GullyHR then tests the page with the studio. A BIM specialist is asked to follow it for an imaginary leaver, and the test shows that the list does not say who holds consultant contacts. That line is added, the page is reissued, and the next real exit follows it. The principals decide whether the signed checklist becomes a condition of the final pay release. GullyHR writes the document; the firm and its adviser decide how it binds anyone. The principals also see, in one afternoon, how little the old exits relied on written steps.
What the firm owns once the package is handed over
Handover is a transfer of ownership, so GullyHR names who keeps each document alive. The administration lead holds the handbook, the letters and the first HR records, and updates them when a rule changes. Each project architect is the first point of call for leave, late working and progression on their own projects. One principal approves pay changes and promotions, and that is written into the pay change page. The simple report goes to the partners on the agreed schedule and shows headcount by role, joiners and leavers, and open actions. Anything the studio cannot yet settle, such as how credit is shown on drawings, is listed as a decision for the partners rather than guessed at. The package covers writing and testing the basics. It does not run HR from day to day, and any point about contracts, working time or notice goes to your own legal adviser before the handbook is issued. The partners also agree a date to review the documents together once the next submission crunch has passed.