Career assessment across every school in your district, on one licence priced per enrolled student.

One organisation account for the district, and this is the honest limit to plan around: there is no school or building entity underneath it. Everyone you add as an administrator sees everything in the organisation. What separates one group from another is the class code — you generate a separate code for each school, each year group or each programme, and every result carries the code it came in through. That works, and districts run it, but it is a naming convention rather than a permissions boundary. If your requirement is that a counsellor at one school must not see another school's named students, we do not meet it today. Say so early and we will tell you where that sits rather than discover it in your security review.

Students are never billed personally, and taking an assessment is free to the student. There are two units, and which one suits you depends on how much of the roll you are testing. The monthly plans are metered per billing period: Team is $79/mo and covers 80 assessments a period, Scale is $199/mo and covers 200, Growth is $999/mo and covers 1,000. There the unit is an ASSESSMENT — every instrument you assign spends one, so a student taking four spends four — and one arriving on a class code counts exactly the same as one you emailed. When the ceiling for the period is reached, the class-code page stops admitting new people. So a 4,000-student district is not a $199/mo deployment: it is either staged across periods, or it runs on the Education Licence, which is the second unit — one rate per enrolled student for the academic year with assessments uncapped, priced by enrolment band and invoiced against a purchase order. The bands are on this page, so you can multiply your own enrolment and arrive at the price before you talk to us. Per enrolled student the licence is dearer than the monthly plans, and that is the design rather than an oversight: the plans meter individual assessments for hiring and coaching, while the licence covers the whole roll for the year with assessments uncapped, retakes included, the career and skills corpus licensed with it and no ceiling to run into in March. The one place a monthly plan covers a school's own students is below the licence floor, where there is no licence to quote at all.

You can use the underlying data; you cannot press a button and get a submission. What comes out is a CSV of results — who completed what, when, and their outcome — plus a PDF summary with cohort distribution and RIASEC and Big Five averages. That is the raw material a programme lead maps into whatever template the state expects. What does not exist, and what other vendors do offer: there is no EdFacts-formatted export, no state-SIS-shaped file, no CCRI indicator calculation and no year-over-year progression view. Reports carry outcomes rather than individual item answers.

No. There is no SIS integration of any kind — no roster import, no bidirectional sync, no connector for PowerSchool, Infinite Campus, Skyward or anything else, and none is in progress. Your SIS stays the canonical career-readiness record and JobCannon stays beside it. The only path from our data to yours is the CSV export, which your team maps by hand. If a vendor comparison has SIS sync as a scored requirement, we lose that line, and it is better that you score it correctly.

Sign-in is Google, and that includes Google Workspace for Education accounts, because those are Google accounts. There is no SAML, no Microsoft Entra ID, no Clever, no ClassLink, no Okta, and no SCIM or OneRoster provisioning. Counsellors are added one at a time as organisation administrators — there is no bulk staff import. Students on a class code do not sign in at all in the usual sense: they enter the code and pick their own username, and no email address is collected from them.

Honestly: you roll it out, we do not. There is no implementation service, no parent-communication template and no recorded training course — describing one would be inventing a deliverable. The one written classroom artefact that does exist is six 45-minute lesson plans for grades 6-8, two per grade, cited against the Arizona ADE eCTE standards and sitting in the coordinator resources area; there is nothing equivalent for grades 9-12, and no playbook wrapped around them. What the platform gives you is that a rollout needs almost no configuration: generate a class code per school or year group, share it, and students are answering within seconds with nothing provisioned per student. Where you want per-person tracking and automatic chasing instead, paste an email list and each person gets a single-use link plus up to three reminders on an interval you set between 1 and 14 days. We will get on a call with your programme lead and help you plan it; we will not pretend a delivery team exists.

The COPPA posture is data minimisation rather than parental consent, and the distinction matters for a district. On a class code we collect no email address and no demographics — a student enters a code and picks a username — and the production posture carries no third-party advertising trackers, no voice or video capture, no precise geolocation and no peer-sharing feature, which is what the FTC's enforcement record actually turns on. What we do NOT have is a verifiable-parental-consent workflow for under-13s; if your district requires one, that requirement is unmet. FERPA-aligned school-official handling and a signed Data Processing Agreement are in scope for a district engagement, students can delete their account and the data attached to it, and we do not sell student data. Data is resident in the EU; residency is not selectable, so there is no US-only option for a district that requires one.

Partly, and it is worth knowing which part. From Scale upward, exported PDF reports carry your logo instead of ours, and the share page a student lands on carries your organisation's name and colours. A district-owned domain such as careers.yourdistrict.edu is not a self-serve setting — it is a manual DNS-and-hosting setup we do by hand for a district engagement, so treat it as scoped work rather than a switch. Language is independent of any of this: the platform ships in English plus 22 additional languages live in production, Spanish among them.