Stefano's workspace grows with the season: in September he builds the company network, in winter he signs internship agreements, in spring he runs matching and mediation, in summer he collects outcomes. This is a mid-cycle Wednesday — four tabs in use (Mediation Inbox, Offer Moderation, Company CRM, Placement). The rest sit where they belong, until they're needed.
08:30 — The Mediation Inbox
Stefano runs the career services office at a mid-sized Italian university, with a small staff and a budget that doesn't grow. Wednesday morning he opens the platform on the office screen and starts with the Mediation Inbox.
The university has switched message review on: it is a setting the school turns on or off itself, on any plan. Since then, every message a company wants to send to one of its students arrives here first, instead of going straight to the student. Before InTransparency, recruiters either contacted students directly through LinkedIn (no oversight) or emailed Stefano's office and asked him to forward (slow, error-prone, no record).
He approves almost all of the waiting messages as they are. Two he edits: one stated pay below the collective agreement's (CCNL) minimum, and he flags it to the company; one offered a fixed-term contract that didn't comply with Italian labor rules for that role. He rejects one outright (a multi-level marketing pitch dressed up as a sales role).
Every decision is recorded. If a student or a parent ever asks how a company contacted them, the answer is in the record.
09:00 — Offer Moderation
Next, the Offer Moderation queue. This too is the university's choice, switched on in its settings: postings from partner companies wait for staff approval before students see them.
One is fine, and he approves it. One mentions "stage curriculare" in the description but offers a part-time work contract: he flags the company. One is from a company the office has had complaints about (they ghosted students in a previous internship cycle); he holds it pending a conversation with the company.
10:00 — Stage CRM
The Company CRM kanban is up next. He drags two cards from "First contact" to "Convention drafted" — both are companies that responded to last month's outreach. He drags one card from "Convention signed" to "Stage in progress" — a student started yesterday at an automation firm in Brescia.
The kanban is a system that used to be three spreadsheets and a shared mailbox. Now it's one view. His staff member Chiara sees the same view and updates her cards in parallel. They never overwrite each other.
11:00 — The placement pipeline
Friday's board meeting needs a placement update. In the old workflow he'd email the secretariat, ask for the spreadsheet, wait two days, manually pivot it.
He opens Placement Pipeline and pulls the live view: the internships in progress, the ones starting next month, the ones completed last month. For each completed internship he sees the mid-stage and final evaluations the tutor and the company submitted, the hours logged, and any flags raised along the way.
He exports a CSV for the board. Not because the platform's dashboard is bad, but because the rector likes Excel.
12:30 — Lunch, and an email
At lunch he gets an email from a recruiter at an automation systems integrator near Brescia. They want to interview a second-year ITS student named Marco, who isn't enrolled at his university (Marco is at the Bergamo ITS Academy). The recruiter asks if Stefano can introduce them to the Bergamo career office.
Stefano forwards the contact, then notes the request in his platform. The platform is built for the full institutional landscape — universities, ITS Academy, technical schools — and his Bergamo counterpart uses the same workflow. The introduction is a one-line email.
14:30 — Algorithm registry
In the afternoon he has a quarterly check-in with the university's DPO. The DPO wants to see the algorithm registry — the public page that explains how the platform computes its scores. Stefano pulls it up. The DPO reads it and asks two questions: which data goes into a score, and how a student asks for a person to review it.
InTransparency publishes the registry, so Stefano doesn't have to write one from scratch. The assessments that belong to the university stay with the university and its DPO.
What changed
What changed isn't that Stefano works less. He works on different things. The hours that used to be spent reformatting spreadsheets and forwarding emails are now spent on company outreach, student coaching, and the placement strategy conversations he's wanted to have for years.
The board sees real numbers, not a survey. The students get messages the office has already read. The companies have a single point of contact. The staff sees the same view.
That's the platform from the career office.