Challenges

The brief

Requirement: 2 simultaneous bookings of 1 slot: exactly 1 succeeds; no online cancellation less than 24 hours ahead.

Industry: Health practices: independent physiotherapy practices with 1 to 5 practitioners and 1 front desk. Type of tool: Booking and reminders system. Form: web app. Who uses it: 1. Receptionist: books, moves and cancels for every practitioner. 2. Practitioner: sees their own day, marks visits attended or missed. 3. Patient: books or cancels their own appointment online. 4. Owner: sets hours and services, reads the reports. The problem it solves: The diary is a paper book or a shared calendar, and reminders go out by hand. Double bookings and no-shows leave paid hours empty, and nobody can say how often. Capabilities: Core workflow: 1. A week view for each practitioner shows free and taken slots of 15 minutes. 2. The receptionist books a service of 30, 45 or 60 minutes with a chosen practitioner. 3. A patient books from a public page: service, practitioner, then a free slot. 4. An appointment can be moved or cancelled, and the freed slot is bookable at once. Rules: 5. Two appointments of 1 practitioner never overlap, also when 2 people book at the same moment. 6. Booking is refused outside opening hours, during time off and less than 2 hours ahead. 7. A patient can cancel online until 24 hours before; later, the page tells them to call. Reminders and reports: 8. A reminder goes to a visible outbox 48 hours and 2 hours before; moving or cancelling replaces it. 9. The owner sets opening hours, services (duration, price) and each practitioner's time off. 10. A monthly report gives booked hours, cancellations and no-shows by practitioner. Records and admin: 11. Each role does only what Who uses it gives it; the server refuses the rest. 12. Every change to an appointment is logged (who, when, before, after); the log cannot be edited. 13. Patients and appointments can be searched by name, phone or date and exported as a file by the owner. 14. Every list has an empty state and every form names the field at fault. Records: Patient (name, phone, no-shows); Appointment (practitioner, service, start, status); Service; Time off. Out of scope: 1. Clinical notes and anything medical: the product gives no advice. 2. Real messages: the outbox only. 3. Payments and insurance claims. How it is checked: 1. As receptionist, book a 45-minute service. Pass: it is in the week view and 2 reminders are in the outbox. 2. In 2 windows, book the same slot at the same moment. Pass: exactly 1 succeeds. 3. As patient, cancel an appointment 3 hours ahead. Pass: refused, with the message to call. 4. As practitioner, open another practitioner's day by its address. Pass: refused. 5. Move an appointment. Pass: 2 new reminders replace the old ones, and the log shows before and after. Thresholds are inclusive: at most 5 means that 5 passes. What to send: 1. Link: the live demo with invented seed data; its sign-in page shows a demo account for each role. 2. Repository: public, with a seed command. 3. README sections, titled exactly: Setup in one command; Capabilities delivered (each number: done or not done); What a buyer gets (source code, setup guide, seeded demo; what is not included); Known limits; AI tools used and for what; What was hard. 4. Recording: at most 4 minutes, the checks in order. 5. Entry text: what it does and how many capabilities are done. Not allowed: 1. A template or generator that already is this product. 2. A capability shown with no rule behind it, or code written for the demo data only. 3. Real people or companies in the data. 4. A paid plan: free tiers, test modes and local models must be enough. 5. Work done before Monday. How to vote: 1. Does the core workflow work from start to end? 2. How many of the 14 capabilities marked done really work when you try them? 3. Would a physiotherapy practice pay for this as it stands? What you build is yours. If it reaches the podium, you can list it for sale on Vemly. Build it during the challenge week.

What you can win

• 11st place: 26,500 points and the badge "Challenge winner".
• 22nd place: 14,000 points and the badge "Challenge: second place".
• 33rd place: 7,000 points and the badge "Challenge: third place".
• +Every valid entry: 880 points and the badge "Challenger".

In Vemly challenges: points and badges only. No money, no gift.

Rules

1. One entry per member. You can change it until entries close.
2. Your entry needs a link to the result. The link starts with https://.
3. Voting opens when entries close. Each member has 3 votes, one per entry, never for their own entry.
4. Nobody sees the vote counts before voting closes.
5. Every member can vote. A vote counts when the account has a confirmed email and was more than 72 hours old when the vote was given.
6. Ranking: the most counted votes first. If two entries have the same votes, the one sent first is ahead. An entry with no counted vote is not on the podium.
7. Vemly can hide an entry that breaks the community rules.

Community rules · All times are in UTC.

Entries0 entries