HR Policy Packages for Interior design firms
What this looks like in your business
Design firms learn their rules the hard way: a designer asks whether a Saturday handover earns time off, a client's lawyer asks who owns the drawings, a freelancer posts a project image before it is approved. A policy package is the set of written answers GullyHR drafts so these questions stop landing on the principal. Starter, Core and Complete cover different depths, and every policy follows one structure with an employee FAQ, a workflow and forms. Drafts go to your own legal adviser before issue. You choose the package after a short call about how your studio actually works.
Where unwritten rules cost a design firm most
The costliest gaps in a design firm sit where creative work meets client property and long hours. A designer works from a laptop that holds client plans, supplier prices and unreleased renders, but no policy says where files may be stored or who may share them. Handover weeks stretch late into the night, and the question of recognition for that time is settled case by case, which means two designers on the same flat can be treated differently. Site visits mean travel, yet claims are approved by whoever is nearest. Supervisors direct vendor crews in the firm's name without a written line between instruction and negotiation. Freelancers join with no statement on confidentiality or use of the firm's name. When a client changes the brief midway, nothing says how extra work is shared or who may refuse. Without written rules each of these is argued afresh, and the argument is remembered by the person who lost it. A policy package turns these arguments into pages the studio can point to, calmly, before the next handover.
Choosing which policies your studio can really run
GullyHR does not hand over a full pack and wish you luck. It first lists the documents you already hold, even if they are only a leave email and an offer template, then compares them with the way your people work. For most studios the first policies to settle are working hours across studio, client premises and sites, leave and attendance for people who move between places, handover-week hours and recognition, travel and expense claims, confidentiality of client designs and renders, use of laptops and shared drives, conduct on client premises and a route for raising a complaint. Starter covers the questions that cause most disputes, Core adds the policies a growing studio needs next, and Complete reaches into the full set in stages. Each policy follows the same structure, so a junior designer reads one and understands how to read the rest. Management choices, such as how generous handover recognition will be, are settled with you before drafting, because a policy that nobody can afford to follow is worse than none.
A worked example around handover-week hours
Picture a studio with two project managers and nine designers that has argued over handover nights three times in a year. The principal chooses a Core package, and the first policy drafted is working hours and handover weeks. GullyHR first asks what really happens: who stays, who decides, what is promised and what is forgotten. The principal decides that a handover night earns time off in the following week, approved by the project manager and recorded on a one-line form. The draft policy states the rule, the approver, the form and an employee FAQ that answers whether a half day counts. Then GullyHR checks for conflicts with the leave policy, which says all time off needs a week's notice, and resolves the clash in writing. A supervisor who works a Sunday handover is covered by the same page. The package goes to the studio's legal adviser, who changes two lines of wording. After issue, the first handover under the new rule is read back with the project manager to see whether the form was used.
Owners, forms and what remains your decision
Every policy needs a keeper and a place to be found. In a design firm the studio head or operations lead should keep the set, with dated versions in one shared folder and old copies removed. Project managers should know the policies on hours, travel and handover recognition well enough to apply them on a site visit. Site supervisors need the conduct and vendor-instruction pages in a form they can read on a phone. Freelancer engagement and confidentiality pages belong in the pack handed to anyone who joins a project, together with a short note on who to ask. Forms, such as the handover-time record and the expense claim, should be one page and live where the team already works. A policy is issued by you, after your legal adviser has confirmed the wording, and read by each person with a record that they have. What stays with you: the choices behind each policy, from how generous recognition is to how firmly client files are protected, and every exception that you decide to grant.