Trade experience
30 years
Field work, design, installation and support.
School security is not one product. It is a layered operating plan supported by cameras, door hardware, communications, visitor screening, evidence workflows and trained people. The point is not to buy more equipment. The point is to help staff see sooner, decide faster and document what happened without losing time inside disconnected systems.
Confluence Security works from the real campus outward. We look at arrival patterns, after-hours access, buses, exterior doors, hallway pinch points, common areas, parking areas and incident response. Then we specify what should stay, what should connect and what should be replaced because it no longer supports a defensible security posture.
Trade experience
30 years
Field work, design, installation and support.
Unified operations
1 platform
Cameras, doors, buses and events in one view.
Existing hardware
90 percent
Open architecture can often support what is already installed.
Service area
4 states
Colorado and Wyoming primarily, plus Utah and New Mexico
A district needs layers, not isolated devices. The outer layer is the perimeter, parking areas, bus loops, athletic entrances, service yards and approach roads. That layer tells staff who is arriving, where a vehicle went and whether an exterior event is developing before it reaches the building.
The next layer is the single point of entry. A school entrance should guide visitors through a controlled path where staff can see them, speak with them, screen credentials and deny access without exposing the rest of the building. Visitor management is strongest when the entry camera, door event and visitor record live in the same case history.
Inside the building, corridors, commons, cafeterias, gym areas and office zones need coverage that explains movement. A hallway camera should not just show that someone walked past. It should give enough detail to identify direction, clothing, timing and the next camera where that person appears.
The final layer is the classroom door. That means practical locking that staff can operate under stress, clear status indicators, code-compliant egress and procedures that match the hardware. Technology cannot override life safety code, and it should never force a teacher into the hallway to secure a room during an emergency.
Separate systems create separate timelines. The access control log says a door opened at 8:42. The camera system has video at 8:42. The bus system may show when a student arrived, and the license plate system may show a vehicle at the lot entrance. If those records require four logins and four searches, the district loses time at exactly the wrong moment.
A unified platform brings cameras, door access and license plate recognition across every building and every bus into one operating view. The administrator can move from a door alarm to the related camera, from a vehicle read to the nearest entrance camera, and from one school to another without starting over.
This is also where Genetec matters. Open platform design lets a district standardize operations without being forced into one hardware shelf. The district owns the strategy. The platform coordinates the work.
Most districts already own useful equipment. A good plan should not start by throwing it away. Open architecture works with roughly 90 percent of what is already installed across hundreds of manufacturers, so a district rarely has to rip and replace everything at once.
Analog cameras can often come into the platform through video encoders. Useful network cameras can be retained when they still provide enough pixels on target and still receive security firmware updates. Doors, readers and panels can be phased based on risk, age and integration limits.
The practical benefit is budget control. Districts can spend first where the risk is highest and where the existing system is weakest. That may mean exterior doors this year, bus video next year and older classroom wing cameras after that.
Video is only valuable if staff can find the right clip and preserve it properly. Modern systems allow search by attribute instead of scrubbing hours of video. A user can narrow a search by time, direction, clothing color, vehicle class or camera group, then export the result with an evidence trail.
Retention should be chosen on purpose. A district with daily incidents, parent requests, transportation claims and law enforcement requests may need longer retention than a quiet elementary school. Storage planning should include camera count, resolution, frame rate, scene motion, compression, retention target and whether buses upload video automatically or only when docked.
Evidence workflows matter. A clip should be exported, shared and logged without copying files onto thumb drives or personal desktops. Chain of custody is not a police-only issue. It is how a district explains what happened and who accessed the record.
Camera hardware is typically only 20 to 35 percent of installed cost. Cable, pathway, mounting, power, switch ports, storage, licensing, programming, commissioning and as-built documentation make up the rest. A budget that only counts camera boxes will miss the real number.
For planning, budget roughly 1,000 to 2,500 dollars per camera fully installed for a standard interior and exterior mix. That is a budgeting range, not a quote. Pole-mounted exterior cameras, parking structures, long conduit runs, core drilling, trenching, fiber work and lift work move the number higher.
Access control has a similar pattern. The reader is usually the cheap part. The cost lives in the door hardware, power, fire interface, cabling, programming, testing and making the opening safe and code compliant.
Districts normally buy school security through a mix of grants, cooperative purchasing and local procurement. The right path depends on whether the project is mostly product, mostly installation labor, or a construction project with public notice requirements.
The cleanest route is often to buy hardware at cooperative contract pricing and bid the labor locally. That shortens procurement while keeping installation competitive and documented. Grants can fund the project, but the purchase still has to follow the district's purchasing policy and the grant's rules.
Two recent posts answer questions districts ask us most often. The first covers the end of E-Rate support for school bus Wi-Fi and how to fund the onboard router as security infrastructure instead. The second walks through Colorado stop-arm camera enforcement law, including the vendor compensation limits that rule out the revenue-share model used in other states.
For planning, budget roughly 1,000 to 2,500 dollars per camera fully installed for a standard interior and exterior mix. Camera hardware is often only 20 to 35 percent of installed cost. Pathway, cable, mounting, storage, licenses, switch capacity, programming and commissioning make up the rest.
There is no single retention period that fits every district. Many schools choose 30 to 90 days for general campus video, then preserve incident clips separately. The right answer depends on policy, claims history, parent requests, transportation needs, storage budget and district counsel.
Usually, yes. Open architecture can often support existing cameras, door systems and analog cameras through encoders. We still evaluate whether each camera has enough pixels on target and whether it can still receive security firmware updates.
No. A phased plan is often better. Keep useful equipment, replace unsafe or unsupported equipment first, and move buildings into a common platform over time.
The district should own and control its video according to its policies, records rules and vendor agreement. We design the system so access is role-based, audited and controlled by the district.
Parents may have rights to inspect video showing their own child when it is treated as an education record. If other students are identifiable, the district may need redaction, consent or a controlled inspection process. District counsel should decide how each request is handled.
Continue through the school security cluster and related campus planning pages.
A school district camera system should be designed by zone, not by camera count. Entrances, corridors, commons, parking areas, buses and exterior approaches each need the right field of view, resolution, retention and network design so staff can identify what happened without putting unsupported devices on the student network.
Explore School camerasSchool access control should control how people enter, move and respond without trapping anyone inside. The strongest designs combine a single point of entry, visitor screening, secure credential technology, code-compliant door hardware and camera events that open the right video the moment a door alarm occurs.
Explore Access and visitorsA school emergency notification system should alert the right people at the right level, connect staff with responders and attach live camera context to the event. The goal is not just a louder alarm. The goal is faster shared understanding between the school, district, dispatch and law enforcement.
Explore Emergency responseThe best school security funding source depends on the project. Cameras, entry control and visitor management often fit COPS SVPP or Colorado School Security Disbursement, while interoperable communications, mass notification and radio coverage are a stronger fit for Colorado SAFER. Grant amounts, deadlines and eligibility change every cycle, so districts should confirm current terms before relying on any figure.
Explore Grants and fundingColorado school security requirements are best understood as documented reasonable care, privacy compliance and careful technology configuration. The Claire Davis Act does not require cameras, but it does increase the importance of documented assessment, remediation and execution. Colorado also has narrow school-specific restrictions on facial recognition, and school video can trigger FERPA review when students are identifiable.
Explore Colorado requirementsCollege and university campus security needs one federated platform across academic buildings, residence halls, parking, event venues and emergency communication points. The goal is to let campus safety teams manage access, video, parking events and incident review without treating each building as a separate system.
Explore Higher educationTalk with Confluence Security about a unified K-12 security plan that respects your current equipment and budget.
Kindly provide your contact info and a team member will get in touch shortly.