Designing a role-based scouting platform for six operational roles

Technical project profile | Selected team experience | Anonymized organization

Project summary

Valentin Lica led frontend development for an internal scouting platform used by a professional football organization. The work was completed outside Koro Solutions. The product brought player discovery, match tracking, structured evaluation, review, and leadership oversight into one role-aware interface.

This profile documents the system and Valentin's contribution. It does not claim a quantified business outcome because no client-approved adoption, time-savings, decision-quality, or performance measure was supplied.

Project facts

• Product: Internal scouting and player-evaluation platform
• Contributor: Valentin Lica
• Documented role: Frontend lead for the platform
• Users: Scout, Scout Manager, Corporate, Director, Youth Scout, and Youth Scout Manager
• Technology: Next.js, shadcn/ui, Tailwind CSS, Directus, Azure authentication, and Figma
• Case classification: Selected team experience completed outside Koro Solutions

Project question

How could one internal product support a shared scouting lifecycle while giving six organizational roles different permissions, actions, and levels of oversight?

Documented requirements

The existing process involved people with different responsibilities for observation, review, management, and leadership visibility. A generic interface would either expose too much information or force every user through controls that did not match the work they needed to perform.

The frontend therefore needed to support complex, data-heavy workflows without flattening the organization's permission model. It also needed to remain consistent as player records, matches, evaluations, and review states changed.

Implementation

Role and permission model

The interface was organized around six roles. Scouts and youth scouts required efficient paths for player discovery and structured input. Managers needed review and control. Director and corporate users required broader oversight. Available actions and visible information changed with the authenticated role.

Scouting workflow

The product connected the documented lifecycle of data collection, evaluation, review, management, and oversight. Player exploration, player-record management, match tracking, and structured evaluation were presented within the same interface system.

Frontend architecture

Valentin developed the frontend in Next.js using reusable components from shadcn/ui and Tailwind CSS. Directus supported backend content and data workflows. Azure authentication provided secure access. The architecture had to present large, dynamic datasets consistently while preserving role-specific behavior.

Documented scope

• Frontend architecture and implementation
• Role-based and permission-aware user experiences
• Player exploration and record-management interfaces
• Match tracking and structured evaluation workflows
• Azure authentication integration
• Directus data and API integration
• Reusable components for complex data views
• Responsive behavior across the product

What the evidence supports

The supplied project materials state that the platform was delivered as a full-featured internal product used across multiple departments and that scouting workflows were centralized within one system. The materials also document Valentin's responsibility for the frontend and the six-role model.

No usage analytics, before-and-after process measures, client interview, or independent technical audit was supplied. For that reason, this profile does not claim faster decisions, higher scouting accuracy, improved collaboration, or a specific operational return.

Evidence basis and limitations

This account is based on Valentin's CV and portfolio brief, both supplied for Koro's review. The source materials were checked for consistency across role, technology, and project scope. The organization is intentionally anonymized, and no logo, proprietary screen, confidential dataset, client quotation, or unsupported metric is used.

The evidence establishes relevant technical experience. It does not establish a Koro Solutions client engagement or an independently verified client outcome.

Why this experience matters

The project demonstrates the ability to translate a real organizational hierarchy into a coherent digital product. That capability is relevant when Koro clients need internal tools with complex permissions, structured review, data-heavy interfaces, or workflows that change by user role.

Attribution

Valentin completed this work outside Koro Solutions. It is presented as selected team experience and as evidence of the product-engineering experience he can contribute when supporting Koro engagements.