****❓Problem Statement

The system faces a discrepancy between real-world occupancy (e.g., 90 or 95 out of 100 units occupied) and app-based occupancy (e.g., 80 units, as some residents do not use the app). This gap complicates billing, as the payment model relies on unit counts, and creates challenges for both the service provider and apartment management in understanding true app adoption. Additionally, as more residents join the app over time, tracking their joining date becomes critical to ensure billing reflects actual usage and to provide the society panel with clear data on resident engagement. The goal is to develop a robust system to track, display, and reconcile these datasets while incorporating joining dates for transparency and accuracy.

Current Payment Model

The payment structure operates on a per-unit basis with flexible billing cycles:

• The billing formula follows a simple multiplication: Number of Units × Rate (e.g., 100 units × ₹300/month)
• Multiple payment frequency options exist: monthly, semi-annually, or annually
• The system calculates charges based on the total number of units registered in the society panel

Data Tracking Requirements

The system must track two types of occupancy data:

1. Manually Entered Occupancy:
   • Reflects real-world occupancy (e.g., 90 or 95 out of 100 units occupied).
   • Entered by apartment management via the society panel.
   • Represents the actual number of occupied units, regardless of app usage.
2. App-Based Occupancy:
   • Reflects the number of residents who have registered and been approved via the app (e.g., 80 out of 90 occupied units).
   • Captured automatically through app registrations and society panel approvals.
   • May be lower than real-world occupancy due to non-adoption by some residents.

Key Considerations

1. User Adoption Tracking: You need to track when residents start using your app, as this affects billing and usage statistics.
2. Temporal Data: The joining date of residents becomes critical for:
   • Accurate billing calculations
   • Understanding adoption patterns
   • Providing insights to both your team and society management
3. Reconciliation Need: There's a need to reconcile the manually entered occupancy data with the system-tracked data through app registrations.

✅ Proposed Data Representation Solution

To address these challenges, implementing dual data representation appears to be the most viable solution:

Two-Tiered Data Display