From the room

Nathaniel, in the chat, after Kate's and Paul's check-in tools. Not answered on the day.

It could help with one piece: a running record of which students are where, and when each one was released. It shouldn't be what decides who a child goes home with. In the Standard Reunification Method, which many districts use, students wait apart from arriving parents; each parent fills out a reunification card, staff check photo ID and custody, a runner brings the student, and a final step accounts for every child. Federal guidance says a plan should verify that an adult is authorized to take custody. The method runs on paper, and reunification can follow a power outage, so a plan that uses an app still needs a paper way it has practiced. Minnesota requires every school board to adopt a crisis management policy, written with law enforcement and emergency managers; the statute lists drills but doesn't mention reunification. Your district's crisis team decides what a tool may do, not the person who built it.

Behind Patrick's follow-up to Paul in the chat, which went unanswered.

No: hiding and protecting keep a Sheet tidy; they don't lock it. Google's help says protection shouldn't be relied on for security: anyone with access can still print, copy, and export the file, and every editor can unhide a hidden sheet. The real gate is who the spreadsheet is shared with. A web app set to run as you (Execute as: Me) uses your access, so staff can use the app without being shared on the spreadsheet; the app's own code then decides what each person sees, and the deployment's Who has access setting decides who can open it at all. Inside your district's Google domain the script can usually tell who is visiting; for other domains or personal accounts it may get a blank. FERPA asks for reasonable methods so that staff reach only the records they have a legitimate educational interest in. Your district's data privacy lead decides what that means for a given tool.

Behind Sean's question to Paul about where scripts break.

Each run of a script gets six minutes; a custom function used in a cell gets thirty seconds. Daily allowances are per person, and a Google Workspace account (school accounts are Workspace accounts) gets more than a personal one: 1,500 email recipients a day instead of 100, and six hours of trigger time a day instead of ninety minutes. One person can run thirty scripts at once. Since September 2026 a spreadsheet can hold 20 million cells, up from 10 million, but a Sheet slows down long before it's full. Google's advice is to read a whole range in one call, work on it, and write it back in one call, rather than cell by cell. Apps Script's own cache holds up to 100KB per item for at most six hours, and may let go sooner. Google says quotas can change, so check its page before planning around a number.

Behind Sean's "many hands make light work," and Ken's portal, which travels this way.

The script does. Whoever makes the copy owns it and gets their own copy of the script, and their changes never touch yours. What's tied to a person stays behind. Installable triggers, such as a timed run or a run when a form is submitted, belong to whoever made them, so the new owner sets them up again. A web app is a deployment, so the copy has none until its owner deploys it, and then it has its own address. The first time the new owner runs it, Google asks them to approve what it can reach. A share link ending in /copy instead of /edit opens a Make a copy prompt. Before sharing, clear out the data and remove any keys or settings stored with the script. A district can turn Apps Script off or limit sharing outside the district, so a copy that runs for you may not run for a teacher in another district.

Behind Dan's advice to set up version control first, and Sean's guide to GitHub for teachers.

Yes, two ways. In the Apps Script editor, Project History keeps the versions you create, usually one each time you deploy, up to 200, and can highlight what changed. It isn't a record of every save, and going back means copying the old code in by hand. For full version control, Google's free tool clasp copies a project's files to your computer, where they can live in a Git repository on GitHub. clasp pull brings the online code down; clasp push sends yours up and replaces what's there, so edit in one place at a time. It needs Node.js 20 or later, which usually takes administrator rights to install, and the Apps Script API turned on in your Apps Script settings. On a district laptop that may be a request to your technology office: it's level 4, the workbench.

More: level 4, the workbench, on Three levels.

Behind Ken's secure report portal.

Parents have a right to see their child's education records. Before a school discloses records by any route, FERPA asks it to use reasonable methods to identify and authenticate the person receiving them. The rule doesn't name a method. Federal guidance asks for certainty that fits how sensitive the data is, and describes the factors: something you know, something you have, something you are. A one-time code sent to an email address is one such check; how much it proves depends on where the address came from, who else can read that inbox, and whether a family can reach only its own student's reports. Either parent keeps full rights unless a court order or similar legal document says otherwise. In Minnesota, the state treats these reports as private student data, and districts keep them secure until they reach families. The district chooses its method and answers for it; this isn't a ruling on any one tool.

Behind Meghan's three audiences and Sean's privacy inventory.

Since the 2022-23 school year, Minnesota's educational data law, section 13.32, has rules for technology providers that handle student data under a school contract. That data isn't the provider's property. The provider can't sell or share it or use it commercially, must tell the school about a breach, and must return or destroy the data within 90 days after the contract ends unless renewal is expected. Within 30 days of the start of each school year, a district must give families direct notice, by mail, email, or something like them, of each curriculum, testing, or assessment technology provider with access to student data, which data, and whom to ask; families can inspect the contracts. A separate part limits remote monitoring of school-issued devices (location, camera, microphone, keystrokes, browsing) to listed exceptions. That covers the families; staff and the business office are the district's to decide, with its data practices official.

More: 13.32, on Sources.

Behind Dan's intelligent textbooks, and ahead of the November session on assessment.

Partly, and researchers have worked on it for decades. Since Corbett and Anderson's 1994 paper, intelligent tutors have used knowledge tracing: each step a student takes updates the tutor's estimate of whether they know a skill. Valerie Shute's stealth assessment builds the measuring into a game or task, so students show what they know by doing it. Both rest on careful design: a map of the skills, much like a concept graph; a plan for which actions count as evidence of each one; and studies showing the estimates agree with other trusted measures. Clicks count only when the task actually requires the skill, and these models can carry bias. One correction to the record: Canvas does track mastery, through Outcomes and the Learning Mastery Gradebook, scored from rubrics and assessments a teacher aligns to standards. What it doesn't do is infer mastery from page activity, which is the gap Dan described.

More: assessment, on Sources.

Behind the morning's breakout rooms: a missed notice, latecomers to move, and two hosts agreeing they're not Meet's strongest feature.

Do most of the setup before the meeting. Check your edition first: Google's help lists Education Plus and the Teaching and Learning Upgrade among those that can create rooms, so not every school account can. A host can build the rooms in the Google Calendar event and pre-assign people by typing names, dragging, or shuffling. Turn on Host Management and add co-hosts beforehand: its settings can't change once rooms are live, and people can be made co-hosts only from the main room. Each participant gets a prompt on screen and must click Join; anyone who cancels stays in the main room, so say out loud and in the chat that rooms are opening, and ask everyone to bring the Meet tab to the front. Set the timer, which every room can see. Hosts can join any room, and a room can ask for help.

More: Hosts, for running the session with your own group.