Writing is the work that takes the longest to mark and the longest to teach back from. Writeiq is built to give you that time back, without taking the marking work out of your hands.
The questions below come from English faculties at independent, Catholic, and government schools across Victoria. They cover the things people want to know before they bring this to a Head of School or a procurement officer.
About Writeiq
Who is Writeiq for?
Writeiq is for English teachers and Heads of English in Years 3 to 12, and for the school leaders who sit alongside them and want to see what the writing data is saying across cohorts.
It was built in Australian schools first. The primary and secondary content libraries are written separately, the curriculum alignment covers nine frameworks (Victorian, Australian, IB, VCE, NESA, QCAA, SCSA, UK), and the moderation language assumes how Australian faculties actually work.
If you teach English, lead an English faculty, or are responsible for whole-school literacy, Writeiq is built for you.
Is Writeiq safe for student data?
Yes. Student writing is hosted in Australia (AWS Sydney), encrypted at rest with AES-256, and never used to train any model: ours or anyone else's.
Edsthetic complies with the Privacy Act 1988 (Cth) and the Australian Privacy Principles. We sign Data Processing Agreements with schools that need them, and our subprocessor list is public. The detail is on the security page, including incident response, data deletion, and the staff training programme.
If your procurement team has questions we have not answered there, email us and we will respond within a working day.
What does it cost?
Four enrolment tiers per product. Writeiq starts at $3,600 a year for a school of up to 300 students; Allocateiq at $2,400. Bundle the two and save approximately 25%. All prices exclude GST.
The full breakdown is at /pricing, including a buyer-led calculator for your school's size and the complete feature matrix per tier.
Pilot schools pay nothing for the first term, and lock in the lowest pricing afterwards.
Teacher judgement
Does Writeiq replace teacher judgement?
No, and we have built it on the assumption that you wouldn't want it to. Writeiq scores writing against the IWAF rubric and surfaces patterns across a class or cohort. Teachers retain the final word on every score and every piece of feedback.
The work the platform handles is the consistent dimension-by-dimension scoring and the writing of dozens of similar comments: the parts of marking that drain the week. The judgement work, the sitting with the piece, the conversation with the student, the moderation meeting, all of that stays with the teacher. That is where it belongs.
If anything, Writeiq makes moderation conversations easier, because the whole faculty is now looking at writing through the same lens.
How long does marking take per piece?
Roughly 60 to 90 seconds per piece for a typed submission. Scanned handwriting takes longer because Vision has to transcribe first, usually under three minutes for a Year 9 piece.
Teachers in the Riverside College pilot reported saving 8 to 12 hours of marking time per assessment cycle compared to marking by hand. That is not the headline; the headline is what you do with those hours. Most of them tell us they spend more time on the students who need the conference, less time on the students who don't.
This number will firm up after Term 3 2026, when we run a structured survey across pilot schools and publish the result with a third-party evaluator footnote.
What if I do not agree with the score?
Adjust it. Every dimension score and every comment is editable before you save. Your edit becomes the final record: the saved score is the score you decided on, not the one Writeiq suggested.
We log overrides quietly in the background, not as a check on you, but so that we can see where the platform's judgement and the faculty's judgement diverge. Over time, those overrides feed back into the way the rubric is calibrated and the way feedback is written. Your override does not make the score wrong; it makes the score yours.
Curriculum and standards
Does Writeiq align to my curriculum?
Yes. Writeiq supports nine curriculum frameworks across primary and secondary: Victorian Curriculum 2.0, Australian Curriculum v9, IB MYP, IB PYP, VCE, NESA (NSW), QCAA (Queensland), SCSA (Western Australia), and the UK National Curriculum.
Choose your framework once at the school level. The IWAF bands map onto your curriculum's achievement standards and language, so the report a Year 8 English teacher sees uses the descriptors and codes their school actually reports against. The full mapping is at /band-framework-correlation.
If your school uses a framework we do not yet support, tell us. The mapping work is bounded and we can usually add a framework within a term if there is a school waiting on it.
What about VCE and NAPLAN?
Writeiq is formative, not summative. It does not replace VCAA marking, and it does not replace NAPLAN scoring. Nothing in Writeiq counts towards a student's official mark anywhere.
What it does is tell you, much earlier than NAPLAN can, where the cohort is weakest. If a Year 7 group is consistently low on Text Structure but strong on Vocabulary, you know what to teach in the back half of the term, not after the results come back the following year.
For VCE, the value is the same. Writeiq doesn't give the official VCE grade, but it gives the teacher a reliable read on the dimensions VCAA assesses, weeks before the SAC.
Data and privacy
Do students need email accounts to use Writeiq?
No. Students do not need email accounts, passwords, or single sign-on to use Writeiq. This is a deliberate design decision: many primary and lower-secondary students do not have school-issued email, and mandating it would exclude them.
Three student-access paths are available, ranked from most-recommended:
- Class Links (recommended): each class has a unique signed URL minted by the school administrator. Students click the link or scan its QR code to enter Writeiq directly. The link itself is the credential, signed and scoped to a specific school and class.
- Student Access Code: a school-set code (like
ENG7AorRIVER2026) that students type once per device. The administrator rotates the code by archiving the prior task and issuing a new one for the next assessment. - SSO (opt-in): schools with mature student identity infrastructure (Google Workspace for Education, Microsoft Entra ID) may enable student SSO. Off by default; on only if the school turns it on.
The database table that stores student data has no authentication fields: no password hashes, no SSO links, no auth.users foreign keys. An optional parent-contact email column exists for end-of-task report PDF delivery, but it is never used for student sign-in. This holds across all bulk import workflows: importing a student CSV creates demographic and class-assignment data only, never an authentication identity.
Where is student data stored?
In Sydney, Australia, on Supabase Postgres running on AWS Sydney (ap-southeast-2). Data is encrypted at rest with AES-256 and in transit with TLS 1.3.
The only data that leaves Australian infrastructure during normal operation is when teachers send student writing to Anthropic's Claude API for analysis or transcription. Anthropic's API is hosted in the United States and operates under a zero-retention contract for API-submitted content: nothing teachers submit is retained by Anthropic or used to train future models. The resulting scores, feedback, and original writing samples are stored back in Sydney.
Full subprocessor list, retention periods, and the journey of each data type is on the security page.
Do you train language models on our students' writing?
No. Submission content is never used to train any language model: ours, Anthropic's, or anyone else's. Anthropic's API terms include a contractual zero-retention guarantee for API-submitted data; this is part of how Edsthetic uses the service.
The IWAF framework itself is calibrated using a separate corpus that schools opt into during pilots (currently anonymised submissions from the Riverside Demo school plus pilot schools who have explicitly agreed). When a pilot school's data is added to calibration, it is the school's explicit choice, documented in the pilot agreement, and the school may withdraw consent at any time without affecting their access to the platform.
Can my IT team verify your security claims independently?
Yes. We publish a detailed Security & Privacy Overview (PDF, v1.6) intended to give your school's privacy and IT teams the technical facts they need to populate their own Privacy Impact Assessment for Writeiq. The document covers authentication, encryption, data flow, subprocessor responsibilities, incident response, and our roadmap for independent certification.
Edsthetic does not complete or sign Privacy Impact Assessments on behalf of schools. The PIA remains the school's responsibility under departmental policy, but we provide every fact the school needs and respond to direct questions from your privacy officer within two working days at legal@edsthetic.com.au.
External verification on the roadmap: independent OWASP ZAP DAST scan in Term 3 2026, ST4S Readiness Check Term 3 2026 with badge attainment mid-2027, formal third-party penetration test in 2027, SOC 2 Type II in 2028.
Getting started
How do schools start?
Pilot first. One full term, free, no commitment to continue. We work directly with the lead teacher or Head of English, not a support queue, and we are honest about what is in beta.
The pilot ends with a conversation about whether to continue commercially. Pilot schools lock in the lowest pricing tier when they do, and a few have stayed at the pilot rate for the first commercial year as a thank-you for the early feedback.
To apply, fill out the form at the pilot section on the homepage. We respond inside two working days.
Can I import classes and staff from Compass, Edval, Sentral, Edumate?
Yes. If your school management system can export a OneRoster 1.2 CSV bundle (a standard format that Compass, Edval, Sentral, Edumate and most others support), drop the ZIP into Settings → Data import. We extract users.csv, classes.csv, and enrollments.csv from the bundle and normalise them into three pre-filled imports for you to review: classes, staff, students.
Each one runs through a dry-run validation before any data is touched. You see exactly what will be inserted, updated, or archived, plus any errors and warnings. Commit when you are happy. Per-table audit log for every import.
If your SMS doesn't do OneRoster but does do plain CSV export, you can also upload class, staff, and student CSVs separately; same validation flow. CSV templates are downloadable from the Data import tab so you don't have to guess column names.
What CSV format do you need?
Three separate CSVs with documented columns, downloadable as templates from the Settings → Data import tab inside Writeiq.
- Classes:
code, year_level, display_name, archived - Staff:
email, first_name, last_name, role, faculty, classes, archived: theclassescolumn is pipe-separated, e.g.9A|9B|10C - Students:
student_uid, first_name, last_name, year_level, email, classes, archived:student_uidis your SIS identifier; we generate one if blank, but populating it makes future imports idempotent
Headers are case-sensitive and exact. Empty cells are allowed for optional fields. The dry-run validation tells you about any rows that won't import and why, before you commit anything.
What if my CSV has errors?
You see them before any data changes. The Validate step runs a dry-run that returns a list of errors and warnings with row numbers and specific column references. Examples: "Row 14 column email: invalid email format", "Row 23 column classes: class code 7Z does not exist".
Errors block the commit until you fix them. Warnings (less serious things, like a year-level outside the supported range) you can explicitly acknowledge before proceeding.
The whole flow is reversible up until you click Commit. You can change file, change mode (merge vs replace), re-validate, or cancel entirely; no data is touched.
Why didn't my staff get their invitation email?
Most commonly: it's in spam, or your school's mail filter is blocking edsthetic.com.au because the domain is recent and your filter is being cautious.
What to check, in order:
- Ask the recipient to check their spam folder and search for
from:invitations@edsthetic.com.au. - Have your IT team whitelist
edsthetic.com.auat the school's email gateway. We supply the SES sender configuration (SPF, DKIM, DMARC) on request to hello@edsthetic.com.au. - From the Users tab, click "Resend invitation": this generates a fresh claim URL and re-sends.
- As a last resort, the admin panel has a "Copy claim URL" option per pending invitation. The administrator can paste this link into a separate email or message channel.
How do I trial it?
Two ways, depending on what you need.
To see how the platform behaves with realistic data, the Riverside College demo school is fully populated: classes, students, sample submissions, leadership analytics, the whole picture. Open app.writeiq.com.au and use the demo school access details (we share these on request, or they are in the Pilot Welcome Pack at /help).
To trial it with your own staff and students, that is the pilot. Free for a term, your data, your school, real classroom use. Apply here.
Still have a question?
If something isn't here, ask us directly.
We genuinely read every email. If you are evaluating Writeiq for your school and want to talk through how it would fit your context, whether that is moderation, faculty workload, curriculum mapping, or how to introduce it to a sceptical colleague; we would rather hear from you now than have you guess.