PB-02 · playbook · owned by Jon & Zak · creative

creative.

Where ideas, stories and experiences take shape. The craft standard — how Creative pitches, reviews, approves and ships work, from concept to delivery.

last reviewedApr 2026
version0.1
statusin development
01

the short version.

Creative is the heart of what makes Zeal’s work distinctive. It shapes ideas, stories and experiences — from initial concept through to final delivery.

This playbook will grow as processes are formalised. For how Creative roles work within projects, see PB-01 projects. For how Creative fits within the wider organisation, see OS-04 structure & departments.

Sections marked in development below are tracked in the Processes subfolder of the Creative playbook in Dropbox. They’ll move into this page as they’re drafted.

02

creative tools & software standards.

in development

The standard creative software suite, version requirements, and any tool-specific guidelines that protect creative output and downstream compatibility.

to develop

Document the standard creative software suite, version requirements, and tool-specific guidelines — including how exceptions are agreed when a project genuinely needs an off-stack tool.

owner · Jon
03

deck & presentation assembly.

in development

How client-facing presentations get built — templates, approval steps and brand compliance, so every deck that leaves Zeal looks like a Zeal deck.

to develop

Document the process for creating client-facing presentations — templates, approval steps, brand compliance, and the relationship to OS-03 brand.

owner · Zak
04

visual content guidelines.

in development

Standards for visual content creation: resolution, format, colour profiles, output specifications. The bones that keep visual quality predictable across a project.

to develop

Document resolution, format, colour profiles, and output specifications for visual content — with worked examples per output type (LED, projection, print, screen).

owner · Zak
05

file naming & management.

in development

File naming conventions, folder structure and archiving standards for creative assets — so the next person who opens the project folder finds what they expect.

to develop

Document file naming conventions, folder structure and archiving standards for creative assets. Reconcile with the Dropbox folder shape in PB-01 — where files live.

owner · Jon
06

creative review & approval.

in development

The internal review workflow, sign-off stages and how creative feedback is managed — so no first draft survives the second pair of eyes, on purpose.

to develop

Document the internal review workflow, sign-off stages, and feedback handling. Includes the relationship to the Creative Lead role defined in PB-01.

owner · Jon · Zak
07

render standards.

in development

Render specifications, quality benchmarks and delivery formats for different output types — the things that turn a finished render into something the rest of the chain can rely on.

to develop

Document render specifications, quality benchmarks and delivery formats for each output type.

owner · Zak
08

design file handover to technical.

in development

The handover from Creative to Technical — what files are required, what format is expected, and how communication flows when there’s a question.

to develop

Document the handover process from Creative to Technical — required files, formats, communication standards. Sister section in PB-03 technical.

owner · Jon · Josh
09

change log.

department leads
versiondateauthorsummary
0.126 Apr 2026SteveDraft structure published.