LLatticeworkSCHOOL MANAGEMENT, CONNECTED

Implementation

A thoughtful start.
A practical rollout.

Use a guided walkthrough to define your scope. Setup, data preparation and acceptance depend on your school’s structure, records and chosen modules.

  1. 01

    Discovery

    Map the school you actually run.

    Identify branches, academic sessions, teams and permissions. Walk through admission, fee, academic and campus-service processes, including approvals and exceptions.

  2. 02

    Data & configuration

    Get the foundations right.

    Review and map student, guardian, staff and opening fee records. Confirm ownership, duplicates and historical sessions. Agree an import approach and validate a sample before any migration.

  3. 03

    Integrations

    Connect only what you need.

    Configure school-owned payment and communication accounts, approved templates and webhook endpoints. Optional Google road planning requires additional keys, billing and location-sharing review.

  4. 04

    Acceptance & introduction

    Prove the workflows with your team.

    Validate permissions and selected journeys with representative test records. Review receipts, report cards, payroll and operational outputs. Train users by role and agree the rollout sequence.

Migration scope, delivery dates, support arrangements and commercial terms are agreed for each institution. This website does not promise an automatic migration or a fixed deployment timeline.

Before your demo

Bring your
everyday questions.

Your branch structure, student count, fee process and priority modules help make the walkthrough useful. Please share a description of your needs, rather than student records or payment credentials.

Request a walkthrough

A useful starting checklist

  • Number of branches and academic sessions
  • Teams and their access responsibilities
  • Current tools and data formats
  • Fee and finance approval processes
  • Parent communication requirements
  • Modules to introduce first

Common questions

The details, answered.

Does Latticework support more than one campus?

The application supports branches, branch grants and academic-session context. The exact setup and school-wide access should be agreed and validated for your institution.

Is there a parent mobile app?

There is a responsive parent web portal with linked-child access. This site does not claim a native iOS or Android app-store application.

Can parents pay fees online?

The application includes Razorpay checkout, verification and reconciliation workflows. Your school’s provider credentials, webhook configuration and live acceptance checks are required before enabling real payments.

Does transport include live bus tracking?

No. The current module manages fleet, routes, assignments and draft planning. Estimated planning uses geographic distances. Optional Google road routing is a configured pilot; live GPS tracking is not included.

Are SMS and WhatsApp ready to send immediately?

These integrations require school-owned credentials, approved provider templates and the relevant communication consent. Provider acceptance and actual delivery are distinct; live delivery needs validation.

Can you migrate our existing records?

The source data, mapping, history and validation requirements need review first. Agree the migration scope and sample acceptance as part of your implementation plan.

How much does it cost?

Request a scope-based discussion covering your institution size, enabled modules, integration needs and rollout. No unverified package prices or service guarantees are published here.

Your school. Your workflows.

See how it all connects.

Walk through the modules, roles and setup your institution needs.

Plan your walkthrough