3 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+Require sign-in so only staff with our district accounts can respond. Restrict the form to users…
Execute — do the immediate task
+Require sign-in so only staff with our district accounts can respond. Restrict the form to users with emails at district.edu and block anonymous responses. Ensure the Collect email addresses option is enabled and that response editing is disallowed. Confirm the restriction applies whether respondents open the form inside the intranet or off-site.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before sending this to the admin team, make it clear why sign-in is required and lower friction.…
Improve — make it easier to accept
+Before sending this to the admin team, make it clear why sign-in is required and lower friction. Add a short note explaining 'You must sign in with district account to ensure confidentiality' on the first screen, enable automatic email collection so they don't type addresses, and surface a troubleshooting note for staff who use personal devices and see an access error.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+I keep enabling sign-in only after some responses arrive, then have to reconcile anonymous entries…
Become — change the pattern
+I flip sign-in on after responses have already been collected
I keep enabling sign-in only after some responses arrive, then have to reconcile anonymous entries with staff lists. That pattern creates missing identifiers and mistrust. Which habit should I change so sign-in is set before distribution, and what two operational steps will prevent accidental open-access publication in the future?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other forms and surveys work people do in Google Forms.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.