Complete dissertation appendix
This complete applied case preserves the project scenario, governance, assessment, solution analysis, implementation guidance, safeguards, measures, risks, sustainability provisions, and decision checklist developed in the dissertation.
Project Context: Older 100-apartment building constructed during the 1970s; internet modernization treated as a coordinated initiative encompassing infrastructure, affordability, adoption, support, and continuous improvement.
This report applies the dissertation’s digital divide conceptual model to the modernization of internet services in a 100-unit apartment building constructed during the 1970s. It is intended for property owners, housing authorities, project managers, technology consultants, internet service providers, community organizations, and funders responsible for planning or delivering the upgrade.
The conceptual model treats the digital divide as an interconnected system rather than a single connectivity problem. Infrastructure must align with affordability, devices, resident skills, trust, institutional support, service quality, and long-term sustainability. It therefore guides practitioners from initial diagnosis through implementation, measurement, evaluation, and continued improvement.
The proposed remodel should not be managed solely as a cabling, fiber, or Wi-Fi installation. The project should be managed as a digital inclusion initiative supported by a building technology upgrade.
The project will be successful only when residents can:
Obtain reliable internet service in their apartments.
Afford the service without creating an excessive household burden.
Use suitable devices to connect.
Understand how to enroll, connect, and resolve routine problems.
Trust the provider, property management, and data-handling practices.
Use the connection for education, employment, telehealth, government services, communication, and other meaningful activities.
The recommended approach is a bundled solution consisting of:
A professional assessment of the building’s pathways, wiring, backhaul, wireless conditions, and electrical capacity.
A building backbone capable of supporting current and future service levels.
A service design that reaches every apartment rather than only common spaces.
Affordable resident service options with clear pricing and no hidden requirements.
Resident communication, multilingual onboarding, digital navigation, and technical support.
Performance, adoption, affordability, and resident-outcome monitoring.
A continuous improvement process that addresses gaps after deployment.
A construction-complete project is not necessarily a successful project. Success occurs when the technical installation produces sustained resident participation and measurable improvements in daily life.
The purpose of the project is to provide every household in the building with a practical pathway to reliable, affordable, secure, and usable internet service.
The remodel should address five connected needs:
Availability. Can the service physically reach every apartment?
Performance. Does the service support education, remote work, telehealth, streaming, communication, and multiple household users?
Affordability. Can residents maintain the service after introductory prices, grants, or subsidies end?
Adoption. Do residents understand the service and have the equipment, confidence, and support required to use it?
Sustainability. Can the property, provider, and community partners maintain the infrastructure and resident-support system over time?
The primary goal is not merely to make 100 apartments serviceable. It is to increase the number of households that consistently use reliable broadband for meaningful purposes.
Increased household broadband adoption.
Reduced dependence on smartphones as the only household connection.
Lower internet costs relative to household income.
Improved service reliability, speed, and in-unit coverage.
Increased participation in online education and workforce training.
Improved access to telehealth and public services.
Increased resident confidence in using digital services.
Fewer disruptions caused by installation, billing, enrollment, or maintenance problems.
A support model that remains available after construction is complete.
Infrastructure that can be expanded or upgraded without another major building remodel.
A small project steering group should oversee the project from assessment through post-installation review.
| Role | Primary responsibility |
|---|---|
| Project sponsor | Approves scope, budget, major agreements, and project priorities. |
| Project manager | Coordinates schedule, stakeholders, risks, vendors, reporting, and decisions. |
| Property manager | Coordinates building access, resident notices, unit scheduling, and daily operations. |
| Technical lead | Reviews architecture, pathways, equipment, testing, cybersecurity, and performance. |
| Resident representative group | Reviews resident needs, communication, disruption concerns, pricing, and support. |
| ISP or network operator | Provides backhaul, service plans, network operations, and escalation support. |
| Contractor | Installs and certifies cabling, conduit, equipment, and unit connections. |
| Community partner | Provides outreach, enrollment assistance, digital navigation, or device support. |
| Finance or funding representative | Tracks capital expenses, operating expenses, grants, and long-term commitments. |
| Compliance representative | Reviews permit, accessibility, housing requirements, privacy, and contractual safeguards. |
The steering group should meet regularly during design and construction and at least quarterly during the first year of operation.
Residents are the primary beneficiaries but may hold the least formal authority within the project. The governance structure must correct this imbalance by giving residents meaningful opportunities to influence:
Service affordability.
Installation scheduling.
In-unit access procedures.
Privacy expectations.
Preferred communication methods.
Language and accessibility requirements.
Support hours and channels.
Common-area access.
Acceptable-use and network-management policies.
Resident engagement should occur before the technical design is finalized, not after contracts have already been signed.
The MDU modernization project depends on coordinated participation across resident, property, technical, regulatory, community, and funding interests. The stakeholder structure should be treated as part of the project design because the technical installation, resident adoption, affordability, privacy, accessibility, and long-term sustainability are controlled by different participants.
The following stakeholders are identified in the project scenario, governance structure, assessment activities, solution bundle, implementation plan, risk controls, and continuous-improvement process. Core governance stakeholders participate throughout the project; specialist and support stakeholders are engaged when their particular responsibilities are triggered by project conditions.
| Stakeholder | Project-specific role |
|---|---|
| Residents/resident households | Primary beneficiaries and end users. Define service expectations, affordability needs, installation constraints, privacy expectations, preferred communication, accessibility and language needs, support requirements, and whether the completed service is usable for education, employment, telehealth, public services, and communication. |
| Resident representative group | Provides structured resident voice in governance; reviews need, pricing, disruption concerns, communication, support, privacy, and implementation experience before and after deployment. |
| Property owner | Authorizes property-level improvements, grants or negotiates access to building spaces and pathways, establishes expectations for infrastructure ownership, and supports long-term operational and upgrade decisions. |
| Project sponsor | Approves project scope, budget, major agreements, priorities, and key decision gates; provides executive accountability for the initiative. |
| Property management company/property manager | Coordinates building access, resident notices, apartment-entry scheduling, construction logistics, daily property operations, and communication between residents and the project team. |
| Maintenance personnel/building operations staff | Provide knowledge of existing building systems and pathways, support access to utility and telecommunications spaces, and participate in ongoing maintenance coordination after installation. |
| Project manager | Coordinates schedule, stakeholder engagement, vendors, risks, reporting, decisions, phase gates, and transition from construction into operational review. |
| Technical lead/technology consultant | Assesses building pathways and network conditions; reviews architecture, equipment, coverage, capacity, testing, cybersecurity, scalability, maintainability, and technical performance. |
| Internet service provider/network operator | Provides or operates backhaul and resident services, defines service plans and pricing, supports activation and escalation, meets performance requirements, and participates in ownership, maintenance, and vendor transition arrangements. |
| Wiring/cabling/construction contractor | Installs and certifies conduit, cabling, equipment, pathways, and unit connections; documents as-built conditions and corrects construction or quality deficiencies. |
| Permitting authorities/building-code officials | Review and authorize work involving permits, fire-stopping, electrical and building-code requirements, access conditions, and other regulatory construction requirements. |
| Housing authority/housing agency | Provides housing-policy and compliance perspective, supports resident protections and applicable requirements, and may participate in ownership, funding, oversight, or project sponsorship depending on the property. |
| Community organizations/community partners/digital navigators | Provide trusted outreach, multilingual communication, enrollment assistance, digital navigation, device support, practical training, and referrals that help residents adopt and sustain service. |
| Funders/finance or funding representative | Track capital and operating costs, grants, reserves, recurring commitments, affordability support, and the long-term financial sustainability of infrastructure and resident-support services. |
| Compliance representative | Reviews permits, accessibility, housing requirements, privacy, contractual safeguards, resident protections, and procurement requirements that affect equitable participation. |
| Device-assistance/refurbishment partners | Support residents who lack suitable devices through referral, loan, refurbishment, purchase assistance, or other device-access pathways connected to the project. |
| Legal reviewer/counsel, as required | Reviews provider agreements, right-of-entry terms, exclusivity, infrastructure ownership, open-access provisions, privacy obligations, and vendor-exit terms when legal review is required. |
| Environmental/hazardous-material reviewer, as required | Evaluates asbestos, lead, or other hazardous-material conditions before intrusive work and advises on safe construction constraints and required controls. |
| Independent quality-assurance/testing personnel, where appropriate | Independently verify installation quality, pathway certification, in-unit performance, coverage, and compliance with project acceptance requirements before full closeout. |
The project steering group should use this role definition to assign accountability before procurement and construction begin. When one organization or individual performs multiple functions, the project charter should still clearly distinguish responsibilities so that resident support, compliance, technical quality, affordability, and long-term operations are not left unassigned.
The assessment should determine:
Where provider services enter the property.
Available backhaul capacity.
Condition of existing copper, coaxial, telephone, and Ethernet cabling.
Availability and condition of vertical risers and horizontal pathways.
Whether pathways extend to every apartment.
Available conduit capacity.
Location and security of telecommunications rooms.
Rooftop and exterior mounting options.
Electrical capacity, grounding, cooling, and backup power.
Fire-stopping and building-code requirements.
Presence of asbestos, lead, or other hazardous material restrictions.
Wall, floor, and construction materials that may block wireless signals.
Accessibility requirements for equipment and resident-facing controls.
Areas where new construction could disrupt residents.
Ownership of existing cabling and equipment.
Current provider agreements and right-of-entry restrictions.
The assessment should produce a current building diagram, photographs, cable-test results, riser maps, equipment inventory, and a list of inaccessible or high-risk areas.
A privacy-protective resident survey should determine:
Current internet provider and service type.
Monthly service cost.
Satisfaction with reliability and speed.
Whether the internet service is regularly disconnected because of cost.
Dependence on mobile-only service or public Wi-Fi.
Number and type of devices in the household.
Education, employment, telehealth, and public-service needs.
Preferred language.
Accessibility requirements.
Need for enrollment or technical assistance.
Concerns regarding privacy, billing, installation, or property management.
Preferred communication and training formats.
Residents should be able to respond anonymously when possible. Participation in the survey should not be tied to lease enforcement or eligibility decisions.
The project team should examine:
Providers currently serving the property or surrounding area.
Available technologies and advertised service levels.
Wholesale, bulk, retail, and low-cost service options.
Whether multiple providers can use shared infrastructure.
Minimum contract terms and price-escalation provisions.
Installation, activation, equipment, and termination fees.
Data caps and network-management practices.
Customer-support expectations.
Provider performance in comparable properties.
Options for open-access or neutral-host infrastructure.
Ownership of improvements at the end of the contract.
The project team should document the difference between the visible problem and its underlying causes.
| Barrier area | Possible conditions in the MDU | Required response |
|---|---|---|
| Infrastructure | Aging coaxial or copper, inadequate risers, missing pathways, and poor wireless penetration. | Modernize backbone and distribution pathways. |
| Affordability | High monthly rates, activation fees, equipment rental, promotional pricing that later increases. | Negotiate sustainable low-cost tiers and transparent pricing. |
| Provider market | Exclusive access agreement or limited competition. | Consider open-access, neutral-host, or competitive procurement. |
| Devices | Households lack suitable computers or rely on outdated equipment. | Establish device referral, loan, refurbishment, or purchase assistance. |
| Digital skills | Residents need help with accounts, passwords, applications, or online safety. | Provide digital navigation and practical training. |
| Trust | Residents fear hidden charges, surveillance, lease consequences, or misuse of personal information. | Use transparent policies and trusted community messengers. |
| Language | Notices and enrollment materials are not understandable to all residents. | Provide translated, plain-language communication and interpretation. |
| Accessibility | Portals, equipment, training, or support channels are not accessible. | Include disability access in procurement and testing. |
| Institutional | No owner policy for digital inclusion, support, or future upgrades. | Adopt clear governance and service standards. |
| Construction | Hazardous materials, limited pathways, noise, dust, or unit-access concerns. | Develop a resident-protective construction and relocation plan. |
| Sustainability | Grant supports construction but not recurring operations. | Create a multiyear operating and replacement plan. |
| Support | Responsibility is unclear when a resident cannot connect. | Establish a documented service and escalation pathway. |
A barrier should not be marked resolved simply because the corresponding equipment has been installed. The project team must verify that the affected resident can use and benefit from the solution.
Does the solution address the actual root cause? Installing common-area Wi-Fi does not resolve a problem caused by the absence of reliable in-unit service. Providing fiber to the building does not resolve unaffordable monthly rates. Offering a discount does not resolve the lack of devices or resident distrust.
Can the solution be implemented within the available budget, building conditions, schedule, permits, staffing capacity, and resident-disruption limits?
Will the architecture provide sufficient coverage, capacity, reliability, security, scalability, and maintainability for this particular building?
Does the solution protect residents from avoidable risks of privacy breaches, inaccessible service, hidden costs, displacement, unsafe construction, vendor lock-in, or service loss after a grant ends?
Fiber is extended from the building entry point through the building and into each unit.
Strong long-term capacity.
High reliability.
Reduced dependence on aging internal wiring.
Easier support for future speed increases.
Higher construction cost.
Potentially significant work inside units.
Additional pathway and fire-stopping requirements.
Greater disruption if the building lacks usable conduit.
Fiber backhaul is delivered to the property, and existing or new internal cabling is used to reach apartments.
Lower cost than full fiber-to-unit construction in some buildings.
May reuse serviceable coaxial or structured cabling.
Can be completed faster where pathways are limited.
Performance depends on existing cable condition.
Additional electronics may be required.
Long-term upgrade capacity may be lower than fiber to each unit.
A centrally managed network provides wireless access in units and common spaces.
Centralized management.
Potential for simple resident onboarding.
Useful where new in-unit cabling is difficult.
Older construction materials may block signals.
Poor design may create coverage gaps or congestion.
Privacy and network-separation controls must be carefully implemented.
Wireless should not be selected without a professional site survey.
The property installs shared pathways or network infrastructure for use by multiple providers.
Reduces long-term dependence on one provider.
May improve service choice and pricing.
Makes future provider changes easier.
More complicated governance and contracting.
Requires clear ownership, maintenance, and access rules.
Local providers must be willing to participate.
Temporary wireless service is used while permanent pathways are designed and constructed.
Can provide faster short-term relief.
Useful when construction approvals are delayed.
May have capacity, line-of-sight, weather, or reliability constraints.
Should not become an indefinite substitute for the permanent solution.
The final architecture should be selected after the building and resident assessments. For planning purposes, the preferred approach is a bundled solution with the following elements:
High-capacity fiber backhaul to the building.
Secure, properly powered telecommunications rooms.
Documented and labeled risers, conduits, pathways, and equipment.
Fiber, certified structured cabling, or validated coaxial technology to every unit.
Professionally designed common-area Wi-Fi.
Capacity planning for peak evening use and multiple devices per household.
Separate networks for residents, building operations, guests, and management systems.
Backup-power planning for essential network components.
A technology replacement and upgrade schedule.
At least one clearly defined low-cost service tier.
No unexpected activation, installation, or equipment charges.
Plain-language disclosure of total monthly cost.
Protection against rapid price increases following introductory periods.
Enrollment support for qualifying programs where available.
Procedures for residents experiencing short-term financial hardship.
Clear rules for bulk-service charges if the internet is included in rent or fees.
Multilingual project notices and enrollment materials.
In-person and remote enrollment assistance.
Installation appointments that accommodate work, school, disability, and caregiving schedules.
Digital navigator or community-support referrals.
Device-assistance partnerships.
Basic online safety, password, telehealth, education, and employment workshops.
A clear help desk with published response and escalation expectations.
Resident orientation at move-in after the initial project is complete.
Resident privacy statement.
Clear limits on the information shared between the provider and property management.
No use of internet service data for unrelated lease enforcement.
Accessibility requirements in contracts.
Service-level and performance requirements.
Vendor-exit and transition provisions.
Ownership documentation for all installed infrastructure.
Annual review of pricing, adoption, service quality, and resident satisfaction.
Appoint project sponsor and project manager.
Establish the steering group.
Define the population and project boundaries.
Confirm funding limitations and required completion dates.
Review existing provider and property agreements.
Establish preliminary success measures.
Decision gate: Proceed only when the team agrees on the problem being solved and recognizes that the project includes adoption, affordability, and support, not construction alone.
Conduct building technology assessment.
Survey residents.
Hold resident listening sessions.
Review provider market and pricing.
Identify permits, hazardous materials, and construction restrictions.
Establish baseline adoption and performance data.
Decision gate: Proceed only when the team has enough information to distinguish infrastructure barriers from affordability, device, skill, trust, and governance barriers.
Develop technical alternatives.
Calculate capital and recurring costs.
Evaluate service and ownership models.
Develop procurement requirements.
Include resident support, accessibility, privacy, and affordability in the solicitation.
Score proposals using causal, feasibility, technology, and safeguard fit.
Decision gate: Do not award the project solely on the lowest construction cost. The selected proposal must include an acceptable operating model, resident pricing, support structure, and sustainability plan.
Verify speed, latency, coverage, and reliability.
Test enrollment and installation procedures.
Gather resident feedback.
Confirm accessibility.
Test help desk and escalation processes.
Correct design problems before building-wide installation.
Decision gate: Proceed to full deployment only after the pilot meets minimum technical and resident-experience requirements.
Publish the construction schedule.
Provide advance multilingual notices.
Coordinate unit entry and resident accommodations.
Protect resident property and privacy.
Install, label, photograph, and document infrastructure.
Test every pathway and serviceable apartment.
Conduct independent quality assurance where appropriate.
Conduct resident enrollment events.
Assist with account creation and equipment setup.
Provide device and training referrals.
Complete post-installation testing.
Resolve early service tickets quickly.
Track activation without publicly identifying nonparticipating households.
Review technical performance monthly during the initial launch.
Review adoption and affordability quarterly.
Gather resident satisfaction feedback.
Evaluate whether identified populations are benefiting.
Adjust pricing, outreach, support, or technology when outcomes are not improving.
Outputs are the countable products created by the project.
Completed building technology assessment.
Current telecommunications and riser diagrams.
Resident-needs assessment.
Provider-market analysis.
Approved project charter and scope.
Signed right-of-entry and service agreements.
Issued permits and approvals.
Installed backhaul and building distribution infrastructure.
Number and percentage of units made serviceable.
Number of common-area access points installed.
Number of units tested and certified.
Number of residents contacted through outreach.
Number of residents receiving enrollment assistance.
Number of households enrolled.
Number of devices distributed or referred for assistance.
Number of resident training sessions conducted.
Number and type of support tickets resolved.
Completed privacy, accessibility, support, and escalation procedures.
Completed as-built documentation and maintenance records.
These measures confirm whether the project was delivered. They do not, by themselves, confirm that the digital divide has narrowed.
| Measure | Suggested use |
|---|---|
| Units serviceable | Confirm universal physical reach. |
| Installation success rate | Identify appointment, pathway, or activation failures. |
| In-unit speed | Confirm actual rather than advertised service. |
| Latency and packet loss | Assess suitability for video, telehealth, and remote work. |
| Uptime | Assess reliability. |
| Coverage complaints | Identify wireless dead zones. |
| Peak-period performance | Detect congestion and oversubscription. |
| Mean time to repair | Assess operational support. |
| Repeat trouble tickets | Identify unresolved or systemic problems. |
| Measure | Suggested use |
|---|---|
| Household adoption rate | Determine whether residents are subscribing. |
| Low-cost plan enrollment | Measure use of affordable options. |
| Total monthly household cost | Detect fees and pricing burden. |
| Service disconnections | Identify affordability or billing problems. |
| Mobile-only household rate | Determine whether households have moved beyond smartphone-only access. |
| Enrollment abandonment | Identify confusing processes or documentation barriers. |
| Device availability | Determine whether connectivity can be meaningfully used. |
Ability to complete schoolwork from home.
Participation in online courses and tutoring.
Ability to work remotely or complete job applications.
Access to telehealth and patient portals.
Access to government benefits and public services.
Resident confidence in managing accounts and passwords.
Reduced travel to obtain public internet access.
Satisfaction with cost, reliability, support, and privacy.
Increased use of online small-business or income-generating tools.
Reduced reports of missed activities caused by unreliable connectivity.
Outcome data should be collected proportionately and with privacy protections. The project does not need to collect sensitive household information that is unrelated to improving the service.
| Risk | Likely effect | Mitigation |
|---|---|---|
| Hidden construction conditions | Cost and schedule increases. | Conduct intrusive surveys where permitted and include contingency funds. |
| Hazardous materials | Work stoppage or health risk. | Complete environmental review before opening walls. |
| Exclusive provider agreement | Reduced competition and resident choice. | Obtain legal review and negotiate open-access provisions. |
| Poor in-unit wireless coverage | Resident dissatisfaction. | Complete predictive design and physical site testing. |
| Resident distrust | Low enrollment. | Use resident representatives and trusted community partners. |
| High recurring price | Low adoption or disconnection. | Negotiate long-term affordability protections. |
| Contractor quality problems | Service failures and expensive rework. | Require certification, documentation, testing, and retainage. |
| Vendor lock-in | High future costs. | Define infrastructure ownership and exit requirements. |
| Inadequate support | Repeated outages and resident frustration. | Establish help desk service levels and escalation routes. |
| Low device ownership | Limited benefit despite connectivity. | Partner with device programs and refurbishment providers. |
| Language or accessibility gaps | Exclusion of affected residents. | Require translated and accessible communications and services. |
| Grant expiration | Loss of service or support. | Fund operating costs and reserves before deployment. |
| Privacy concerns | Low trust and possible harm. | Limit data collection and separate provider and property-management data. |
| Resident displacement during work | Safety and housing disruption. | Phase construction and provide accommodations where necessary. |
| Oversubscription | Poor peak-hour performance. | Use realistic capacity planning and monitoring thresholds. |
Communication should be frequent, consistent, plain-language, and available through multiple channels.
Residents should receive:
An initial explanation of the project and its purpose.
A description of what will and will not change.
Information about pricing and service choices.
Notice of any required apartment access.
Construction and installation schedules.
Contact details for questions and accommodations.
Privacy information.
Instructions for enrollment, equipment, and support.
Progress updates when schedules change.
Final instructions after activation.
Communication should be delivered through printed notices, email, text messages, resident portals, community meetings, and direct outreach where appropriate. Materials should be translated into the primary languages used in the building and made accessible to residents with disabilities.
During the first six months, review:
Outages and degraded service.
Support-ticket volume.
Installation failures.
Coverage complaints.
Peak-hour performance.
Repeated equipment issues.
Resident communications and unresolved complaints.
Household adoption.
Low-cost plan participation.
Disconnections and enrollment abandonment.
Device and training needs.
Resident satisfaction.
Differences in participation by building area or household characteristics, where collection is appropriate and privacy-protective.
Whether students, seniors, people with disabilities, multilingual households, and mobile-only households are benefiting.
Determine whether:
Pricing remains affordable.
Provider performance meets contractual commitments.
Infrastructure needs capacity expansion.
Resident-support partnerships remain active.
Equipment replacement reserves are adequate.
New technology or provider options should be considered.
Policies and agreements require revision.
Project outcomes justify continuation, expansion, or redesign.
When outcomes remain unchanged, the project team should revisit the barrier analysis rather than assume residents are unwilling to participate.
Low adoption may indicate cost, distrust, poor outreach, or difficult enrollment.
Low telehealth use may indicate privacy concerns, limited skills, or inaccessible platforms.
Continued student connectivity problems may indicate device shortages or poor in-unit coverage.
High support volume may indicate inadequate installation, confusing equipment, or weak resident onboarding.
Strong initial adoption followed by disconnection may indicate unsustainable pricing.
Before declaring the project complete, the project manager should be able to answer yes to the following questions:
Has the project identified the specific connectivity and participation problems experienced by residents?
Have infrastructure barriers been separated from affordability, device, skill, language, trust, and support barriers?
Has baseline information been collected?
Have residents influenced the design?
Are property management providers, contractors, community partners, and funders clear about their responsibilities?
Have power imbalances been considered?
Can every apartment receive usable service?
Has the design been tested in representative units?
Does the design support future growth?
Are cybersecurity, privacy, and accessibility requirements included?
Is there a sustainable, affordable service option?
Are total costs clearly disclosed?
Is support available for enrollment, devices, and digital skills?
Can residents obtain help after the construction team leaves?
Are permits, pathways, environmental conditions, and unit-access procedures resolved?
Are quality testing and documentation required?
Is there a clear escalation process?
Are outputs being tracked?
Are resident outcomes being measured?
Is performance monitored during peak use?
Is the team prepared to modify the solution when results are not improving?
Is long-term operation funded?
Is the responsibility for maintenance clear?
Is infrastructure ownership documented?
Are replacement, expansion, and vendor-transition plans in place?
The project should proceed as a coordinated initiative across property, technology, affordability, and resident support. The selected technical design should be based on a detailed site assessment rather than a predetermined preference for fiber, coaxial, or managed Wi-Fi.
The strongest implementation will likely combine a modern building backbone, reliable in-unit distribution, competitive or protected pricing, resident-centered enrollment, device and digital-skills support, clear privacy safeguards, and ongoing performance management.
The project should not be closed when the last cable is installed. It should move into an operational improvement phase and remain there until evidence shows that residents are connecting, remaining connected, and using the service to improve educational, employment, health, civic, and personal opportunities.
Under this approach, the MDU remodel becomes more than a building improvement. It becomes a sustainable digital inclusion program in which infrastructure creates access, affordability enables adoption, support enables participation, and continuous evaluation protects the long-term value of the investment.
Figure AC81 Multiple Dwelling Unit