The proposed pilot

What’s proposed

• Free for three months for one counselor’s group of students, or a few advisories. The school can widen it later if it wants.
• No obligation. Nothing renews or charges automatically, and students never pay. Any price after the pilot would be agreed in writing first, and the school decides.
• No district has approved Weekly yet. No student uses it with a school account until the steps below are done.

What students can use on day one

Everything here is in the app today. You can try all of it in the demo, or take the five-minute counselor tour.

• One step for today, sized to the study time the student sets, read from their own Google Classroom.
• A warning when work won’t fit the time before it’s due, with choices: add time, do a smaller version of their own plan, or ask for more time.
• A quick check-in when a planned step was missed, with no streaks or blame.
• “I’m stuck”: a short message to a teacher or counselor that the student reviews and sends themselves.
• Dates from a pasted school email, such as a quiz a teacher announced only by email.
• Reminders the student adds to their own Google Calendar.

Features on the roadmap marked “being built” aren’t part of the pilot unless they’re released before it starts.

How it gets approved

1. A staff member files the request. At San Ramon Valley Unified, that’s the “Digital Learning Tool Approval” request on the staff IT ticket page. Students can’t file it. We provide the text and answers.
2. The district reviews student privacy and signs the California Student Data Privacy Agreement with the company that runs Weekly.
3. The district’s Google Workspace admin allows Weekly for the pilot group only. Google blocks unapproved apps for students under 18 until then.
4. The counselor introduces Weekly to the group, and students connect their own accounts.

What the counselor does

Students use Weekly on their own. There’s no dashboard to watch and no weekly admin work. The counselor’s part is:

• At the start: introduce Weekly, for example with the tour (about 10 minutes), and note each student’s missing-work count in Classroom.
• At six weeks and at the end: note the missing-work counts again, and ask students three questions: Did you use Weekly this week? Did it help you start work sooner? Would you keep using it?
• Along the way: notice what students say in regular check-ins, and what they ask for help with.

Only totals are shared with us, never individual students’ answers or counts. Weekly collects no usage data, so this is how the school judges whether it helps.

Student data during the pilot

• Weekly reads the student’s own classes, assignments and turn-in status from Google Classroom, read-only. It never reads grades, rosters, Gmail or Drive, and it can’t change anything in Classroom.
• There’s no Weekly server or database. The student’s plan stays in their own browser, so we can’t see it.
• While Weekly is open, it deletes work two weeks after it was due, and pasted emails two weeks after they were added. Signing out deletes everything it saved.
• Our host keeps basic request logs (page addresses, which can include Classroom ID numbers, IP address, browser type and time) for a short time, then deletes them.
• No ads, no analytics, no AI.
• Full details are in the privacy policy. The district’s signed agreement controls over it.

Support, and if something goes wrong

• Questions and problems: schools@getweekly.study. We aim to reply within two school days. Privacy questions can also go to privacy@getweekly.study.
• Who’s responsible: today, Weekly’s developer. Before the agreement is signed, a registered company will run Weekly, with an adult officer signing for it and responsible under the agreement.
• A security problem: we notify the district within 72 hours of confirming a breach that may involve student data, or sooner if the agreement says so.
• Turning it off: the district’s Google admin can switch Weekly off for everyone at once, at any time. Classroom is unchanged either way.

Accessibility before students join

Automated accessibility checks (WCAG 2.2 AA) run on every screen at laptop and phone sizes, and the app works with a keyboard and on screens 320 pixels wide. Automated checks don’t catch everything, and a hands-on screen-reader review hasn’t been done yet. If the district needs one before students join, we’ll do it first.

How the pilot ends

• At the end, the school chooses: continue, on terms agreed then in writing, or stop.
• To stop, the Google admin sets Weekly to Blocked, and students sign out to clear their devices. Weekly can no longer read Classroom once it’s blocked.
• We delete any correspondence about the pilot within 30 days of a request, and confirm in writing.

Known limits

• Classroom and the teacher always come first. Weekly can be out of date or get a date wrong, and it tells students to check Classroom.
• Weekly needs an internet connection to open.
• Weekly checks Classroom by itself for about an hour after a student signs in with Google. After that, a tap on Refresh checks again.
• Until Google finishes reviewing Weekly’s branding, Google’s sign-in window shows the getweekly.study address instead of the Weekly name and logo.