OwnerTabs
Back to all guides

How the OwnerTabs dashboard works

Think of the dashboard as triage. It helps you spot what’s open, pick the next thing, and jump into the correct property context. The dashboard is not where the details live — the property is.

Who this is for

Audience
  • First-time users who want a clear “what do I do now?” path.
  • Returning users who want a fast daily rhythm (without missing details).
  • Teams juggling many properties and switching context all day.

How to use it

Steps
  1. 1
    First login: create (or pick) a property and add basics you’ll need under pressure (access, shutoffs, key contacts, key docs).
  2. 2
    Daily: scan open incidents → pick the property/unit → do the work inside the incident.
  3. 3
    Use dashboard actions to start something, but always store the outcome under the property (incident/record/file/contact).
  4. 4
    When it’s done: close the loop with a one-line resolution + attach the proof (invoice, photos).

Key workflow

Repeatable
  • 30 seconds: scan what’s open → pick a property → open the incident → update status.
  • 2 minutes: attach files (proof) + add one record if you learned anything reusable.
  • Every time: property first, then action (no “floating” work).
  • End of day: close resolved incidents and leave the one-line outcome.

What the dashboard is (and is not)

  • Is: a quick scan of open work, and a launchpad into the right property/unit.
  • Is not: the place to dump details, invoices, or notes without context.

If the info isn’t attached to the property (and usually an incident), you won’t find it when you’re in a hurry — and neither will a teammate.

A simple daily operating rhythm

  1. Triage: scan open incidents and pick the top 1–3 that matter today.
  2. Work in context: open the property/unit, then the incident, then take action.
  3. Leave breadcrumbs: status update + who you contacted + next step (even if it’s “waiting on parts”).
  4. Close cleanly: resolution line + attach the invoice/photos + record the lesson if it’s reusable.

Practical example (30 seconds)

Example

A guest reports a leak at one unit:

  1. Dashboard → open the property/unit.
  2. Open (or create) the incident → add photos + a short timeline + current status.
  3. Log who you contacted and when you’re following up.
  4. Attach invoice/photos as files → close the incident with the one-line fix.

Outcome: next time, you can answer “what happened, who handled it, and what fixed it?” in seconds.

Common mistake

Watch out

Starting with a file upload or a note and figuring out the property later. That creates orphaned work. Pick the property first, then capture the details.

Rule of thumb

Rule

If someone else can’t open the property and understand the current state in 30 seconds, you’re missing either status, proof, or the one-line resolution.

Next guide

OwnerTabs for any size portfolio

Next, see what changes as you scale (and what breaks without a consistent system).

Read guide
Apply it

Open a tool and start working with the property record.

Each guide pairs with a workflow. The next step is to put it into practice.

Open toolsAll guides