What a Scope of Works Means in a Production Consultancy Review

When a network or an event organiser asks us for written guidance on a new audiovisual set-up, the first document we draw up is the scope of works. People often expect the review itself to come first, but nothing useful can be reviewed until everyone agrees what is being looked at. A scope of works is a short written statement of the questions the consultancy will answer, the rooms or stages involved, the equipment and signal paths under review, and the form the final report will take.

I mention it as the sound engineer on the team because audio is where vague briefs hurt most. A request to look at the sound for a festival can mean the front of house system, the monitor mixes, the broadcast feed, or all three. Each is a different piece of work with a different amount of time behind it. The scope settles that before anyone opens a drawing or visits a site, and it saves both sides a good deal of correspondence later.

A useful scope reads like a plain list of commitments. It names the site or sites, states which systems are included, lists the documents we will be given to work from, and says what we will hand back. For a Production Consultancy job that handback is usually a written report with an equipment review, a set of recommendations in priority order, and notes on anything that needs a site visit to confirm.

We try to keep the wording free of jargon, because the reader is often a producer or an operations lead rather than a technician. If a term has to appear, such as gain structure or return feed, we explain it in a line beside the item. The point of the scope is that a person who was not in the first meeting can pick it up months later and understand exactly what was agreed and why.

• Sites, rooms or stages covered by the review
• Systems included: sound, lighting, camera control, signal routing
• Documents and drawings supplied by the client
• Format and contents of the written report
• Number of review meetings, if any

The exclusions matter as much as the inclusions. A scope that lists only what is covered invites the assumption that everything else is covered too. We therefore write down what falls outside: installation work, purchasing on the client's behalf, commissioning of equipment, and any system in the building that was not named. If a client wants to extend the review to the lighting rig after reading the first draft, that is a perfectly ordinary request, and it is handled as an addition rather than slipped in.

Another common exclusion is anything that depends on information we have not seen. If the venue's power distribution drawings are not available, we say so and mark the related comments as provisional. That is not a way of avoiding responsibility. It is an honest statement of what the report can and cannot stand on, and it lets the reader decide whether to find the missing drawings before acting on the advice.

Plans change while a review is under way. A venue is swapped, a broadcaster adds a second camera position, a festival decides to stream one stage that was never meant to be seen. When that happens we do not quietly absorb the change, and we do not ignore it. We note it in writing, say what it affects in the report, and agree with the client whether the original scope stands or is amended.

This habit of writing things down feels formal at first, but it protects the client most of all. A report that was written against an earlier version of the plan can give advice that no longer fits, and nobody notices until equipment arrives on site. Dated amendments to the scope make it obvious which version of the plan each recommendation belongs to, and they give a later reader a clear trail to follow.

If you are the person commissioning a review, read the scope as though you were the person who has to act on the report in six months. Check that every room you care about is named, and that the language describing the deliverable matches what you expect to receive. If it says equipment review, ask whether that means a list of what you own, or an assessment of whether it suits the new set-up.

Ask also who on your side supplies the drawings, and by when. A review is only as good as the material it starts from, and delays at this stage are the commonest reason a written report arrives later than hoped. None of these questions is awkward to raise. We would much rather answer them before work begins than discover a mismatch when the report is already written.

• Is every room, stage or gallery you care about named?
• Does the deliverable match what you expect to receive?
• Who supplies drawings and when?
• What is listed as outside the review?

Once the report is delivered, the scope does not simply go in a drawer. It becomes a checklist against which the report can be read: every question the scope promised to answer should have an answer, and anything marked provisional should be easy to find. Clients who keep the two documents side by side tend to get more out of the recommendations, because they can see which advice is firm and which waits on further information.

It also helps when a second team takes over. A new technical manager or an incoming production company can read the scope and learn quickly what was examined and what was not. In that sense the scope is a small piece of institutional memory, written in plain words and kept short enough that people actually read it.