Skip to main content
GullyHR

HR process design · Architecture firms

HR Foundation Package for Architecture firms

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 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.

The first weeks

  1. 01

    Agree the scope and fee in writing with the partners, naming the five processes and the handbook sections the studio most needs.

  2. 02

    Collect existing offer letters, the intern agreement, the leave diary and the current pay sheet by role into one folder.

  3. 03

    Interview two project architects and one junior about how joining, leave and late working are handled today in their teams.

  4. 04

    Draft the five one-page processes and the first standard letters, with a named owner and a record for each step.

  5. 05

    Test each process with a project architect and an intern, correct the gaps found, then hand over the handbook and report layout.

The operating context

Build the minimum HR structure in a usable sequence

An architecture firm sells design and drawing sets over long project timelines. It keeps good people only while the work stays interesting and the step from drawing board to project architect is visible.

Principals and partnersProject architectsJunior architects and internsDraughtspeople and BIM or CAD specialists3D and visualisation artistsSite architects
Workplace scene for Architecture Firms: Principals, Drawings and Site Teams

The decision to work through

Prioritise employee records, essential policies, role ownership and recurring processes around the starting workforce. Workforce to consider: Principals and partners, Project architects, Junior architects and interns.

Records to prepare

Baseline inventory, implementation plan and accepted foundation documents. A workforce issue to consider: Late nights gather before each presentation and approval deadline, and the same few people carry them every time.

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.

  • Residential and villa architecture practices
  • Commercial and corporate campus architecture firms
  • Hospitality architecture practices
  • Institutional architecture firms, schools and hospitals
  • Interior-architecture hybrid practices
  • Sustainable and green building specialists

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

An audit reviews what you already do and rates it. The Foundation Package builds what is missing. If the studio has no handbook, no written processes and no HR records, GullyHR writes and tests them for an agreed scope and fee. You can start with the package and audit later, or the other way round. The first conversation is free.

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