| Required entrances and internal protection points | A cheaper package may omit a required area | Ask for the missing coverage to be included before comparing totals |
|---|---|---|
| Occupied and partly armed operation | The same device count may support different daily use | Ask each proposer to demonstrate the required operating pattern |
| Alarm recipients and response arrangements | A phone notification and an agreed monitoring service cover different responsibilities | Compare the same response requirement and identify who acts |
| Survey, installation and commissioning | A hardware price may exclude work needed to deliver an operating system | Separate equipment-only pricing from the installed and tested proposal |
| Handover and ongoing service | A low initial price may leave maintenance or user support outside the scope | List included work, recurring charges and separately chargeable work |
Consider two quotes for the same shop: one includes final-position checks and a customer handover; the other stops at equipment supply. The second may still be appropriate if another appointed installer covers the missing work. Until that responsibility and cost are explicit, the quotes are not comparable.
Check whether the proposed architecture fits the building
Architecture is a way to meet the agreed protection plan. A finished, occupied property may make new cable routes disruptive. An office retrofit may have usable existing alarm circuits worth examining before replacement. A new build may offer accessible cable routes from the outset.
Ask each proposer to explain how its layout reaches the required protection points. If an important point cannot be served in the proposed arrangement, revise the design before accepting the proposal. Do not reduce necessary coverage to preserve a preferred equipment package.
The wireless alarm architecture guide explains the wired, wireless and hybrid choices and the site checks that distinguish them. Here, the selection question is whether the proposed arrangement can fulfil this project’s scope.
Match each essential claim to evidence
A specification matters when it answers an actual requirement. Ask for evidence tied to the proposed devices, interfaces and configuration, rather than accepting a general brand statement.
| Requirement in the proposal | Evidence to request | Decision if it is missing or does not match |
|---|---|---|
| Required areas and user operations | Exact product documentation and the proposed operating configuration | Keep the affected capability unresolved; do not assume it from device capacity |
| Retention of existing equipment | Compatibility evidence for the specific connection and devices | Compare a replacement option if reuse cannot be supported |
| A required certificate or approval | The applicable document and its product/system scope | Resolve the mismatch before treating the proposal as meeting that requirement |
| A planned extension | Supported device categories, capacity and a layout for the agreed next stage | Price the necessary upgrade separately if the current proposal cannot support it |
Separate three outcomes: supported, unresolved and unsuitable. Missing evidence is an unresolved question, not proof that a product lacks the capability. An identified mismatch with an essential requirement is a reason to revise or exclude that proposal. Optional features should not compensate for an essential mismatch.
For expansion, distinguish an agreed next phase from a vague possibility. A planned storage-room extension belongs in the comparison now. An unspecified future building does not justify treating every spare feature as essential. This keeps the system selection focused without promising that expansion will never require redesign.
Resolve the monitoring requirement before ordering
If professional monitoring is part of the agreed response, identify the intended Alarm Receiving Centre, the proposed reporting connection and who will arrange acceptance. A statement that a system supports a protocol does not by itself settle whether the proposed service can receive and handle this installation’s events.
Keep a monitored proposal conditional until the relevant technical and service arrangements are resolved. If the project instead requires authorised users to receive notifications and act themselves, compare that arrangement explicitly; do not assume that a monitoring service is included.
Use the ARC integration planning guide for the detailed reporting and acceptance work.
Compare the delivered system, not just the supplied hardware
Before choosing between technically suitable proposals, establish who will survey, install, configure, test and hand over the system, and who will handle subsequent faults or changes. These commitments make the proposal deliverable rather than merely purchasable.
If a distributor supplies the equipment, confirm availability or agreed delivery dates for the specified items, and the route for replacement and technical support. A technically suitable proposal can still miss the project’s installation or service needs if these commitments remain unresolved.
For a wireless proposal, pairing a detector during setup and validating it at its final position answer different questions. Include final-position checks in the delivery scope. Where remote reporting is required, include its separate acceptance rather than treating a local alarm as evidence that the recipient received it.
Compare one-time equipment and installation costs separately from recurring services. If a proposal leaves a necessary task to someone else, name that party and include the task in the comparison. Select among proposals that cover the agreed work; use price and useful optional features to distinguish those suitable options.
Make a shortlist with clear next actions
Use the evidence and scope comparison to place each proposal in one of three groups:
• Ready for final selection: essential requirements are supported, the site plan is credible, required reporting and service arrangements are resolved, and delivery responsibilities are included or assigned.
• Needs clarification: a material capability, excluded task or service arrangement remains unresolved. Request a specific answer or revised proposal before ordering.
• Needs a different design: an essential requirement conflicts with the proposed capability or layout. Revise the design or choose another suitable proposal.
This is the system-selection stage. Distributors separately evaluating a manufacturer’s stock arrangements, commercial terms and longer-term supplier relationship can use the brand evaluation guide for EMEA distributors.
To discuss a Roombanker professional wireless intrusion alarm proposal, bring the site plan, required protection points, daily operating pattern and intended alarm recipients. Ask for a proposal that maps those requirements to equipment, evidence and delivery work, then compare it with alternatives on the same basis.