When you run five projects, the question is not what is available but where.
Roll up, then drill down
Start with total, active and inactive projects, then open each project for units and bookings.
Compare projects
Available, booked and sold-out counts per project show which sells fast and which needs attention.
Keep project data tidy
Name projects clearly, set city and status, and archive finished ones.
Why one dashboard for many projects
Developers with several projects often manage each one in a separate sheet or system. Leadership then spends hours assembling a combined picture, and comparisons between projects are slow and unreliable. A single dashboard showing all projects, with the ability to drill into each, saves time and improves decisions.
It also helps sales teams that sell across projects, because they can see availability everywhere in one place.
What to show at the top level
At the business level, show total units, available, held, booked and sold, along with booking value and collections. A simple chart of bookings over time and a breakdown by project give leadership a quick sense of momentum.
Keep the top level uncluttered. A handful of meaningful numbers is more useful than dozens of widgets.
Drilling into a project
Clicking a project should show its own availability, unit mix, bookings, collections and construction status. From there, users should be able to open individual units or bookings. This path from overview to detail makes the dashboard a working tool rather than a static report.
Filters for phase, unit type and status help focus on the question at hand.
Comparing projects fairly
Compare projects using rates and shares rather than raw counts: the share of inventory sold, visits per booking, average days from enquiry to booking. Raw counts favour larger projects and can hide strong performance in smaller ones.
Consider project age. A project launched last month cannot be compared directly with one selling for two years.
Collections across projects
Show collections and overdue amounts by project. A project with strong bookings but weak collections needs a different response from one with slow bookings. Seeing both together helps leadership allocate attention.
Link these numbers to the remaining-payments view so action can follow immediately.
Keeping project data tidy
A combined dashboard is only as good as the data behind it. Use consistent unit types, statuses and naming across projects. Inconsistent definitions make comparisons meaningless.
Assign an inventory owner for each project and reconcile monthly, so that every project contributes accurate numbers.
Access by role
Not everyone needs every project. Give project teams their own views and leadership the combined view. Partners may see only the projects they sell. Role-based access keeps the dashboard relevant and protects sensitive information.
Make sure restricted users cannot reach other projects’ data through direct links.
Using the dashboard in reviews
Open the dashboard at the start of weekly or monthly reviews. Ask what changed since the last review, which project needs attention and what actions are planned. Decisions made from shared data are faster and less contentious.
Export reports when needed for banks, investors or board meetings, but keep the live dashboard as the source of truth.
A worked example
In a monthly review, the dashboard shows that one project has sold most of its inventory but has high overdue collections, while another has strong collections but slow bookings. Leadership assigns extra collections support to the first and approves a marketing push for the second.
Both decisions take minutes because the numbers are already on screen and agreed by everyone in the room.
Common mistakes
Common mistakes include different status definitions in each project, dashboards built from manual exports and comparing raw counts across projects of different size and age. Each makes the combined view misleading.
Another mistake is building a dashboard nobody uses. Bring it into regular reviews from the start.
Questions teams often ask
Should each project have its own dashboard? Yes, alongside the combined view. Project teams need detail; leadership needs the overview.
How often is data updated? Ideally live, because the dashboard reads directly from inventory, bookings and payments.
In short
Use one dashboard for all projects with drill-down to each, compare with rates rather than counts, show bookings and collections together, keep definitions consistent, control access by role and use the dashboard in every review.
A dashboard checklist
Top level: total, available, held, booked and sold units, booking value, collections and overdue amounts, with a bookings trend. Project level: availability by phase and type, bookings, collections and construction status, with links to units and bookings.
Data: consistent statuses and unit types, an inventory owner per project and monthly reconciliation. Access: project views for teams, the combined view for leadership and restricted views for partners. Use: opened at the start of every weekly and monthly review. When all of these are in place, the dashboard becomes the place where decisions are made.
Start with the top-level view, add project drill-downs next and refine the numbers after the first few reviews based on the questions leadership actually asks.
Keep it simple, keep it accurate and keep it in use.
One last tip
Review the dashboard layout every quarter.
Can I filter projects?
Yes, by status and city, with list and grid views.