← Back to Loom
Loomfor Schools

Sources you can trust. Reasoning you can show.

Loom is Temple Seven’s research tool, where students build investigations. They gather evidence from authentic public-domain primary sources — books, newspapers, maps and pictures, each traced to the library or museum that holds it — make claims, tie every claim to its sources, and reach conclusions a teacher can open and check.

Comprehension made visible, in the age of the AI essay.

Why it matters now

An essay can be generated. A chain of evidence has to be built.

When a finished essay proves little about who understood what, the work worth assessing is the reasoning itself: which sources a student found, what they claimed, and how each claim rests on a page. Loom makes that visible. Every quote is checked word for word against the page it cites, every claim shows the sources for and against it, and every hand-in is a frozen version that cannot be edited afterwards.

AI is changing what schoolwork can prove. A polished essay can be produced in seconds, detectors can wrongly flag honest work, and banning AI does not prepare students for a world that runs on it. Loom takes a different path: it puts AI inside a process where the thinking is what gets made, seen and assessed.

  • AI that has to cite. Loom’s research assistant suggests passages and links from the archive, and anything it helped with is marked as AI-assisted. For each assignment the teacher decides how much it may do: off, suggestions only, or full.
  • Evidence AI cannot fake. Every quote is checked word for word against the page it cites, every claim shows its sources for and against, and every hand-in is frozen on our servers, so the record of how the argument was built cannot be rewritten afterwards.
  • Students who audit the AI. In an “Audit the AI” assignment, students check an AI answer’s citations against the original scans and mark what holds up and what does not: the skill this era asks of them.

Temple Seven does not decide what is true. It shows where each claim came from, so a teacher and a student can check it together.

Watch an Audit the AI assignment: the research assistant answers once, citing a page for every claim, and students check each citation against the scan.

Audit the AI · 1:17
Who it’s for

Classrooms, departments, campuses and reading rooms

Teachers

Set a research question, hand every student their own copy of a starter investigation, and open each hand-in as a frozen version — click any claim through to the page it rests on.

Schools and districts

Seats on one annual licence. Bring people in by invitation, by verified email domain or through your LMS, and see who did what in an audit log.

Universities

Seminars, methods courses and theses: peer review on a frozen version, a full version history, and citations out to Zotero, Mendeley and EndNote.

Libraries

Teach source evaluation with sources traced to the institutions that hold them, and keep a shared reading list in one library investigation everyone on the licence can open.

How a class works

Four steps from a question to work you can check

  1. 1

    Make a class

    A teacher creates a class and shares its six-character join code — or students arrive from the LMS already in the right course.

  2. 2

    Post an assignment

    Give it a brief, a due date and, if you like, a starter investigation. Each student gets their own copy to build on; nobody edits anyone else’s.

  3. 3

    Students build the case

    They pin books, quoted passages, page scans, newspaper clips and maps from the archive, write their claims, and connect each claim to the sources that support or contradict it.

  4. 4

    Hand in, and check

    A hand-in is a frozen, fingerprinted version the student cannot change afterwards, marked late by our server’s clock if it is. The teacher opens it and lands on the cited page with one click.

Watch it on screen: make a class, post an assignment from a starter investigation, open exactly what each student handed in, and return it with the rubric.

How a class works · 1:46
In every seat

A seat is a person, and a person gets all of Loom

There is no per-feature tier on a school licence. Every seat — student or teacher — carries:

  • All of Loom

    Subscriber-size investigations: cards for books, quotes, page scans, newspaper clips, maps, images and notes; claims with the evidence for and against; the yarn that connects them.

  • The archive

    Public-domain books, newspapers, maps and pictures — original scans and enhanced editions — searchable to the page, each traced to the library or museum that holds it.

  • Classes and assignments

    Join codes, starter investigations, due dates, frozen hand-ins, and peer review on a frozen version.

  • Version history

    Every card and connection, dated — so a teacher can see how an argument was built, not only where it ended.

  • Citations out

    MLA, APA and Chicago bibliographies, Word export, and BibTeX and RIS files for Zotero, Mendeley and EndNote.

  • A research assistant that cites or stays silent

    Every sentence it writes cites the student’s own cards or is removed before the student sees it, and a quotation it offers must appear word for word on its page. Use draws on one shared monthly allowance across the licence.

  • LTI 1.3 and Deep Linking

    Launch from Canvas, Blackboard, Moodle, D2L Brightspace, Sakai and other LTI 1.3 platforms.

  • An administrator console

    Seats and invitations, verified-domain joining, roles, a handling policy (including legal hold), an audit log and a data export.

AI Workspaces (the research agent that builds an investigation for you) are not part of a seat. Single sign-on through your identity provider is on our roadmap; today people join by invitation, by a verified email domain, or by launching from your LMS.

Watch the license console: invite people, choose what students under 18 see, set the handling policy, and read the audit log.

For administrators · 1:27
Your LMS

Launch from the course students already use

Loom is an LTI 1.3 tool, so it is registered once in a learning platform that supports the standard — Canvas, Blackboard, Moodle, D2L Brightspace, Sakai and others.

  • Students click the link in their course and arrive signed in — no account to create and no password to forget.
  • Teachers attach a specific investigation to an assignment from inside the LMS, with Deep Linking.
  • Launches work inside the LMS’s own frame and set no third-party cookies.

Your LMS administrator can register the tool from our setup guide, which lists every URL to paste in.

Privacy

Student work stays the student’s

  • No advertising, and student information is never sold or used for marketing.
  • Site analytics are switched off for school accounts, whatever the cookie banner says.
  • Teachers see their class’s roster and hand-ins; administrators see the roster and an audit log. Nobody at the school reads a student’s private investigation.
  • Investigations belong to the student who made them. Your licence can set how long class records are kept after someone leaves.
  • The research assistant cites the student’s own cards for every sentence it writes, or stays silent.

Read the school security & privacy summary →

Is Loom up right now? Our system status page shows the automated checks we run every 10 minutes, 30- and 90-day uptime, and any incident notes.

Pricing

Per-seat annual licence

Pilots and quotes open soon. Licences are invoiced annually against a purchase order, or paid by card if your department prefers, and seats can be added mid-term.

Request a pilot

Try Loom with a class

School pilots open soon. Loom is launching for everyone first; if you would like to hear when pilots open, write to contact@templeseven.com.

Tell us a little about your school and we will be in touch about a pilot or a quote. Fields marked * are required.

We use these details only to reply about a pilot or a quote. See our Privacy Policy.