Moving beyond spreadsheets: resource allocation for activity centres

Map the resources behind one visit

For an illustrative school day visit, list session times, group size, spaces, equipment, staffing and catering. Include preparation, cleaning, travel and maintenance where relevant. This is a planning example, not a customer booking.

• Which resources cannot serve two groups at once?
• Which decisions need a supervisor, and which can front-line staff make?
• Who needs to know when numbers, times or activities change?

Separate enquiries from confirmed bookings

Agree consistent statuses and the rules for moving between them. A telephone enquiry is not a confirmed booking. Staff need one current record and clear responsibility for updating it, even if some day-to-day communication remains in messaging apps.

Test software against your own workflow

Ask for a demonstration of a visit involving several resources, then change the timing, group size and programme. Look beyond the calendar: can staff see what still needs a decision?

• Can availability be checked across spaces, people and equipment?
• Are permissions, change history and pending decisions clear?
• How will spreadsheet records be cleaned, imported and reviewed?

Introduce the process in stages

Pilot a common workflow with a small team before extending it. AI may help draft summaries and follow-up suggestions, but important arrangements require staff review. A generated suggestion must not be treated as a confirmed booking or an instruction to allocate resources.

Distinguish existing work from the new platform

Our Sai Kung case is a Hong Kong deployment of a tailored system and infrastructure. The new venue platform is an early partner programme; scope is agreed per project. The case does not mean the new platform already offers every feature described in that deployment.