diff --git a/docs/dev/stories.md b/docs/dev/stories.md
index e69de29..7b1dd7b 100644
--- a/docs/dev/stories.md
+++ b/docs/dev/stories.md
@@ -0,0 +1,73 @@
+# Stories
+
+User stories describing real world repair-cafe situations and workflows.
+
+## Repairer cancels on short notice
+
+One of the repairers cancels his attendance to a repair-cafe on short notice.
+
+### Analog workflow
+
+If possible, assign existing repair appointments to other repairers, and align new time schedule with the guests using phone calls. If not possible, cancel repair assignments using phone calls.
+
+## Guest cancels a repair appointment on short notice
+
+A guest cancels a repair appointment on short notice. This frees a timeslot for an additional repair appointment.
+
+### Analog workflow
+
+If there are fitting devices on the waiting list, the owner is called and a repair appointment is offered. If no fitting devices are available, the last appointment of the day is re-scheduled to the free slot, in alignment with the guest.
+
+## Guest misses a repair appointment or causes trouble
+
+The guest is added to a blacklist.
+
+## The last repair appointment of a repair-cafe must get canceled
+
+Because of delays or other issues, the last repair appointment of a repair-cafe event cannot happen anymore.
+
+### Analog workflow
+
+If possible, the last repair appointment is cancelled using a phone call with the guest.
+
+## All slots for a repair-cafe are very early assigned
+
+### Analog workflow
+
+Deactivate registration form and give a hint on the homepage that the event is already fully booked.
+
+## All slots for some device types are already very relay assigned
+
+### Analog workflow
+
+Further registration is still possible, but a hint is added that repair assignments for devices types XYZ are not possible anymore.
+
+## Creation and handling of waiting lists
+
+If a repair appointment is not possible for a device, because of high demand for this device type of cancellation of a repairer, the guest is contacted and asked to register the device again for a later repair-cafe, or if the device shall be registered for a later repair-cafe.
+
+### Analog workflow
+
+Guest registers again: It's possible that again no slots are free, and the repair appointment is canceled again. The information that the guest had the device already registered for a repair-cafe is lost.
+
+Organizer registers device: Increased organization effort and there is a high probability that the guest doesn't keep the repair appointment.
+
+All canceled devices are moved to the "canceled devices" section of the forum manually. These devices are considered during the planning of the next repair-cafe, and the forum entry is moved to the section of the next event.
+
+## The guest doesn't confirm the appointment and doesn't reply to mails
+
+### Analog workflow
+
+Try to call guest by phone.
+
+If the organizers cannot reach the guest, the repair-appointment is canceled by mail. If possible, another guest form the waiting list is contacted.
+
+## Some device types are not repaired during a repair-cafe
+
+Some device types are not repaired during a repair-cafe. These devices are assigned to repairers for "offline" repair.
+
+### Analog workflow
+
+Align with repairer: If the repairer accepts the device, the contact data of repairer are given to the guest.
+
+For TV: Type plate and issue description is given to a repairer, and options are evaluated. If a repair is possible, the guest shall bring the TV to the Haus Einstein. When the repair is done, the guest get's an update by mail.