LALITE — STAFF-BUILT APPLICATION RELEASE WORKSHEET
Updated 10 September 2026
Guide: https://lalite.org/school-it-guide/ai/staff-built-app

Application / version / date:
Business purpose / manual alternative:
Business owner / technical owner / second support person:
Intended users / consequence of a wrong result:
AI-written code only, or live model integration? Explain:
Data route: input -> application -> storage/external service -> output -> deletion
Approved data / destination / retention / deletion owner:
School-owned repository / hosting / sign-in / secrets location:

RELEASE EVIDENCE (record expected result, actual result and evidence)
[ ] Two-account server-side authorisation test.
[ ] Failed save, interrupted connection and clear recovery messages.
[ ] Repeated submission and duplicate-action behaviour.
[ ] Keyboard, zoom and relevant assistive technology checks.
[ ] Dependency and security review proportionate to the application.
[ ] Backup restored and recorded version deployed by a second person.
[ ] For live AI: disclosure, misleading output and untrusted-input tests.
[ ] Local application and privacy approvals recorded.

Costs / capacity / monitoring / support hours:
Recovery procedure / fallback / retirement process:
Decision: prototype only / limited pilot / approved for the stated use
Conditions / accepted limitations / evidence:
Approver / date / next review:

Reopen approval when data, audience, integrations or operational importance
changes. Do not enter real student information in an unapproved prototype.