Background
The Strata Reserve Planning (SRP) Depreciation Portal is a comprehensive platform built for a British Columbia property management company specializing in strata reserve fund planning and depreciation reporting. The goal was to replace fragmented, manual processes with a centralized digital workflow covering inspections, appointments, surveys, and client documentation.
The platform serves four distinct user roles — Admin, Client, Inspector, and Assistant — each with tailored dashboards, permissions, and workflows. Given the sensitivity of the financial and property data involved, the system was designed from the ground up as a secure internal business tool rather than a public-facing application.
The Challenge
Several interconnected challenges shaped the direction of the project:
Domain-Specific Filtering Logic — Rather than hard-coding business rules that would quickly become outdated, a flexible question CRUD system was built with configurable settings, empowering the company to tailor survey questions and document filtering based on their own domain expertise.
Legacy System Integration — The company had an established Dropbox workflow for storing client documents. Rather than forcing a migration, the Dropbox API was integrated directly into the platform, enabling seamless upload, preview, download, and archival. Documents were organized by strata ID, and upon survey completion, automatically moved to a designated "completed" folder alongside the file ID — preserving compliance records while keeping active workflows clean.
Multi-Role Complexity — Four user roles with overlapping but distinct permissions needed to coexist within a single platform, each requiring its own views, route protections, and data access patterns.
Security & Compliance — Strict security measures were required to handle sensitive client data, including Canadian data residency compliance, role-based access control, and restricted account creation tied to verified business onboarding.
Research & Discovery
The project began with detailed user personas representing each primary user type, capturing demographics, daily workflows, and the specific value the platform would deliver. These informed the creation of user flow diagrams for all four roles, mapping every interaction from login through to task completion — establishing clear navigation structures, permission boundaries, and feature priorities early on.