Comparing Two Example CCTV Enquiry Notes When Only One Lists the Requested Documentation

Why the document request decides the quality of the reply

An enquiry note is the first written record of what a premises manager wants. When the note asks for a quotation but never says which documents should come with it, the reply may be technically sound and still leave the reader chasing paperwork later. This guide uses two fictional enquiry descriptions written for a proposal-writing workshop in Sarawak. Neither describes a real building, a real supplier or a real price. The exercise is simple: read both notes, mark the places where the document request could be clearer, and write one revised phrase for each weak spot.

Keep the purpose narrow. You are not judging whether the writer chose the right equipment or the right layout. You are judging whether a supplier reading the note would know what to send back. That distinction matters because documentation requests are easy to fix in a sentence and expensive to fix after a quotation has been circulated to a committee.

A useful enquiry note does three things. It states the site context in general terms, it names the documents the writer expects to receive, and it says who will read them. The two examples below differ mainly on the second point.

Example A: a note that names the documents

Example A is written by a fictional facilities coordinator for a small office in Sarawak. The note reads, in substance: we are reviewing our monitoring arrangements and would like a quotation. Please include a written scope describing what will be installed and where, a simple list of the equipment proposed, a note on how recordings will be stored and for how long, and a short handover checklist showing what will be demonstrated to our staff before the job is closed. Please also state what information you need from us before a site visit.

Mark the strengths first. The note names four document types, so the reader knows the reply is more than a price. It asks what input is needed, which invites a site survey conversation rather than a blind quotation. It separates the quotation from the handover checklist, so the writer can see that the job does not end at installation.

Now mark the weaknesses. The note does not say who approves the documents or by when. It does not say whether the equipment list should be a single page or a full schedule. It does not say whether the storage note should cover retention duration in plain language or only the recording method. These are small gaps, but each one can produce a reply that is correct and still awkward to circulate.

A brand context point, offered as background rather than as part of the fictional note: Eyonic Security Systems plans, supplies and installs monitoring systems with camera placement, recording and remote viewing for homes, offices, shops and industrial sites. That scope is the kind of work a note like Example A is trying to describe.

Example B: a note that asks for a quotation only

Example B is written by a fictional branch administrator for a different site. The note reads, in substance: please quote for a monitoring system for our premises. We want to see what is available and compare options. Kindly send your best price.

This note is not wrong. It is simply thin on documentation. A supplier reading it can reasonably reply with a price and a short product description, because that is all the note asks for. The writer may then discover, after the reply arrives, that the committee also wanted a written scope, a storage note and a handover checklist. The cost of that discovery is another round of messages and a delayed decision.

Mark the places where the document request is missing. There is no list of expected documents. There is no statement of who will read the reply. There is no mention of a site visit or of what information the supplier should request. There is also no indication of whether the writer wants a comparison of options or a single recommended approach, which are different documents.

The lesson is not that Example B is careless. It is that a short note produces a short reply, and a short reply is hard to defend in a committee meeting where someone asks what happens after installation. The fix is a single added sentence, not a rewrite.

The marking exercise: where to put your ticks

Run the comparison as a short workshop. Give each participant both notes and ask them to mark three things in different ways: a tick where the document request is clear, a question mark where it is implied but not stated, and a cross where it is absent. Then ask each person to write one revised phrase for every cross.

A worked example of a revised phrase for Example B: please include a written scope, an equipment list, a note on how recordings are stored and for how long, and a handover checklist showing what will be demonstrated before the job is closed. Please also tell us what information you need before a site visit.

That sentence does most of the work. It converts an open request into a document list, and it invites the supplier to ask questions rather than guess. It does not name equipment, coverage or layout, which keeps the note at the level a premises manager can write without technical training.

A second worked example, for the timing gap in Example A: please send the documents at least five working days before our committee meeting on the date shown below. Treat the five days as an author heuristic for the exercise, not as a rule drawn from research. The point is that the note should state a date, not that five is the correct number.

A third example, for the audience gap: the reply will be read by our premises committee and by our finance officer, so please keep the scope and checklist in plain language and put any technical terms in a short glossary.

What a complete document request looks like

After the marking exercise, assemble the ticks into a short template the group can reuse. A complete request usually covers five items: the documents expected, the audience who will read them, the date they are needed, the information the supplier should ask for, and the point at which the job is considered closed.

The fifth item is the one most often left out. A handover checklist is a document, and asking for it in the enquiry note sets the expectation early. It also gives the writer something concrete to check on the day the work finishes.

For readers who want to see how a supplier describes its own installation scope, the CCTV installation services page is a reasonable next stop. Read it as an example of how one company frames the work, not as a substitute for your own document list. The same applies to any supplier page: the note you write should stand on its own.

Where a site has door access as well as monitoring, the document request can be extended with one line about user roles and backup entry. Eyonic notes that smart locks work best when the door condition, user roles and backup method are reviewed before installation, and that for business use it usually checks whether a standalone smart lock or an access-control panel is more appropriate. That is a useful prompt for a question in your note, not a recommendation for your building.

Turning the comparison into a one-page enquiry note

The final workshop step is to merge the best of both examples into one page. Start with the site context in two sentences. Add the document list as a short set of bullets. Add the audience and the date. Add the question about what the supplier needs before a visit. Close with the handover expectation.

Keep the page free of equipment names and layout detail unless the writer genuinely knows them. A premises manager who writes a document request does not need to specify camera placement or recording configuration; those belong to the site survey conversation. The note should make clear that a survey is expected, and that the documents will follow it.

A brand context point for the workshop facilitator: Eyonic Security Systems lists site survey, camera placement, NVR setup and remote viewing among its service areas. These are useful as prompts for what a supplier might discuss at a survey, but they are not a checklist the writer must reproduce in the enquiry note. The note asks for documents; the survey produces the technical detail.

One more caution for the group. Do not let the exercise drift into judging prices. The fictional notes contain no figures, and the workshop should not invent any. If a participant wants to discuss budget, redirect them to the document list: a written scope is what makes a budget comparable, and that is the skill the exercise is teaching.

A short review checklist before the note is sent

Before the note leaves the desk, run a five-question check. Does it name the documents expected? Does it say who will read them? Does it give a date? Does it ask what the supplier needs before a visit? Does it say what will be demonstrated at handover?

Score each question as clear, implied or absent, using the same marks from the workshop. Treat the score as an author heuristic for the exercise, not as a validated instrument. A note with five clears is ready to send. A note with any absent item should be revised before it goes out.

Finally, keep a copy of the note with the reply. When the documents arrive, the copy shows what was asked for, and the comparison between request and reply becomes the next workshop example. That habit is the real output of the exercise: a written record that makes the next enquiry easier to write and easier to check.