Updated 15 October 2026. A practical buyer guide from Zama Engineering Systems.
Buying CCTV cameras and installation as one project is different from comparing cameras on a shop shelf. The finished result depends on the camera views, recording arrangement, cable routes, power, administration and the people who will use the recordings. A camera with an impressive specification can still be a poor purchase if it is installed in the wrong position or connected to an arrangement that does not meet the business’s needs.
For an existing Kenyan business, the most useful question is often whether to retain, improve or replace the present installation. A new business faces a related decision: which architecture is appropriate now, and which choices will make later expansion manageable? IP, analogue and supported mixed arrangements should be evaluated against the actual site and operating requirements. The architecture label alone is not a reliable measure of image usefulness or overall project quality.
This guide focuses on those infrastructure decisions. It explains how to brief an installer, examine reusable equipment and compare migration proposals. It does not provide a universal product ranking or claim that every device using the same broad technology will work together. ZES can assess a proposed installation or upgrade and define equipment, configuration, testing, training and support subject to the agreed scope and confirmed compatibility.
Define the tasks the cameras must support
Start with the questions that authorised staff need to answer. Do they need an overview of activity in a yard, a useful view of deliveries at a defined point or a way to review movement through an entrance? These purposes differ. A wide scene may show that something happened without showing the detail required to understand it. The project brief should state the task for each important view.
Avoid treating the number of cameras as the main requirement. Two proposals with the same camera count can produce very different results because the positions, lenses, lighting and recording configuration differ. A useful schedule connects each proposed camera to a location and purpose. That makes it easier to review whether the design covers the intended activities rather than simply filling a recorder’s available channels.
Include the times when each task matters. A reception area may operate mainly during the day, while a loading area may remain active in the evening. Tell the installer about vehicles, shutters, lighting changes and seasonal layout changes that could affect the scene. These operational details help determine what needs to be demonstrated during assessment and acceptance instead of being discovered after installation.
Understand the architecture in practical terms
An IP camera forms part of a network-based video arrangement. An analogue camera installation uses a different video connection and recording architecture, with exact capabilities depending on the camera, recorder and supported signal format. For procurement, the important point is that these are system choices, not just camera choices. The installer should show how the selected devices connect, receive power, record and become available to authorised users.
Ask for a simple diagram of the proposed arrangement. It should identify the cameras, relevant connection equipment, recording or management components and viewing locations. Where existing infrastructure is retained, mark it separately from new work. The diagram does not need to expose sensitive technical information in a general tender document; it needs to make the project boundaries understandable to the decision-makers.
Avoid assumptions based on familiar terms. Network-based does not automatically mean cloud recording, and remote viewing should not be confused with where footage is stored. Similarly, an existing analogue installation is not automatically unsuitable simply because it is older. The correct decision follows an assessment of the actual equipment and requirements, including the operational and maintenance implications of the proposed finished arrangement.
Separate image requirements from technology labels
A buyer may hear that one category of camera always produces better images than another. That is too broad to guide a real project. The useful result depends on the selected model and the scene in which it operates. Ask for evidence relevant to your location rather than relying on a showroom image or a photograph captured under different lighting and distances.
Describe what needs to be visible at the important point in the scene. If the objective is to review a delivery handover, agree where that handover takes place and what a representative demonstration should show. If the purpose is general activity awareness, state that separately. Do not allow a broad overview demonstration to stand in for a more demanding detail requirement.
Include recorded playback in the review. A live view alone does not demonstrate the quality and usability of the stored material that staff will later examine. The acceptance process should use the proposed recording settings and normal viewing workflow. Where conditions cannot be reproduced during the initial survey, record the uncertainty and plan a suitable later test rather than presenting an unverified expectation as a guaranteed result.
Inventory the existing installation carefully
An upgrade should begin with an equipment inventory. Record camera and recorder identities, their locations, observed condition and available documentation. Include displays, cabinets, connection equipment, power arrangements and relevant software or licences. Ask the current administrator which views are useful, which are unreliable and which tasks are difficult. The technical inventory and the user’s experience provide different but complementary information.
Do not equate an operating device with a suitable device. A camera may display a picture but fail the new requirement for a particular scene. A recorder may still function but lack the confirmed capacity or supported features required for the proposed expansion. The assessment should distinguish equipment that is suitable to retain from equipment whose role requires further confirmation.
Record ownership and support responsibility as well. In a rented property, some infrastructure may belong to the landlord or a previous tenant. The customer should establish permission before altering it. Where original documentation is missing, include the cost and limitations of investigation in the project plan. A transparent inventory makes the migration proposal easier to evaluate and provides a reference when the finished system is handed over.
Treat reusable cabling as a question to investigate
Existing cable routes can represent valuable infrastructure, especially in an occupied building. However, a route, a cable and a complete connection are different things. A usable containment route does not establish that the cable inside it is suitable for a new purpose. The installer should explain which elements can be assessed, which tests are appropriate and which parts remain inaccessible or uncertain.
Ask a reuse proposal to identify the exact retained segments and the reason they are considered suitable. If an adaptor or conversion device is proposed, confirm the supported application, environmental requirements and effect on maintenance. A seemingly inexpensive bridge between old and new equipment can add another component that someone must understand and support later. That may still be worthwhile, but it should be a conscious decision.
Compare reuse with replacement on the whole project. New cabling may involve disruption and finishing work, while retaining unsuitable infrastructure may cause repeated faults or restrict the intended upgrade. The assessment should make these tradeoffs visible without declaring either approach universally best. Where testing cannot establish suitability, record the risk and agree how an unsuccessful reuse attempt would be handled commercially.
Examine power as part of the design
Every camera arrangement needs a defined power plan. Buyers should understand which components supply or depend on power and which parts are included in any backup proposal. Ask the installer to identify these relationships in the project documentation. A backup arrangement that covers one component may not cover the complete path needed for the intended recording or viewing function.
The proposal should state the assumptions used to select power equipment and the responsibilities for specialist electrical work. Do not treat an available socket as evidence that every electrical requirement has been assessed. Building conditions, equipment locations and maintenance access matter. Where an electrician or another specialist is needed, make that interface explicit so it does not emerge as an unplanned extra during installation.
Discuss the desired response to a power interruption in operational terms. What should the customer be able to do, for how long under the agreed assumptions, and what limitations apply? Confirm the selected design through appropriate authorised testing. Avoid accepting a vague promise of uninterrupted operation. The useful outcome is a documented arrangement with understandable dependencies and a procedure for reporting any loss of service.
Bring the IT team into network decisions
Where the proposed system uses the business network, involve the person responsible for that network early. The installer should explain the expected connections, management needs and viewing arrangements. IT should review the proposed relationship with existing infrastructure and business services. This reduces the chance of a completed camera installation depending on a network change that nobody has approved.
Ask who supplies, configures and supports each relevant network component. If the quotation relies on existing equipment, identify it and record what has been checked. If dedicated equipment is proposed, state its purpose. The business should understand which contractor to contact when a camera, a connection or a viewing workstation is unavailable, rather than being passed between suppliers without a clear responsibility boundary.
Remote access deserves a separate discussion. It should be configured through an approved, supported method with appropriate user permissions and ownership. The procurement brief should identify who needs access and from which working context without demanding broad access for everyone. Exact security configuration belongs with competent administrators and the selected product guidance, not with improvised shortcuts designed only to make a demonstration work quickly.
Specify recording requirements before choosing storage
The recording arrangement should follow the customer’s intended use and information-handling policy. Ask which cameras need recording, under what operating conditions and how authorised staff will search and review it. The desired retention period is one input, but it is not a complete storage specification. The selected equipment and recording configuration must be assessed together.
A proposal should state the assumptions behind its storage recommendation, including the planned configuration and any factors that could change the outcome. Do not accept an exact retention promise without understanding those assumptions. Ask how the customer will confirm recording is taking place and how changes to settings or camera quantities affect the original plan. This helps prevent an upgrade from quietly reducing the useful history available for review.
Information retention also requires an owner. The customer should decide who approves access and how relevant records are handled under organisational policy and applicable obligations. The installer can explain technical configuration options, but installation alone is not a legal compliance assessment. Keep the policy decision and technical implementation connected while recognising that they are different responsibilities.
Check exact compatibility rather than brand familiarity
Products from a familiar brand are not automatically interchangeable across every generation or software version. Likewise, products from different suppliers may support selected functions together without supporting everything the customer expects. Ask for compatibility to be confirmed at the level of the intended configuration: exact equipment, relevant software, required features and the proposed management arrangement.
Create a short list of the functions that matter. These might include recording, playback, authorised remote viewing or a specific administration workflow. A basic connection test may confirm only part of that list. Where an integration is important, request a demonstration or documented confirmation appropriate to the project before committing to the purchase. Record any functions that will remain unavailable.
Compatibility also has a maintenance dimension. Ask what happens when a component is replaced or software is updated. Who will check the effect on the rest of the installation? A proposal that depends on several suppliers should explain the support boundaries. The customer does not need a guarantee that nothing will ever change; it needs a manageable process for preserving the agreed functions as the system is maintained.
Compare retaining, migrating and replacing
There are usually several reasonable ways to approach an existing installation. Retaining the present architecture may be sensible where the equipment meets the important requirements and remains supportable. A staged migration may suit a business that needs selected improvements while controlling disruption. A wider replacement may be justified where the existing arrangement cannot meet the intended tasks or creates an impractical maintenance burden.
Ask the installer to compare options against the same outcomes. For each option, identify retained equipment, new equipment, installation work, operating limitations and likely future changes. This makes the decision about business value rather than simply choosing the newest category. It also prevents a partial upgrade from being priced against a comprehensive replacement as though the two delivered the same result.
The customer should consider disruption as well as expenditure. Replacing infrastructure in an occupied office may require access arrangements and finishing work that a smaller intervention avoids. Conversely, repeated small changes may become inefficient if a major refurbishment is already planned. Explain the relevant building programme to the installer so the recommendation can fit the timing of the business rather than treating the camera project in isolation.
Make a phased migration genuinely useful
A phased migration should describe both the first usable result and the intended later arrangement. Without that distinction, the customer can spend money on temporary connections that become expensive to remove or maintain. Ask which components are permanent, which are transitional and why the temporary stage is justified. Include any expected limitations in the phase-specific handover.
Each phase needs a clear acceptance test. If the first phase improves the loading area, the customer should be able to use the agreed loading-area views and recordings before the next phase begins. Do not leave essential administration or documentation unfinished on the assumption that the entire site will eventually be upgraded. Funding and building plans can change, so each completed stage should stand on its own agreed scope.
Keep the migration record current. Mark which devices and routes remain from the earlier installation and which have changed. Update the support contacts and user instructions. This is particularly important where more than one architecture operates during transition. Clear records prevent future technicians from guessing how the system was assembled and help management evaluate the cost and benefit of the next stage.
Evaluate a hypothetical office upgrade
Imagine a hypothetical office with an existing analogue installation that provides useful corridor views but limited coverage of a newly created reception area. Management also wants selected authorised managers to review relevant recordings more easily. The correct response is not automatically to replace every camera. The assessment should examine the present recorder, views, infrastructure and management workflow against the new requirements.
One proposal might retain suitable existing components and add a supported arrangement for the new area. Another might propose a broader migration because the present equipment cannot support the required functions. Both should explain the intended result, compatibility evidence, installation disruption and maintenance responsibility. The customer can then compare complete options instead of judging them solely by camera price.
Acceptance would include the new reception task and the agreed recording-review workflow, alongside checks that retained functions still operate as intended. Any limitations would remain visible in the handover. This example is illustrative rather than a claim about a completed ZES installation. It shows why the upgrade decision begins with requirements and evidence, not a rule that old technology must always be discarded.
Evaluate a hypothetical warehouse extension
Consider a separate hypothetical warehouse expanding into an adjacent unit. The business wants useful views of a new loading activity while retaining its existing administration arrangements. The project has physical questions about cable routes and equipment locations, operational questions about delivery movements, and technical questions about the capacity and compatibility of the current recording arrangement.
The installer should assess these together. A proposed new camera position may provide a suitable view but require a route that crosses another tenant’s space. Existing recording equipment may have apparent room for expansion but still require confirmation against the intended configuration. The business should resolve property permissions and infrastructure assumptions before ordering equipment based on a simple device count.
A sensible proposal would show the new work, retained elements and any management changes. The acceptance test would use a representative loading activity and check recorded playback through the agreed workflow. Documentation would then be updated to include the extension. This approach makes expansion a controlled project rather than an informal addition whose cabling, settings and support responsibilities are remembered only by the person who installed it.
Compare installation quotations line by line
When comparing quotations for CCTV cameras and installation, create a common list of deliverables. Include the equipment schedule, routes and containment, power-related work, configuration, viewing setup, recording configuration, testing, training, documentation and support. Ask each supplier to identify customer-provided items. This reveals whether an apparent price difference reflects different equipment choices or simply missing work.
Check how uncertainty is priced. A supplier may need to inspect a concealed route or test existing cabling before confirming reuse. A provisional item can be reasonable when its basis and approval process are clear. An unexplained allowance is harder to manage. Ask what evidence will resolve the uncertainty and how the customer will approve any resulting change before extra work begins.
Review the expected finished condition of the premises. Visible cable management, labels, equipment mounting and making good can affect the practical quality of the installation. Specify relevant expectations rather than assuming every proposal includes the same finish. Good procurement makes these details reviewable, while still allowing the installer to recommend a suitable method for the building and agreed budget.
Use demonstrations that match real conditions
A convincing demonstration should answer a defined question. Ask to review the intended scene, relevant operating conditions and recorded result rather than a generic promotional video. If the customer needs to understand activity at an entrance during a lighting change, the demonstration should address that situation as far as practical. Record any conditions that cannot be assessed before final commissioning.
Involve the people who will actually use the system. A manager may be satisfied with a live overview while the supervisor responsible for reviewing incidents needs a practical search and playback process. Both perspectives matter. Let users try the agreed tasks during acceptance so the team can identify training needs and usability problems before sign-off.
Keep the evidence proportionate. A small installation may need a concise test sheet, while a larger project may require a structured camera schedule and documented results. The principle is the same: the customer should know what was checked and what the result was. Avoid treating a quick display of several live camera tiles as proof that every recording and operational requirement has been met.
Prepare secure, usable administration
Administration should reflect responsibility. Decide who can view, review recordings, manage users and approve configuration changes. The exact roles available depend on the selected system, but the organisational decision should come first. Ask the installer to explain how the agreed roles are implemented and what limitations apply. Shared unrestricted access is rarely a good substitute for a defined operating process.
The handover should identify the owner of administrative access and the process for future staff changes. Sensitive access information should be transferred through the customer’s approved method, separately from widely circulated project documents. Confirm any ongoing installer access needed for the support arrangement and how the customer can review it. These are ownership questions, not optional finishing details.
Also identify who approves updates and configuration changes. A well-intentioned adjustment can affect recording, views or access. The customer needs a straightforward route for requesting changes and recording what was done. This protects the usefulness of the installation over time and makes fault investigation easier because support staff can distinguish a new problem from an intentional change in operating settings.
Budget for ownership after installation
The initial invoice is only part of the ownership decision. Ask about licences, subscriptions, planned maintenance, support visits, replacement components and additional training where applicable. Do not assume every system has the same continuing costs. A proposal should identify which costs apply to its actual configuration and which services are optional rather than bundling them into vague claims about lifetime value.
Support terms should identify how faults are reported, what information is needed and the agreed service arrangements. Separate product warranty, workmanship provisions and paid maintenance. They can cover different situations. Ask how responsibility is handled when retained equipment or infrastructure contributes to a problem, especially in a mixed or phased installation with components from different periods.
An equipment and configuration record supports better budgeting. Management can see what was retained, what was replaced and which items require future review. The aim is not to predict every possible failure. It is to avoid an arrangement where the business cannot establish what it owns or why a particular component was selected when the next expansion or maintenance decision arrives.
A practical decision meeting before approval
Bring procurement, the operating manager and relevant IT or facilities staff together before approving the preferred proposal. Ask the supplier to explain the design against the agreed tasks, highlighting retained infrastructure and unresolved assumptions. The meeting should produce decisions rather than simply another product presentation. Assign an owner to any remaining question and establish whether it affects the purchase decision.
Confirm the programme, access arrangements and acceptance process. If work must happen outside normal operations, record that requirement and its effect on the quotation. Identify who can approve a change during installation. Agree the handover documents and training audience. These details help the project move from an appealing proposal to an executable plan that the customer can review at completion.
The preferred architecture should emerge from this discussion as a justified choice. It may be a retained analogue arrangement, an IP installation or a supported transition. What matters is whether the selected configuration meets the agreed purpose, can be operated responsibly and has a clear maintenance path. That is a more reliable purchasing basis than assuming one technology label guarantees a professional result.
Avoid confusing central viewing with central recording
A business with several branches may want managers to review selected views from one location. That requirement does not by itself determine where recordings should be held or how every branch should be connected. Ask the designer to separate the viewing objective, recording objective and administration objective. Each can have different dependencies and should be evaluated against the customer’s connectivity, information-handling and support arrangements.
For each branch, record the local tasks that must remain usable and the functions that depend on connections outside the site. The proposal should explain what staff can expect when a dependency is unavailable, using the selected configuration rather than general claims about cloud or network technology. This helps management avoid assuming that a convenient central display proves that all recordings are complete and retrievable at every branch.
Choose a representative branch for a pilot where the scale of the programme justifies it. Include the users responsible for local operation and central review. Their acceptance tasks should cover the actual workflow, including how a request is passed between them. Use the pilot to improve documentation and responsibilities before repeating the arrangement, while retaining flexibility for branches with different layouts or operating conditions.
Distinguish faults from changing requirements
After an upgrade, a reported problem may have several explanations. A device may be unavailable, a user may need training, or the business may be asking the installation to cover an activity that has moved. The support process should collect enough context to distinguish these situations. Useful information includes the affected view, when the issue was noticed, the task being attempted and any known operational or building change.
Avoid solving every complaint by replacing a camera. If shelving blocks an agreed view, the first question concerns the changed scene. If users cannot locate a record, review the recording and search workflow before assuming the image equipment is responsible. A structured investigation is more efficient and can prevent unnecessary spending on hardware that does not address the underlying issue.
Keep approved requirement changes separate from corrective work. If the business creates a new loading point, that may call for a revised scope rather than a warranty repair. Clear records make this distinction fair to both customer and installer. They also help future planning by showing where the original installation still meets its purpose and where the operation has developed new needs.
Ask ZES to assess the appropriate installation path
Prepare the site location, a description of the areas to cover, the tasks you want recordings to support and any available information about existing cameras and recorders. Include planned renovations, expansion, operating hours and known access restrictions. If equipment identities are unclear, say so rather than guessing. These details help an assessment focus on the decisions that affect cost, disruption and usefulness.
For broader project preparation, read the ZES CCTV installation guide. To discuss retaining, upgrading or replacing your present arrangement, request a CCTV assessment from ZES. The resulting scope should explain the selected equipment, infrastructure, configuration, testing, training and support, with actual compatibility confirmed. A good camera project gives the business a defined operational result and the records needed to maintain it.