Partner pilot

Get verified. Help students show up.

Verified UW TAs publish course sessions students can trust. Verified organizers publish official events. Both carry a badge that says who you are, so nobody has to guess.

For TAs & peer leaders

Turn office hours into a session students can actually find.

Post a review, study or course meetup in under a minute. LoopIn puts the time, place, capacity and course context on one card — and marks it as course staff, not a classmate.

Apply for TA verification

Free during the pilot. Reviewed by a person, usually within a few days.

Interactive demo: publishing as a verified partner

Create session STEP 1 OF 3

A walkthrough, not the real app — click through to see what your post looks like to students.

01 A badge students can see

Your role is checked once and shown on everything you post.

02 Posts that carry context

Course and term travel with the session, so it lands in front of the right people.

03 A say in what gets built

You are early enough that your feedback still changes the app.

How the pilot works

From this page to your first post.

Four steps, one of which is us reading your application properly. No automated approvals — a badge is a claim LoopIn makes to students about you, so a person checks it.

Apply

Pick your role and use your @uw.edu address. It takes about a minute.

Show your role

Link a course staff page or RSO listing, or name someone who can confirm it. We check what you send.

We review by hand

Every application is read by a person. You will hear back either way.

Post for campus

Once approved, publish a real session or event with your verified role on it.

Being straight with you about step 3. Automatic invite email is not set up yet, so this is a manual review queue — we read applications and reply ourselves. That also means there is no download link on this page: the TestFlight build is private, and it goes out after your role is approved, not before. If you would rather not wait on a badge, the general waitlist is on the home page.

Trust is part of onboarding

Students should know who is posting.

The pilot uses the same three layers LoopIn's onboarding will use before anyone gets TA or organizer posting rights.

Layer 01

An active university email

Everyone starts here. Your @uw.edu address is confirmed with a one-time code, so an address that no longer works cannot hold a badge.

Layer 02

The role itself

TAs show course evidence; organizers show an RSO or official listing. What you send us stays private — it is never shown on your profile or anywhere else in the app.

Layer 03

A badge with edges

A TA badge is scoped to one course and one quarter and expires with the term. Organizer access can be revoked. A badge is a statement about now, not forever.

Regular students can still create ordinary sessions. Nothing here takes anything away. Verification is only needed to publish a TA-labelled course session or an official organizer event — anyone with a LoopIn account can start a study session today.

Be early on purpose

Your campus needs people who start things.

Join the small UW founding group helping make LoopIn useful before it opens to everyone.

  • Reviewed by a person, not a filter.
  • Your evidence is private and is never shown publicly.
  • Free during the pilot, and you can ask us to remove your application at any time.

Request verification

Apply for the pilot

Applications are reviewed by hand. We use what you send here to check your role and to email you about pilot access — nothing else, and no spam.

Student-built. LoopIn is not affiliated with, endorsed by, or sponsored by the University of Washington.