Quiz Them on Their PhonesText only
Sectioned Unit Test Form With Verified Key

A complete sectioned unit-test Form script with a blueprint, independently checked key, points and full-score test response.
Works on any free AI · Best tool: Any AI chat (ChatGPT, Claude, Gemini)
ROLE: Act as a unit-test blueprint designer, independent key verifier and sectioned FormApp developer.

CONTEXT: A teacher needs a complete phone-based unit test for [CLASS] on [UNIT] with [TOTAL MARKS] distributed across named sections.

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [BOARD OR EXAM]
- [UNIT]
- [LEARNING OUTCOMES]
- [SECTION PLAN]
- [TOTAL MARKS]
- [TIME LIMIT]
- [DIFFICULTY MIX]

DO THIS:
1. Build a blueprint mapping each item to outcome, section, difficulty and marks before writing questions.
2. Write original, source-honest questions and do not call them PYQs unless supplied and cited by the teacher.
3. Solve every item independently and attach a check-this-yourself link to every computational answer.
4. Generate one complete executable FormApp script using page-break sections, quiz mode, correct choices, point values and logged URLs.
5. Check that section subtotals equal the total marks and that navigation preserves any stated optionality.
6. Provide a full-score response sequence and a pre-release audit for content, scoring and phone display.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Include a calculus section item asking for the integral of x^2 from 0 to 3.
Expected result or check target: The independently verified value is 9, and the item’s points appear identically in the blueprint, key and script.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=integrate%20x%5E2%20from%200%20to%203
(paste-fallback: integrate x^2 from 0 to 3)
Encoding note: Spaces use %20 and ^ uses %5E.

OUTPUT FORMAT:
1. UNIT-TEST BLUEPRINT
2. SECTIONED REVIEW COPY
3. INDEPENDENT VERIFIED KEY
4. COMPLETE SECTIONED FORMAPP SCRIPT
5. RUN IT — script.google.com → New project → paste → Run → View → Logs
6. MARKS RECONCILIATION
7. FULL-SCORE TEST RESPONSE

QUALITY AND TOOL GUARDRAILS:
- Output one COMPLETE executable FormApp code block with every section, item, key and point value included.
- After the code, print exactly: script.google.com → New project → paste → Run → View → Logs.
- Never claim a URL creates the Form, never fabricate a PYQ source and never let item points differ from the blueprint.
- Use plain ASCII maths in Form text and label all solver links check this yourself.
- Never describe an AI answer as verified. Every external check must be labelled “check this yourself” for the teacher or student to inspect personally.
- Do not invent exam facts, source citations, marks distributions, tool IDs or inaccessible links. Separate mathematical proof from computational checking.

=== TOOL-LINK OUTPUT CONTRACT — follow every rule exactly ===
1. You may output clickable links ONLY to: wolframalpha.com/input?i= · symbolab.com/solver?query= ·
   geogebra.org/graphing|geometry|3d|cas?command= · math.stackexchange.com/search?q= · oeis.org/search?q= ·
   artofproblemsolving.com/community/q1_ · khanacademy.org/search?page_search_query= ·
   overleaf.com/docs?encoded_snip= · latex.codecogs.com/png.image? · docs.google.com/forms/...viewform?usp=pp_url
   (Forms only with entry.N IDs I paste in) · plus any URL I give you or that appears in this prompt's whitelist table.
2. NEVER output: desmos.com links with query strings (they load blank), invented geogebra.org/m/ IDs, Khan topic
   URLs, DIKSHA dial codes, Wolfram quiz/demo slugs not in my table, or mathsolver.microsoft.com (dead site).
3. Write queries in plain calculator syntax (x^2, sqrt(x), pi, 3/4) — never LaTeX — EXCEPT Overleaf and CodeCogs
   payloads, which are LaTeX.
4. Percent-encode the query part: space→%20, +→%2B, ^→%5E, =→%3D, [→%5B, ]→%5D; in LaTeX payloads also
   \→%5C, {→%7B, }→%7D, %→%25, #→%23, &→%26, newline→%0A. GeoGebra ?command= exception: encode ONLY + as %2B;
   leave ( ) = ^ ; as typed.
5. One link per line, formatted exactly:  CHECK → <full raw URL>   (no markdown brackets, nothing after the URL).
6. Directly below every link, print:  (paste-fallback: <the un-encoded query or commands>)
7. Before printing any link, silently decode your own URL and confirm it reproduces the query character-for-character;
   rebuild it if not. If a URL would exceed 1,800 characters (Overleaf: 6,000), print only the paste-fallback.
8. Label every link "check this yourself" — never claim the link proves your answer is correct.
9. On phones these links must be opened in a browser, not an installed app — say this once at the end.
Sectioned Unit Test Form With Verified Key

✅ How to use this effectively
