This week’s AnyShift development update is about a practical step in preparing temporary work: checking the relevant student or flexi-job information with the worker’s permission. We have implemented an RSZ integration in the app, and it is live. Job students and flexi-jobbers can give AnyShift a mandate so that we can carry out the relevant checks.
This is a team update based on information I have confirmed for publication. AnyShift is one of the businesses I work on, rather than an independent investment being reviewed here. The focus of this entry is the live integration and the problem it addresses, not a claim about market leadership or measured time savings.
The problem behind the integration
Finding a shift and preparing the administration are connected parts of the same experience. A person may be ready to work, but the relevant information still needs to be checked. For a staffing platform, making that step understandable matters alongside publishing shifts or helping employers organise their planning.
The product direction is to bring this check into the app journey through a mandate from the worker. That gives this week’s development a specific purpose: connect the staffing process to the relevant official information with permission. It is a narrower and more useful statement than saying that every administrative requirement has become automatic.
What is live now
The confirmed release is the RSZ integration for checking job-student and flexi-job status through a mandate given to AnyShift. RSZ is the Dutch abbreviation for Belgium’s National Social Security Office, also known as ONSS in French. This article does not specify a release day before publication or announce additional functionality beyond that confirmed scope.
The previous AnyShift development update covered the redesigned employer and shifter experience, employer access in the app, direct contracts and clock-in/clock-out. Those features provide context for the product’s development; they are not new releases being announced again this week.
The mandate is an important part of the story
The official Student at Work guidance describes access requests for flexi-job information and remaining student hours. It explains that the worker approves access and can cancel it in Accesstomydata. That is the public-service context; it is not a description of every screen or data field in AnyShift.
For readers, the distinction is straightforward: a mandate is permission for the relevant check. It should not be confused with a promise that any person can take any shift. This update makes no claim that the integration replaces every check, contract or administrative step involved in an assignment.
A practical product lesson
The lesson I draw from this work is that useful staffing software needs to connect the visible task with the information behind it. A shift listing is one part of the journey. Understanding what can be checked, through whose permission, is another. The quality of that connection deserves attention without needing a long feature list.
We are sharing the integration as live work, not as a roadmap promise. There are no adoption figures, customer quotations or performance results in this update because none are being announced. For questions about using the current flow, contact the AnyShift team. Future journal entries will distinguish released work, testing and plans in the same way.