A partner may offer equipment, a room, printing or staff time, but each resource comes with conditions. A shared resource plan makes those conditions visible before the project depends on them in its invitation or design.

Planning Shared Resources for a Community Art Project

Distinguish a possible contribution from a confirmed resource. The project also needs to understand collection, access, supervision, return and replacement arrangements where they apply.

Make promises through the people who can actually deliver them. An enthusiastic conversation does not establish a venue booking, a staffing commitment or permission to use equipment. Record confirmed arrangements separately from ideas still being explored. This protects the collaboration from discovering too late that its public invitation depends on an assumption nobody approved.

Three useful steps

1. List the resources the activity needs in practical terms.
2. Confirm what each partner can provide and under which conditions.
3. Identify a realistic alternative for any essential unresolved item.

Fit project arrangements around the real setting rather than treating it as an empty stage. A shop, library or community room continues to serve people who may not be taking part in the artwork. Consider entrances, routine activity, staff time and the use of shared equipment. The art project should explain how it will coexist with these functions.

Consider a small example

For example, a projector being available in the building does not establish that the project can use it at the required time or connect its files to it. A simple test and booking check can prevent an avoidable problem.

A local partner brings knowledge and relationships as well as practical resources. Do not reduce the relationship to access to a room or an audience. Ask what the proposed activity means for the partner's ordinary work, what effort it creates and what they hope to learn or receive. The answer may change the format before a public invitation is issued.

Where the approach can go wrong

Do not count staff assistance as unlimited merely because a partner is supportive. Time and responsibilities should be discussed as explicitly as physical equipment.

Clarify the difference between a host, a collaborator and a delivery partner. These roles can overlap, but they involve different expectations about decisions, labour, public credit and responsibility. A short shared note can prevent each person from assuming the other is handling an essential task. Revisit it when the project expands or the people involved change.

Consider the people and the context

Budget conversations should include the work around the public event as well as the event itself. Preparation, meetings, travel, materials, access support, documentation and removal may all require resources. Ask what the proposed fee covers rather than assuming the same scope on both sides. A clear breakdown supports realistic choices without pretending that every project has the same cost structure.

Describe the scale honestly. A conversation with a small group can produce valuable material, but it does not automatically represent a whole neighbourhood. Keep the setting, invitation and limits visible in any account of the work. This makes the project easier to understand and avoids turning a situated encounter into an unsupported claim about what a community thinks.

Turn a finding into a decision that somebody can act on. If the invitation was difficult to understand, specify which part needs rewriting and test the new version. If a resource was missing, identify who can address it before the next session. A report that records every issue without changing the plan is less useful than a short review that leads to a clear improvement.

What to carry into the project

A useful resource plan turns offers into usable arrangements and shows where the project still needs to simplify or find support.

Related reading

Maintaining a Partnership When Staff Change; Ending a Community Art Partnership Well; Creating a Role Map for a Collaborative Art Project.

Background and further reference

University of the Arts London: archive record for A Million Minutes.