Smart approval procedure
Only special cases reach your desk for approval – everything else runs through by itself.
Approvals are a trade-off: they give control but cost time – and they cost it from the people who have least of it. Zeitwart resolves that by making sure only the cases that genuinely need a decision reach anybody's desk.
You decide where approvals apply
The procedure is switched on per organisational unit and inherited downwards. Meeting rooms then go through without a query, while the assembly hall, the laboratory or the event space require a release. Who may approve follows from the corresponding permission in that unit.
Requests land where they belong
As soon as a booking needs a release, a request appears in the queue of everyone in that unit who may approve. A central collecting address can be added on top – useful for an office that screens requests first. The two can be switched independently.
Where a reason is needed, you make the field mandatory. And where approvers keep asking the same questions, you store a free text that appears additionally in the request e-mail: deadlines, who to ask, internal rules. The text is set per unit or given globally.
The real trick: automatic release
The decisive setting is automatically approve unanswered requests at the start of the appointment. If a request is left lying, it is released by itself shortly before the start – with a lead time you set in minutes.
That inverts the logic: no longer does every booking need an active yes, only an objection needs an action. Holidays, illness or a full inbox then stop blocking room usage. Anyone who wants to work more strictly leaves the switch off and keeps the classic four-eyes principle.
Where this pays off
universities releasing lecture theatres and laboratories while leaving seminar rooms open
companies with representative rooms that have to be coordinated
public institutions letting rooms to outside groups
anywhere one person is currently the bottleneck for every room request
Benefits at a glance
approvals only where they are needed – switchable per organisational unit
requests reach every authorised person and optionally a central address
mandatory reason, plus your own note in the request e-mail
automatic release shortly before the start prevents requests being left lying
settings inherited down the tree and overridable per unit