How to Close an Amenity for Scheduled Work

Step 1: give the ticket a schedule

Set the scheduled start and end dates for the work. Until they exist, the Asset Impact tab shows Schedule Required and will not let you link anything, because the closure window is derived from the work.

Step 2: link the affected amenities

Open the Asset Impact tab and select the amenities the work will affect. You can link more than one, and you can add more later. Link everything genuinely affected, not only the obvious one. Pool work usually takes the change rooms with it; elevator work in a tower often takes the moving room bookings that depend on that elevator.

Step 3: check the closure window

The Closure Window is the period the amenity will be unavailable. Make it match reality rather than optimism. A closure that ends the day the contractor hopes to finish produces a booking on the evening of an overrun, which is a worse outcome than a slightly generous window.

Step 4: choose what the amenity becomes

You choose the state the amenity takes during the window:

• Maintenance, for the normal case of work happening.
• Inactive, where the amenity is simply not available.

Step 5: confirm the closure

This is the step that makes it real. Choose Confirm Closure. Kore checks for bookings that overlap the window and shows you what it found, along with the choice between cancelling those bookings and only blocking new ones. Make that choice, then confirm.

Until you do, the tab warns you plainly that the dates are still bookable.

Step 6: tell people

Cancellations notify the affected residents automatically, but people who never had a booking learn nothing from a cancellation they did not receive. For anything more than a short closure, post news as well, and say when the amenity comes back.

What the closure report tells you

The report states, for every booking it touched, how much money went back and whether the booking was actually cancelled.

If something goes wrong partway, it says so specifically rather than reporting that nothing happened. A booking that was cancelled and refunded is counted and its refund included in the total, even when the run could not finish. Where the system genuinely cannot tell what happened to a resident's money, it says the outcome is unknown and asks you to check that refund against the property's accounts, instead of reporting zero.

The preview you approve before closing an amenity behaves the same way. If it cannot read the bookings, it tells you, rather than showing “nobody affected”.