Data Panda brings your Bloqs Cliëntvolgsysteem data together with the data from the rest of your organisation. From one place, we turn it into dashboards, automations, AI workflows and custom apps your care and reintegration teams use every day.
Bloqs Cliëntvolgsysteem is a modular Dutch client-tracking platform built for organisations delivering WMO, Jeugdwet, UWV reintegration and UWV jobcoaching trajectories. Provider teams compose what they need from bloqs like Basis, Documentbeheer, KMS, HR, Zorgcontracten, Algemeen traject, Projecten and the UWV-specific modules, with VECOZO declarations and UBL invoicing wired in.
The point of pulling Bloqs into a warehouse is that every trajectory generates client records, hours, dossier tasks, leave hours and invoices, and the relationship between them is what tells you whether the organisation is healthy. The team-leader sees the planning. The warehouse sees billable hours against awarded ZIN or PGB volume, declarations rejected by VECOZO, jobcoaching trajectories whose evaluations are running late, and the cost-per-trajectory across funders. Next to your accounting package, your roostering and your municipality contracts, Bloqs becomes the operational signal of the provider in real time.
Caseload, hours, declarations and outcomes per client, trajectory and funder.
Let Bloqs events fire the rest of the provider stack.
Use trajectory history to forecast risk and workload.
Internal tools on Bloqs data for regiomanagers and bedrijfsbureau.
A list of concrete reports, automations and AI features we have built on Bloqs Software data. Pick the one that matches your situation.
Which trajectories are running over their indicatie, and where are we still going to recover hours?
Hours booked against awarded indicatie per client and trajectory, with the remaining runway in weeks. Ranks the trajectories whose burn rate makes the next milestone tight, so the coach has the conversation with the casemanager before the indicatie runs out, not after.
How healthy is our VECOZO declaration flow this month?
Submissions, rejections and resubmissions per i-standaard message and funder, with a top-rejection-reason table. Stops the situation where finance only learns about a structural rejection pattern when the cashflow drops two months later.
Does the next quarter's caseload match the coaches we have?
Committed trajectory hours against planned coach capacity per regio and quarter, with leave hours and contract end dates on the same view. Hire-or-reassign decisions move forward to the quarter before evaluations start slipping.
Trajectory profitability per funder, declaration-cashflow health and recurring-cost structure tied to hours and indicatie data. Funder-by-funder margin moves from spreadsheet juggling to a live view of which contracts are carrying the provider.
Tender pipeline, awarded volume against contracted volume per gemeente and renewal calendar per municipality. Account conversations with municipalities lean on usage data, not on what the casemanager remembers.
Caseload, evaluation timeliness and dossier-task SLA on one board across regio. Resourcing and planning decisions are made against data, not against whichever team-leader pings hardest in Teams.
UBL invoices generated from Bloqs trajectories post into Exact Online with funder, VAT and ledger coding aligned. Finance sees declaration revenue against trajectory cost on the same ledger view, without keying invoices twice.
Providers running Yuki for the back office let Bloqs UBL invoices flow in automatically, with client and funder dimensions kept on the journal entry. Yuki stays the single source for the audit while Bloqs stays the operational system.
When dossiertaken cross their deadline in Bloqs, the responsible casemanager gets a structured Outlook mail with client, traject and direct link back. The escalation no longer depends on the team-leader spotting the red row in the planning.
When VECOZO returns a structural rejection pattern, the finance and zorgadministratie channel in Teams gets a daily summary with rejected message types, top reasons and the trajectories behind them. Cashflow risk is named the day it appears, not in next month's MT meeting.
Claude reads the dossiernotities, hours and milestones from a trajectory and drafts the evaluation report in the funder's template. The coach reviews and signs, instead of staring at an empty Word document at the end of a heavy week.
The warehouse view of caseload, declaration health and trajectory profitability lands in Power BI as a refreshed directie-dashboard, with regio and funder slicers. Board prep stops being a monthly Excel export from each module.
These are the 14 tables we currently pull from Bloqs Software into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your Bloqs Software data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Yes. The standard pull covers the core tables behind Basis (clients, invoices, internal hours, dossier tasks, leave hours) and we extend per provider for the modules in active use, including UWV reintegratie, UWV jobcoaching, Zorgcontracten and KMS. Modules a provider does not run stay out of the warehouse so the model stays clean.
Yes. Submissions, rejections and resubmissions are kept as separate events with funder, message type and reason, so declaration-health reporting is built on the actual i-standaard exchange and not on a single status field. Cashflow forecasting can take the rejection-rate trend into account directly.
We review your Bloqs Software setup and the systems around it. Together we pick the first thing worth building.