A Training Exercise for Explaining a CCTV Quote’s Scope to a New Facilities Coordinator

Why a read-back beats a walkthrough

Handing a new facilities coordinator a CCTV quote and walking them through it line by line feels like training. It is really a briefing. The coordinator nods, the manager talks, and nothing tests whether the second person can tell a settled term from an open one.

A read-back reverses the roles. The coordinator reads the quote back in their own words, and the manager listens for three things: what the document actually commits to, what it leaves open, and what the coordinator has quietly assumed. Those three categories are the whole exercise.

This is a training exercise, not a procurement method. It uses a hypothetical, redacted quote summary so nobody is exposed and no real commercial terms are rehearsed. The point is to build the habit of asking "is this stated, or am I filling a gap?" before a real quote lands on the desk.

It also fits how CCTV work is usually described. Eyonic Security Systems plans, supplies and installs monitoring systems with camera placement, recording and remote viewing for homes, offices, shops and industrial sites, so a quote for that kind of work naturally mixes supplied equipment, installation activity and configuration steps. A coordinator needs to hear those strands separately.

Set up the exercise: the redacted quote summary

Write a one-page summary, not a real quote. Strip the supplier name, the prices, the site address and any personal names. Keep the shape of a quote: a short scope paragraph, a list of supplied items, a list of activities, and a closing block of terms.

A workable example for a Sarawak office might read like this, entirely invented for practice:

Scope: supply and install a monitoring system for a two-floor office, covering the main entrance, a rear service door, a reception area and a small store. Recording equipment to be located in a locked room. Remote viewing to be set up for two nominated staff.

Supplied: cameras, recording unit, cabling, fixings, a monitor.

Activities: site survey, installation, configuration, handover briefing.

Terms: access to the premises during working hours; power points to be available; building owner consent for any fixing to shared walls; training on handover; support arrangements to be confirmed.

Notice how much is deliberately vague. "Remote viewing for two nominated staff" does not say on what devices. "Support arrangements to be confirmed" is an open term wearing a term's clothing. "Building owner consent" is a dependency, not a promise. That vagueness is the teaching material.

Keep the summary short enough to read aloud in a few minutes. The exercise fails if the coordinator spends the session reading rather than explaining.

Round one: the coordinator explains the scope in their own words

Ask the coordinator to explain the summary to you as if you were a colleague who had never seen it. No notes beyond the page. They should cover what is being installed, where it is going, what happens on the day, and what the office is expected to provide.

Listen for four failure patterns, which are common enough to name as a checklist rather than a claim about how often they occur:

Substitution. The coordinator says "cameras will cover the car park" when the summary never mentions a car park. They have imported an assumption from a previous job.

Collapse. They merge supply and installation into one promise, losing the fact that some activities depend on site conditions.

Silent gaps. They skip the open terms entirely because open terms are uncomfortable to say out loud.

Overreach. They describe outcomes, such as "nothing will be missed", that no quote can honestly promise.

Score each pattern as present or absent. That is an author's heuristic for structuring feedback, not a validated instrument. The value is in the conversation the score triggers, not the number.

When the coordinator substitutes or overreaches, do not correct them immediately. Ask: "Which line told you that?" The pause while they search the page is the lesson.

Round two: sorting statements into three buckets

Now give the coordinator three labels and ask them to sort every statement they made in round one.

Stated. The quote says it plainly. "A site survey is included" belongs here if the activities list names it.

Unresolved. The quote gestures at it but does not settle it. "Support arrangements to be confirmed" is the obvious example. So is "remote viewing for two nominated staff" if the devices are not named.

Needs supplier confirmation. The coordinator cannot resolve it from the document at all and must ask. Whether the recording unit's location has power and network reach, whether the building owner will permit fixings, and what the handover briefing actually covers all sit here.

The distinction between the second and third bucket matters. Unresolved terms are the supplier's to clarify in the quote. Supplier-confirmation items are questions the coordinator must raise before anyone signs. A coordinator who treats every gap as "the supplier will sort it" has learned the wrong lesson.

A useful prompt at this stage: "If you had to write one email before approving this, what would be in it?" The answer should be a short list of questions, not a request for a discount.

Where the scope usually hides: activities, not items

New coordinators gravitate to the equipment list because it is concrete. The activities list is where scope actually lives, and it is usually the thinner section.

Take the phrase "site survey". It sounds routine. But a survey is the step that turns a generic quote into a specific one, because it is where the supplier looks at the actual premises. A quote that lists a survey is telling you the final arrangement is not yet fixed. A coordinator who reads "site survey included" as "everything is decided" has misread the document.

Camera placement behaves the same way. The summary may say cameras cover certain areas, but the specific positions are typically settled during the survey, not in the quote. That is normal, and it is not a loophole. It does mean the coordinator should expect the arrangement to be confirmed on site rather than treat the quote as a final layout.

Recording and remote viewing are configuration activities, not just boxes. "NVR setup" and "remote viewing" describe work that happens after the hardware is mounted, and that work depends on the office's network and on who is authorised to view what. A quote can list these activities without settling the details, and the coordinator's job is to notice the difference.

If the office is also considering door access, the same logic applies. Smart lock door access is described in Eyonic's own review material as working best when the door condition, user roles and backup method are reviewed before installation, with a check on whether a standalone lock or an access-control panel suits the business. That is a scope question, not a product question, and it belongs in the read-back.

A worked example: the Kuching office scenario

To make the exercise concrete, borrow the shape of a real project type without copying its details. Eyonic's published project note for a Kuching Immigration Office describes practical support for a public office focused on arrival flow, staff areas, visitor movement and dependable daily operation. That is a useful template for what a scope paragraph should try to capture: the areas that matter and the daily reality they serve.

Now imagine the redacted summary above is for a similar public-facing office. Ask the coordinator to answer three questions in role:

Which parts of this scope map to arrival flow, staff areas and visitor movement, and which parts are simply equipment?

If the office must keep operating during installation, what does the quote assume about timing and access, and is that assumption written down?

Which statements would you refuse to repeat to a colleague until the supplier confirms them?

The third question is the heart of it. A coordinator who can name their own uncertainties is more useful than one who projects confidence. The exercise rewards the honest answer.

You can vary the scenario for a smaller commercial office using the shape of Eyonic's note on an engineering consultancy setup in Kuching, which describes support for staff movement, visitor handling, tidy cabling and clearer daily site control. The areas differ, but the read-back method is identical.

Debrief: what the coordinator should be able to say

Close the exercise by asking the coordinator to summarise the quote in three sentences: what is confirmed, what is open, and what they will ask before proceeding. If they cannot do it in three sentences, the sorting in round two was not finished.

Then compare their read-back to the original summary. Every statement they made should trace to a line, or be flagged as their own assumption. Statements that trace to nothing are the ones to work on next time.

A short written record helps. Ask them to keep a one-page note with three headings, Stated, Unresolved and Ask Supplier, and to update it whenever a quote is revised. Over a few exercises the note becomes a personal checklist, which is more durable than a briefing they half-remember.

One caution for the trainer: resist the urge to fill gaps with your own knowledge of how installations usually go. If you supply the answer, the coordinator learns that gaps get filled by whoever is most senior in the room. Let the gap stay open and let the question stand.

When the exercise is done and a real project is on the table, the natural next step is to talk the scope through with the supplier directly. Eyonic's own product material invites readers to WhatsApp about a product, and the same instinct applies here: unresolved terms are best settled in conversation with the people who wrote the quote, not guessed at internally.

Adapting the exercise for your own premises

The exercise scales. For a single shop, shorten the summary to one paragraph and run only round one. For a larger site with several buildings, add a fourth bucket for "depends on another contractor", because shared walls, power and network often sit with someone else.

Keep the redaction discipline every time. No prices, no supplier names, no addresses, no personal details. The moment the exercise uses a real quote, people start defending positions instead of practising the read-back.

Finally, rotate who plays the coordinator. A premises manager who has to explain a quote aloud discovers their own assumptions quickly, and that is the most useful outcome the exercise can produce. The goal is not a perfect read-back. It is a habit of separating what the document says from what the reader hopes it says, and of naming the difference out loud before a project moves forward.