How I Built the Kit Registration EXE Programme
Turning kit registration into a governed workflow with cleaner intake, validation, status tracking and operational handoffs.
The Kit Registration EXE Programme was built to standardise a process that depended on many small handoffs: intake, validation, registration, exception handling and status updates. The issue was not one big failure point. It was the accumulation of manual checks and unclear ownership.
How I Built It
I mapped the registration flow from request to completion, then separated the process into clear states. Each state had an owner, required information, validation rules and an expected next action. That became the logic for the application and the automation flows around it.
The programme used Power Apps for structured intake, Power Automate for notifications and status routing, and SharePoint or Excel-backed registers where the business needed familiar working files. The emphasis was on reducing ambiguity without making the process feel heavy.
What It Does
The tool captures registration requests, validates required fields, tracks current status, flags exceptions and sends reminders when action is pending. It gives the team a single view of what is submitted, what is blocked and what is completed.
What I Learned
Automation works best after the process is made explicit. Once the states, owners and validation rules were clear, the technology became straightforward. The real value came from turning informal coordination into a visible operating flow.