What “One Panel” Should Show on Day One

A single screen earns its place by answering the three questions you ask before coffee. Everything else can wait until you know which numbers you act on.

Last updated: October 12, 2026

A single screen earns its place by answering the three questions you ask before coffee: who's arriving, what's still open, and what came in overnight. Everything else on a panel can wait until you know which numbers you actually act on. The mistake most hosts make is building the whole control room on day one, then stopping looking at it.

Key Takeaways

• Three questions decide the first screen. Who's arriving, what's still open and what came in.
• A panel is a filter, not a filing cabinet. If a number never changes a decision, it doesn't need the space.
• Most day-one panels are too full. Extra tiles add scanning time without adding answers.
• One place beats three tabs. The point is to stop opening several apps to answer one question.
• Add a tile when you act on it. A dashboard grows in pieces, one decision at a time.

The three questions a host asks first

Before coffee, most hosts ask the same three things. Who's arriving today? What's still open to sell? And did anything come in while I was asleep? Those three questions set the shape of the day, and a panel that answers them well has already earned its place.

The first question is about people, not numbers. You want to know who checks in, who's already in-house and who leaves this morning, because each one pulls a task: a welcome message, a mid-stay check, a turnover to schedule.

The second is about availability. You want to see, at a glance, which units are open tonight and whether the rates on those open nights are the ones you meant to set. A number that's wrong here is a booking you lose or a price you regret.

The third is about the outside world. Bookings, cancellations and messages arrive on their own schedule, and the value of a panel is that it catches them in one place instead of five inboxes. Answer those three, and everything else becomes a nice-to-have.

Three is the right number for a first screen because each question maps to an action. Who's arriving is a task to prepare. What's open is a price to check. What came in is a reply to send. A question that doesn't map to an action is one you can leave for later.

What belongs on the screen

Start with the arriving list. A single line per stay, showing the unit, the guest name and the check-in date, tells you where to point your attention first. This is the tile you'll open more than any other.

The order matters as much as the content. Arrivals sit on top because a person waiting at a door outranks a number in a chart. Availability comes next, because it's what you change when you spot a gap. Incoming follows, and the numbers rest at the bottom for the days you have time to look.

Next comes availability. LOCALSBNB shows each connected channel's own source price and status in one calendar, so a night that looks open in one place doesn't quietly clash with a rate you set in another. You see the source, not a summary that hides where a number came from.

Then the incoming side. New bookings, changes and cancellations for the day belong together, so you catch them in one sweep. The inbox is part of this, and it connects to Airbnb only, which is worth knowing before you expect every channel's messages to land in the same box.

Finally, one short line of the numbers you run on. Occupancy, average daily rate (ADR) and revenue per available room (RevPAR) sit together on the Home dashboard. On day one you won't act on them daily, but they show you the shape of your own performance without a spreadsheet.

That's the whole first screen. Arrivals, availability, incoming, and a short line of numbers. Four blocks, and a clear answer to each of the three questions.

What people add too early

The temptation is to build the whole control room on day one. Most of the tiles you'd add, though, answer questions you don't ask yet.

Owner statements come first for many hosts, because they sound serious. But at the start you're usually the owner, and a statement you send to yourself adds a column, not a decision. Add it when someone else is owed a report.

Staff permissions are similar. Role-based access matters the moment more than one person logs in, and not much before. On day one, a long permissions screen just slows you down while the first guest is already at the door.

Deep reporting is the third one. Twelve months of comparison, by-month breakdowns, market benchmarks — none of it helps before you have your own season to compare against. Until then, a benchmark you can't explain is worse than no benchmark at all.

The test for any tile is simple. Does this number change something I do today? If the answer is no, it belongs on a list of things to add later, not on the first screen.

There's a subtler trap than too many tiles: two tiles that disagree. A booking list and a calendar that don't match make you trust neither, and you end up checking the source anyway. When two blocks on the same panel conflict, that's a connection problem, and no amount of rearranging fixes it.

Reading the panel without checking three places

The real prize isn't a pretty screen. It's not opening three other apps to answer one question. A panel that holds only part of the answer still sends you elsewhere, and the checking never stops.

So the panel has to connect, not just display. If the calendar only knows about one channel, you'll still open the others to check availability. If the inbox only reaches one place, you'll still scroll through app notifications. The value comes from the connection, not the layout.

One more sign that a panel is doing its job: you stop narrating it to yourself. When you no longer think "let me check the calendar, then the inbox, then the bookings app", the screen has absorbed the work and the three questions have one home.

Then make it a habit. Open the panel once, at the same time each morning, and answer the three questions before you touch anything else. The routine is what turns a dashboard from a screen you visit into a screen you trust.

Expect the panel to be wrong once in a while. A guest cancels by phone, a cleaner moves a turnover, a rate gets edited on the channel itself. The habit isn't to trust the screen blindly; it's to check it first, then confirm anything that looks off at the source. A panel still saves time when it's mostly right, because the rest is where the money hides.

When you want to see it on your own listing, you can start at localsbnb.com. Set up the four blocks first, live with them for a month, and only then decide what deserves to join them.

FAQ

What if I run only one unit?

One unit still asks the same three questions. The panel just gets shorter, and the arriving list has one line instead of a dozen. With a single unit you can hold the day in your head for longer, so the panel's job is to catch what arrives while you're out, not to replace your memory.

Do I need the performance numbers on day one?

No. They're worth having, but they earn their place once you act on them. Add them when you find yourself opening a spreadsheet to answer the same question twice a week. Until then, arrivals and availability are the blocks that change your day.

Should every channel's messages sit on the panel?

Only the ones the inbox actually reaches. It connects to Airbnb only, so plan for the rest to be handled where they already live.

A day-one panel isn't a control room. It's a short answer to three questions you ask before coffee, and it should be honest about what it can reach. Build the four blocks, resist the rest, and let new tiles earn their place one decision at a time. See how it looks on your own listing at localsbnb.com.

---

This is general guidance for hosts, not legal, tax or insurance advice. Local rules and platform terms change, so check the current requirements of your local authority and the terms each platform applies today.