Checking Door Names in a Site Enquiry Against an Approved Floor Plan

Prepared for Eyonic CCTV.

A practical guide for Sarawak premises managers on reconciling temporary door names in a draft access control enquiry with the approved floor plan, using a simple three-column label register and a made-up worked example.

Why door names drift between the enquiry and the plan

A draft enquiry is written quickly. Someone walks the premises, points at a door, and types whatever comes to mind: back door, side entrance, the one near the stairs. The approved floor plan, drawn earlier and reviewed more carefully, may call the same opening something else entirely. Neither document is wrong on its own. The problem is that they were written at different times, by different people, for different purposes.

When the two documents are read side by side during a site survey, the mismatch becomes visible. An installer reading the enquiry may count two doors; the plan may show three openings, one of which is a store room door that nobody mentioned. Before any discussion of hardware, the names need to line up.

This guide is about that reconciliation step only. It does not cover access methods, credential types, equipment settings or schedules. It is a labelling exercise: match the words in the enquiry to the words on the plan, record who confirmed each match, and keep the record with the project file. Eyonic Security Systems, also known as Eyonic CCTV, plans, supplies and installs CCTV systems for homes, offices, shops and industrial sites in Sarawak, and a site survey is part of how such projects begin. The same discipline of matching written labels to the actual building applies whether the conversation is about cameras or about door access.

A made-up example: two doors, four names

The following example is invented for illustration. It does not describe a real building, a real floor plan or a real project.

A fictional office manager in Sarawak is preparing a draft enquiry about door access for a small two-storey office. While walking the building, the manager writes two temporary names in the draft: "front glass door" and "back door near the pantry".

Later, the manager opens the approved floor plan. The plan labels the first opening "Main Entrance (Ground Floor)" and the second "Rear Service Door (Ground Floor)". A third opening appears on the plan that the draft never mentions: a door to a small store room, labelled "Store 1".

The reconciliation produces three findings. First, the two temporary names map to two plan labels, so the enquiry can be rewritten using the plan's wording. Second, one plan opening has no counterpart in the enquiry, which is a question for the person who wrote the draft, not an assumption to be filled in. Third, the temporary names should be kept in the record as aliases, because the person who walked the building will recognise them and can confirm the mapping.

Nothing in this example says which door should have a lock, what kind, or who should use it. Those are separate decisions. The example only shows that a draft can contain fewer, more, or differently named openings than the approved plan, and that the difference is worth writing down before the enquiry goes further.

The three-column note: label, document, confirmation owner

A single small table is enough to hold the reconciliation. Three columns, one row per door name, kept with the project file and updated as confirmations arrive.

Column one, Label: the name as it appears on the approved floor plan. Copy it exactly, including any floor or room reference. This is the name the enquiry should end up using.

Column two, Document: where the name was found. Write the document title and the wording used there, for example "draft enquiry: back door near the pantry". If a name appears in more than one document, give it more than one row or list the documents in the same cell. The point is that a reader can trace each name back to its source.

Column three, Confirmation owner: the person who will confirm that the plan label and the enquiry wording refer to the same opening. Write a role or a name, not a guess. If nobody has confirmed yet, write "unconfirmed" rather than leaving the cell blank, so the gap is visible.

A copyable plain-text version of the note looks like this:

Label | Document | Confirmation owner Main Entrance (Ground Floor) | Approved floor plan; draft enquiry says "front glass door" | [role to confirm] Rear Service Door (Ground Floor) | Approved floor plan; draft enquiry says "back door near the pantry" | [role to confirm] Store 1 | Approved floor plan only; not in draft enquiry | [role to confirm]

Keep the table short. If it grows past a page, the enquiry is probably trying to describe too much at once, and the extra rows should be split into a second note rather than squeezed in.

Reading the plan before rewriting the enquiry

The order matters. Read the approved floor plan first, on its own, and list every opening it shows. Then read the draft enquiry and list every door name it uses. Only then put the two lists side by side.

Reading the plan first prevents a common slip: the draft's wording starts to feel like the correct name because it was written most recently. The approved plan is the reference document, so its labels should anchor the table.

When a plan label is ambiguous, for example two doors on the same corridor with similar names, do not resolve it by choosing the one that sounds more likely. Mark both rows unconfirmed and ask the person who owns the plan. A wrong match is harder to notice later than a missing one, because it looks finished.

This is also the stage to note openings that the plan shows but the enquiry omits, and openings the enquiry mentions but the plan does not show. Both are questions, not errors to be corrected silently. The enquiry may legitimately be about a subset of the building, or the plan may predate a renovation. The table records the question; the confirmation owner answers it.

Where the reconciliation sits in a wider security project

Door naming is a small task, but it sits inside a larger sequence that most premises projects follow: survey the site, agree what is being covered, then plan the installation. Getting the names right belongs to the first step, because everything after it refers back to those names.

For projects that include cameras as well as door access, the same labelling discipline carries over. Camera placement decisions depend on knowing which opening is which, and a recording setup is only as clear as the names used to describe the areas it covers. Eyonic's CCTV security systems work covers planning, supply and installation of monitoring systems with camera placement, recording and remote viewing for homes, offices, shops and industrial sites. A site survey is listed among the services, which is where a walk-through of the premises and its openings would naturally happen.

If the enquiry also touches on door access, the labelling work feeds directly into it. Eyonic's access control system installation page is the natural next stop once the door names are settled, because a conversation about door access needs agreed names before it can go anywhere useful. For business premises, the choice between a standalone smart lock and an access-control panel is something Eyonic usually checks, and that check depends on knowing which doors are being discussed. Smart lock door access is described as good for controlled convenience when user permissions and backup entry are planned properly, and the review notes that door condition, user roles and backup method should be reviewed before installation. None of those reviews can start while two documents call the same door by different names.

A short checklist before the enquiry leaves your desk

The following checklist is an author heuristic, not a researched standard. Treat the items as prompts rather than a score.

One: every door name in the draft enquiry appears in the three-column note. Two: every opening on the approved floor plan appears in the note, even if the enquiry does not mention it. Three: every row has a confirmation owner or is marked unconfirmed. Four: temporary names are kept as aliases so the person who wrote them can recognise the mapping. Five: the note is stored with the project file, not in a chat thread that will scroll away.

A suggested timing, offered as an example rather than a rule: for a small office with a handful of doors, the first pass through the table might take under an hour, and confirmations may take longer because they depend on other people. The table is finished when the confirmation column has no blanks, not when the first pass is done.

When the enquiry is ready to discuss, the note travels with it. Anyone reading the enquiry can then see which names came from the plan, which came from the walk-through, and who confirmed the match. That is the whole purpose of the exercise: not to produce a perfect document, but to make the differences visible while they are still cheap to fix.

Further reading

For the provider’s public service information, see Eyonic CCTV’s access control system information.

Eyonic CCTV, also known as Eyonic Security Systems, plans, supplies and installs CCTV systems for homes, offices, shops and industrial sites in Sarawak.