All guides

Money, Revenue Desk, about 6 minutes

Filing your end of shift report

The Revenue Desk is your end of shift report. The app fills in everything it can measure. You write the six things it cannot: what you moved, what you fixed, and what the next shift needs to know.

Open the desk

Why this matters: the handover is read by the next manager before they touch anything. A thin report costs somebody else an hour tomorrow.

  1. Sign in at app.hostassist.ai.
    You should see the dark dashboard with the menu on the left.
  2. Click Money, then click Revenue Desk.
    You should see a page headed End of shift report with today's date and an estimate of about 15 minutes.
  3. Read any grey warning under the heading.
    If it says you are not on the shift roster, reply times cannot be counted for you. Ask an admin to add you.
The end of shift report screen showing the heading, the already measured strip of tiles, and the first numbered section for pace.
Step 3 Measured numbers at the top, then six numbered sections you fill in.

Read what is already measured

Why this matters: these numbers are counted for you. Retyping them wastes your shift and introduces mistakes.

  1. Read the strip headed already measured, nothing to fill in.
    You should see median reply, slowest reply, still waiting, clients checked in, requests closed and open, price changes seen, and over ceiling.
  2. Treat n/a as no data, not as zero.
    A median reply of n/a with 0 answered means nothing was replied to in this window, so there is nothing to average.
  3. Check requests open before you finish.
    The small line under it tells you how many were open before today, which is the part that has been sitting.
The already measured strip showing median reply, slowest reply, still waiting, clients checked in, requests closed, requests open, price changes seen and over ceiling.
Steps 4 to 6 Eight measured tiles. If one is wrong, that is a data problem to raise, not a box to correct by hand.

Section 01, pace

Why this matters: naming the window that is behind is what turns a vague worry into a job the next shift can pick up.

  1. Pick the window that is furthest behind pace: 0-7 days, 8-30 days, 31-60 days, 61-90 days or All on track.
    The button you pick stays filled in, and only one can be chosen.
  2. Write what you did about it in the box below.
    Name the property and the dates. Two sentences is plenty.
  3. Note any cancellations worth mentioning.
    Leave it blank if nothing was unusual. Name the property if several came from one place.
Section 01 pace, with buttons for 0 to 7 days, 8 to 30 days, 31 to 60 days, 61 to 90 days and all on track, above a box for what you did about it.
Steps 7 to 9 Compared against the same time last year, or against target. One window, then the action you took.

Section 02, what you actually moved

Why this matters: this is the record of your day. It is also what the weekly client report is built from.

  1. Fill in the four counts: priced up, priced down, orphan gaps filled, min stay changes.
    Counts only. The detail goes in the box underneath.
  2. Write the three moves that mattered most.
    Give the property, the dates, the change and the reason. Be specific enough that somebody could check it.
Section 02 what you actually moved, with count fields for priced up, priced down, orphan gaps filled and min stay changes, and a box for the three moves that mattered most.
Steps 10 and 11 Four counts and three stories. That is the whole section.

Section 03, faults you cleared

Why this matters: these look like pricing problems and are not. Logging them separately stops the same false alarm coming back next week.

  1. Fill in the three counts: stuck at floor or ceiling, no price push in 24 hours, calendar blocks that should not be there.
    A listing stuck on its floor is a setting. A blocked calendar is not a rate.
  2. Write what you did about them in the box underneath.
    If you raised it with somebody else, say who, so the next shift can chase it.
Section 03 faults you cleared, with counts for stuck at floor or ceiling, no price push in 24 hours and calendar blocks that should not be there.
Steps 12 and 13 Faults are counted apart from price moves on purpose, so nobody reads a settings bug as a pricing decision.

Sections 04 to 06, market, risk and blockers

Why this matters: events are the single biggest lever and the one most often missed. The handover is required because the next shift starts by reading it.

  1. In section 04, write any new events found in your markets today.
    Write none if there were none. A blank box reads as not checked.
  2. Add any competitor move worth acting on, and the biggest opportunity you did not get to.
    Being honest here is expected. It carries to the next shift and is not held against you.
  3. In section 05, name the biggest risk in the next 14 days and anything pacing to miss target.
    Name the property and how far behind it is.
  4. Write the handover for the next shift.
    This one is required. Write it for the person reading it cold tomorrow morning.
  5. In section 06, say what stopped you doing your best work today.
    Access, data, a broken tool, waiting on somebody. Leave it blank if nothing did.
Section 05 risk and handover, with a field for the biggest risk in the next 14 days, one for anything pacing to miss target, and a required handover box.
Steps 14 to 18 The handover box is the one field the next manager reads first.

Finish the shift

Why this matters: saving a draft keeps your work. Submitting is what tells the team the shift is closed.

  1. Tick morning sweep done and close sweep done if you did them.
    Both sit just above the buttons at the bottom.
  2. Click Save draft at any time.
    Your answers are kept and you can come back to the same report.
  3. Click Submit and post to pricing-admin when the shift is finished.
    The report is posted to the team channel, so treat submit as sending it.
The two buttons at the bottom of the report, Save draft and Submit and post to pricing-admin.
Steps 19 to 21 Save as often as you like. Submit once, at the end.

Three things that catch people out

Why the app fills in half the form

Reply speed, open requests and price pushes are all things software can count exactly. Asking a person to retype them adds nothing and quietly adds errors.

What software cannot see is judgement: why you dropped that rate, what you would have done with another hour, what you are worried about next week. That is the half you write.