Someone joins
HR has the details, but IT and facilities enter them again. We connect the change to agreed accounts, equipment and tasks, reducing rekeying and first-day delays.
HR has the details, but IT and facilities enter them again. We connect the change to agreed accounts, equipment and tasks, reducing rekeying and first-day delays.
New permissions are added while old access and approvals remain outstanding. We connect the change to checks and follow-up, reducing rework and unnecessary access.
Who checks accounts, licences, laptops, badges and keys? We connect revocation and returns to an owner and feedback, reducing checklists and retrospective investigation.
These are examples, not a fixed package. We bring people, systems and agreed rules together around one vision. Start where your team can gain the most.
Enter volumes, minutes and costs. The calculator compares freed-up hours and work value with implementation, licences and maintenance. Reduced contractor use, overtime or avoided additional staffing can turn capacity gains into financial savings.
An estimate, not proven savings. We validate assumptions and outcomes together with your staff.Work with us to embed your BIO2 measures into delivery: revoke access on time, record approvals and follow up exceptions. Your team and CISO determine risks and appropriate measures; Service Automation Suite helps execute configured checks and record outcomes. This supports accountability, not automatic BIO2 compliance.
A new colleague needs more than an account. Departure requires more than revoking access. Equipment, approvals, tasks and suppliers need to follow. Service Automation Suite connects that work to the data and systems you already have.
Person, role, department and date provide the trigger. Your HR system remains authoritative.
Accounts and digital permissions retain their place in your existing IAM setup. There is no need to replace it.
Service Automation Suite combines source data, a matrix and agreed rules. We connect access changes to equipment handover, tasks, signing and feedback, including a route for errors.
The same approach also applies beyond employee workflows: a request, a document or a supplier ticket. Not everything at once; start where work gets stuck today.
Together, we define the outcome, configure connections and checks, and test the full workflow. Before go-live, we agree acceptance criteria and who handles later changes and exceptions.
Discuss your first outcomeAnother application, script or spreadsheet solves something. But who then manages the process across teams and suppliers? You need not replace everything. Start with one handover and make it repeatable.
A change is recorded, but access, assets and tasks lag behind.
Status and follow-up become scattered across cases, mailboxes and tickets.
Documents, advice and signatures require separate handovers.
Collaboration needs clear access, purpose limitation and minimal data sharing.


Leaving date and role provide the trigger. HR remains authoritative.

Define end dates, exceptions, approvals and step owners.


Revoke accounts and badge access; arrange device and asset returns.
Read results back. Failed steps remain open with their owner.
Rx.MissionA case status or document triggers agreed follow-up.

Check purpose, necessary data, case type and permitted actions.


Explore generation, signing and registration through available interfaces.
Return status and document references. Validate API versions and retention rules.
Microsoft Intune
A discrepancy or report needs assessment, not an automatic disruptive action.

Apply agreed thresholds and involve the appropriate operations or security role.


Link investigation, suppliers and recovery to the same report.
Keep timestamps, decisions and outcomes. Escalate under your incident procedure.



Digital signingService Automation Suite links the change and activities to the employee and the relevant assets. Issue, updates and returns are recorded against those same people and assets.
Who did what, when and with which approval? Status, execution results, signed documents and exceptions return to the change and activities, making resolution auditable.
Service Automation Suite reports progress and agreed updates back to HR through the configured integration. AFAS or Youforce remains the source for employee data; TOPdesk brings execution and evidence together.
Orchestration and control across the entire chainNo prescribed software stack. For each workflow, we identify available interfaces and record what exists, what needs configuration and what still needs development.
Connect employee data to time tracking, access, assets and service.
Connect access rights, devices and badges to the same employee lifecycle.
Each party keeps its own system; agreements and feedback stay connected.
Explore handing over case status, document references and follow-up.
Include document generation, signing and registration at the source.
A design approach, not a claim that national services are already connected.
With Service Automation Suite, we connect existing systems and define how work should flow between them. We gather the data a workflow needs and bring status and follow-up together. Source registers remain authoritative; Common Ground principles guide the design.


HR
Cases & permitting
Service & assetsAcross the workflow: purpose limitation, access, secure exchange and logging. Illustrative landscape; interfaces are validated per environment.
Integrate & gather. We identify authoritative sources and the data and events needed. Available interfaces connect the systems the municipality already uses.
Define & execute. Together, we agree who may do what, when actions follow and how exceptions are handled. Service Automation Suite supports execution, checks and feedback across systems.
Visibility & reuse. Bring progress, exceptions and ownership into one view without making Service Automation Suite a replacement source register. Validated workflow agreements can provide the basis for another department or municipality.
We validate alignment per pilot and identify existing components and development needed. This is not Common Ground certification or VNG approval.
Drawing on municipal experience, we build security into the workflow: from authorisations and checks to logging and follow-up. BIO2, privacy and applicable legislation are considered from the start. The municipality remains responsible for risk assessment and compliance.

Link role and HR changes to approval, updates and revocation of permissions.
Record: Trigger, approval, change executed and outcome.
Compare inventory with records and route discrepancies for review.
Record: Source, owner, discrepancy and completed follow-up.
Define decision rules and approvals; verify outcomes after execution.
Record: Change rationale, decision maker, test and feedback.
Connect reports, responsible teams and vendors to your incident procedure.
Record: Timeline, actions, owner and escalation decision.
Configure failure paths, restart rules and manual follow-up; test recovery with operations.
Record: Failure, recovery attempt, current state and owner.
Keep relevant process results and document references under agreed rules.
Record: Traceable checks, outcomes and exceptions.
Define scope, risks, controls, owners and evidence with security leadership. BIO2 covers more than the process controls Service Automation Suite can support.
Official sourceWork with privacy officers to define necessary data, lawful basis, recipients and retention. Assess processor agreements and whether a DPIA is needed.
Official sourceProcess evidence can support checks. ENSIA remains a municipal accountability process; Service Automation Suite does not replace self-assessment or review.
Official sourceDetermine applicability, responsibilities and formal reporting routes with security and legal teams. A service ticket is not automatically a statutory report.
Official sourceAgree document references, metadata, retention and disposal with information management. Service Automation Suite does not replace the DMS, records system or digital archive.
Official sourceAgree API access, security, service delivery, export and portability. Record the applicable terms contractually.
Official sourceInclude accessibility in forms and portals. Assessment and declaration relate to the relevant channel, not merely its integration.
Official sourceThis selection supports discussion, not a complete compliance assessment. Applicable requirements depend on workflow and environment. Logos and framework names identify sources; they do not imply certification or endorsement.
The VNG model as the basis for processor agreements with your municipality.
Download model agreementGIBIT 2025 with specific agreements for your engagement and services.
View contract agreements
Scope4mation ISO 27001 certification within the stated scope.
View certificate & packData storage in the Netherlands, with agreements on backups and access.
Discuss your deploymentDigital autonomy in practice
Digital services run from application and case handling to delivery by teams and suppliers. Case management, HR and service applications retain their own roles. With Service Automation Suite, we connect agreed data and process steps, with clear data ownership and responsibilities.
Start with one handover. Document connections, checks and operations for reuse. When suppliers change, assess what can stay and which mappings, API connections and tests need to change. Preserve existing investments and make portability a concrete agreement.
Read our view on digital autonomyA big ambition does not require one big project. Together with your team, we choose one bottleneck, configure the workflow and validate the outcome. The next use case builds on it. Automation and control grow together, without starting over each time.
You know the work; we help define rules, connect, configure and test. Reusable components and AI help us accelerate analysis, configuration and changes. Our advisers review the implementation; your team validates the outcome. Less rebuilding and less specialist investigation for your staff.
We agree who maintains, changes and follows up. You need not build all technical expertise yourself: we guide your team and agree what support remains necessary.