technical.
The bridge between imagination and reality. Technical translates creative intent into deliverable technical reality — on time, to standard, and safe.
the short version.
Technical exists to make sure what is imagined can be achieved, what is planned can be delivered, and what is delivered meets the standard.
Technical sits between Projects, Creative, and Operations. Creative defines the intent. Operations runs the kit. Technical owns the translation — feasibility, design, paperwork, signal flow. For how Technical fits within the wider organisation, see OS-04 structure & departments.
Sections marked in development are tracked in the Processes subfolder of the Technical playbook in Dropbox. They’ll move into this page as they’re drafted.
feasibility process.
How Technical assesses creative concepts for feasibility — timelines, sign-off points, and the escalation path when a concept needs to be adapted.
Document the feasibility assessment process — including how concerns are raised early, how trade-offs are negotiated with the Creative Lead, and when escalation goes to the PM.
owner · Joshtechnical design workflow.
Brief to technical design — review stages, collaboration with Creative, and the deliverables Technical owns at each phase.
Document the workflow from brief to technical design — review stages, collaboration touchpoints with Creative, and the output deliverables at each milestone.
owner · Joshpaperwork & documentation standards.
Risk assessments, method statements, power calculations, rigging plans — the technical paperwork that protects the project, the team, and the venue.
Document the standards for technical paperwork — risk assessments, method statements, power calculations, rigging plans — including templates and review responsibilities.
owner · JoshCAD & drafting standards.
Software standards, drawing conventions, file formats and version control. The rules that keep CAD work readable and reusable across projects and time.
Document the CAD software standards, drawing conventions, file formats and version control expectations — with named templates and a clear story on layer/colour/lineweight discipline.
owner · Joshinterfaces with creative & projects.
The touchpoints, communication expectations and handover standards between Technical and the rest of the business — especially Creative and Projects.
Document the touchpoints and handover standards between Technical, Creative and Projects. Sister sections sit in PB-02 creative and PB-01 projects.
owner · Josh · Woodyequipment specification.
How equipment is specified, sourced and confirmed during the technical design phase — and how that connects to CurrentRMS and to PB-04 operations.
Document the equipment specification process — from initial design through to confirmation in CurrentRMS — and how it hands off cleanly to Operations for prep.
owner · Joshchange log.
| version | date | author | summary |
|---|---|---|---|
| 0.1 | 26 Apr 2026 | Steve | Draft structure published. |