To get the most out of classroombookings, take some time at the beginning to set it up to work the way your school works.
Once you've got it installed, the recommended order for configuring it is:
- School Details
- The School Day
- Week Cycle (Academic Year, followed by Weeks)
- Recurring bookings
Use the school details page to set your school's information (name, website address and logo) as well as display options for the Bookings page.
Booking in advance
Use this option to limit the number of days ahead that teachers can make bookings, based on the current day when making the booking.
Example: booking in advance is set to 3 days. On Monday, teachers can book rooms between Monday and Thursday.
This option changes the focus of the bookings page.
- One day at a time: The booking page shows bookings for a single day, for all rooms and all periods. Users navigate by date.
- One room at a time: The booking page shows bookings for a single room, for all days of the week and all periods. Users navigate by week and room.
This determines which data aspect is shown on the bookings table, and is dependent on the Display type set.
The School Day
Use the school day section to set up how your day operates - primarily, the lesson/period times. You do not need to enter breaks - just the periods that you want rooms to be able to be booked on.
It is not recommended that periods overlap.
Some people find it useful to add "Before school" and "After school" periods, if rooms are sometimes used "out of hours".
Academic Year & Week Cycle
Classroombookings needs to know about the Academic Year before the timetable weeks can be configured. Use the Academic Year link to set the start and end date for the academic year, typically from September to July.
Use the Week Cycle page to configure the timetable weeks. These are essential for making recurring bookings, mainly used for the traditional timetabled lessons. The flexibility in defining the weeks allows multi-week timetables to run throughout the academic year; but instead of alternating in a week one/week two fashion, you define each week in the year to a specific timetable week.
When you create a recurring booking, it is assigned to a room and period for the given day on the timetable week that the date falls on.
Example: creating a booking for Period 1 in Room 1 on a Monday in "Week 1" will ensure that the booking occurs every Week 1 on a Monday at Period 1 in Room 1.
If you only operate a simple one-week timetable, a week still needs to be added. Give it a name like 'Timetable', and tick all of the weeks in the year.
It is possible to prevent bookings from being made on certain fixed singular dates or date range throughout the academic year using the Holidays feature. Make sure to enter just the dates that fall within the actual holiday - do not include the "break up" or "returning" date.
Holidays affect bookings for all rooms and all periods on the holiday's dates.
Use this section to set up the rooms that can be booked.
If you wish to highlight certain features of the rooms, you can do this with custom fields. Common uses for these are things like room capacity, number of computers, and whether certain features are available, like printers and projectors.
You can save time by creating the fields you want to use first, and then adding the rooms.
When adding a room, some of the information you enter (e.g. owner, location and photo) will be accessible and visible on the bookings page to other users.
The Room owner setting allows you to designate a classroombookings user as the owner of that room. This gives the user the special permission of being able to delete other user's bookings in their room.
Users are central to accessing classroombookings. There are currently only two types of users: Administrator, and Teacher. Administrator users can do anything within the system. Teacher users can only create bookings for bookable rooms, up to number of days ahead as configured in the Booking in advance setting mentioned above. Teacher users to not have access to any of the management features.
It is also possible to bulk import users from a CSV file using the Import users page.
The CSV file needs to be formatted with the following columns:
username, firstname, lastname, email, password
If you choose to set a password for the imported users on the Upload page, the field in the CSV file will be ignored.