A timeline can contain research, design, printing and installation dates while saying almost nothing about what allows those tasks to proceed. Printing needs approved artwork. Artwork needs checked text and confirmed object information. Object presentation may need a specialist decision before its final dimensions are known. If those inputs are absent, a coloured bar on a schedule does not make the work ready to begin.

Build the programme around decisions and dependencies as well as activity. The aim is to show which answer is needed, who can give it and what changes if it arrives late. This is particularly useful for small teams whose members hold several roles. They need a schedule that distinguishes a genuine prerequisite from a convenient preference, and an approval from a general expression of enthusiasm for the project.

Use the timeline to expose uncertainty rather than conceal it behind exact dates. An object may be provisionally selected while its display conditions remain unresolved. The drawing can proceed as an exploration, but the programme should say which later decisions still depend on that answer. This prevents progress in one workstream from being mistaken for permission to commit another team to manufacture, print or install an arrangement that has not yet been checked.

Define what must be true at opening

Begin with the conditions required for the exhibition's intended public operation. These include the coherent content and actual venue, object, technical and access arrangements established by the responsible people. Do not define completion only as every contractor leaving the room. Hosts need usable information, relevant alternatives must be available and outstanding work needs an appropriate status.

Identify which conditions are essential to the central exhibition and which belong to optional extensions. A core object comparison may be necessary to make the story intelligible, while an additional process film may enrich it without being indispensable. This distinction helps the team make responsible choices if time tightens. It does not authorise omitting work required for safe, lawful or appropriate operation.

Record who confirms each opening condition. A designer's visual approval cannot replace an object-care decision or a venue's required readiness checks. Keeping the approvals distinct makes the schedule more accurate and prevents a single milestone called final sign-off from concealing several different decisions that may need different evidence and people.

Work backwards through actual prerequisites

For each essential output, ask what must be available before work can be completed. A printed panel needs the correct final file, not simply a date when writing is expected to finish. That file may depend on image permissions, checked captions, layout and a physical proof. Write those relationships explicitly before assigning hopeful dates to each activity.

Use confirmed supplier information rather than inventing a universal lead time. Ask what the supplier's current production allowance includes, what information starts the clock and which changes would require a revised programme. A delivery estimate based on fully approved artwork cannot be treated as though it begins while the team is still debating the exhibition's central text.

Trace dependencies far enough to reveal the important uncertainty, but keep the schedule usable. Not every minor internal task needs to appear in the shared programme. The useful level is the one that lets another colleague recognise why a decision matters and what work cannot proceed without it. Detailed team checklists can support the main timeline without overwhelming it.

Give each decision gate an input and an outcome

A gate is a decision with an identifiable basis, not a meeting title. For text release, the inputs may include checked wording, confirmed object associations and the laid-out proof. The outcome is approval of named files, a specific revision request or a decision that the material is not ready. Record which outcome has actually occurred instead of assuming that holding the meeting means approval was given.

Name the person or role with authority and identify the information they need in advance. A rushed request sent on the intended approval date can fail because the reviewer has not seen the necessary evidence. Agree the review process early, including a route when the usual decision-maker is unavailable. Do not create an imaginary delegate or infer approval from silence.

Keep the gate proportionate to consequence. A small correction to an internal note may not need the same process as a changed loan, structural specification or consequential factual statement. The programme should help people route decisions appropriately. Treating every edit as equally important can slow work while making the significant approvals less visible.

Separate parallel tasks from work that only appears independent

Some activities can proceed together: editing a stable section while preparing a confirmed image inventory, for example. Other tasks appear parallel until a shared assumption changes. Fabrication and interpretation may both depend on an unresolved object choice. Identify that common dependency instead of assuming that starting both teams early automatically reduces the overall duration.

Record provisional work clearly. A designer can explore layouts using an assumed panel quantity, but that does not make the quantity approved. A fabricator may provide a preliminary assessment without authorising final manufacture. Distinguish exploration from commitment so that useful early work does not quietly lock the project into an unconfirmed decision.

Ask what rework an early start could create. Sometimes a provisional task is worthwhile because its learning reduces a larger uncertainty. Sometimes it produces polished material likely to be discarded. The timeline should support that judgement by making the assumption and consequence visible, rather than measuring progress solely through the number of activities marked as started.

Schedule people and shared resources as real constraints

Identify work that competes for a person, space or service. One editor cannot necessarily complete several intensive approvals simultaneously. A shared loading route may serve another programme, and an installation room may not be available during every nominal working hour. The project timeline needs to connect with those actual conditions rather than assume unlimited parallel capacity.

Confirm availability with the people concerned. A volunteer's general willingness to help is not a booking for a specific production day. A supplier's early interest is not confirmation that a revised date remains possible. Record which arrangements are agreed, which are provisional and when the team must obtain a firmer answer.

Avoid using an individual as an invisible buffer for every delay. Extending work into evenings may appear to rescue the timetable while creating fatigue, mistakes or unavailable decision coverage. A realistic programme changes scope, sequence or resources through agreement. It does not rely on undefined extra effort simply because the opening date is fixed.

Show how a changed decision affects downstream work

When a proposed change arises, identify the affected outputs and commitments before approving it. Replacing an object can alter its caption, image, mount, case arrangement, transport and host explanation. The request may sound small when described as one object, but its schedule consequence depends on those relationships. Use the dependency map to make the actual effect understandable.

Keep a concise change log with the reason, decision, responsible role and programme consequence. This does not require elaborate software. It prevents a team from continuing with an obsolete assumption because the latest choice was made in a conversation they did not attend. Connect the log to current files and dates so that a recorded decision can be acted on.

Distinguish an essential correction from an optional improvement. A factual error or unmet required condition may need urgent attention despite inconvenience. An extra decorative feature should be judged against its benefit and effect on the core work. The timeline makes that trade-off visible; it should not be used as a blanket excuse either to accept every late idea or to preserve a known problem.

Prepare fallback decisions before a delay becomes a crisis

For a fragile dependency, identify the latest useful decision point and a coherent alternative. If a loan is uncertain, the fallback may involve different material or a narrower explanation. If a non-essential film cannot be completed, the alternative may be a checked static account. The substitute must be evaluated honestly for what it communicates and what conditions it introduces.

Do not call an unplanned blank space a fallback. A workable alternative needs content, practical arrangements and an approval route. Nor should it pretend to provide the original experience in every respect. Record which part of the story changes and whether the central question remains understandable. This protects coherence while allowing a smaller deliverable when the preferred option is not available.

Keep required specialist and venue decisions outside casual substitution. A different object or equipment arrangement may need a fresh assessment. The fallback is not a licence to bypass that work because the schedule is tight. Planning it earlier gives the team a better chance of obtaining the necessary information and making a responsible choice.

A hypothetical photography exhibition protects its print decision

Imagine a hypothetical exhibition with photographs from several lenders. The programme initially shows design finishing on Monday and printing starting on Tuesday. A dependency review reveals that image permissions and the final credit wording are not yet confirmed for part of the selection. The printer's production period assumes approved final artwork. This is an illustrative scheduling example, not a report of an actual lender or supplier.

The coordinator creates a clear release gate for each print group. Confirmed material can proceed through the agreed checks, while the uncertain group has an identified decision point and an appropriate alternative selection under review. The team asks the supplier about the actual consequence of a later file rather than assuming that the original delivery promise remains unchanged.

When one permission remains unresolved, the team makes the planned substitution through the relevant content and design checks. It updates the layout, caption inventory and programme. The value of the timeline is not that it prevented every delay. It made the dependency visible early enough for the exhibition to retain a coherent checked selection without disguising an assumption as a completed approval.

Track evidence of completion, not the colour of a bar

At a progress review, ask what output or decision establishes that a task is complete. Writing nearly finished and design mostly done can hide unresolved questions that block the next stage. Use statuses that distinguish work underway, awaiting information, under review and approved for the stated purpose. Keep them understandable to colleagues outside the specialist team.

Review the critical upcoming decisions rather than reciting every completed task. Which input is missing? Which reviewer needs material? Which supplier condition has changed? Assign the next action and record its consequence for the programme. A shorter focused review can be more useful than a long meeting that reports activity without resolving the prerequisite preventing progress.

After opening, preserve the actual programme and significant deviations for future work. Do not reuse its dates as universal durations for another exhibition. Record the conditions that made those timings possible or difficult: selection stability, review availability, supplier assumptions and venue access. The reusable knowledge is the relationship between work and decisions, not an attractive schedule graphic detached from how the project was delivered.

Decision recordIncludeWhy it matters
InputThe evidence or file needed for reviewA date alone does not make work ready
AuthorityWho can approve the particular matterDifferent approvals have different owners
OutcomeApproved version, revision or unresolved statusA meeting is not automatically a release
DependencyWork affected by the answerConsequences become visible
Fallback pointWhen and how an alternative is chosenDelay does not force unplanned improvisation

Questions specific to this guide

Should every task have its own approval meeting?

No. Match review and approval to the actual consequence and organisational arrangements. Significant decisions need clear ownership, but minor internal tasks need not be turned into unnecessary gates.

Can design begin before all research is complete?

Some exploratory work can be useful if assumptions and limits are explicit. Distinguish provisional development from approval for manufacture or publication, and record what could require rework.

What if the opening date cannot move?

The date does not remove dependencies. Compare coherent scope alternatives, obtain required decisions and agree realistic resources. Avoid treating unavailable time as a reason to bypass necessary checks.

Further reading

Authoritative background on related planning and access questions. These resources provide context; they do not endorse this guide or replace the current requirements for your specific setting.