Staff Handbook Policies for Game Development Studios in New Zealand

A staff handbook can save a game studio a lot of trouble, but only if it actually matches the way your team works. Many New Zealand studios copy policies from overseas publishers, rely on a generic office handbook that does not fit creative production, or treat the handbook as if it can override employment agreements. Those mistakes can create real problems around overtime expectations, crunch periods, IP ownership, remote work, online conduct and contractor classification.

For game development studios, handbook policies are not just about basic HR administration. They shape how you manage deadlines, player community contact, confidential builds, moderation conduct, bring-your-own-device rules and collaboration across designers, artists, developers, QA and marketing staff. If the rules are vague, inconsistent or legally off point, the handbook can become evidence against the employer rather than a helpful internal guide.

This guide explains what staff handbook policies for game development studio operations should cover in New Zealand, where the legal boundaries are, what to check before you ask staff to follow them, and the common drafting mistakes that catch founders before they hire their first worker or before they rely on a verbal promise about workplace standards.

Overview

A well-drafted handbook helps a game studio set clear workplace expectations, support legal compliance and reduce avoidable people issues. In New Zealand, the handbook usually sits alongside employment agreements, contractor arrangements and day-to-day management processes, rather than replacing them.

The main legal question is not whether you should have a handbook, but whether the policies are accurate, consistent with employment law and suitable for the way your studio actually operates.

• Make sure the handbook does not conflict with individual employment agreements.
• Decide which policies are mandatory workplace rules and which are guidance only.
• Address studio-specific issues such as confidential game assets, IP ownership, player community conduct, anti-harassment standards, remote work and data security.
• Check whether your team includes employees, casual workers and contractors, and avoid using one policy set as if everyone has the same legal status.
• Set fair and realistic expectations around hours, leave, crunch periods, overtime approval and after-hours communication.
• Explain disciplinary and complaint processes carefully so managers follow fair process in practice.
• Review privacy, device-use and monitoring policies before collecting staff data or reviewing communications.
• Update the handbook when your studio changes size, work model, platform relationships or production structure.

What Staff Handbook Policies for Game Development Studio Means For New Zealand Businesses

For a New Zealand game studio, a staff handbook is usually a practical rulebook, not a shortcut around employment law. It should tell your team how the workplace operates while staying consistent with minimum legal rights and each person's contract.

That matters because studios often grow fast and informally. A founder may hire a programmer, a concept artist and a community manager within a few months, then realise each manager has different expectations about hours, communications, online behaviour and approval processes. A handbook gives the business one set of internal standards.

What a handbook usually does

A good handbook helps the business set expectations on day-to-day matters that would be clunky to place in every employment agreement. It can explain how the studio handles attendance, remote work, expenses, leave requests, code of conduct issues, health and safety, social media and use of studio equipment.

For a game development business, it may also deal with production-specific issues such as:

• protection of source code, design documents, art files and unreleased builds
• approval rules for using open source tools, third-party assets and AI tools
• communications with streamers, players, publishers and platform partners
• moderation standards for Discord servers, community channels and test groups
• spoiler management, embargoes and content leak prevention
• conflicts of interest, side projects and moonlighting in the games industry
• remote access, version control and cyber security requirements

What a handbook does not do

A handbook does not replace a written employment agreement. New Zealand employers still need compliant employment agreements, and the minimum rights in employment law continue to apply whether or not the handbook says otherwise.

A handbook also should not be used as a backdoor way to change pay, hours, duties or leave rights without agreement. If you want to change a contractual term, you generally need to follow a proper consultation and variation process rather than just reissuing the handbook.

Why game studios need tailored policies

Studios have workplace risks that do not always appear in standard office templates. Creative work can spill into late nights. Team members may work across time zones. Staff may use personal devices, home networks and online platforms as part of the job. Informal chat channels can blur the line between social interaction and work communication.

This is where founders often get caught. They assume a simple internet template will cover employment issues, then discover the template says little about crunch expectations, confidential assets, online harassment, moderation authority or ownership of work created on side projects.

Tailored staff handbook policies for game development studio teams also help protect the studio's culture. A small team can be damaged quickly by unclear behaviour standards, favouritism in leave approvals, inconsistent remote work rules or poor handling of complaints about bullying, discrimination or inappropriate online conduct.

How the handbook fits with contracts and worker status

The handbook should line up with your legal documents and organisational structure. If some people are employees and others are genuine contractors, you may need different onboarding materials and policy expectations.

Before you classify someone as a contractor, check the real nature of the relationship. Calling a person a contractor does not settle the issue if the studio controls their hours, integrates them into the business and treats them like staff. Misclassification can create serious employment risk, and a handbook that applies identical employment-style rules to everyone can make that worse.

Founders should also think about the hierarchy of documents. Your employment agreements should deal clearly with matters such as role, pay, hours, confidentiality, intellectual property and termination rights. The handbook can expand on internal procedures, but it should not silently contradict those terms.

Legal Issues To Check Before You Sign

Before you ask staff to acknowledge a handbook, confirm that the document is legally accurate, internally consistent and realistic for your studio to follow. A policy you cannot apply fairly is often worse than having no policy at all.

Employment agreement consistency

Your first check is whether the handbook conflicts with employment agreements. If one document says staff have flexible hours but the handbook says everyone must be online from 8.30 am to 5.00 pm, the inconsistency can create confusion and disputes.

Check for alignment on:

• ordinary hours of work
• overtime or time in lieu arrangements
• remote or hybrid working expectations
• availability outside standard hours
• leave approval processes
• confidentiality and IP obligations
• disciplinary procedures and standards of conduct

If you want the handbook to be binding on certain operational matters, say so clearly in the employment agreement and make sure the policy wording is reasonable and capable of change only through a fair process.

Minimum employment rights

Your handbook cannot undercut minimum legal rights in New Zealand. Policies about annual holidays, sick leave, public holidays, rest and meal breaks, parental leave and record keeping should be checked carefully against current legal requirements.

Studios sometimes make avoidable mistakes during busy production periods. For example, a manager may circulate a policy saying all hands are required during a release week and no leave will be approved. A studio can manage staffing and require notice for leave requests, but it still needs to act lawfully and reasonably.

Health and safety

Health and safety is not only about physical office risks. A game studio may have workstation issues, fatigue, stress, psychosocial risks, remote work hazards and late-night communication practices that affect worker wellbeing.

Your handbook can support compliance by setting practical rules around:

• ergonomic setup and reporting discomfort
• working from home assessments
• fatigue management during major milestones
• incident reporting
• bullying and harassment prevention
• safe use of equipment and studio premises
• responsible event attendance and travel conduct

Be careful not to write lofty safety commitments that managers ignore in practice. If production leads expect repeated unpaid late nights, the handbook will not protect the business from the risk created by that culture.

Privacy and monitoring

If your studio collects staff information, monitors devices, reviews communications or uses access logs, privacy settings and handbook wording need attention. New Zealand privacy obligations still matter in an internal workplace setting.

Tell workers what information you collect, why you collect it, how it is stored, who can access it and when monitoring may occur. This is especially relevant where staff use chat tools, cloud storage, project management systems, test devices or personal hardware for work.

Policies should address:

• bring-your-own-device use
• password and access control requirements
• recording meetings or calls
• surveillance or activity monitoring
• retention of HR and performance information
• handling of player data or tester information where relevant

Confidentiality and intellectual property

For most studios, this is a core issue. The handbook can reinforce confidentiality and IP expectations, but the key legal obligations should also appear in employment agreements and contractor agreements.

Think carefully about what needs to be covered:

• ownership of code, artwork, music, narrative content and design systems created in the role
• treatment of prototypes, pitch decks and internal tools
• restrictions on sharing screenshots, footage or development details
• approval rules for public speaking, portfolio use and case studies
• expectations around side projects that overlap with the studio's work

Founders often rely on assumptions here. A verbal understanding that all studio work belongs to the company is not enough.

Discipline, complaints and fair process

Your handbook can explain misconduct categories, reporting lines and investigation steps, but it should not promise a rigid process that managers cannot follow. New Zealand employment law places weight on procedural fairness, and sloppy handling of complaints can create exposure even where the underlying concern is genuine.

Policies should be clear on who staff can speak to, how concerns are raised and how the studio handles matters such as bullying, harassment, discrimination, conflicts of interest, misuse of confidential information and inappropriate online behaviour.

Keep the language balanced. Avoid statements that suggest the business will dismiss staff immediately for broad categories of conduct without investigation or an opportunity to respond.

Contractor boundaries

Before you give the handbook to freelancers or contractors, decide what parts really apply to them. A contractor can be required to follow security rules, confidentiality expectations and site conduct standards, but applying full employee-style behavioural and HR controls may muddy the legal relationship.

This matters in game studios that engage animators, composers, QA testers or narrative consultants project by project. The main risk is treating contractors like employees in practice while using contractor paperwork for convenience.

Common Mistakes With Staff Handbook Policies for Game Development Studio

The most common mistake is treating the handbook as a generic admin document when it actually sets the rules your managers will rely on. If the wording is vague, copied from another business or inconsistent with how the studio works, problems usually show up at the worst possible time, such as before a release, during a complaint or after a resignation.

Copying an overseas template

US and UK handbook templates often use different legal concepts, leave rules and disciplinary language. A New Zealand studio that adopts them without review can end up with policies that are inaccurate or misleading.

Overseas templates also tend to assume larger HR teams and formal office structures. Small studios often need something simpler and more practical.

Trying to make the handbook override the contract

Some founders insert a broad statement saying the studio may change any policy at any time and staff are automatically bound. That does not solve conflicts with contractual terms, and it can create legal and employee relations issues if used aggressively.

If a change affects a contractual entitlement or materially alters how someone works, you usually need more than a handbook update.

Ignoring crunch and after-hours expectations

Game studios sometimes avoid discussing crunch because it feels culturally awkward. The result is worse. Team members receive mixed signals, managers pressure staff informally and no one knows whether late-night messaging is optional or expected.

A sensible policy does not need to glorify long hours. It should set realistic expectations about approval, wellbeing, breaks, escalation and who can authorise urgent work outside normal hours.

Weak online conduct rules

Studio culture often plays out on Slack, Discord and social media as much as in the office. A handbook that only refers to in-person behaviour misses a large part of the workplace.

Policies should cover respectful communications, moderation authority, conflicts in public channels, harassment, offensive jokes, leaks, impersonation risks and use of personal accounts when staff identify themselves with the studio.

Overreaching on side projects

Founders understandably want to protect the studio's ideas, but a blanket ban on all outside creative work may be hard to justify and bad for morale. A better approach is to define conflicts, require disclosure in certain cases and focus on overlap with studio business, confidential information, competing projects and use of company resources.

Forgetting managers need training too

A handbook is only useful if managers understand it. Team leads often create legal risk when they improvise responses to poor performance, inappropriate behaviour or leave requests.

Common manager errors include:

• promising flexible arrangements that conflict with policy
• failing to document concerns
• searching devices or messages without checking privacy settings
• calling someone a contractor while managing them like staff
• skipping fair process because a deadline feels urgent

Using unclear acknowledgement wording

Staff should know what they are acknowledging. If the sign-off says they agree to every current and future policy as a contractual term, that may go too far. If it says nothing at all, the studio may struggle to show workers were informed of key rules.

The acknowledgement should reflect the handbook's actual legal status and sit neatly with the employment agreement.

FAQs

Is a staff handbook legally required for a game development studio in New Zealand?

Not usually as a standalone legal requirement, but it is often a very sensible business document. You still need compliant employment agreements and proper workplace processes.

Can we change handbook policies without employee agreement?

Sometimes, but not always. Minor operational policies may be updated more easily, while changes affecting contractual terms or important working conditions usually need consultation and agreement.

Should contractors receive the same handbook as employees?

Usually no. Contractors may need selected policies, such as security, confidentiality and site conduct rules, but giving them a full employee handbook can blur worker status.

Can the handbook say all work created by staff belongs to the studio?

You can set that expectation, but the safest approach is to cover IP ownership clearly in employment and contractor agreements as well. The handbook should support those clauses, not replace them.

What policies matter most for a game studio?

The most useful policies usually cover code of conduct, anti-harassment, confidentiality, IP, remote work, device and data security, leave and hours, complaints, health and safety, social media and side projects.

Key Takeaways

• Staff handbook policies for game development studio businesses should be tailored to the way your team actually works, not copied from a generic overseas template.
• The handbook should support your employment agreements, not conflict with them or try to replace them.
• Studios should pay special attention to confidentiality, intellectual property, remote work, online conduct, community interactions, side projects and cyber security.
• Policies about hours, overtime, crunch periods, leave and after-hours communication should be realistic, lawful and consistently applied.
• Privacy, monitoring and device-use rules need careful drafting before you collect staff data or review communications.
• Employees and contractors should not automatically receive the same policy treatment, especially where worker status is not straightforward.
• Managers need to understand and follow the handbook, because poor implementation often creates more risk than poor drafting alone.
• If you are reviewing or negotiating staff handbook policies for game development studio and want help with employment agreements, contractor classification, confidentiality and IP terms, privacy and workplace policy drafting, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.