Chapter 8: Bookings and Loans: Organizing Rooms, Devices and Courses
EdumapsOrientation
1
What is this about?
- With Edumaps, schools can not only collect teaching material, but also organize bookings and borrowing.
-
Typical examples:
-
- book iPad cases
- borrow projectors
- reserve rooms
- offer training courses
- manage consultation times
- coordinate project dates
-
This pinboard explains the basic idea using simple school examples.
-
⚙ start
2
3
When is booking worthwhile?
-
Booking functions are worthwhile when several people use the same inventory or the same appointments.
-
Examples:
-
- there are only a few devices
- rooms are limited
- courses have participant limits
- appointments should not be assigned twice
- a participant list is needed
-
For simple information, a normal map without booking is often enough.
Course booking
4
5
6
Set participant limit
Loans
8
9
Good loan description
10
Example: Loan iPad cases or Lego kits
-
A simple device loan in Edumaps can be structured like this.
-
Example:
-
The school wants to lend one iPad case and one Lego kit.
-
Possible boxes:
-
- iPad Case 1
- iPad Case 2
- Lego Kit Robotics
- Projector Media Room
- Document Camera
-
Each box describes:
-
- what is included
- where it is picked up
- when it must be returned
- who is responsible
-
Tip:
Use clear names so users do not book the wrong item.
11
12
Avoid double bookings
-
A booking system helps prevent the same device or room being reserved twice.
-
Important:
The booking rules must match the real school process. -
Clarify:
-
- Can one person book several devices?
- How far in advance may users book?
- Can bookings be cancelled?
- Who resolves conflicts?
- What happens if something is not returned?
-
Tip:
For the start, use simple rules. Complicated systems are used less reliably.
Organization
13
14
Practice
16
Mini task: Plan a loan map
-
Plan a simple loan map for your school.
-
Task:
-
- Choose one inventory area, for example iPads.
- List the available items.
- Define clear names for the boxes.
- Write pick-up and return rules.
- Decide who may book.
- Decide who is responsible.
- Test the booking process with one example.
-
Goal:
The process should be understandable without additional explanation.
17
Typical mistakes
-
Typical mistakes are:
-
- Devices are not named clearly.
- Return rules are missing.
- The participant or booking limit does not match reality.
- Nobody is responsible for maintenance.
- Old bookings are not checked.
- The process is too complicated.
-
Tip:
Start with one small loan area before organizing everything at once.
18
Checklist before start
-
Before using a booking or loan map, check:
-
- Are all items or courses clearly named?
- Are dates and time periods understandable?
- Are limits set correctly?
- Are pick-up and return rules written down?
- Is the responsible person named?
- Has the process been tested?
- Do users know where to find the map?
-
A good booking map saves questions because the rules are visible directly in the map.