For decision makers at K-12 districts, charter networks, and universities in Puerto Rico

A new security technology project for a school or campus in Puerto Rico realistically takes 10 to 12 months from the first planning conversation to a fully live, supported system. Public K-12 districts and universities tend to land at the longer end because of formal procurement. Charter networks can move faster, but the sequence of steps is the same. The timeline below assumes a mid-sized project such as campus-wide video surveillance, access control, visitor management, or a combination, with the network and power work needed to support it.

If your leadership team is asking “how long will this take,” this is the answer we give clients before any proposal is written.

Why security technology projects take longer than the install

The installation itself is usually the shortest part of the project. What takes time is everything around it: agreeing on what problem you are solving, confirming the building can support the equipment, securing funding inside a fiscal calendar, getting through procurement, and scheduling work around students.

Skipping any of these steps does not shorten the project. It moves the delay to a later, more expensive stage. A district that rushes to purchase cameras before assessing its network often discovers in month eight that the switches, cabling, or power are not ready. A university that installs access control before agreeing on who manages credentials ends up with doors that work and a policy vacuum around them.

The month-by-month structure below is designed to prevent those surprises.

Month 1: Define the problem and the decision group

Before anyone talks about products, the institution needs a shared answer to one question: what specifically are we trying to change?

Typical answers we hear in Puerto Rico schools and campuses:

• Faster, more reliable visibility into incidents across multiple buildings
• Control over who enters buildings during and after school hours
• Replacing an aging system that no longer receives support or parts
• Meeting a requirement tied to insurance, accreditation, or a funding program
• Better coordination with local police or campus security during an emergency

This month also sets the decision group. For a K-12 district, that usually means the superintendent’s office, facilities, IT, and school safety, with a board contact identified early. For a charter network, it is often the executive director, the operations lead, and a school leader from each site. For a university, it typically includes campus security, IT, facilities, and the office that manages procurement and compliance.

Output of Month 1: A one-page problem statement and a named decision group. This document becomes the reference point for every later trade-off.

Month 2: Site assessment and current-state audit

This is the step most often skipped, and the one that saves the most money later.

A proper assessment looks at each site and documents:

• Existing cameras, door hardware, intrusion devices, and how much of it is worth keeping
• Network capacity, switch age, PoE availability, and available ports per building
• Cabling pathways, especially in older concrete structures where new runs are labor-intensive
• Power quality and backup, including what happens to the system during an outage
• Physical conditions: salt air exposure, roof access, coverage gaps, lighting at night
• Campus maps with building names, entry points, and hours of operation

In Puerto Rico, two items deserve extra attention. First, power resilience: every device in the system needs a clear answer for how it behaves when utility power drops, whether that is UPS, generator, or both. Second, environmental exposure: exterior devices near the coast face corrosion faster than manufacturers’ spec sheets assume, and enclosure and mounting choices should reflect that.

Output of Month 2: A written current-state report per site. Many institutions find this report valuable on its own, because it also surfaces network and electrical issues unrelated to security.

Month 3: Scope, specification, and phasing

With the problem defined and the sites documented, the project can be scoped. This is where “we want cameras” becomes a specification a contractor can price.

A good specification covers:

• Coverage requirements by location, not by camera count
• Access control scope: which doors, what credential type, who administers it
• Integration expectations between video, doors, alarms, and visitor systems
• Retention, storage, and who has access to footage, including the policy side
• Network and electrical work required to support the devices
• Phasing: which sites or buildings come first, and why

Phasing matters for every segment. A district with 20 schools should not attempt all 20 at once. A university may prioritize residence halls and after-hours buildings before academic spaces. A charter network might pilot one campus, refine the standard, then replicate it.

Output of Month 3: A scope document with a realistic budget range and a phasing plan. This is also when the institution decides whether to use a standard bid, a request for proposals, or a cooperative purchasing route.

Month 4: Funding and internal approvals

Security projects in education rarely fail on technology. They stall on money and calendar.

This month is about aligning the project with how the institution actually pays for things:

• Puerto Rico’s public fiscal year runs July 1 through June 30. Projects that need new budget lines must be positioned before the budget is finalized, not after.
• Federal and reconstruction-related funding programs each carry their own documentation, eligibility, and reporting requirements. Confirm early which costs qualify and what evidence must be kept.
• Multi-year approaches, including maintenance agreements, can spread cost and make approval easier than a single large capital request.
• Board or trustee approvals have their own meeting calendar. Missing a cycle can cost 30 to 60 days.

Output of Month 4: A confirmed funding source, an approved budget ceiling, and a procurement path with dates attached.

Months 5 and 6: Procurement

Procurement length is the biggest variable between segments.

Public K-12 districts generally follow formal bidding rules with published notices, question periods, and evaluation committees. Two months is a realistic minimum; three is common.

Universities typically run through a central procurement office with its own thresholds and review steps. Public institutions follow rules similar to districts. Private universities often move faster but still require competitive quotes above certain amounts.

Charter networks usually have the most flexibility and can complete vendor selection in four to six weeks, provided the scope document from Month 3 is clear.

Regardless of route, this is where the quality of the earlier work pays off. Vendors responding to a vague scope will price defensively or leave gaps. Vendors responding to a documented site assessment and a clear specification will price accurately, and proposals will be comparable.

Output of Month 6: A signed contract with a defined scope, schedule, and acceptance criteria.

Month 7: Design finalization and pre-construction

After contract award, the selected contractor produces the detailed design: device locations, cable routes, panel placements, network configuration, and integration plans. This is also when equipment is ordered.

Island logistics matter here. Lead times for equipment shipped to Puerto Rico are longer and less predictable than mainland estimates suggest. A contractor with local warehousing and established supplier relationships reduces that risk. Build a delivery buffer into the schedule rather than assuming best-case shipping.

Pre-construction also covers permits, coordination with the institution’s IT team on network changes, and agreement on work hours. For schools, that typically means after hours, weekends, and breaks.

Output of Month 7: Approved drawings, ordered equipment with confirmed delivery windows, and a site-by-site installation schedule.

Months 8 and 9: Installation

Installation on an active campus is scheduled around people, not around the contractor.

For K-12, the summer break in June and July is the most valuable window for disruptive work such as cabling and door hardware. December break and Semana Santa offer shorter windows for smaller phases. Universities often have more flexibility in academic buildings during intersession but tighter constraints in residence halls.

Hurricane season, June through November, overlaps with the summer install window. Plan for it: exterior work should have weather contingencies, equipment should be stored securely on delivery, and the schedule should tolerate a lost week without pushing go-live into the start of classes.

Work is typically sequenced as: network and power infrastructure first, then cabling and mounting, then devices, then head-end equipment and software.

Output of Month 9: Installed and powered devices across the phase-one sites, ready for commissioning.

Month 10: Commissioning, testing, and training

Commissioning verifies that every device does what the specification said it would. Each camera is checked for field of view and night performance. Each door is tested for lock, unlock, schedule, and alarm behavior. Integrations are tested end to end. Backup power is tested by actually cutting power, not by reading a spec sheet.

Training happens in parallel and should be role-based. Front office staff need visitor management. Security personnel need live monitoring and incident review. IT needs system administration and user management. Leadership needs to know what reports exist and how to request footage.

Output of Month 10: A signed acceptance document per site and trained staff in each role.

Month 11: Go-live and operating procedures

Technology goes live when the institution is ready to operate it, not when the last device is powered on.

This month closes the gap between system and policy:

• Who responds to a door-forced alarm at 2 a.m., and how are they notified?
• Who approves and issues credentials, and how quickly are they revoked when someone leaves?
• How long is video retained, who can request it, and how is that request documented?
• What is the procedure when a device goes offline?

These decisions belong to the institution, not the contractor, but a good contractor will bring templates and examples from similar campuses.

Output of Month 11: Written operating procedures and a live system with defined ownership.

Month 12: Review and long-term support

The final month is a structured look back and a plan forward.

Review what the system has recorded and resolved. Compare it against the Month 1 problem statement. Identify coverage gaps, false alarm patterns, and any devices that need adjustment.

Then settle the support model. Security systems are not install-and-forget. Firmware updates, camera cleaning in coastal environments, battery replacement, and software licensing all recur. A maintenance agreement with defined response times is usually less expensive than reactive repairs, and it keeps the institution from becoming the system’s de facto integrator.

Output of Month 12: A phase-two plan, if applicable, and a signed support agreement.

How the timeline shifts by institution type

Stage	Public K-12 district	Charter network	University
Decision group	Larger; board involvement	Small and fast	Cross-departmental
Site assessment	Many sites; longer	Fewer sites; faster	Varied building types
Funding	Fiscal year and federal cycles	Grants and operating budget	Capital planning cycles
Procurement	2 to 3 months, formal	4 to 6 weeks	1 to 3 months, varies
Installation window	Summer break critical	Summer plus flexibility	Intersession; residence hall limits
Realistic total	11 to 14 months	8 to 10 months	10 to 13 months

Frequently asked questions

Can the timeline be compressed?

Yes, but only by starting earlier, not by skipping steps. Institutions that begin planning in the fall for a summer installation are the ones that go live before the next school year. Starting in spring for a summer install almost always slips into the following year.

What is the most common cause of delay?

Network and power readiness. Cameras and door controllers are only as reliable as the infrastructure behind them, and that infrastructure is frequently older than anyone realizes until the assessment.

Should we replace everything or build on what we have?

The assessment answers this. Reusing cabling, door hardware, or serviceable cameras can reduce cost significantly. Reusing unsupported software or failing switches simply relocates the problem.

Does one contractor need to handle network, electrical, and security?

Not necessarily, but coordinating three contractors adds time and creates handoff risk. Where a single firm can take responsibility for the infrastructure and the security systems together, the schedule is easier to hold and accountability is clearer.

How does hurricane season affect planning?

It compresses the safe window for exterior work and increases shipping uncertainty. It also raises the importance of backup power and equipment hardening. Plan for it in Month 3, not Month 8.

About Bonneville Group

Bonneville Group has served Puerto Rico and the Caribbean for more than 40 years as a telecom, electrical, and IT contractor. We work with schools, campuses, and public institutions to plan and deliver security technology projects with the network and power infrastructure to support them, and we stay involved after go-live through structured maintenance and managed IT services.

If your institution is at Month 1 and wants a realistic picture of what the next year looks like, we are glad to walk through it with you.