Why Suivo’s CIAW App Requires a Connection, and Why That’s the Feature, Not the Bug

Belgian sites often have patchy signal. Here’s why our Check in at Work app refuses to work without a live connection, what that means for compliance, and how to handle the no-signal corner cases in practice.

If you have evaluated more than one Belgian Check in at Work app, you have probably been told that “offline mode” is a must-have. We disagree, and so does any inspector who has ever audited an attendance record. Suivo’s Check in at Work app requires an active mobile or Wi-Fi connection at the moment of registration. This is a deliberate design choice, not a missing feature. Every CIAW record we submit to the NSSO is captured live, with a verifiable timestamp the worker cannot influence after the fact, on a device that has just been authenticated against our backend. That is the compliance posture we sell, and it is the reason we are comfortable defending any single record at audit. This article explains why connectivity-required matters, what the alternatives genuinely look like, and how to handle sites where signal is intermittent, without compromising the integrity of your registrations.

Quick Navigation

• Why connectivity-required is the right default
• The hidden risk of “offline mode” CIAW apps
• Practical options for low-signal sites
• Connectivity-required vs offline-mode at a glance
• Operational checklist
• What 2027 brings
• Managing CIAW with technology
• Frequently Asked Questions

Why connectivity-required is the right default

The Belgian Check in at Work regime exists to give the NSSO a verifiable record of who was on a site, when, and under whose responsibility. The official framework is published on the Belgian Social Security portal and detailed in the NSSO Check in at Work guidance. The whole point of the regime is non-repudiation: the record exists, the regulator has it, and the parties on the site cannot change it later.

When a registration is captured live, the workflow is simple and defensible:

1. The worker authenticates against our backend.
2. The registration, identity, site, timestamp, geolocation if available, is created on our servers in real time.
3. The NSSO submission goes out from there.

Nothing sits on a private device between the moment of capture and the moment the NSSO sees it. That is what makes the record audit-proof. The trade-off, that the worker needs a live connection to register, is a price worth paying for an attendance record that no party can manipulate after the fact. The Belgian Data Protection Authority guidance also rewards systems that minimise local storage of personal data; connectivity-required is the cleanest way to honour that.

⚠️ Important regulatory note: A CIAW registration that can be edited locally before sync is, from an inspector’s perspective, a registration that can be backdated. Belgian fines for CIAW violations can reach significant criminal sanctions per offence; the integrity of the record is what defends you when an inspector asks “how do you know this timestamp is true?”. Always design your process around verifiable evidence, not just captured data.

The hidden risk of “offline mode” CIAW apps

Apps that promise full offline registration usually work like this: the registration is written to local storage on the worker’s phone and synced “later.” That sounds harmless until you ask the obvious question, who controls the device between capture and sync?

❌ Registrations sitting in unencrypted-or-decryptable local storage for hours

✅ Registrations created server-side the moment the worker authenticates

❌ Timestamps that depend on the worker’s phone clock

✅ Timestamps stamped by our backend, not by a phone you don’t own

❌ An “offline queue” the worker can theoretically clear, edit, or delay

✅ A live record that exists in our system or doesn’t exist at all

This is not a hypothetical. Apps that ship aggressive offline modes are exactly the tools an inspector will challenge first, and they are the tools most likely to be implicated in disputes over backdated registrations. The “offline” feature your competitor sells you is usually the audit risk that surfaces in year two.

Practical options for low-signal sites

Belgian construction, infrastructure, and rural work do have signal gaps. We do not pretend otherwise. The honest answer is that there are several proven ways to keep connectivity-required compatible with real sites, none of them require us to ship offline mode.

4. Cellular site poles. Suivo’s physical site poles carry their own SIM and connect directly. The worker scans, the pole submits over its own cellular link, the worker’s personal phone signal is irrelevant.
5. Vehicle-tracker handshakes. On sites reached by company vehicles, Suivo’s vehicle tracking hardware can register the workers in the vehicle as they arrive, using the tracker’s own cellular connection. Particularly effective for crews who move between sites.
6. Foreman tethering or MiFi. A foreman’s phone or a dedicated MiFi unit can act as the site hotspot for the morning rush. Plan it the same way you plan a generator: budgeted, maintained, and tested before day one.
7. Site survey before mobilisation. Most Belgian sites have at least one network bar somewhere on the perimeter. Map it during the site setup so workers know exactly where to register.
8. Sites that genuinely cannot connect. Deep tunnels, full Faraday-cage industrial halls, or some remote infrastructure work may not be a fit for any live-CIAW solution, including ours. If you operate primarily on those sites, talk to us about whether the construction industry configuration we’d typically recommend actually fits, or whether the obligation pattern argues for a different setup.

This last point matters: we would rather walk away from a site than ship a feature that lets a worker register from anywhere with any timestamp. The cases where connectivity-required does not fit are rare in Belgium, and being explicit about them protects the integrity of the cases where it does.

Connectivity-required vs offline-mode at a glance

Property	Connectivity-required (Suivo)	“Offline-mode” CIAW apps
Where the registration is created	Backend, in real time	Local storage on the worker’s phone
Who controls the timestamp	Backend clock	Phone clock
Can the record be backdated before sync	❌ No	⚠️ Depends on the app’s design
Defensibility at NSSO audit	✅ Strong, every record is server-stamped	⚠️ Variable, auditor will probe sync delay
Suitable for sites with zero connectivity anywhere	❌ Not without a site pole or hotspot	✅ At a compliance-integrity cost
Risk in chain-liability disputes	✅ Low	⚠️ Elevated where sync is delayed

Connectivity-required is a deliberate trade-off: slightly more operational planning, materially stronger evidence.

Operational checklist

Survey each new site for cellular coverage during mobilisation, not on day one.
Where coverage is patchy, deploy a Suivo site pole with its own SIM at the main access route.
For crews moving between sites, use vehicle tracking handshakes so the connection lives with the truck, not the phone.
Brief foremen and subcontractors on the connectivity-required design before they arrive, the Suivo CIAW FAQ is a useful single-page reference.
Pair CIAW with integrated time tracking so the live record flows directly into payroll without an intermediate file.
Where a site mixes construction and cleaning operations, configure Check in and Out at Work (CIAO) for the cleaning crew on the same platform.
Treat any unexplained capture gap as an operational incident, investigate the cause, document it, fix the network or hardware setup.
Plan the rare “no-coverage-anywhere” case openly with the customer; honesty beats overpromising.

What 2027 brings

Belgian time-registration obligations are widely expected to expand in 2027 to cover every employer with a daily working-hours record, on top of the existing CIAW regime. The detailed legal route is still being worked out and is worth tracking via official channels rather than blog summaries; what matters operationally is that the same data-integrity questions will apply to time records as already apply to attendance.

Three planning points:
Verifiable timestamps matter more under the broader 2027 regime, not less.
Tools that already integrate CIAW with time tracking and asset management will have less to retrofit.
Customers running mixed sectors, construction, concrete, transport, benefit most from a single connectivity-required platform.

Managing CIAW with technology

Suivo, a Belgian IoT and compliance company with over 15 years of experience, builds CIAW tooling around a clear principle: every registration is created live and is defensible at audit. The platform helps you:
Capture registrations server-side via the Check in at Work app, with backend-stamped timestamps.
Solve low-signal sites with site-pole hardware that carries its own SIM rather than relying on the worker’s phone signal.
Extend the same data-integrity model to vehicle tracking handshakes for moving crews.
Cover the cleaning sector’s full entry-and-exit requirements via CIAO without changing the integrity model.
Push verified hours straight into SD Worx, Partena, Acerta, and your ERP through the time tracking integration.
Provide a chain-liability view for main contractors managing many subcontractors, with construction industry configurations tuned to the Belgian regime.
Offer NL/FR/EN local support from a Belgian team that can talk through the live-capture trade-off honestly when a customer is comparing tools.

Suivo’s platform is in production with Belgian builders and operators including Hoogmartens, Cegelec, and Antwerpnatie, who run CIAW alongside asset management and vehicle operations under the same connectivity-required model.

“We deliberately chose a CIAW vendor that does not promise offline mode. The audit story is much cleaner, every record we present to an inspector is a server-side record we can defend, not a phone-side queue we have to explain.” –  Compliance Lead, mid-sized contractor evaluating CIAW tools, Antwerp region

Take Action Today

Don’t let “offline mode” marketing pull you toward a compliance posture you can’t defend. Start by mapping which of your sites genuinely lack reliable connectivity, plan a site-pole or vehicle-handshake deployment for those, and brief your foremen on the live-capture model before mobilising the next project.

For more information on connectivity-required CIAW and how to set it up on real Belgian sites, contact Suivo at +32 3 375 70 30 or visit the Suivo CIAW solution page to see how the platform combines live capture with practical hardware options. You can also explore the full product range, check current pricing, or book a demo.

Free Connectivity Planning Checklist

Want a printable reference to plan CIAW connectivity before your next site mobilises? Our free Connectivity Planning Checklist condenses this article into the survey questions and hardware options that resolve most low-signal scenarios.

Inside, you’ll find:

The five questions to answer during site survey, before mobilisation
How Suivo helps with site poles, vehicle handshakes, and live capture
Real-life lessons from sites operated by Hoogmartens, Cegelec, and Antwerpnatie
A simple decision tree for the rare “no-coverage-anywhere” scenario

Frequently Asked Questions

Does Suivo’s CIAW app work without a mobile signal?

No, and that is the design. Every registration is created live on our backend, so a worker’s device must have a connection at the moment of capture. The Check in at Work solution covers low-signal sites with hardware options like site poles and vehicle-tracker handshakes rather than local storage.

Isn’t offline mode a standard feature in modern apps?

In many product categories, yes. In CIAW it is a compliance trap. A registration stored on a phone before sync is, by definition, editable somewhere in the workflow. Inspectors know this and audit accordingly. The trade-off we have chosen, live capture, with practical hardware for low-signal sites, is what makes our records defensible. See the Suivo CIAW FAQ for how this comes up in conversations with the NSSO.

What about a site with literally no signal anywhere?

Use a Suivo site pole with its own SIM, or rely on a vehicle-tracker handshake at the access route. In the rare cases where neither works, for example, deep tunnel work with no surface access, talk to us before mobilising. We would rather scope honestly than promise a fit that compromises the record.

Will this change when the 2027 time-registration rules arrive?

We expect the data-integrity bar to rise, not fall. Tools already built around live capture will need less reconfiguration to meet the new regime, and the integration between CIAW and time tracking becomes more valuable, not less. The connectivity-required model is the one we expect to age well.