Skip to main content

Dashboard

The Dashboard is the operational starting point for Wamule Development staff. It brings together current totals, alerts, upcoming work, and exceptions from across sales, inventory, applications, collections, and post-sales activity.

The Dashboard helps answer where should attention go next? It does not replace the detailed records that answer what exactly happened and what should we do?

What the Dashboard is for​

Use the Dashboard to:

  • identify new or aging sales work;
  • find overdue follow-ups and upcoming site visits;
  • review reservation and deposit-readiness exceptions;
  • spot application issues, including unavailable preferred lots;
  • monitor lot availability and sales movement;
  • identify due or overdue collections work;
  • review open and blocked post-sales tasks; and
  • open recent activity or related records quickly.

1. Financial and customer-risk alerts​

Review payment discrepancies, missing receipt information, missing proof or references, overdue collections items, and customer commitments due today. These often require immediate verification because they can affect balances, receipts, customer communication, and trust.

2. Lot and reservation conflicts​

Look for reservations nearing expiry, deposit-readiness exceptions, or buyer records connected to unavailable lots. Confirm the lot's core status and active reservation context before communicating availability.

3. Application exceptions​

Review applications awaiting action, missing information, possible duplicate context, and preferred-lot issues. An application alert should lead to a documented human review, not an automatic approval or decline.

4. Sales follow-up and site visits​

Review new leads, overdue follow-ups, upcoming visits, and leads with no meaningful next action. Confirm ownership before the workday becomes busy.

5. Post-sales tasks​

Review urgent, overdue, or blocked post-sales work. Check whether the blocker is clear and whether another staff member, the buyer, or an external party is expected to act.

How to work from a Dashboard card​

  1. Read the card title, count, and date context.
  2. Open the list or record behind the card.
  3. Confirm the record identity and current status.
  4. Read the latest activity and any linked records.
  5. Make the appropriate record-level update.
  6. Add an explanation when the change is not self-evident.
  7. Return to the Dashboard and confirm the item moved or cleared as expected.

Do not change several records merely to make a Dashboard count disappear. Resolve the underlying business condition.

Understanding totals​

Dashboard totals are useful indicators, but they can differ from a staff member's expectation when:

  • a status was not updated;
  • a due date passed without a new outcome;
  • a record is intentionally excluded by a filter;
  • a reservation expired or was released;
  • a payment entry is incomplete;
  • the Dashboard uses a different date range from the report being compared; or
  • the underlying data has changed since the page was opened.

When a total looks wrong, identify the specific records behind it before reporting a system defect.

Example: an application tied to an unavailable lot​

The Dashboard flags one application whose selected lot is unavailable.

  1. Open the application.
  2. Confirm the preferred lot and application status.
  3. Open the lot and review its current status and reservation context.
  4. Review the linked lead's latest activity.
  5. Ask the sales owner to discuss verified alternatives with the buyer where appropriate.
  6. Record the outcome in the lead and application notes.
  7. Do not approve or decline solely because of the Dashboard alert.

Management use​

Managers can use the Dashboard to ask better questions:

  • Why are follow-ups becoming overdue?
  • Which stage has the most aging leads?
  • Are reservations expiring because proof or communication is missing?
  • Are missing receipt numbers caused by training, process, or system design?
  • Are post-sales blockers repeatedly assigned to the same dependency?
  • Which records need a policy decision rather than another reminder?

The Dashboard should lead to process improvement, not only daily firefighting.

Common mistakes​

  • Treating a count as proof that every underlying record has the same problem.
  • Updating statuses without reading the activity history.
  • Assuming an alert disappears immediately without refreshing or waiting for the data to update.
  • Using the Dashboard as a financial ledger.
  • Ignoring small counts that represent high-impact payment, contract, or lot conflicts.
  • Clearing an action item without completing the source work.

Suggested training media​

Screenshot space: Add a full desktop Dashboard screenshot using fictional Training Data. Divide it into five labelled zones: Today’s Attention, Sales & Visits, Lot/Reservation Status, Collections, and Post-sales/Recent Activity.
Screenshot space: Add a close-up of one alert card and the detailed record it opens. Use arrows to show card count → filtered list → selected record → corrective action.
Diagram space: Add a Dashboard decision loop: Notice alert → Open source record → Verify facts → Update record → Confirm alert response.
Video space: Record a 6-minute morning Dashboard review covering one sales item, one lot/reservation item, and one financial exception. Demonstrate why each requires a different source record.