Skip to content
ASRcreative

culture

Cultural & Institutional Work

Cultural work is judged twice: once by the audience, and once by the file.

Start a conversation See the process

In short

Institutional and cultural projects require a partner who can define scope in writing, work inside procurement and funding constraints, meet accessibility obligations, and hand over documentation that survives a change of staff. ASRcreative approaches this work with the same production standards as commercial work, plus the documentation those contexts require.

Creative production for cultural and institutional contexts: museums, festivals, heritage sites, public programmes and funded projects, where scope, documentation, accessibility and accountability are part of the deliverable rather than paperwork added at the end.

Outcomes

What you get out of it

  • Scope, deliverables and responsibilities defined in writing before work starts
  • Documentation suitable for funding, procurement and archive requirements
  • Accessibility considered in the design, not retrofitted after installation
  • Work that can be maintained, re-run or re-staged by the institution itself

Deliverables

  • Written scope and technical specification suitable for procurement processes
  • The produced work: music, audiovisual pieces, installations or a combination
  • Accessibility provisions agreed for the context — captions, transcripts, level and light considerations
  • Full technical and operational documentation for the institution's team
  • Archive-ready files and metadata for long-term preservation

Process

How the work runs

  1. 01

    Context and constraints

    The institution, the programme, the audience, and the rules that apply — funding conditions, procurement, heritage or safety limits.

  2. 02

    Scope definition

    Deliverables, responsibilities, milestones and acceptance criteria written down in a form your process can approve.

  3. 03

    Design

    The creative proposal, developed with accessibility and operation treated as design inputs from the beginning.

  4. 04

    Production

    Execution against the approved scope, with documented decisions at each milestone.

  5. 05

    Installation and acceptance

    Delivery, installation where relevant, and testing against the agreed acceptance criteria.

  6. 06

    Documentation and archive

    Operational documentation for staff and archive-ready files with metadata, so the work outlives the project team.

Documentation is a deliverable, not overhead

In cultural and public-sector work, a piece that cannot be explained, audited or re-staged is only half delivered. Funders ask what was produced and how the money was used. Successors ask how to run it. Archives ask for files in formats that will still open in fifteen years.

Treating that as part of the production — written scope, decision records, technical documentation, archive files with metadata — is cheaper than reconstructing it under deadline, and it is what makes a project reusable rather than a one-off expense.

Accessibility designed in

Accessibility retrofitted after installation is usually a compromise: captions burned over a composition that never left room for them, or an audio level set for a room that was mixed for something else.

Considering it while the work is being designed — legible text sizes, caption space, sensible levels, alternatives for audio-led content, physical access to the viewing position — produces better work, not just compliant work.

Working inside institutional constraints

Procurement rules, fixed budget lines, committee approvals and immovable opening dates are not obstacles to work around; they are the shape of the project.

Scope written to fit that shape — with clear milestones, clear acceptance criteria and clear ownership of each dependency — removes most of the friction that cultural projects usually absorb late.

Before you write

What we need from you

  • The programme or exhibition this belongs to, and its dates
  • The funding or procurement framework and any conditions attached
  • The space or channels involved, and their technical constraints
  • Accessibility obligations that apply in your context
  • Who operates and maintains the work after delivery
  • Reporting and archive requirements

You do not need all of it to make contact. Anything you can answer makes the reply more useful; anything you cannot is part of what gets worked out together.

Start a conversation

FAQ

Questions people actually ask

Can you work inside a procurement or public funding process?

Yes. That means scope, deliverables, responsibilities, milestones and acceptance criteria written in a form your process can actually approve, and decision records kept as the work proceeds so reporting does not have to be reconstructed at the end.

How is accessibility handled?

As a design input, agreed at the start for your specific context — caption space planned into the composition rather than burned over it, levels that work at real operating conditions, alternatives for audio-led content, and physical access to the viewing position considered before installation rather than after.

What happens to the files after the programme ends?

Archive-ready files with metadata are part of the delivery, alongside operational documentation for staff. The test is simple: can the institution re-stage or explain the work in ten years, with none of the original team available.

Next step

Start a conversation

Describe the project and what it has to achieve. You get a written answer with scope and next steps, not an automated quote.

Start a conversation Other ways to reach us