Loket | Craftor · 2025 · iOS & Android
Designing Faster Check-In Workflows for Event Teams
Product Designer



THE BEGINNING
Craftor is an event-day operations tool built for two very different people at once: organizers staying on top of everything, and check-in crews who just need things to work fast at the gate. The first release focuses on check-in, the moment where everything either holds together or falls apart.
HOW MVP WAS SCOPED
Rather than trying to cover every creator need at once, the first release focused on the most critical event-day needs. It defined the minimum set of capabilities needed to make Craftor usable at launch, while separating broader creator needs into later phases or out of v1.
Tap to exploreHover to explore
LAUNCH MVP
LATER PHASE
OUT OF SCOPE
CORE CHALLENGES
Once the MVP scope was defined, the challenge was making the operational flow clear, role-aware, and reliable.
To move forward, we first needed to align on what the first release had to deliver.
ALIGNING INTENTIONS
Beyond solving usability issues, the first release also had to support the needs of both product and operations.
WHAT ARE THEIR INTENTIONS?
The MVP needed to make event-day needs easier to enter, understand, and complete.
STRUCTURING THE CHECK-IN FLOW
The MVP connected event access, check-in, and recovery into one operational sequence. It supported two valid check-in methods: scanning stayed the default for speed, while Ticket Finder was available as an alternative.
Click the map, then use the arrows to explore
Check-in route
Event List
CHECK-IN INTERFACES
The flow supported two valid check-in methods: scanning for speed, and Ticket Finder as an alternative.
To keep check-in operational in live conditions, it also needed clear recovery states: a ticket that was already used, a scan that doesn't go through, and a camera the app can't reach. Each one gives the crew a way forward instead of a dead end, so the line keeps moving.
Below, the gate is yours: check guests in with either method and see each of these states for yourself.
Next result: Next result: Check-In Success
Camera: |

J**n D*e
Waiting Scanable Code
ADAPTING EVENT CONTEXT BY ROLE
The same event view adapted what it surfaced first by role, giving crews a more focused operational view and admins broader visibility across progress and performance.
Crew view
Their own progress

Flow World Tour "Anime Shibari 2024 - 2025" - Jakarta
14 Aug 2025 • 18:00 JST
Checked by You
212
Cat 1 - Superb: 96
Cat 2 - Reg: 50
Cat 3 - Presale: 0
See More![]()
Event Details
TotalsCrews see their own check‑ins. Admins see the whole event against its total, split between them and the crew.
Admin view
The whole event

Flow World Tour "Anime Shibari 2024 - 2025" - Jakarta
14 Aug 2025 • 18:00 JST
Check-in Report (All)
51.2%of total attendees512/1000
- Checked by You
- 212
- Checked by Crew
- 300
Cat 1 - Superb: 48%96/200
Cat 2 - Reg: 25%50/200
Cat 3 - Presale: 0%0/200
See More![]()
Check-in Crew List
8 Crews
Search crews
Rudiger Simangunsong
Total Checked-in: 41
Event Details
WHAT HAPPENED AFTER LAUNCH
Craftor was developed as an initial MVP for event-day operations, designed to establish a usable foundation for organizers and check-in crews.
Early validation
One early signal came from live use during Raisa's AmbiVert tour concert. Overall, crew feedback was positive, suggesting the flow felt usable in the field. One refinement point also emerged after rollout: the success state after scanning still needed clearer feedback to make confirmation feel more immediate.
Expected impact
Clearer event-day operations — Teams could move through event access, role-based visibility, and check-in in a more structured sequence.
Stronger role relevance — Admins and crews saw different levels of information based on what they needed to monitor and act on.
LESSON LEARNED
This project taught me that a strong MVP is not about including more, but about making the right things work together from day one. In operational tools, speed, role clarity, and recovery all shape whether the product is actually usable.