question.software · the classroom front door

Write questions. Run them with a class. Review responses.

question.software is the classroom application in the question.* family. Two parts of the loop run today: a signed-in teacher authors an activity, and a student opens an opaque share link and submits a response with no account and no roster import. Two parts do not: launching by a human-readable class code is not built, and reading the responses back as the creator is built and switched off — the route is registered and refuses, naming its reason, because no store supplies the feed. Roster-linked student history was not measured for this page.

Talk to us about question.software See the workflow →

Powered by question.technology, the shared question-authoring and response engine behind the question.* family. This page renders no checkout, no card field, and no price. Every capability below carries one of four states: running, built and switched off, not built, or unmeasured.

Powered by question.technologythe shared authoring and response engine for the question.* family

Author and submit run todayregistered authoring routes for a signed-in creator, and a public submit route a guest reaches through a share link

No roster to startthe running guest path takes a submission with no roster import and no student account

No checkout on this pageno card field, no price, and nothing here can charge a school

One engine, several branded front doors

question.technology is the shared question-authoring and response engine behind the question.* family — front doors such as question.consulting, question.management, and question.company, each aimed at a different buyer. These are branded front doors, not separate companies or separate codebases: they share one engine, one security model, one support operation, and one roadmap. question.software is the practitioner front door — the daily classroom author-to-response workflow, rather than an explanation of the shared engine.

Powered by question.technology. A school pays for the underlying platform and the capabilities it selects, so it does not pay repeatedly for the same engine through different brands. Each page states each capability as running, built and switched off, not built, or unmeasured.

The critical path

From question to response

A question begins as authored content and ends as evidence a teacher can use. Two stages of that path run today and two do not, so each stage below carries its own state rather than one label for the whole loop. The complete author-to-response loop has not been observed running end to end.

Author

Running

Write the prompt, answer choices, answer key, explanation, and source in one place. This is the built path: a signed-in creator posts and reads questions, question sets, and question types through the question.technology authoring routes, and those routes are registered in the API and gated so authentication runs before anything is read. The system does not verify factual accuracy, so the author remains responsible for the content -- there is no AI checking or generating your questions.

Review

Individual preview unmeasured; department approval unmeasured

A teacher reopens and rewrites their own questions through the authoring routes, which are running. A dedicated preview-and-revise surface, and formal department workflows -- assigned reviewers, approval states, restricted publishing -- were not measured for this page, so this page says unmeasured rather than guessing in either direction.

Launch by share link

Share link running; class code not built

Choose the questions and mint an opaque share link, which resolves to the activity for anyone holding it. That is the launch mechanism that exists: the share-link mint and the token resolve are both registered in the API. A human-readable class code -- mint, expiry, collision handling, and abuse controls -- is not built; a search of the question.technology routes and store for a class-code, session-code, room-code or join-code identifier returned nothing while a control key in the same files returned hits.

Join

Running

A student opens the share link and submits a response without creating an account. This is the built path: the public submit route stores the answer, runs moderation on the server rather than trusting the browser, and is rate limited. A guest submission carries a session label, not a verified permanent student identity, and it does not follow a student into another class or school year.

Results

Creator results built and switched off; longitudinal history unmeasured

The creator-facing responses read is registered and owner-scoped, and today it refuses: it answers 501 qt_creator_submissions_unavailable because the store method that would supply the responses feed is not implemented. That refusal is deliberate -- an all-zero feed would be indistinguishable from a teacher who truly has no responses, which is a lie the route will not tell. Longitudinal reporting, automated scoring, and exports were not measured for this page.

Start without setup debt

The plan is that a teacher can author an activity, preview it, launch it, and join once as a student without importing a roster or creating student accounts. That first run is deliberately small: it is meant to prove whether the workflow is useful before a school commits time or student data.

Share-link participants are guests for that session. Their names are not verified, and their results do not automatically follow them into another class or school year. A guest session needs enough of a label to tell responses apart during that session; it does not become a permanent student profile.

The running guest path works without a CSV roster upload, so a school is not asked to hand over student data before the workflow has proven useful to that one teacher.

Add roster-linked history only when the school chooses

Connecting roster identities for persistent progress, class history, or reporting across activities is unmeasured on this page: it is not claimed here and its absence is not asserted here either. What is true today is that the running guest path stores a session label and does not convert guest activity into a permanent student profile.

Classroom moments

Three ordinary classroom moments

The classroom loop is aimed at the low-stakes moments a teacher already has, not at high-stakes testing. Each moment below says which of its steps run today and which do not.

None of the three has been observed running end to end for a real class, and each is written with that stated rather than implied.

Quick check

Write two or three questions midway through a lesson, hand out the share link, and collect responses without importing a roster -- enough to decide whether to continue, explain the idea differently, or give another example. Authoring and guest submission both run today; reading the responses back as the creator refuses today, so this moment is only partly served.

Exit ticket

Launch a short activity near the end of class through a share link. Guest participation runs today for classes that do not need persistent student accounts or longitudinal records. Reading the submissions back through the creator-facing route is switched off, so what students submit is stored and the product does not return it to the teacher.

Review day

Bring questions from several lessons into one review activity and run them with the class. Saving questions and question sets runs today through the authoring store; organizing and reusing them, and department-level shared libraries and approval workflows, were not measured for this page.

Build a lasting question library

The plan is to keep useful questions — and the reasoning behind them. Each question can carry its answer key, explanation, source, and author, so the next teacher can judge where it came from. These three capabilities are deliberately not bundled: each is marked available separately, only after it has been observed working end to end.

A common worry is that "library" quietly means a shared district database from day one. It does not. Saving a question or a question set runs today in one teacher’s own space through the authoring store. Organizing and reusing were not measured for this page, and each of the three carries its own state rather than one bundled claim.

Save

Running

Retain an authored question or question set so it can be reopened later. This is the running authoring store: question and question-set records are created and read through the registered authoring routes.

Organize

Unmeasured

Grouping saved questions by subject, unit, course, or a teacher-defined label was not measured for this page. It is neither claimed nor denied here.

Reuse

Unmeasured

Copying a saved question into a new activity without changing the original was not measured for this page. It is neither claimed nor denied here.

Sources and explanations are authored on the question record itself, which is the running authoring store. Whether a completed session result stays tied to the exact version a student received — delivered-version immutability — is unmeasured on this page and is not claimed. Version comparison and restoration, department review states, and approved shared libraries are unmeasured too, so this page does not claim a department has one governed source of assessment content.

Share link to stored responses

From a share link to stored responses

The teacher mints an opaque share link; students open it and submit responses without accounts. Both halves run today. A submission carries a session label, not a verified permanent student identity, so it does not become named history on its own.

A reasonable concern is whether responses silently count as an official grade. They do not: a submitted response is evidence of what one guest session recorded, never an automatic grade-book entry.

Reading those responses back as the creator is built and switched off. The route is registered and owner-scoped, and it answers 501 qt_creator_submissions_unavailable because no store implements the responses feed. That refusal is the design: returning an empty feed would be indistinguishable from a teacher who genuinely has no responses, and the route will not tell that lie. Automated scoring, exports, longitudinal reports, and delivered-version immutability were not measured for this page.

Privacy & data handling

Less student data by default

The shared question.technology response path takes responses that do not require a respondent account, and that is the path running today: a guest reaches an activity through an opaque share link and submits without a student account and without a roster import.

The design does not call for advertising identifiers, cross-site tracking, or device profiles used for marketing. It will still keep the operational records a service needs to run and to protect itself — so this page does not claim “no tracking” as an absolute. The distinction is deliberate: prohibited advertising and device profiling on one side, documented operational logs on the other.

A share-link session stores the activity, the submitted responses, a limited session label, and those operational records. The submit route is documented as carrying no student identifiers: it does not need a student email address, an advertising ID, or a persistent device identity to let a guest answer a question.

The honest answer to “what data leaves the classroom” is: only what this page already lists. CSV export, third-party API sync, and an SFTP feed are unmeasured on this page and none is offered here.

Designed for separation — not a verified-isolation claim

The authoring routes are gated so authentication runs before anything is read, and share-link tokens are opaque rather than guessable. Whether those two facts add up to verified tenant isolation is unmeasured: no cross-workspace-denial or share-link-boundary test was run for this page, so this page claims no isolation guarantee. Administrative roles, department governance, configurable retention, and district controls are unmeasured.

Retention periods, school-configurable deletion, administrative exports, and account-closure procedures are unmeasured on this page and none is described here. This page does not promise certified compliance, zero logging, automatic deletion, or complete district control, and it does not claim a FERPA or COPPA certification. The product is designed to support a school’s obligations.

Access should follow the work people are authorized to do

What exists today is one creator’s authoring workspace and the running share-link submission path. Broader school controls — administrative roles, retention settings, department governance — are unmeasured on this page. This is not a district-administration surface and is not described as one.

A teacher controls their own authoring workspace and decides when to mint a share link; a student holding that link reaches the activity and can submit, and the link does not grant authoring or administrative access — the authoring routes require a signed-in creator. Department reviewers, school administrators, centralised provisioning, and district-level policy controls are unmeasured on this page and are not described as available.

Data should remain understandable and recoverable

Authored questions, session responses, and account information are held as separate records rather than one indefinite data pool. Data fields and retention behavior will be documented by feature, including what is stored for guest submissions. School-managed exports and administrator-directed workspace closure are unmeasured on this page; when they exist, export scope, deletion timing, and backup expiration will be stated in the service terms rather than behind a generic promise of data portability.

A clear line between the product and the roadmap

Rather than blend future capabilities into present-tense prose, here is the state of each capability, in four states and nothing else. Some of this loop runs today; some of it refuses today and names why; some of it is not built; and some of it we have not measured and will not guess about.

Four states, and nothing else. Running means the path exists in the product and is registered in the API. Built and switched off means the path exists and refuses, with the reason named. Not built means we searched for it and it is not there. Unmeasured means we did not measure it and will not guess in either direction.
Capability	Status
Author prompts, keys, explanations, and sources	Running -- registered authoring routes, signed-in creator
Save a question or a question set	Running -- authoring store
Launch an activity by an opaque share link	Running -- share-link mint and token resolve
Join a session as a guest without an account, and submit	Running -- public submit, server-side moderation, rate limited
Review submitted session responses as the creator	Built and switched off -- registered and owner-scoped, answers 501 qt_creator_submissions_unavailable while no store supplies the feed
Launch an activity by a human-readable class code	Not built -- the share link is the launch mechanism that exists
Individual preview and revision surface	Unmeasured
Organize and reuse a personal library	Unmeasured
Workspace and share-link access limits	Unmeasured -- no boundary test was run for this page
Data separation between workspaces	Unmeasured -- no isolation test was run for this page
Delivered-version result provenance	Unmeasured -- no immutability test was run for this page
Advertising or device profiling on responses	Unmeasured across the product; the public submit route is documented as carrying no student identifiers
Department review, approval, and shared libraries	Unmeasured
Roster-linked longitudinal history	Unmeasured
District administration and retention controls	Unmeasured
School-managed exports and account closure	Unmeasured
Live payments	Off on this page -- no checkout, no card field, no price is rendered here

What this product does not do

question.software is not a finished classroom-assessment system. Launching by a human-readable class code is not built. Reading responses back as the creator is built and switched off, and refuses with its reason named. Reusable libraries beyond saving, delivered-version immutability, roster-linked history, district administration, retention controls, and exports are unmeasured: they are not claimed here, and their absence is not asserted either.

Guest submissions are not intended for official grades, high-stakes examinations, accommodations management, attendance, or verified student identity. This page renders no checkout and no price, and it carries no invented schools, users, results, metrics, customer quotes, or brand marks, because none exist and none may be fabricated.

Money honest-off

No surprise transaction

This page renders no price, no checkout, no card field, and no Buy, Subscribe, or Start-trial button. Nothing here can charge a school or convert one into a paid customer.

The contact links let a reader ask about the current product. They do not create a purchase, subscription or payment agreement. This page offers no payment action.

Talk to us about question.software Ask what runs today

FAQ

Questions schools ask before trying it

Do students need accounts?

No. The guest path runs today and requires no student account: a student opens an opaque share link and submits a response, carrying a session label rather than a verified permanent identity. There is no class code -- the share link is the way in. Roster-linked identity and longitudinal history were not measured for this page.

Is a roster required?

No roster is required for the guest path that runs today: the public submit route takes a response without one. Roster linking for named history across classes or terms was not measured for this page, so this page does not claim it and does not deny it.

Can it administer graded or high-stakes tests?

No, and that is a policy, not a build gap. Guest sessions are for classroom checks, exit tickets, and review activities — not identity-assured exams, official grades, attendance, accommodations management, or high-stakes assessment administration. A submission carries a session label, not a verified student identity, so it cannot support a high-stakes result and we will not offer it for one.

What student data would be stored?

The guest path that runs today stores the activity, the submitted response, a limited session label, and the operational records needed to run and protect the service. The submit route is documented as carrying no student identifiers: it does not ask for a student email address, an advertising ID, or a device profile. Retention periods and the full published schema were not measured for this page.

Can another school or class reach our sessions?

Unmeasured. The authoring routes are gated so authentication runs before anything is read, and share-link tokens are opaque. Cross-workspace denial and share-link boundary behaviour were not tested for this page, so this page will not tell you either that isolation is verified or that it is broken.

Can teachers reuse their questions?

Save runs today: questions and question sets are created and read back through the authoring store. Organize and Reuse were not measured for this page. The three are stated separately and never bundled into one claim.

Who owns the questions and the student work?

Questions a teacher creates remain the teacher’s or the school’s content under the applicable school policy and the service terms, and publishing a classroom activity does not place a question into a public marketplace. The school retains control of its education records. This content is used only to store, deliver, and return it through the product — never to sell an advertising profile.

What happens to our work if we leave?

Unmeasured. Export formats, deletion timing, required operational retention, and how a school requests closure were not measured for this page, so no procedure is described here. Those terms will be stated in writing before a school is asked to adopt.

How does this protect student data and support FERPA?

The design collects only what the classroom workflow requires and separates authored questions, session responses, and account information instead of pooling them. FERPA does not certify products, so we do not claim a certification; the product is designed to support a school’s obligations, and the data practices and any district agreement will be documented for review.

What does it cost?

This page renders no price, no checkout, and no card field, and it cannot charge you. Pricing and included limits are not decided; when they are, they will be shown plainly before any purchase decision, with renewal terms, the data agreement, and the exit process.

Talk to us

Ask what runs today, and get the measured answer

Email us to talk through how the parts that run today would fit your school, or to be told the moment a refusing path stops refusing. Nothing here begins a subscription and no card is charged. We will name the state of each capability — running, built and switched off, not built, or unmeasured — rather than hand you a promise page.

Email [email protected].

Talk to us about question.software Read the FAQ →

Powered by question.technology · no checkout on this page · every capability carries one of four states · this page has no student form and does not ask for a student name, email address, or school record; do not submit student data here.