Updated 15 October 2026. A practical buyer guide from Zama Engineering Systems.
CCTV installation in Nairobi should begin with a clear question: what must the recording help you understand when something happens? A camera may show an entire compound yet fail to show the detail needed at a doorway. Another may produce an attractive daytime picture but an unusable night recording. Choosing cameras before defining those requirements can leave a business with equipment that works electrically but does not answer its operational questions.
This guide helps owners, facilities teams and procurement officers plan CCTV cameras and installation as a complete project. It covers site assessment, camera selection, recording, networking, remote access, commissioning and maintenance. It also explains how CCTV fits within wider security systems installation, and how to compare affordable equipment without treating the cheapest camera as the cheapest complete solution.
Zama Engineering Systems, ZES, can assess a proposed installation or an existing system and prepare a scope around the site requirements. Equipment, quantities, integration, support and delivery arrangements must be confirmed through assessment and quotation. The examples below illustrate planning decisions; they are not claims about completed ZES projects or promises that a particular system will prevent every incident.
1. Write an operational brief before requesting camera prices
Start by listing the events that matter. A shop may need to understand movement through the entrance and activity around a till. A warehouse may need evidence of goods being received and dispatched. An office may need to review an unauthorised entry. These objectives lead to different positions, angles and recording requirements, even where the buildings have similar floor areas.
Describe each objective in plain language. “We need to recognise a person approaching the staff entrance” gives the designer a more useful task than “provide clear cameras.” “We need to review which vehicle stopped at the loading point” is more specific than “cover the yard.” Avoid promising identification of every person or number plate from every position. The survey must establish which views can support the desired detail under actual conditions.
Include the people who will use the system. A procurement officer may approve the budget, a security supervisor may review footage and an IT administrator may maintain the network. Each has requirements that should be understood before equipment is ordered. Give one person responsibility for resolving conflicting expectations and signing off the agreed brief.
Finally, record what is outside the project. Neighbouring properties, private rooms and areas without a justified surveillance purpose should not quietly become additional coverage zones. A defined boundary improves privacy, cost control and the usefulness of the final design.
2. Survey the site at the times that matter
A daytime visit is useful, but it cannot fully demonstrate a night-time requirement. Ask the installer how lighting, headlights, shadows and changing activity will be assessed. Where a site operates after dark, include an appropriate low-light review in the scope. Otherwise, record that limitation and agree how the missing evidence will be obtained before final acceptance.
Walk the route of an ordinary person or vehicle through the site. Look for the moments when an object becomes hidden by a door, parked lorry, shelf, advertising board or structural column. These are often more important than the empty floor plan. In a warehouse, the height and arrangement of stock can change a previously useful view. At an entrance, a new canopy or sign may alter illumination.
Record mounting access, cable routes and maintenance access. A camera position that requires difficult access every time it needs attention may create avoidable operating cost. Consider whether installation will interrupt trading, block a route or require coordination with a landlord. Any work at height or near electrical equipment should be planned by competent personnel rather than improvised during installation.
The survey output should identify proposed views, assumptions, inaccessible areas and outstanding decisions. It need not be an elaborate document for a small site, but there should be enough information to explain why each camera is included and what the project will test.
3. Give every camera a specific job
A useful camera schedule contains an identifier, location, intended view and acceptance objective. For example, “CAM-03, staff entrance, observe entry and assess recognisable facial detail under agreed lighting” is a testable requirement. “Outdoor camera, high resolution” is merely a product description. The schedule helps the buyer compare proposals and gives the installer a reference during positioning.
Some views provide context; others capture detail. A wide view may show how an event developed across a yard, while a narrower entrance view may provide detail of someone passing through. Treat these as complementary tasks. Asking a single camera to cover a broad scene and capture fine detail at the far boundary can create unrealistic expectations.
Image usability depends on more than the number printed beside megapixels. Lens choice, distance, mounting angle, illumination and the recording configuration also matter. Manufacturer guidance such as Axis’s discussion of image usability explains why the required scene and purpose should lead the design. Ask suppliers to demonstrate the particular scene rather than relying on a resolution label alone.
Where analytics are proposed, make their purpose explicit. An alert feature should be tested in the intended environment, including ordinary movement that should not produce an alarm. Record any limitations. Analytics should support a defined response process, not create an expectation that the equipment can independently understand every unusual event.
4. Select an architecture that suits the existing infrastructure
An assessment should identify whether the site already has usable cameras, cabling, recorders, switches and power equipment. Reusing an asset can be sensible, but only after its condition, capabilities and compatibility are checked. “The camera still produces a picture” does not establish that it meets the new recording objective or can be managed securely in the proposed system.
Ask the supplier to distinguish an upgrade from a replacement. An upgrade may retain useful components and improve particular weaknesses. A replacement may be appropriate when support, compatibility or physical condition makes reuse impractical. Request the reasons in writing rather than assuming that either keeping everything or replacing everything is automatically economical.
For network-connected cameras, review the supporting network as part of the CCTV project. Switch capacity, available ports, power requirements, uplinks and cable condition can limit the installation. A recorder with spare channels does not necessarily mean the network and power system can support all those additional cameras without changes.
If separate contractors manage the building network and security equipment, identify the boundary between their responsibilities. Agree who provides addresses, network access, approved settings and fault diagnosis. Clear ownership prevents a camera outage becoming a prolonged argument about whether the problem belongs to the recorder, the switch or the internet provider.
5. Design recording around retention and retrieval
Decide how far back authorised users need to investigate an incident, and why. A business that discovers a stock discrepancy after a monthly review has a different requirement from one that reviews every shift. The agreed retention policy should reflect the purpose, organisational requirements and appropriate advice on information handling, rather than simply using all available storage indefinitely.
Storage demand varies with the number of cameras, recording settings, activity and recording schedule. Axis’s storage guidance notes that planning depends on camera configuration rather than one universal fixed calculation. Ask the installer to document the assumptions used for the proposed capacity and explain how actual retention will be checked once the system is operating.
Retrieval matters as much as storage. A supervisor should be able to locate the correct camera and time period without guessing which numbered channel corresponds to an entrance. Use meaningful names and check time settings. Where several devices are involved, inconsistent timestamps can make a sequence difficult to reconstruct even when every recording exists.
Agree how a relevant clip will be exported, where it will be kept and who can authorise disclosure. Test playback of an exported sample on an approved receiving device. A recording that remains locked inside an unfamiliar interface may be difficult to use when the organisation needs it most.
6. Plan power and connectivity interruptions
Power backup should be specified as a requirement for particular equipment and a particular operating objective. A backup unit serving the recorder alone may not maintain cameras, switches or the display. List the components that must remain available and ask the designer to assess the load and proposed backup arrangement together.
Do not confuse local recording with remote viewing. Depending on the architecture, losing the internet connection may affect remote access while local recording continues, or other dependencies may also be affected. Confirm the actual behaviour of the selected products. The handover document should distinguish a camera fault, a local network problem and a loss of internet access.
Where equipment supports additional recording or recovery features, define and test them explicitly. Do not assume that a camera has usable local storage, that recordings automatically reconcile after an interruption or that every model supports the same failover behaviour. Optional features can require compatible software, configuration and licences.
Develop a proportionate contingency process. Staff should know how to report an outage, which areas are affected and what temporary operational measures management has approved. A camera system is one part of security arrangements; its interruption should not leave the organisation without any agreed way to manage the immediate situation.
7. Make remote viewing an owned, controlled service
Remote access is convenient, but the organisation should decide who needs it and for what purpose. Separate routine viewing, playback, export and administration where supported. Giving every user a shared administrator account makes it harder to remove access when someone leaves and harder to understand who changed an important setting.
Agree how authorised access is established, reviewed and withdrawn. The customer should retain appropriate ownership of accounts and recovery details. Avoid leaving a permanent installation dependent on an unnamed technician’s personal account. Any supplier access for support should follow the customer’s approval and security process.
The exact remote connection method depends on the equipment and network. It should be assessed by the responsible IT or security team. This buyer guide does not recommend exposing recorder administration directly to the internet or changing protective settings simply to make an app connect. Convenience should not bypass the organisation’s network controls.
Test the approved remote-viewing workflow using the actual device types and connection conditions expected in service. Check whether the user can select the intended camera, retrieve a recording and understand a connection failure. Document any app subscriptions or hosted services and clarify what happens when they are not renewed.
8. Connect CCTV to a broader security plan
Security systems installation can include several distinct functions: observing events, controlling entry, detecting selected conditions and helping staff respond. Buying these as a bundle does not automatically integrate them. A proposal should explain each requested interaction, the equipment involved and the outcome expected from it.
For instance, a customer may want an access event to help an operator locate a related recording. That request needs confirmation of compatible products, software licences and configuration. A camera and a door reader carrying the same brand name are not enough evidence that the required workflow will operate as expected.
Define the response to alerts. Who receives them during working hours? Who is responsible after hours? What happens if the first person does not respond? Avoid creating so many low-value notifications that staff stop reviewing them. Alert design should be proportionate to the operational need and tested with representative ordinary activity.
Physical arrangements remain important. Reception procedures, controlled keys, appropriate lighting, staff training and secure storage cannot be replaced by video alone. During assessment, record problems that fall outside the CCTV scope and identify who owns them. This makes the limitations of the proposed installation visible before management relies on it.
9. Compare affordable CCTV without buying an incomplete package
Searches for cheap cameras in Kenya can lead to offers that describe only the camera hardware. Before comparing totals, check whether each quotation includes the same recording, storage, power, cabling, mounting, configuration, training and support. A lower equipment price can be offset by omitted work or a replacement needed soon after installation.
Ask for exact models and quantities. Marketing descriptions such as “HD camera” or “complete security kit” may leave important differences unresolved. Check whether the proposed equipment supports the required environment, recording objective and software. Ask who provides warranty support and how a fault is diagnosed before equipment is returned.
Avoid paying for specifications that do not solve your problem. A small office may not need every available analytic feature. Equally, a demanding loading bay may need more careful design than a basic indoor view. Value comes from fit to the requirement, not from buying either the lowest or highest specification everywhere.
Where the budget is limited, phase the work deliberately. Protect the most important views first, while designing supporting infrastructure for the intended next stage where appropriate. Record which areas remain outside coverage. A transparent phased plan is more useful than suggesting that a small package provides comprehensive protection for a much larger site.
10. Understand the cost items in a Nairobi quotation
The final price should follow the survey and agreed scope. Equipment costs may include cameras, recording equipment, storage, network components and power accessories. Installation costs can include cable routes, containment, mounting, access equipment, configuration and testing. Travel, delivery, taxes and necessary making-good work should be stated rather than assumed.
Building conditions can materially affect labour. An operating warehouse, finished office and new building offer different installation access. Existing cabling may reduce work if it is suitable and tested, or increase diagnostic time if its condition is uncertain. Require the supplier to identify assumptions that could change the quoted price.
Separate one-time expenditure from recurring expenditure. Hosted services, connectivity, licences and maintenance can continue after installation. Ask what is necessary for the agreed functions and what is optional. A lifecycle comparison helps management understand the continuing commitment rather than approving only the first invoice.
If several bidders are involved, issue the same camera schedule and acceptance requirements to each. Request separate prices for genuine alternatives. This makes it possible to compare like with like and identify where a bidder has omitted work, proposed a different operating model or included additional capability that needs a clear business justification.
11. Plan installation around the business
Agree a programme with the people responsible for the premises. Specify working hours, access arrangements, contact persons and any areas that require special permission. Staff should know when installers will be present and how disruption will be communicated. Work affecting occupied areas should be coordinated with the site’s normal safety and security procedures.
For a replacement project, identify the recording gaps that may occur while equipment changes. Do not let the business assume uninterrupted surveillance if the approved method requires an outage. Agree temporary arrangements and a sequence that reduces unnecessary interruption to the most important views.
Manage changes through a simple written process. Moving a camera to another building or extending a cable route may affect materials, labour and the original coverage objective. Record the reason, cost and approval. Otherwise, the final installation can drift away from the proposal without anyone understanding the resulting compromises.
Keep an asset record as work progresses. Camera identifiers, locations, relevant equipment details and labelled connections make later support easier. Protect sensitive configuration information appropriately rather than displaying it in public areas. Documentation is part of the installation, not a separate exercise to be reconstructed after the technicians have left.
12. Test the system using realistic scenarios
Commissioning should demonstrate the agreed purpose of each view. Ask a representative person to follow the relevant route and review the recorded result, not just the live screen. Where vehicles matter, use an appropriate controlled test under ordinary operating conditions. Record limitations rather than assuming future users will somehow obtain more detail from the same image.
Include the lighting conditions identified in the brief. A successful daytime test does not close a night-time requirement. If a test must be deferred, list it as outstanding with an owner and agreed completion arrangement. Acceptance should distinguish completed checks from assumptions and unfinished work.
Test recording search, playback and export with the intended operator. Check camera names and timestamps. Where remote access is included, demonstrate the approved permissions and removal of a test user. Where an interruption scenario is in scope, test it through an agreed safe procedure and verify recovery rather than merely stating that backup exists.
Use a concise acceptance record showing the requirement, method, result and any corrective action. This gives both customer and installer a shared definition of completion. It also provides useful evidence when a later alteration, environmental change or equipment fault affects a view that previously worked.
13. Train the people who will use the recordings
Training should cover ordinary tasks rather than a rapid tour of every menu. The operator should know how to find a camera, check whether it is recording, search a time range, export an authorised clip and report a fault. The administrator should understand user access and the controlled process for configuration changes.
Choose a primary operator and a backup. If only one person knows the system, holidays and staff changes can leave the business unable to retrieve relevant footage. Keep an approved quick-reference guide with camera names, support contacts and the steps for requesting assistance. Store sensitive account information separately under the organisation’s access controls.
Explain what the system cannot establish. A wide view may show activity without identifying a person. Missing footage should be investigated rather than immediately attributed to deliberate deletion. A timestamp may need checking against system settings. These distinctions help staff use recordings responsibly and avoid overstating what an image proves.
Agree a review after the system has operated under normal conditions. Users may identify naming problems, inconvenient workflows or a view obscured by ordinary deliveries. Resolve those observations through the agreed support or change process. Training is most effective when the team can relate it to the actual workplace.
14. Keep the installation useful over time
Maintenance should address image usability, recording health, physical condition and administration. A camera can remain online while its view is obstructed or dirty. A recorder can appear normal while storage or time settings require attention. Checks should reflect the installed equipment and manufacturer guidance rather than being limited to whether the screen shows pictures.
Inspect the effect of changes around the premises. New shelves, signs, lighting, partitions or vegetation may affect the original coverage. Ask facilities and operations teams to include security-system review when they plan material layout changes. That is often more effective than discovering the problem after an incident.
Review access when staff responsibilities change. Remove accounts that are no longer needed and control supplier access. Handle updates through an agreed maintenance process, including compatibility review and appropriate backup arrangements. An update should not be treated as a reason to make unrecorded changes to unrelated settings.
A support agreement should state its scope, service hours, reporting channel and exclusions. Separate routine inspection from urgent fault attendance and replacement parts. Management should understand what is included before it relies on the agreement during a disruption. Response commitments need to be written into the actual contract, not inferred from a general statement that support is available.
15. Prepare a quotation request that gets useful answers
Send the site location, operating hours, proposed coverage areas and main incident questions. Include available plans or photographs, current equipment details and known faults. State whether the project is new installation, expansion, repair or replacement. Identify the people who approve the design and those who will operate the completed system.
Describe retention and remote-access requirements, but mark uncertain items for assessment. List any proposed links to access control, alarms or other platforms with exact product details where available. Explain installation restrictions, the desired completion period and the process for approving variations. If a budget range is available, it can help the supplier offer realistic phased options.
Require the proposal to state exclusions and assumptions. Ask for the camera schedule, equipment list, recurring fees, acceptance tests and handover documents. Confirm how warranty and support will be handled. These details make supplier comparison more useful than a list of camera counts and a single total.
ZES can use this information to assess your CCTV installation in Nairobi and prepare a project-specific recommendation. The objective is a system that produces usable recordings, can be operated by your team and has a clear maintenance path. Request an assessment through the ZES contact form, with your location and the outcomes that matter most.
Frequently asked questions
How many cameras does a business need?
The answer follows the required views, not a universal ratio to floor area. Entrances, boundaries, working areas and blind spots must be assessed individually. Two layouts of the same size can need different quantities. Ask the designer to explain the purpose of each proposed camera and any areas that remain outside the scope.
Does a high-resolution camera guarantee identifiable footage?
No. The distance, angle, lens, lighting and recording configuration influence what a recording can show. Test the actual intended scene. A product specification helps select equipment, but the recorded result under agreed conditions is the more useful acceptance evidence.
Can an existing installation be improved without replacing everything?
Sometimes. Begin with an assessment of equipment condition, support, cabling, recording and the unmet requirement. A targeted change may resolve a particular weakness. Where reuse is unsuitable, the proposal should explain why and distinguish necessary replacement from optional upgrades.
Will CCTV stop theft or guarantee recovery after an incident?
No installation can guarantee those outcomes. CCTV can support observation and investigation when its views and recording work as intended. Its value also depends on response procedures, physical security, maintenance and responsible handling of the recordings.
What should I check before making final payment?
Use the agreed contract and acceptance schedule. Check the required views, recording, retrieval, authorised remote access and handover training. Record defects and deferred tests through the agreed completion process. Confirm equipment documentation, account ownership and support contacts rather than relying only on a successful live demonstration.
A worked procurement example: an occupied office building
Consider a hypothetical office with a public reception, staff entrance, shared corridor and small delivery area. The manager initially requests eight cameras because that is the size of a package advertised online. During preparation, the team instead lists four questions: who entered the staff area, when a delivery arrived, what happened in the public reception and whether the delivery door was left open. The number eight becomes a proposal assumption rather than the starting requirement.
The installer surveys those areas and records the viewing objectives. Reception needs context, while the staff entrance needs a more deliberate view of approaching users. The delivery area operates into the evening, so lighting assessment is included. The customer does not request recording inside private offices. The quotation identifies the required network and power work, and states that any connection to the door access system is an optional, separately tested interface.
At acceptance, the receptionist retrieves a sample event, the authorised administrator removes a temporary user and the manager reviews the evening delivery-area recording. One view is partly obscured by a noticeboard, so its position is corrected and retested. The completion record explains which checks passed and which recurring inspections belong to the customer’s facilities team.
This example does not establish an appropriate camera count or price for another office. Its value is the decision process: define the events, assess the scene, price the complete scope and verify the result. A buyer can apply that process to a shop, apartment building or warehouse without copying a package that was designed for a different property.
Reviewing the first month of operation
Schedule an internal review after the system has been used during ordinary working conditions. Ask operators which searches were easy, which camera names were confusing and whether any important view was obstructed during normal deliveries or cleaning. The purpose is to identify practical adjustments while the original design and training are still fresh in everyone’s mind.
Compare observations with the agreed scope. A camera that fails its accepted view needs investigation. A newly requested view of an area originally excluded is a change. Keeping that distinction clear makes the discussion fair to both the customer and supplier. Record any adjustment and repeat the relevant test rather than assuming that moving a camera improves every part of its scene.
Review whether staff are following the access and export procedures. If everyone still asks one administrator to retrieve footage, additional training may be more useful than new hardware. If alerts are ignored, examine the response workflow and relevance of the notifications. Operational problems should be addressed through the process that creates them rather than automatically treated as a reason to purchase more equipment.
Finally, confirm the maintenance and support contacts remain current. A useful installation should be understandable to the people responsible for it, with evidence of what was delivered and a clear route for resolving problems. That is a stronger basis for long-term value than a successful demonstration on installation day alone.
Sources and further planning
For manufacturer discussion of scene-based image usability, see Axis: Quality with a purpose. For recording-capacity considerations, see Axis: Video surveillance storage. These references explain design principles and do not imply a ZES partnership or endorsement.
For related ZES guidance, read CCTV installation cost planning, CCTV maintenance contracts and access control installation. Send your project brief through the ZES enquiry form to request a scoped assessment.