How to use it, all of it.

Use the institution's real registered name, address and board — a platform administrator checks them against the state register, and a mismatch is the most common reason an application waits.

You can pick a plan now or leave it; it can be changed at any time and nothing is charged through this site.

You can sign in immediately. The workspace shows a status page instead of the dashboard until an administrator approves the application, usually within a working day.

Nothing is public in the meantime — the institution does not appear in the directory and its page returns "not found".

The range is pre-selected from the level on your public profile, so a school that has already said it is a senior secondary school is not asked twice.

Nothing is ever replaced. A class you have already created is left exactly as it is and named back to you, never duplicated or renamed — and you can add the standard subjects to a class you built by hand from a button on that class.

1. Pick the range you teach — up to class 5, up to 10, nursery to 12 — and choose whether you write "Class 1" or "Class I". Every class is created, each with a section A, and each with the usual subjects for its stage.
2. Name a class teacher for every section. This is the step everything else depends on — a teacher's access to the attendance register and to marks entry follows from it, and nothing else grants it.
3. Add an academic session if the default one does not match your calendar.
4. At classes 11 and 12, add the streams you actually run — Science, Commerce, Arts — one at a time. Nothing assumes you teach all three.

A teacher who says a section is missing from their register is almost always not named as its class teacher.

One at a time, or by CSV. The importer previews every row and tells you what is wrong before it writes anything — nothing is saved until you confirm.

Only admission number, first name and class are required. Rows are matched on admission number, so importing the same file twice updates rather than duplicates.

Names, guardians, contact details and addresses are encrypted in the database. That has one consequence you will notice: search matches whole names, not fragments. "Sharma" finds Sharma; "Shar" finds nothing, because the column the search runs against is a keyed hash rather than text.

Transfers move a student between sections and keep their history. Removing a student is a soft delete — the record leaves the lists but the attendance and marks that reference it stay consistent.

Teachers hold sign-in accounts. Non-teaching staff are directory records — designation, department, tenure, qualifications, grant-aided post — and deliberately have no login.

Salaries are encrypted and visible only to school administrators. They are not merely hidden from other roles: the record built for anyone else never contains them, so a template cannot render one by accident.

Aadhaar, if you record it at all, is validated by its checksum, stored encrypted, shown as the last four digits, and revealed exactly once per request through an audited action.

Where a mail server is configured, an invitation link goes to the teacher and they choose their own password. Nobody at the school ever knows it — which is the point.

Where mail is not configured or the server refuses, you are shown a generated temporary password once, to hand over. Either way the account is marked must-change, so the credential somebody else has seen cannot survive the first sign-in.

A teacher who is locked out or has lost the invitation can be issued a fresh credential from their record.

Everyone starts present; you mark the exceptions. One save posts the whole class. It works on a phone with one thumb, and it works with JavaScript switched off.

Marking is idempotent — reopening the same day edits it rather than duplicating it. Reports break attendance down by class, section and date range, and export to CSV.

The board files every school's openings under the post itself, so somebody looking for a TGT job sees yours beside every other school's rather than having to know which schools to check. That is why the post comes from the catalogue rather than a text box — "TGT" and "T.G.T." typed into two schools' forms are two posts to a database and one post to a person looking for work.

Applicants need no account. They send a name, a phone number, what they have done, and a CV if they have one. It comes to you and goes nowhere else — no other school sees it and nothing about an applicant appears on any public page, including how many have applied.

The pay range is yours to print or not. Untick it and the advertisement says "on application" while the figures stay on your own screen.

Close a post when it is filled. It comes off both boards, stops taking applications, and everything already sent in stays. A post somebody has applied for cannot be deleted at all — that would take their applications with it.

1. Pick the post from the staff catalogue — TGT, PGT, Clerk, Lab Assistant — and write the line a jobseeker will read. It saves as a draft.
2. Fill in the rest on the next screen: openings, pay, closing date, and what you are asking for. A jobseeker reading three lines applies somewhere else.
3. Publish. It appears on your own public page and on the platform-wide board at the same moment.
4. Print the poster and put it on your notice board. The QR on it opens the application form on a phone.

One application per mobile number per post, so a double tap on a phone does not give you the same person twice.

They see attendance, homework, published results, the fee history, the bus route and hostel bed, and the notices the school sent them — read only. Nothing on those pages can be changed from their side, and there is no route that would let it be: the code says which child and says nothing about which person is holding it, so a change made there could only be attributed to "somebody with the code".

Issue a new code at any time. The old one stops working immediately, including in a browser where it was already open — that is what makes "we will issue a new code" a real answer when a code has been passed around. Withdrawing one does the same and says so on the screen the family lands on.

After eight wrong attempts the code shuts for half an hour, wherever the attempts came from. Issuing a new code reopens it at once.

1. Open the child's record and press "Issue a code" under The family's code.
2. The code is shown once on that screen. After that it is printed on every fee demand for that child, under "For families".
3. The family goes to the address on the demand and types the admission number and the code. There is nothing to sign up for.

This is the only page in the product that anyone can reach and that names a child — everywhere else, a public page carries figures and never a name. It is different because it is behind a per-child code the school issued and can take back.

Work set to a section, with a due date. A teacher sets it for the sections they mark; the office sees all of it, because the office is who a parent rings.

There is no hand-in: this product has no student or parent account, so a submission screen would be a table nothing could write to. What it keeps is the record of what was set, to whom, and by whom.

1. Lay out the school day first — the periods, their times, and which of them are breaks. Every grid in the school is drawn from that one list, so moving the lunch interval later is a single edit rather than a pass over every lesson.
2. Open a section and fill its week a cell at a time: the subject, the teacher, and the room if you use room numbers.
3. A teacher already teaching another section in that period is refused, and the refusal names the class they are with — the clash is never in the grid you are looking at.
4. Every teacher has their own week at Timetable → Teaching load → Week, which is the page to print and hand over.

The teaching-load table answers the question a timetable is usually being checked for, which is not whether it is valid but whether it is fair.

1. Create the exam and add a paper for each class and subject.
2. Teachers enter marks paper by paper. Totals, percentages, grades and ranks are computed as marks are saved.
3. Publish. Publishing locks marks entry and releases the result sheet; unpublishing reverses both.
4. Print report cards from the result sheet — A4, with the masthead, the subject table, the section average and highest, attendance and the class teacher's remarks.

An absent paper scores zero and fails that subject. To excuse an absence, remove the paper for that student rather than leaving it blank — a missing mark is "pending", never a fail.

Every mark is weighed by its exam, then added: a 25-mark test counting 20 and a 100-mark paper counting 80 land in one figure. The subject rows and the total at the bottom are the same arithmetic at two scopes, so a parent who adds the row up gets the total.

A subject is averaged only over the exams that actually tested it. Music examined once a year is not scored as though it had been sat and failed three times.

The pass mark is weighed the same way. A subject whose papers pass at 9 of 25 and 33 of 100 is judged against what the term as a whole asked of it, rather than against either paper.

A child who has not sat every counting exam — or whose marks are only half entered — reads as pending rather than as a pass or a fail, and the sheet says how many of the term's exams they have.

A subject passes on its weighted total. So a child can fail one paper, or be absent for it and score nought, and still pass the term if the rest of it carries them. That is what continuous assessment is for, and it is printed on the sheet so that nobody reads it as an error.

1. Add your terms for the year — Term I, Term II — under Examinations → Terms.
2. On each exam, pick its term and say what it counts for. Give the periodic test 10 and the half-yearly 90 and they behave exactly as percentages.
3. Publish the exams. A term adds up its published exams only; a draft is a working figure marks entry can still change.
4. Open a section from the term for its consolidated mark sheet, or a child for their own subject-by-subject record.

The weights are meant to add to 100 and the screen says when they do not, but it never refuses to save: a term with two of its three exams entered is a state you are legitimately in, and the figures divide by whatever the weights come to.

The co-scholastic half of a report card — punctuality, neatness, games — graded in your school's own words rather than out of eighty. Set the list up once, then fill a section in from the result sheet: one trait down the whole class is quicker than one child at a time.

It prints beside the marks and never inside them. A grade for neatness averaged into a percentage produces a figure that means nothing, which is why the CBSE report format keeps the two apart.

Grades are stored as the word you chose, so renaming a band changes what you grade from now on and leaves cards already printed saying what they said.

A child's whole record — every published examination, subject by subject, with the overall standing — on one printable page. Reached from a report card or a student record.

Published results only. A draft exam is a working figure that marks entry can still change, and a leaving certificate quoting one is a percentage the school will later be asked about.

Each class moves into the next one down the order on your Classes screen — that order is your own, and nothing is read out of a class name. Children in the last class pass out and become alumni.

Roll numbers are cleared, because a roll number belongs to a class; a child held back keeps theirs. Unpaid fees stay with the child and stay on the Dues screen.

An undo puts everybody back, and is refused once anything has been recorded in the new session — 800 children going back after a fortnight of attendance leaves a register full of rows against classes they were never in.

1. Add next year's academic session first, under Classes & sections. The roll-over moves the school from one session into another and cannot invent the second one.
2. Choose the year that is ending and the year it moves into, and ask for the preview. Nothing has moved at this point.
3. Read the list. Every child is on it with the class they would land in, and what they still owe. Tick anybody who is being held back or who is leaving, and redraw.
4. Type the name of the session you are moving into, and press. The new session becomes the current one.

It is not a paid feature and never will be. A school cannot start its next academic year without it, and what you pay us does not change when April arrives.

Every field is a copy taken on the day of issue. The certificate does not read through to the record afterwards, so correcting a spelling next year cannot rewrite a document already in somebody else's filing cabinet.

Issuing closes the child's year as left rather than deleting it — last year's class list still includes a child who went in November — and marks them transferred, which takes them out of the registers, the fee runs and the class lists.

A code and a QR are printed on the certificate. They open a page that confirms the school issued it and whether it still stands, and that names no child: it verifies the document, not who it belongs to.

A mistake is withdrawn, never deleted, and a fresh certificate issued. A verification that answered "no such certificate" for a document the school really issued would look exactly like a forgery.

1. Open the child — from their record, or by picking their class on the Leaving certificates screen.
2. Check what we hold. Anything wrong is fixed on the child's record and the page reloaded, so the certificate and the record never disagree.
3. Say why the child is leaving and how they conducted themselves. Nothing in this product knows either, so nothing is guessed.
4. Issue, print, sign and hand it over.

Unpaid fees are printed on the certificate and are never a reason to hold it back. Withholding a leaving certificate keeps a child out of school — the next one will not enrol them without it — and several states forbid it outright.

Your own bands and their grade points. Set these before an exam is published; changing a scale afterwards recomputes every result that uses it.

Publish an intake and it appears on your public page with a form a parent can fill in on a phone. Applications land in an inbox where you accept, reject or waitlist them, singly or in bulk, and enrol an accepted applicant straight into a student record.

Queue positions are written under a database lock, so two families submitting in the same second cannot share a place. The RTE queue is numbered separately, the reserved share is rounded up and comes out of the seats rather than sitting on top of them, and the whole queue is shown publicly before anyone applies.

The software never accepts an applicant automatically. Every decision is a person's.

1. Create the event. It stays a draft — invisible to everyone outside your staff — until you publish it.
2. Publish, and it appears on your public page and in the open-events directory with an entry form.
3. Work the inbox: accept, reject, waitlist or withdraw entries one at a time or five hundred at once.
4. On the day, check entrants in at the desk by scanning or typing their code.
5. Record placings and publish the results.

A full event still takes entries — onto the waiting list. Turning somebody away at the door loses you the person who would have filled the seat somebody else drops.

Issued in bulk from an event, to everyone accepted or to the winners. Each one gets a number in your own series and a separate random verification code.

Anyone holding the paper can check it at the verification address printed on it. A certificate is revoked, never deleted — deleting one turns a verification into "no such certificate", which is exactly what a forgery looks like and tells the holder nothing.

One-to-one and group threads between your staff. Message bodies are encrypted at rest, and a thread never crosses an institution boundary.

Being on the staff is not being in a conversation: only participants can open a thread, including administrators.

A route with no seat left refuses the next child and says how many children are on it for how many seats. Moving a child to a different stop closes their old ride rather than adding a second one — two drivers each expecting somebody the other has is how a child is left standing.

Nobody is deleted off a bus. A ride is ended on a date and kept, because "who was on that bus in August" is a question asked after something has happened.

1. Add a route, then its stops in the order the bus reaches them. A stop can carry a morning time and an afternoon time; nothing else about it is typed twice.
2. Add the vehicles and put each on a route. The seats on a route are the capacity of the buses actually running it, so a bus marked off the road stops counting towards it the moment you mark it.
3. Pick the driver from the staff register rather than typing a name. Their phone number is already there, encrypted, and it is the number somebody rings in an emergency — a second copy here would be the one that goes stale.
4. Put a child on a STOP, not on a route: the route follows from the stop. A parent says "she waits by the temple", never "she is on route 3".

Transport raises no fee demand. The fee register does that, from your fee structure — two places that can both charge for the bus is how a parent is billed twice. What this screen gives you instead is the rider roll, priced, which is what you need in order to raise those demands.

Whether a copy is out is never stored on the copy — it is the existence of a loan with no return date. Two places recording the same fact is how a library ends up with a book marked "on the shelf" that somebody has at home.

A copy already out cannot be issued again, and the refusal names who has it and since when. A book due today is not overdue: it is due at the end of the day, and fining a child who brings it in at nine is the error this is written to avoid.

1. Catalogue a book once and give it an accession number — the number written inside the cover. Further copies of the same title are added from the catalogue, each with its own number, because a library that counts in titles cannot tell you which copy is missing.
2. Issue from the desk: pick the copy, pick the borrower. Children, teachers and staff are one list, because the person at the desk knows the name and not the category.
3. Take the book back from the same screen. The fine is worked out then and written down.
4. Set how long a book goes out for, and what a late day costs, under "The school's rules". Zero means you do not fine.

A fine raised in July does not change what was charged in June. The amount is written down at the rate in force on the day the book came back, never recomputed for display.

A child boarding somewhere else is moved rather than duplicated: the old bed is vacated the day before the new one starts, so nobody is on two wardens' lists tonight. Nobody is ever deleted off a bed — a stay is ended on a date and kept, because who slept where is a question asked after something has happened.

Cutting a room's beds below the children in it is allowed and reported, not refused. The bed has really gone; refusing the edit would only leave your record claiming four beds in a room with three. The warning at the top of the hostel screen names the children who now have nowhere to sleep.

1. Add a block — a building — and say who it is for: boys, girls or anyone. A child the block is not for is refused, and the refusal names the block that would be right.
2. Add its rooms with the number of beds in each. A block's capacity is the sum of its rooms' and is never stored separately, because a figure like that goes stale the first time a room becomes a store.
3. Name the warden from your staff register. Their phone number is already there, encrypted, and it is the number somebody rings at two in the morning.
4. Give a child a bed. A room with none left is refused and says how many children are in how many beds.
5. Print tonight's roll for lights-out — one page per block, with a column to tick with a pen.

While the hostel is switched on, "Hosteller" on the student form is a statement rather than a tick: the bed list is the answer, and a second, separately editable answer is how the office and the warden come to believe different things about the same child.

There is no "stock in hand" figure stored anywhere. Stock is the sum of the movements, worked out when you open the screen — so there is nothing that can drift away from the entries behind it, which is where every stock system that has gone wrong went wrong.

Issuing more than the store holds is refused, and the refusal says how many there are. So is handing back more than somebody took: three bats out and five back would be the store believing it owns two it never bought.

1. Add an item with what you count it in — pieces, boxes, kilos — and its opening stock. The opening figure is recorded as a receipt, so the store's first number is explicable like every number after it.
2. Say whether it comes back. A cricket bat does; a board marker does not, and only things that come back appear on the "still out" list.
3. Record every movement: received, issued, handed back, written off. Each one says when, how many and who.
4. Set a reorder level and the item appears in the warning at the top when it reaches it. Zero means never warn me.
5. Count the shelf now and then. The difference is written as a correction; the entries behind it are never touched.

Nothing in the store is ever deleted. An entry made in error is reversed by an opposite entry that points at it, because a balance nobody can rebuild from the rows is a balance an auditor cannot accept.

Your public page shows testimonials and visitor ratings in two separate sections, headed "What families have told the school" and "What visitors wrote here". They are different claims — one is your account of what somebody said, the other is what a visitor wrote themselves — and a family choosing a school deserves to see which is which. It is the same principle as the compliance block, where what you declare is kept apart from what an inspector verified.

Once a piece is published its web address stops following the headline, so a link you have already sent to parents keeps working after you fix a typo in the title.

1. Write a piece, date it and publish it. A date ahead of today holds it back until then, so a notice can be written on Friday and appear on Monday.
2. Add a photograph if you have one. It is re-saved without its EXIF, so the location your phone recorded on a picture of the school gate does not go up with it.
3. Add testimonials: who said it, their connection to the school, and when. A letter from 2011 shows as 2011 rather than as this week's opinion.

This product cannot send text messages. There is no SMS gateway behind it, and rather than a button that quietly does nothing, every audience has a "guardians' numbers" download — name, class and number — for whatever you already use to send a text or a WhatsApp broadcast.

E-mail goes out through the mail server a platform administrator has configured AND proved. Until one has been proved, the send button is off and the screen says why: an untested server produces silence, and silence is indistinguishable from success.

1. Pick who it goes to — everybody, a class, a section, a bus route, a hostel block, or every family who owes fees. The list is worked out when you press send, so a child who joined the class yesterday is on it.
2. Write the subject and the message. It goes out as plain text, exactly as written.
3. Build the list. Nothing is sent yet: the next screen shows who is on it and how many have no e-mail address on file.
4. Send. About sixty go at a time and the screen tells you how many are left; press again for the next batch. A family already sent to is never sent to twice.

"No e-mail address on file" and "the mail server refused it" are counted separately and shown separately. One is your office's job and one is the administrator's, and a single "failed" figure is a number nobody can act on.

A paid run cannot be edited. Money has left a bank account, and the one document an auditor will believe is the bank statement — a record edited to disagree with it is worse than a record with a correction in it. So a mistake found after payment is fixed by reversing the run and doing the month again: the reversal mirrors every figure, both runs stay, and they add to nothing.

Basic pay is never editable on a run. It is the snapshot taken when the month was drafted; correcting somebody's pay means correcting their staff record, and letting it be changed in two places would leave the two disagreeing with nothing to say which is right.

1. Start a month. Every teacher and member of staff gets a line at the pay on their record now — the figures are copied, not looked up later, so a rise in July does not rewrite June's payslip.
2. Add allowances and deductions, set days paid for anybody who did not work the full month, and take off anybody who should not be on it.
3. Approve it. It can still be sent back to draft at this point.
4. Mark it paid once the money has gone. That closes it.
5. Print a payslip for anybody from the run.

Every figure on a run is stored encrypted, like the salary on the staff record it came from. A year of payslips one join from a name is worth more to a thief than a single current salary, so it gets the same protection.

This is not double-entry bookkeeping, and that is deliberate. What a school office is asked for is "what came in and what went out, under what heads" — a full ledger with contra accounts would be more correct and would be kept wrongly, which is worse than a simple one kept right.

Payroll posts one line for the month, for its net total, and never one per person. The payroll figures are encrypted; a plain ledger line naming what one teacher earns would undo that for the cost of a single join.

1. Start from the standard heads and change them to suit how your school keeps its books. A head is either income or expenditure, and that is what decides the direction — no figure is ever typed negative.
2. Fee receipts and paid payroll runs post themselves. On the day you switch this on, press "post anything missing" so the ledger covers the whole year rather than starting today.
3. Enter anything else by hand: a donation, a bill, a repair.
4. The statement defaults to the financial year, 1 April to 31 March, because that is the year every board and grant-giver asks about. Any two dates work.

Nothing here is ever deleted. A wrong line is reversed by an opposite line pointing at it, so the total can always be rebuilt from the rows — which is the only form an auditor accepts.

Thirty-three requirements, each citing the rule behind it. You declare; a government officer verifies. The two are kept apart on the record and on your public page, and there is deliberately no single compliance score — averaging a school's own claims into an official-looking number is the failure this feature exists to avoid.

"Not applicable" stays in the denominator. An expired certificate is not compliance, and a blank expiry reads as "not recorded", never as "valid".

Society registration with its renewal history — gaps are reported rather than smoothed over — and office bearers with their terms. Members are never loaded onto a public page.

Government grants track sanctioned, received and utilised as three separate figures, with overdue utilisation certificates flagged.

One-time charges at admission are kept out of the annual figure on purpose. Rolling them together is how "₹12,000 a year" becomes ₹31,000 in the first term without anybody lying.

Every head carries four ticks: charged once, optional, refundable, and waived for RTE. The starter sets set them the way most schools use them — the RTE waiver on everything the school requires, and off for things a family opts into like the bus or a hostel place. Check them against your own state's rules; they are only defaults.

1. Create a table and pick a starter set — government or aided, day school basic or full, or residential. The usual heads appear at zero with their frequency and treatment already set.
2. Type your amounts and save the whole table at once. Nothing is published until you say so.
3. Copy the table to your other classes, then change the amounts that differ. A class that already has a table is skipped rather than overwritten.
4. Next year, use "revise for a new session" to carry the table forward with every amount raised by a percentage, rounded to the nearest ten rupees.

A starter set arrives as a table of zeroes. Publishing one is possible — some institutions genuinely charge nothing — but you have to say so in as many words first.

Circulars from your government office arrive here and are marked read against a receipt written at publication, so an office has a denominator that does not move.

Campus albums are photographs only — no names, no faces identified.

Which pages visitors open and how many go on to apply. Counters only — no visitor identity, no IP address, no cookie. It answers "how many" and is structurally incapable of answering "who".

Every create, update and delete, with the account that did it. Encrypted values never reach the log — only the names of the fields that changed, so the trail is useful for an audit without becoming a second unencrypted copy of your records.

Trends across sessions rather than a snapshot of today: how enrolment has moved year on year, where attendance dips in the calendar, how results have shifted by class and subject.

Built from the same aggregates the public page uses, so a figure here and a figure there cannot disagree.

Result sheets, attendance reports, admission applications and event entries export to CSV from the screen you are looking at.

If your school sent an invitation, open the link and choose your own password — nobody at the school will know it. If they handed you a temporary one, you will be asked to replace it before you can go anywhere.

Accounts are not shared. A shared login breaks the audit trail, so every teacher has their own.

You see the sections you are class teacher of. Everyone starts present; tap the exceptions and save once. Reopening the same day edits it.

With a keyboard, P, A, L, V and H set the highlighted pupil to present, absent, late, leave or half-day.

One paper at a time, keyboard-driven — type a mark, press Enter, the next field is focused. Totals and grades update as you save.

Once an exam is published, marks entry is locked. Ask your office to unpublish it if something needs correcting.

You can write a remark for a child in a section you teach, and only for those children. The restriction is enforced on the server, not just hidden in the interface.

Aggregate statistics only: student and teacher counts, the pupil–teacher ratio, attendance and pass rates. No names, no photographs of identified children, no individual marks, no contact details of any student or member of staff.

A figure over a cohort smaller than the threshold is suppressed and shows a dash instead. A percentage over two students identifies two students.

Two different things, deliberately kept apart. Whether your phone number and address are printed in full is what your plan decides — a free listing keeps Call and E-mail buttons, so a parent can always reach you either way.

Whether they carry a verified mark is not for sale. The mark appears once we have actually checked: a confirmation link sent to your published address is opened, and a platform administrator rings your published number and writes down what happened.

Changing either detail withdraws its mark, and we check the new one. A school on the most expensive plan that has never opened the confirmation e-mail gets its details printed with nothing beside them, because that is the true description of that situation.

The verified mark is about your contact details reaching you. It is not an endorsement, and it is not the "Verified by …" badge an inspection produces — that one is signed by a government office.

Albums of the buildings, the labs, the grounds — the things a parent wants to see before visiting.

Photographs only. Nobody is named, no face is tagged, and a photograph of an identifiable child has no place here: the rest of this platform goes to some length to keep children out of public view, and a gallery is the easiest way to undo that by accident.

Holidays, meetings and exam windows you mark public appear on your page and in the platform-wide calendar. Competitions and fests appear with an entry form while registration is open.

Open the event and fill in the form. You get an entry pass with a code on it straight away; keep the link. If the organiser reviews entries, the pass becomes valid when they accept yours, and the page updates itself.

If the event is full, your entry joins the waiting list in order of arrival. There is no need to enter twice.

Type the verification code printed on the certificate into the address shown beside it. The page says whether it is genuine, who issued it and when — or that it has been withdrawn, and why.

Every institution currently accepting applications is listed, filterable by state and type. The form asks only what the school needs; you get a reference number and your place in the queue on the confirmation page.

Write the reference down. It is how the school identifies your application without you giving your details over the phone.

The institutions in your office's register, and nothing else. An institution outside your jurisdiction returns "not found" rather than "forbidden" — whether it exists is not information the request is entitled to.

You see what a school has declared and what has been verified, kept apart. You never see student records, staff pay or anything else the school holds privately.

Publishing a circular writes a receipt row for every institution in scope at that moment, so a school that later moves district still owes you an answer and your denominator does not move underneath you.

Record an inspection, and sign it as head of office to publish it. A signed inspection appears on the school's public page as "Verified by …" with your office named.

A scheduled inspection is never public.

A per-student plan is charged on the children marked active on the day the invoice is raised. That count is written onto the invoice and never recalculated — so an invoice you were sent in April still says what it said in April, whatever the register does afterwards.

The count is on every invoice, next to the rate, because "on how many children" is the first thing worth checking. It will not match today's register if the roll has moved since, and that is correct rather than a mistake.

Your invoices, what has been received against them and what is outstanding are all on the Subscription screen. Nothing there can be changed from your side: they are our records of what we charged you.

Nothing is charged while you are in your trial, on a free plan, or before your registration has been approved.

An invoice that looks wrong is a question for us rather than something to correct — ask through the help desk and quote the invoice number.

Ask from inside the workspace and it arrives with your institution attached, so nobody has to ask which school you are from — and the whole conversation stays on one screen instead of in somebody's inbox.

Pick what it is about: that is what decides which team sees it first, and each team has a time it is expected to answer within. If nobody answers inside that time the ticket escalates by itself to that team's lead. You do not have to chase it.

Anything a visitor writes on your public page arrives in the same list, so a parent reporting that your seat numbers are wrong reaches you rather than disappearing.

Never put a student's Aadhaar number or anybody's password in a ticket. If we need something like that to answer you, we will say so and tell you where it should go.

A standard authenticator app — scan the code, keep the recovery codes somewhere that is not the same phone. It is required on the platform console and available to every account.

The reset form is deliberately vague about whether an address exists, and tightly rate-limited, because a form that says "no such account" is a way of finding out who has one.

Repeated failures lock an account for a period. A school administrator can clear a teacher's lockout by issuing a fresh credential.

Personal fields are encrypted in the database under a key held separately from the application key. Searchable fields carry a keyed hash beside them, salted per institution — so the same person at two schools does not produce the same value, and a database dump cannot be joined across tenants.

One institution's query cannot reach another's rows: the scope is applied at the model, not remembered at each query.