Implemented system · broader product pilot pending
Year
2025
Why it matters
Live teams needed dependable calling, movement and receiving without working from separate versions of participant state.
The original operating logic was implemented; this public interaction is a protected demonstration, while any broader GEVON product remains a separate pilot.
Live teams needed dependable calling, movement and receiving without working from separate versions of participant state.
What was built
Role-specific Power Apps screens, Microsoft Lists shared state, controlled Power Automate updates and Power BI operational visibility.
Result today
The original operating logic was implemented; this public interaction is a protected demonstration, while any broader GEVON product remains a separate pilot.
01 / Starting point
Live handoffs were vulnerable to ambiguity.
Controllers and receivers needed to see the same participant state under event pressure.
02 / The decision
Give every role one next action on one shared record.
The operating model prioritised state clarity over a complex all-purpose dashboard.
Options
Coordinate through separate messagesUse one shared state model
Decision · Use one shared state model
03 / What was built
Role-specific Power Apps on the existing Microsoft stack.
Lists held state, Power Apps served the operators, Power Automate controlled updates and Power BI provided visibility.
04 / Result today
Implemented logic with protected operational records.
The simulation below uses representative identifiers and remains separate from the maturity of any future product pilot.
System X-ray
See the invisible work behind the experience.
01Operator experienceController and receiver Power Apps viewsANONYMISED02ApplicationRole-specific live operating screensSYSTEM MAP03WorkflowControlled next-person and handoff state changesSYSTEM MAP04DataMicrosoft Lists shared participant stateSYSTEM MAP05VisibilityPower BI operational viewSYSTEM MAP
03 / System + Explore
Follow the operating flow.
Select a node to change the proof stage. Open the detail drawer when you want the deeper technical explanation.
DEMOController
Select the next eligible participant
The controller sees the sequence and triggers the next controlled movement.
What this changes
The handoff begins from one authorised action.
Interactive demonstration
Run the operating logic safely.
The interaction uses representative data and never touches the protected source system.
DEMORepresentative record · participant data protected
GUEST027CHECKED IN
1CHECKED IN2MOVING3RECEIVED4COMPLETE
The original Microsoft 365 operating logic was implemented. This interaction is a safe demonstration, not the live organisation system.
Technical evidence index
Read the implementation detail without opening a control.
DEMOControllerSelect the next eligible participant
The controller sees the sequence and triggers the next controlled movement. The handoff begins from one authorised action.
SYSTEM MAPShared stateUpdate the operating record
The participant changes state in the shared model rather than in a separate private list. Every role reads the same operational truth.
DEMOReceiverReceive the active handoff
The receiving screen exposes the active participant and required next action. The receiver does not need to interpret the entire queue.
SYSTEM MAPVisibilitySee movement and exceptions
Operational visibility reflects shared state without exposing protected original records. Managers can understand the event flow.
05 / Result today
The original operating logic was implemented; this public interaction is a protected demonstration, while any broader GEVON product remains a separate pilot.
An implemented two-point calling and movement-control system built by Krste with Microsoft Lists, Power Apps, Power Automate and Power BI. A broader event-operations product remains a separate validation pilot.