Everything in the product, and what is honestly not

Every member of staff gets their own login, and a permission grid decides exactly what each person can see and do.

Who changed what, and when — a searchable trail of logins, edits and financial actions, kept in your school's own records.

Your school's name in English and Urdu, crest, address and contact details — set once, printed on every document.

Each academic year's records stay their own: fees, results and class lists never tangle across sessions.

The school's academic structure — classes, their sections, and optional groups and shifts — that everything else hangs on.

Which subjects each class takes, each with its own maximum and passing marks.

Add your own fields and dropdown options later, without paying a developer.

The full admission form — family, B-Form, photo, previous school, fee setup — captured once.

The office's most-used screen: find any student by name, father's name, roll number or phone, and see everything about them.

Parents and guardians as their own records, linked to all their children — so siblings are handled as one family.

Move a whole class up at year end in minutes, with history kept — instead of a week of retyping.

A student who leaves drops out of the fee demand and the class lists, keeps their history, and gets their leaving certificate.

Which admission documents each child has actually submitted, and a report of what is still missing.

Families who asked about admission and have not yet joined — follow-ups, and a conversion rate that never flatters itself.

A public application form on your website feeding an approval queue — switched off until you decide you want it.

Keeping in touch with students after they leave.

Not built. A Phase-3 optional module; no part of it exists yet.

What every student owes — fee heads, amounts per class and category, due dates and grace periods before a fine starts.

The month's fee demand for the whole school — numbered vouchers printed three to a page, with student and office copies.

The cashier's screen: the counter queue handled fast, a whole family collected in one go.

A numbered receipt for every rupee taken, recording who took it — reversed if wrong, never deleted.

Reduced and waived fees tracked openly — by amount or percentage, per fee head, with the totals reported to the Board.

Unpaid balances follow the student month to month and across the year-end — and the carry-forward can be undone.

Late fines applied as a batch after the due date, and forgiven case by case when the school decides.

Who has paid and who has not — defaulter lists with parent phone numbers for chasing, the daily collection register, and the recovery percentage.

Parents paying fees by JazzCash, Easypaisa or bank transfer, approved by the office.

Not built. It waits on the choice of a payment provider — a decision, not a technical gap. Payments are recorded by hand at the counter today, and the ledger is none the worse for it.

A percentage tax applied to chosen fee heads.

Not built. The catalogue marks it 'only if legally required' — it waits on your accountant's answer, not on code.

Money in beyond fees, and everything going out — donations, rent, electricity, stationery — with monthly totals and the net position.

What the school should have collected against what it actually did — the Board's key figure, month by month.

The end-of-day cash reconciliation, with signature lines for a proper handover.

Full bookkeeping — chart of accounts, trial balance, profit and loss, balance sheet.

Not built. Simple income-and-expense books and the daily cash register are; formal audited accounting inside the system is a Phase-3 decision for schools that want it here rather than in accounting software.

Mark a class in seconds — 'all present' with exceptions — and the register feeds results, reports and parent alerts.

Staff presence recorded daily, feeding payroll deductions.

The monthly matrix with day columns 1-31, per-student totals and absentee lists the office prints.

The parent hears the same morning their child is marked absent.

Built end to end — template, daily run and delivery log. It starts messaging the day your school connects an SMS provider; until then the screen says so plainly instead of pretending it sent something.

Attendance by fingerprint or QR scan instead of manual marking.

Not built — it depends on hardware at the school gate that must be chosen and installed first.

Exams and terms defined per class, with a printable datesheet for each.

The grid teachers enter marks into — validated against each subject's maximum, with a printable blank sheet for marking on paper first.

Marks become grades by your school's own bands — configurable per school, never fixed by us.

Totals, percentage, pass or fail and class position — by the exact rules parents dispute: a student fails overall if any one subject falls below its pass mark, and tied students share a position.

The report card handed to parents, with the blocks your school wants on it and none it does not.

Merit lists, fail analysis with the specific failed subjects, subject-wise analysis, grade distribution and the annual gazette.

Exam slips printed in batches with photo, roll number and the datesheet — two to a page with a cut line.

Quizzes and exams taken on screen with automatic marking.

Not built — a Phase-3 module, beyond the day-to-day practice of the schools this product was designed against.

Every employee's record — feeding payroll, attendance and staff ID cards.

Salaries built from your own allowance and deduction heads, structured per employee.

Monthly salary runs including advances and loans — with each employee's outstanding balance shown at the moment of entry.

Leave requests, who approved them, and the balances that feed payroll.

Structured teacher evaluation, optionally including student feedback.

Not built — a Phase-3 module.

Bulk messages to parents — by class, by today's absentees, or by everyone owing more than a chosen amount.

Built end to end, templates and delivery log included. It reaches parents the day an SMS or WhatsApp provider is connected; until then every screen says 'no SMS gateway is installed' rather than showing a green 'sent'.

Ready-made messages — late arrival, uniform, missing books — personalised with the child's name, in Urdu and English, sent in one tap.

Announcements and events, published to the audiences they concern — and only when you say publish.

Holidays, the weekly off and events on a month view — with the weekly-off day your school's own choice.

Complaints logged with a category, an owner, a due date and a resolution — not a diary nobody reads again.

Real two-way chat inside the product: one thread per family, staff group threads, and internal notes a parent never sees. Needs no SMS gateway — which is why it works today.

The school's public website managed from inside the system.

Not built. A Phase-3 optional module — most schools already have a website, or want one built properly on its own.

Vouchers three to a page with cut guides, receipts, the clerk's collection sheet, and the paid and pending lists.

Result cards in several layouts, the annual gazette, merit lists and fail analysis — all print-ready.

ID cards printed in batches — for a class, or any hand-picked selection of students.

The School Leaving Certificate with its evaluation grid, plus character, transfer, bonafide and study certificates.

Change what your printed documents show — logo, signatures, and the visibility of every block — with a live preview and no developer.

The school day defined once, every section's week hung on it — and each teacher's own timetable assembles itself from the classes they take.

Homework set by section or whole class, published deliberately, and optionally marked — with an excused child never punished in the average.

The plan for each subject against what was actually taught — coverage and on-schedule reported as separate figures, so 'behind' cannot hide inside 'covered'.

Notes, past papers and links shared with a class — files kept in your school's own storage, links checked before anything is saved.

A conduct record with merits as well as demerits, points, and a fair appeal step — an overturned record counts for nothing and is kept as the evidence it was withdrawn.

Full online course delivery with quizzes and certificates.

Not built — a Phase-3 optional module, beyond current school practice here.

Zoom or Google Meet lessons launched from the timetable.

Not built — a Phase-3 optional module.

Vehicles, routes, stops and who boards where — with a vehicle over its seats shown as the safety fact it is, and fares published for the fee office.

Hostels, rooms, bed allocation and hostel fees for boarding schools.

Not built — on the roadmap for when a boarding school needs it.

The issue desk first: scan or type the accession number, issue, chase and return — with the late fine capped at what the book costs to replace.

Uniforms, textbooks and stationery over the counter — stock computed from its own movements, free issues never disguised as zero-rupee sales, and mistakes reversed rather than deleted.

A canteen till tied to student accounts.

Not built — a Phase-3 optional module for schools that run a canteen.

The visitor book kept as a fire register, the telephone log and the postal register — and nothing in any of them can be quietly deleted.

One search box — Ctrl+K — that finds any student, guardian, member of staff or screen from anywhere in the panel.

A generic, configurable report builder behind every report.

Said plainly: the forty-plus reports a school actually needs are built and in daily use, one by one. The configurable engine underneath them is not, and we count it as not built rather than pointing at the reports and calling it done.

Bring your existing registers in from Excel — column mapping, and an error preview before anything is committed.

Take a full copy of your school's data whenever you want — CSV any spreadsheet can open, so there is no lock-in.

One delivery pipeline for every alert the system sends, with a log of what was delivered and what failed.

Built. Its SMS leg reaches phones the day an SMS provider is connected — and says so on screen until then.

Your school's own words — class or grade, section or stream — and Urdu where it matters, set per institute.

What your school's files add up to against your plan — metered honestly, and never used to cut a clerk off mid-term.

The health page that can tell the difference between a job that failed and a job that was never scheduled at all — the classic silent failure, detected.

Parents see fees due, attendance, homework, notices and published results for each of their children — and can message the school and be answered.

Students see their own timetable, homework, study material and published results.

Teachers mark attendance, enter marks and set homework from a phone — scoped to their own classes and nobody else's.

Native Android and iOS apps with push notifications for parents, students and teachers.

Not built yet. The parent, student and teacher web portals are live and work on a phone; the store apps are the next stage in the catalogue's own build sequence, now that the portals have proven the API.

Logins for hundreds of parents without an IT department — bulk generation and printed credential slips.

Bulk logins and printed credential slips work today. Sign-in by SMS one-time code switches on once an SMS provider is connected.

Your school's records live in their own PostgreSQL database, completely apart from every other school's.

A new institute is created with its own address and sensible defaults, and is usable the same day — not staring at an empty system.

Each subscription tier says what it includes — students, staff, storage — and the platform enforces it.

Bytevancer invoices the institute and tracks payment — entirely separate from the fees your school charges parents, and never confused with them.

Bytevancer's own control panel for provisioning, support and platform health — with every action it takes recorded.

Your name, crest and colours — on screen and on every printed voucher, result card and certificate a parent receives.

Pass marks, fine rules, grade bands, terminology, date formats — your school's own rules, set by you, never hard-coded by us.

Every school's database backed up nightly, kept to a retention policy — and test-restored automatically to prove it can actually come back.

Built, scheduled and restore-verified. The deployment must point backups at off-site storage before they protect against losing the server itself — a copy kept on the machine it protects is not protection, and the backups screen says exactly that.

A read-only record of everything Bytevancer's own staff did to your institute — including simply looking at your data. It has no delete button, on purpose.

Several campuses of one institute under one linked view.

Not built. Each campus can run as its own institute today; a linked multi-campus view is a roadmap item.