
AI-Powered Student Admissions Validation for an Italian University
- Client
- University · Italy · one of Europe's largest private universities, several branches
- Industry
- Education
- Department
- Operations
- Region
- Italy · Europe
Twice a year, four to eight admissions staff spent one to two months checking around 20,000 applications by hand: does the form match the ID, is the photo a proper portrait, is it the same face. Every check missed is a wrong identity in the student record. Now a robot does the checking, around 90-95% of it correctly, and people see only the cases that need judgement.
A working model of the approach on sample data. It plays on its own and pauses when scrolled away; nothing here touches a live system.
The results
- ~20,000
- admissions validated a year
- Two intake windows. Approximate working figure from the delivery team.
- ~90–95%
- of applications the robot handled correctly
- Recalled by the delivery team. The rest went to people in Action Center.
- 3+ yrs
- in production
- 2022 to 2025, supported and maintained by us throughout.
The challenge
Our client is one of Europe's largest private universities, based in Italy, with several branches. Applicants apply through an online admissions portal, upload their identity documents and a photo, and the admissions office reviews each application and replies when something is missing or wrong. One branch runs admissions on a separate, API-based system. There are two intake windows a year and around 20,000 admissions to validate.
Every application was checked by hand. Staff opened the uploaded identity document, read it against what the applicant had typed into the form, judged whether the document was one of the formats the Italian state accepts, and looked at the photo twice: once to see whether it met the portrait rules (a flat background, not a selfie taken in a bathroom), and once to see whether it was the same face as on the ID.
What it was costing them
- Peak-load staffing. Around four to eight people tied up for one to two months, twice a year, exactly when the admissions office is busiest.
- Judgement by eye. Identity matching at around 20,000 applications a year, done by whoever was on shift.
- Identity risk. A mismatched ID, an unacceptable document format or a photo of someone else, missed once, becomes a wrong identity in the student record.
- Applicants waiting. Every day of manual backlog is a day an applicant waits to hear that something is missing.
- Two channels, one manual process. The portal and the API-based system both had to be covered by the same manual checks.
- Form against the ID
- Document type accepted in Italy
- Data valid and well formed
- Portrait rules for the photo
- Same face as on the ID
The approach
We built a UiPath robot that works the admissions process like a member of the admissions team: it validates each application end to end, hands the cases it cannot complete to staff, and reports the rest.
How every application is validated
- Rules from the admissions team. We collected the validation rules from the admissions staff and their knowledge of the process, and turned them into explicit, testable checks.
- Portal automation. Unattended UI automation logs into the admissions portal, opens each application and reads the submitted form and uploaded documents, for every branch on the portal.
- API integration. The branch on the API-based admissions system is handled by the same automation through its API.
- Document understanding. UiPath Document Understanding classifies the uploaded document and extracts its data: ID cards, passports, driving licences and tax ID documents, each in the several formats accepted in Italy.
- Form-to-document matching. The extracted ID data is compared field by field with what the applicant entered in the form.
- Data validity. Regex patterns and type- and format-specific rules check that each value is real and well formed, and that the document type and format are acceptable.
- Photo validation, built in-house. Our own Python algorithms check the photo against the portrait criteria and match it to the face on the ID document.
- Human in the loop. When the robot cannot extract every field or information is missing, the case goes to admissions staff in UiPath Action Center, and the results are reviewed at the end of the process. The robot never guesses.
- Exception reporting. Anything wrong or missing is flagged to the university in a regular Excel report, so staff contact only the applicants who need it.
- Portal & API intake
- Document Understanding
- Form-to-ID match
- Validity rules
- Photo checks
- Action Center
- Excel exception report
Built to run every intake
- Orchestrated from UiPath Automation Cloud, with the robots on virtual machines inside the university's own network.
- Designed and built to UiPath best practice.
- We administered the Automation Cloud tenant and the robots' Windows infrastructure.
- Support, upgrades and maintenance of the robot and its infrastructure from 2022 through 2025, with admission-process corner cases handled as they appeared.
Technology
| Layer | What we used |
|---|---|
| Automation | UiPath Studio, unattended robots (UI automation) |
| Document AI | UiPath Document Understanding |
| Human in the loop | UiPath Action Center |
| Orchestration | UiPath Automation Cloud (Orchestrator) |
| Photo validation | Python, our own portrait-criteria and face-matching algorithms |
| Data validation | Regex and rules-based checks |
| Integration | API integration with the API-based admissions system |
| Reporting | Excel exception report |
| Infrastructure | Windows virtual machines on the client network |
The outcome
The original project documentation is lost, so the figures below are approximate: working figures and recollections from the delivery team, not audited measurements.
| Before | After | |
|---|---|---|
| Checking an intake | Around 4-8 staff for 1-2 months, twice a year | The robot validates; staff handle the exceptions |
| Manual review a year | Roughly 1,350-5,400 hours (derived from the staffing above) | The bulk moved to the robot |
| Form against ID, document type, data validity | By eye | Automated checks on every application |
| Portrait rules and face match | By eye | Our own Python algorithms |
| Cases needing judgement | Mixed in with everything else | Routed to Action Center |
| Standard applied | Whoever was on shift | One standard, every intake, every branch, portal and API |
- Around 20,000 admissions validated a year across two intakes, from 2022 to 2025: more than 60,000 applications over the engagement.
- Around 90-95% of applications handled correctly by the robot. The rest, and every case with missing information or fields it could not extract, went to people.
- The manual checking moved to the robot. Staff now handle only wrong or incomplete cases; the delivery team describes the savings as enormous, though they were never formally measured.
- One validation standard for every applicant, every intake, across all branches and both channels.
- 3+ years in continuous use, supported, upgraded and maintained by us throughout.
- 1-2 months 4-8 staff checking by hand
- Exceptions only staff handle wrong cases
- About 90-95% handled correctly by the robot
The risk most teams miss
An admissions robot fails at the worst possible moment: the first week of an intake, when volume spikes and a portal change, a new document format or a Windows update on the robot's machine stops it cold. Our support covered the robot and the infrastructure it ran on, and corner cases were handled as they appeared, so each intake started on a working robot.
Built with
The tools this ran on, by the layer each one carried.
- Apps & integration
- Automation
UiPath StudioUiPath's design environment for building RPA workflows.
UiPath Document UnderstandingUiPath's document classification, splitting and extraction, with human validation.
UiPath OrchestratorCentral control for UiPath robots: queues, schedules, assets and credentials.
UiPath Action CenterHuman-in-the-loop tasks for UiPath robots.
UiPath Automation CloudUiPath's hosted platform for orchestration, document AI and human review.
- Data & cloud
Next step
Start the same conversation
Tell us the process that keeps breaking. We will come back with what it would take to fix it, what it would cost, and what we would measure.
Or write to us directly: •••••@•••••••.•••
- A reply from a partner within one business day
- Fixed scope and fixed fee, agreed before we start
- The maps and the backlog are yours either way




