Start with a portfolio map and a practical objective
A multi-site project needs a reason for coordination. The objective may be reducing repeated service uncertainty, planning a capital program, aligning lighting quality across locations or addressing a group of known failures. State that objective before collecting fixture counts, because it determines which information is most useful and how the work should be prioritized.
Create a property list with addresses, facility types, operating hours and the main concerns at each location. Identify which sites need immediate service and which need assessment before a scope can be defined. Include the decision-maker and access contact for every property; they may be different people. For a Mississauga portfolio of offices, industrial units and plazas, this first overview can reveal both common opportunities and important differences. A coherent program begins with those distinctions rather than a promise to install the same package everywhere.
Collect comparable information without flattening site differences
A consistent survey structure makes properties easier to compare. Record fixture families, approximate quantities where known, mounting conditions, operating patterns, controls and maintenance history. Use the same definitions across sites so one property’s reported fixture count is not confused with another property’s lamp count or replacement-component count. Uncertain information should be marked as uncertain until verified.
At the same time, preserve details that change the work: warehouse racking, restricted parking, tenant access, ceiling conditions and exterior elevations. These are not minor exceptions to a standard price; they can influence equipment, labour and phasing. Photographs should be connected to an address and recognizable area. A folder full of similar fixtures without location references is difficult to use. The goal is enough consistency to support portfolio decisions and enough detail to prepare an appropriate scope for each building.
Separate shared standards from site-specific choices
A portfolio standard can define useful expectations for documentation, preferred equipment families, control behaviour or appearance. It should also explain when a different solution is justified. A low-ceiling garage and a high-bay distribution facility cannot be treated as the same application simply because both currently use aging fixtures. Distribution, environment, mounting and access must remain part of selection.
Where repeatable equipment is appropriate, consider how future replacement and product changes will be handled. Keep confirmed model information and compatibility details rather than relying on a general label such as standard LED. Control standards deserve the same care: a common naming convention may be useful across every site, while identical schedules may be unsuitable. The standard should make later work clearer and more manageable, not create an obstacle when a property’s actual operating conditions call for a different approach.
Build priorities that owners can understand
Portfolio decisions often compete with other building needs. A useful lighting plan explains why each item is proposed: a current defect, recurring maintenance problem, poor light distribution, tenant requirement or planned energy improvement. Separate these reasons rather than combining them into one large replacement recommendation. The owner should be able to see what each phase addresses and what remains afterward.
For financial comparisons, use stated operating-hour and equipment assumptions. A site with extended warehouse shifts differs from a small office occupied only on weekdays. Access requirements and the condition of retained equipment can also affect the comparison. Where incentives are being considered, review the current program pathways for the actual measures and properties; do not assume one site’s eligibility applies to every location. A clear priority plan remains useful even if budgets, tenant timing or funding expectations change.
Coordinate scheduling through named property contacts
A central project contact can approve a program, but individual buildings still need access and operational coordination. Identify who can admit personnel, arrange tenant communication, move obstructions and authorize site-specific changes. Record delivery windows, shift patterns, parking restrictions and any room bookings that affect the work. These details should be confirmed before a location enters the installation schedule.
Phasing can be organized by property, building area or type of work, depending on the practical constraints. Avoid assuming that the fastest geographical route is the best operating sequence. A warehouse shutdown window may matter more than proximity to the next address. For property management programs, a short site-readiness checklist can help the responsible team confirm arrangements without creating unnecessary administration. The exact responsibilities should be visible in the agreed scope so each building knows what must happen before work begins.
Use a representative first phase where uncertainty is high
A first phase can test assumptions about equipment performance, access, controls or occupant acceptance before a wider rollout. Choose a location that represents the important challenges rather than only the easiest building. Define the questions to be answered: whether a fixture distribution suits the task, whether a control sequence works during quiet periods or whether an access plan fits normal operations.
Document what is learned and decide whether it applies to other sites. A successful office installation does not establish suitability for a warehouse or exterior parking area. Even similar buildings may have different drivers, circuits or layouts. A phased approach is most useful when it informs specific decisions, with clear approval points for subsequent work. It should not become an open-ended demonstration that leaves the remaining portfolio without a defined path or creates assumptions that have never been checked at the other properties.
Keep closeout information connected to each address
A coordinated program should leave site-specific records that remain useful after the central project ends. Depending on the agreed scope, these may include equipment details, zone names, control settings, completed areas and follow-up items. Keep each property identifiable within the portfolio record so a future service request can locate the relevant information quickly.
Record approved differences from the original standard and the reason for them. If a product changes during a later phase, make the distinction visible rather than assuming all properties received identical equipment. Where networked controls are involved, clarify accounts and responsibilities for each site and for any central administration. The exact handover should be specified in the proposal. Good records support future maintenance and budgeting; they should not be described as a broad compliance certification or a technical report unless that deliverable has actually been included.
Begin with the next useful decision
A portfolio does not need every detail resolved before the first discussion. Provide the property list, current concerns, intended timing and any existing fixture or service records. Explain whether the priority is urgent repairs, a capital plan, consistent lighting quality or control coordination. This makes it possible to identify the next useful step for each site rather than forcing all locations into one stage of the process.
Use a site assessment request for buildings where the scope is unclear, and request lighting service for defined existing problems. Relevant projects may include LED retrofits, maintenance planning or networked controls. The coordinated approach should make decisions easier for the owner while preserving the practical details that determine whether each individual property receives suitable lighting work.
Questions facility managers ask
Does multi-site work require identical fixtures everywhere?
No. Shared standards should support appropriate selection, useful records and manageable maintenance. Different mounting heights, environments, distributions and controls can require different equipment.
Can some sites receive repairs while others receive upgrades?
Yes. A portfolio plan can contain different scopes and stages. Keep immediate repairs, assessment questions and capital improvements distinct so priorities and approvals remain clear.
What should be provided before a portfolio assessment?
Start with addresses, facility types, known concerns, operating hours and responsible contacts. Existing plans, fixture records and service history can then be linked to the relevant property.
Can a first site establish the approach for the others?
It can inform shared decisions when conditions are representative. Each additional site still needs its differences reviewed, particularly equipment compatibility, access, layout and operating requirements.