Frequently asked questions

An integrated school system: attendance, grades, teacher time logs, announcements, calendar, reports and the school office — in one app your staff and students already sign into.

K–12 and similar schools in the Philippines. Day to day it serves school admins, registrars, principals, teachers, students and (on higher packages) parents.

One Gradwit site can host many schools. Each school has its own people, classes and records; schools cannot see each other’s data.

No. Gradwit helps you keep the records those forms need and can print common school forms (for example SF2, SF9 and SF10 on Advanced). Your division’s rules still apply.

No. Staff and students use a modern browser on a phone, tablet or computer. Clock-in uses a shared station page that shows a rotating QR code — a spare tablet or desktop in the faculty room is enough.

Three packages. Every school gets the core (accounts and roles, people, classes and terms, audit log, two-step sign-in). Features on top depend on the package:

Your vendor sets the school’s package and can switch individual features on or off.

Yes. Many schools begin on Basic for attendance, grades and clock-in, then move up when they want report cards, a parent portal or messaging.

Most of it is. A few Premium/Advanced items (for example online payments and a general AI assistant) are still on the roadmap and are not switched on until they ship.

With a login ID (often the student or employee number) and a password. There is no school code to type: the account already belongs to one school.

They get a temporary password (usually on a printed slip), choose their own password, and — unless they are a clock-in station — read and accept the privacy notice.

Ask the registrar or school admin. They reset it in Users and Roles; Gradwit does not email a reset link on Basic (many students have no email yet).

After five failed attempts the account locks for about 15 minutes, then opens again by itself.

Yes for staff. School Admins are encouraged to turn it on (authenticator app plus recovery codes). Another admin can switch it off if someone loses their phone.

Open the class for that session, mark each student (or mark the rest present when you are done), and save as you go. Incomplete sessions stay incomplete until everyone has a status. Saves can wait on the phone if the connection drops, then sync when it returns.

Usually until the end of the next school day. After that, only people with permission to edit past attendance can change it, and a reason is kept in the audit log.

On Basic you enter a term grade per student, submit the sheet, and someone else approves it. On Advanced, a gradebook can turn quizzes and tasks into the term grade using the school’s formula. Students only see grades from approved sheets.

A station in the school shows a QR code that changes often. You scan it while signed in on your phone to clock in or out. Times come from the server, so the station does not need a correct clock. Missed clock-outs can be corrected with approval.

On Premium, yes: DepEd-style DLPs and DLLs, optionally drafted with AI, edited as one document, printed, and submitted for checking.

Their own dashboard, grades (once approved), attendance, announcements and calendar items meant for them — never other students’ records.

On Advanced, a parent portal lets linked parents view their children’s grades, attendance, schedule and more. On Premium they can also message the teachers who teach those children.

No. Draft and submitted grades stay with the teacher until the sheet is approved. Then students (and parents, when the portal is on) can see them.

Roles and permissions. Default roles (Teacher, Registrar, Principal, School Admin) are seeded and editable except School Admin. Menus only show what someone may use; the server still checks every request.

Yes. CSV import for students and staff (with a dry run that lists bad rows), printable credential slips, and — on Premium — bulk edits from a spreadsheet.

Depending on the package and permissions: school register and movement forms, monthly attendance (SF2), promotion (SF5), progress report cards (SF9), permanent records (SF10), and related reports. Advisers can print for their own section where the form allows it.

Yes. Important changes (people, grades, roles, settings, logins and more) are logged with who, when and what changed. The log cannot be quietly edited.

Yes. A School Admin can download the school’s data as CSV (data portability).

Yes. Attendance, scanning to clock in, and student views are designed for small screens first.

One-by-one attendance and score cards keep each save on the device until the server has it, then send them in order when the connection is back.

The product UI is in English today. AI lesson plans (Premium) can be written in English or Filipino when that feature is on.

Schools only collect the fields the system is built for. Access is permission-based; sessions expire; passwords are hashed; the connection is HTTPS. Philippine privacy law (RA 10173) still applies — the school remains the personal information controller.

No. Isolation is enforced in the database so a mistake in a query cannot leak another school’s rows.

On managed cloud infrastructure in a region close to the Philippines (Singapore), so pages stay responsive during school hours.

Daily backups of the database and uploaded files, kept for a set retention period, with a restore process the vendor can run if needed.

The vendor creates the school, picks a package and issues the first School Admin account. That admin finishes setup (year and terms, levels, subjects, sections, people) using the in-app guides and CSV templates.

Plan a couple of weeks before classes: school admin setup, a short office walkthrough, a faculty orientation (sign-in, clock-in, practice attendance and grades), then student sign-in in the first week.

Day-to-day account help (password resets, lockouts) is handled by the school. Product and hosting questions go to the vendor who runs your Gradwit site — or write [email protected] / [email protected].