File-First Transport
Sync can complete through portable media or customer-controlled file movement. LAN or WAN transport can move the same artifacts without changing the trust model.
Synchronization Architecture
Teacher spokes. Campus hubs. HQ consolidation. Offline-first by design.
Indelo synchronization is built for schools and school groups that need distributed operation without surrendering records integrity, auditability, or institutional control.
Multi-tier topology
One sync mechanism across classroom, campus, and head office.
The Indelo synchronization design uses a three-tier operating model: teacher laptops act as limited-scope spokes, campus SQL Server installations act as operational hubs, and HQ acts as a hub-of-hubs for school groups.
Each tier participates through controlled packages and durable origin identity, allowing the institution to scale beyond a single campus while preserving clear authority boundaries.
Review platform architectureTeacher Spoke
Term-scoped working setCampus Hub
Operational authorityHQ
Group consolidation and verification
Term-scoped working setCampus Hub
Operational authorityHQ
Group consolidation and verification
Why it matters
Synchronization should preserve trust, not merely move data.
Indelo treats sync as institutional trust infrastructure. Packages, scopes, guards, watermarks, and quarantine make distributed work safer instead of weaker.
Tamper-Evident Packages
Package chaining, hashes, signatures, and verification detect and refuse silent modification, replay, gaps, or out-of-order imports.
Scoped Teacher Devices
Teacher spokes receive a term-scoped working set tied to assignments, not a full school replica. The institution controls who may write what.
Hub Serialization
The receiving hub is the serialization point. Apply order is authoritative, and superseded versions survive through journal and audit discipline.
Repository Guard Parity
Synced data passes through the same validation paths as local data, including write guards, range validation, and locked-term protection.
Quarantine Instead of Silent Failure
Rejected entries are placed into review rather than quietly bypassing controls or corrupting institutional records.
Operating reality
Built for schools where power and connectivity are not guaranteed.
Indelo’s synchronization architecture turns difficult operating conditions into explicit design cases rather than afterthoughts.
Power-cut safe imports
A power cut mid-import is harmless. Sync resumes exactly where it stopped, and importing the same package twice changes nothing.
Teacher notification loop
Rejections are quarantined for administrator review — and the teacher is notified automatically, with delivery on the record.
Customer-owned data movement
No third-party relay is required to hold readable school data. Institutions move sync packages through their own devices, networks, or approved channels.
Version discipline
Packages carry migration level information so machines must converge on compatible application/database versions before syncing.
Soft-delete propagation
Operational deletes are controlled state changes rather than destructive distributed erasure.
Multi-campus readiness
To HQ, each campus hub behaves like a larger spoke whose scope is the whole campus, enabling group reporting without flattening campus authority.
Teacher and attendance workflows
Distributed teaching work without losing institutional control.
The synchronization model supports teacher-side work such as marks and lesson attendance while keeping registrar setup, locks, users, and governance under campus authority.
Per-lesson attendance can coexist with daily register workflows, allowing schools to preserve report-card continuity while gaining deeper operational visibility.
Teaching Assignment ScopeTeacher Spoke EntrySigned Sync PackageCampus Hub ValidationHQ Consolidation
Frequently asked questions
Synchronization questions for enterprise school groups.
Does Indelo synchronization require constant internet access?
No. Synchronization uses file-first packages that can move by USB, LAN share, VPN, or customer-approved transport. Network movement is an optimization, not the foundation.
What happens if power fails during import?
A power cut mid-import is harmless. Sync resumes exactly where it stopped, and importing the same package twice changes nothing.
How does Indelo prevent unsafe sync imports?
Packages are chained, signed, version-aware, and verified. Silent modification, replay, gaps, out-of-order imports, and unsafe version drift are detected and refused.
What happens when an entry is rejected?
Rejected entries are quarantined for administrator review. The originating teacher can be notified automatically on the next sync, with delivery and acknowledgement on the record.
How does HQ work in a school group?
Each campus hub synchronizes upward to HQ, allowing group-level consolidation and verification while campus hubs remain operational authorities for their campuses.
Enterprise deployment
Discuss offline-first synchronization for your institution.
Explore how Indelo can support teacher devices, campus hubs, HQ consolidation, records integrity, and multi-campus governance.