A new school operations platform

One clear view of the school day.

SchoolSync is being designed to connect student attendance, staff records, fees, expenses, and the principal's daily review without forcing schools through a maze of unrelated modules.

Shape the pilot with us Explore the workflow

Early conversations are open with school leaders and administrators.

Tuesday · Daily brief Good morning, Principal

Concept

08:31Gate activity

12Needs review

₹Fee desk ready

Attendance events, exceptions, and office work in one morning view.

Designed around four moments that decide whether a school system is useful.

01 Morning gate
02 Front office
03 Fee counter
04 Principal review

Follow the work, not the menu

From the first arrival to the final review.

Our first release is planned around the flow of a real school day. Each action should leave a clear record and each exception should have an owner.

7:45 AM
Students arrive with a QR identity
A school-controlled device records the arrival. Duplicate, unknown, and delayed events are surfaced for review.
Gate operator
8:00 AM
Staff check in at the campus
Face-based attendance is planned with clear enrollment, retry, manual review, and a non-biometric fallback decision.
School admin
11:30 AM
The office records fees and expenses
Receipts, adjustments, dues, fund entries, evidence, and approvals follow one traceable process.
Accounts team
3:30 PM
Leadership reviews the day
The principal sees attendance exceptions, collection activity, pending approvals, and items that need action.
Principal

Initial product focus

Attendance, people, and money should tell the same story.

Concept illustration of a school office using SchoolSync on a laptop

Product concept

The daily brief

Start with what needs attention.

A useful dashboard should lead with late arrivals, unmatched scans, pending corrections, fee activity, and approvals instead of decorative charts.

Student QR attendance

Issued identities, school-managed scanning, timestamps, duplicate protection, an exception queue, and a defined offline sync path.

Explore attendance

Staff profiles and payroll

Staff profiles, campus assignments, leave context, salary calculation, disbursement, and carefully governed face enrollment.

Explore people and payroll

Fees, expenses, and funds

Fee plans, thermal and email receipts, dues, payments, expenses, audit history, and analysis designed for reconciliation.

Explore fees and finance

Communication and data tools

WhatsApp dues alerts, email delivery, controlled imports, useful exports, and delivery or job history.

Explore communication

Built with each role in mind

The same day, seen at the right level.

SchoolSync is planned around scoped access. People see the information required for their work, with sensitive changes attributed and reviewable.

Principal

Exceptions, staffing, collections, approvals, and a concise daily view.

Administrator

Students, staff, classes, devices, identities, and record corrections.

Accounts

Charges, receipts, dues, expenses, funds, and closing reports.

Teacher

Assigned classes, student register, own attendance, and leave context.

Responsible by design

School records deserve decisions before features.

Children's data, staff biometrics, and financial records cannot be treated as ordinary form entries. These safeguards are requirements for the build and pilot.

Minimum necessary data

Define why each field is needed, who may see it, and when it should be removed.

Tenant and campus boundaries

Enforce school and campus scope on the server for every operational record.

Human review

Require reasons and suitable permissions for corrections, reversals, overrides, and sensitive changes.

Evidence before claims

Publish security, compliance, uptime, and customer claims only after the implementation proves them.

Questions from school leaders

What is decided, and what comes next?

Is SchoolSync available to use today?

SchoolSync is currently in product definition and landing-page preview. We are speaking with school leaders to validate the first workflows before a pilot release.

What is planned for the first release?

The proposed first scope covers school setup, role-based access, student and staff records, QR student attendance, staff attendance, fees, expenses, and a management summary. The final pilot boundary will be confirmed with participating schools.

Will it work when the internet is unreliable?

Offline attendance is a design requirement, not a released claim. It will need idempotent sync, visible conflict handling, and testing on the actual devices and networks used by pilot schools.

How will biometric and child data be handled?

The build plan calls for data minimization, strict role scope, protected biometric templates, explicit lifecycle decisions, audit events, and legal review before launch. Detailed choices will be published only after they are implemented and verified.

Can a school help shape the pilot?

Yes. We are looking for practical feedback on arrival, attendance correction, staff enrollment, fee collection, expense approval, reporting, onboarding, and support expectations.

Help shape SchoolSync

Tell us how your school day actually works.

We will use the conversation to understand your attendance, office, and finance workflows. This is an early product discussion, not a software sign-up.

vyapartechstudio@gmail.com