Category: EduTech Solutions from a Teacher-Coder

Teachers evaluating an online assessment platform reasonably want to know what it can see, what it can prevent, and where its technical limits lie. Here are straightforward answers to several questions we have received about student monitoring and secure testing.

Does the platform show all activity on a student’s computer?

No. Innovation Assessments is not remote-surveillance software and does not provide teachers with a complete view of a student’s computer.

It does not record the student’s screen, activate the webcam, inspect personal files, or produce a history of everything the student does on the device.

During a proctored Testapp assessment, the system can record browser events connected to the test, including:

• Leaving or returning to the test tab
• Moving focus away from the test window
• Exiting or entering full-screen mode
• Pasting or copying text
• Attempting certain blocked shortcuts or right-click actions
• Resizing the browser window
• Time spent away from the test
• Time spent on questions
• Restarting or resuming a session
• Test start, saving, and submission events

Teachers can review these events in the proctor log. The system also summarizes combinations of events that may deserve attention, such as repeated tab departures, long periods away, or a tab departure followed by pasted text.

These records provide context; they are not proof of misconduct. A focus change, for example, could result from browser controls, accessibility software, an input method, or an ordinary notification. Teachers should interpret logs alongside the student’s explanation and the circumstances of the assessment.

Do students have to install an application?

No. Students ordinarily use Innovation Assessments through a web browser. They do not need to install a separate monitoring application or browser extension.

This makes the platform easier to use on school-managed Chromebooks, conventional computers, and tablets. It also means the platform operates within the security boundaries imposed by modern browsers.

A browser-based application cannot inspect an entire device in the way that specially installed device-management or remote-proctoring software sometimes can.

Does Testapp include a lockdown browser?

Testapp includes a configurable secure-testing mode, but it should not be described as a traditional operating-system-level lockdown browser.

When strict security settings are enabled, Testapp can require students to remain in the test tab and, on supported devices, remain in full-screen mode. Leaving the tab, leaving the browser window for more than the allowed grace period, or remaining outside full-screen mode can automatically lock the test.

Once locked, the student cannot simply continue. The teacher must review the situation and readmit the student.

Testapp can also:

• Restrict an assessment to one active browser tab or device session
• Require single-use access codes
• Enforce time limits
• Automatically submit when secure time expires
• Limit audio playback when configured
• Preserve responses through autosaving
• Record security and session events
• Let teachers monitor progress in real time
• Block or readmit individual students

iPads use a compatibility mode because mobile Safari handles full-screen and focus events differently from desktop browsers. Brief keyboard or browser-interface changes are tolerated, while an extended app or tab departure can still trigger a lock when strict tab locking is enabled.

Can students go wherever they want during a test?

A web application cannot physically prevent a student from opening another application, using another device, or consulting material outside the browser.

What Testapp can do is establish consequences within the assessment. Under strict settings, leaving or hiding the test tab can lock the attempt. On supported desktop browsers, leaving the browser window or full-screen mode beyond the grace period can also result in a lock.

Teachers can choose settings appropriate to the situation. A low-stakes practice test may use monitoring without aggressive locking, while a controlled examination can use access codes, a timer, one-session enforcement, tab locking, and full-screen expectations.

Does it detect Google Lens?

Not directly.

A normal website cannot reliably ask a browser, “Is Google Lens being used?” Google Lens may be accessed in several ways:

• Through another browser tab
• Through another application
• Through a browser feature or extension
• Through a phone pointed at the screen
• Through functionality integrated into the operating system

Testapp can detect the browser consequences of some of these actions. If using Lens causes the student to leave the test tab, move to another application, exit full screen, or paste material into an answer, those events may be logged. Under strict security settings, leaving the test environment may lock the test.

However, Testapp cannot identify every use of Google Lens by name. Use on a second device would not be visible to the browser at all.

The accurate claim is therefore: Testapp can detect and respond to many browser behaviors associated with leaving the assessment, but it cannot guarantee detection of Google Lens itself.

Does it detect browser extensions?

It does not inventory or identify installed extensions.

Browsers deliberately prevent ordinary websites from obtaining a complete list of a user’s extensions. This is an important privacy and security restriction.

An extension may still produce detectable behavior. For example, its use might:

• Move focus away from the test
• Hide the test tab
• Exit full-screen mode
• Paste text into an answer
• Trigger a blocked shortcut
• Open a separate window

Those resulting events can be recorded, and some can trigger an automatic lock. An extension that operates entirely inside the page without generating a browser event may not be distinguishable from ordinary activity.

For this reason, schools seeking stronger control should combine Testapp with managed-device policies that disable unapproved extensions during testing.

What about language-setting changes?

Testapp does not directly monitor or forbid a student’s operating-system language, keyboard layout, or browser-language setting.

That restraint is important. Multilingual students may need an alternate keyboard or input method to type accented characters or non-English text. A language or keyboard change is not inherently suspicious.

If changing a setting requires the student to leave the test window, the resulting tab, focus, or full-screen event may be recorded. The platform records the browser event—not a claim about why it occurred.

Testapp also includes an accent-character toolbar for written answers, reducing the need for students to leave the page merely to enter common accented characters.

Would using Google Lens or an extension trigger a lock?

It may, depending on how the tool is used and how the teacher configured the test.

Examples:

• Opening Lens in another tab could trigger a tab-leave lock.
• Switching to another application could trigger a browser-leave lock.
• Leaving full screen for longer than the grace period could trigger a full-screen lock.
• Pasting generated or copied text would create a paste event, but paste alone is primarily logged and risk-flagged rather than treated as conclusive proof.
• Using Lens from a separate phone would not be detectable by the student’s test browser.

The lock is triggered by observable departures from the secure test environment—not by reliable identification of a particular product or extension.

What is the best way to use these protections?

Technical controls work best as one part of a larger assessment design. Teachers should consider combining secure Testapp settings with:

• Clear testing expectations
• School-managed browser and extension policies
• Thoughtfully randomized or individualized questions
• Questions requiring course-specific reasoning
• Short testing windows
• In-person supervision where appropriate
• Follow-up conversations when logs raise questions
• Comparison with a student’s established work

No browser-based platform can promise complete control over every device, application, extension, or second screen. Testapp instead provides a practical combination of deterrence, session control, automatic locking, event evidence, and teacher review—without pretending to provide invisible access to the student’s entire computer.

The goal is not to replace professional judgment. It is to give teachers better information and stronger control over the assessment environment while remaining honest about what browser technology can and cannot do.

AI-content disclosure: This article was generated by AI after reviewing the current Innovation Assessments application code. It is published under a separate account to distinguish AI-generated material from articles written by the site owner.

There are certain questions that seem perfectly ordinary in educational software until one stops to ask why they are being asked at all.

An email address is a good example.

For years, asking for an email address during account creation has been standard practice nearly everywhere online. It is familiar. It gives a student something recognizable to type into a login box. It can also be useful when a school has approved Google sign-in or another email-based workflow.

But most of my own students do not need email to use Innovation Assessments. They enter a classroom number and a short PIN. That takes them where they need to go. If the platform can identify the right student, enroll that student in the right course, save the work, and return the teacher’s feedback without collecting another piece of personal information, why collect it?

Well, get this: now we do not.

Student registration now begins with the minimum

The public student registration page has been reframed as Obtain Student PIN or Password. It asks for the student’s first and last name—or, in an Alias-Only course, the permitted first name and a system-created alias. It does not ask the student for an email address, and it does not offer the student an opportunity to connect a personal Google account.

Behind the scenes, the software creates a unique internal username so that the account can function normally. That internal value may look a little like an email address because it occupies the same long-established database field, but it is not the student’s real email address and does not receive mail.

This means a student can still:

– receive a classroom PIN;

– enter a course;

– complete and save work;

– receive scores and feedback; and

– participate in live classroom activities.

None of that requires us to know the student’s email address.

Schools remain in control when email really is useful

There are schools that authorize student email and Google sign-in, and there are circumstances in which those tools genuinely help. Innovation Assessments has not removed that choice.

Instead, the choice now belongs to the teacher or school. A teacher may deliberately enter an approved school email address while adding or editing a student. The page displays a reminder to confirm that the school permits the information to be stored. A student cannot independently attach a Google account and quietly expand the information connected with the record.

That distinction matters to me. The software should not make a privacy decision on behalf of a school merely because collecting more information is convenient.

A cleanup tool for existing rosters

The My Students page now includes a tool to sanitize existing student email addresses. When a teacher chooses to use it, the system replaces real addresses with unique internal `@myschool.com` identifiers while preserving the student account, enrollments, submissions, scores, and feedback.

The tool requires classroom PIN login to be enabled first, because students need a working way to return after their email-based login has been removed. It also avoids changing accounts shared with another teacher, where one person’s cleanup decision could otherwise disrupt another class.

This is intentionally not an automatic sweep. A teacher sees a warning before proceeding because students who previously signed in by email or Google will need to use the classroom number and PIN afterward.

Alias-Only courses go a step further

Some schools permit only a first name and an alias to appear in an outside instructional system. Innovation Assessments now supports that model at the course level. An Alias-Only course creates a privacy-safe surname and a non-identifying account reference, while the teacher keeps the real-name connection in the school’s own authorized records.

This is not the right arrangement for every classroom. It is available for the schools that need it, without forcing the same restriction upon everyone else.

Privacy is often a series of small decisions

There is no single button that makes educational technology private. Privacy comes from asking practical questions over and over:

Do we need this information? Who is permitted to enter it? Who can see it? How long should it remain? Can the same educational purpose be accomplished with less?

Removing the student email box may look like a small change. Technically, it was not quite as small as it looked! The registration, login, Google identity, PIN, roster, and account-cleanup workflows all had to agree with one another. Pedagogically, however, the idea is beautifully simple: collect what the class needs and do not casually collect what it does not.

That is the direction in which I want Innovation Assessments to continue growing.

—

*Transparency note: This article was generated with AI assistance from a review of the current Innovation Assessments source code and was reviewed for publication by Innovation Assessments.*

One of the most effective ways for students to master new content is to own it. When a student has to synthesize a topic, identify what matters, and teach it back to their peers, the learning sticks.

However, in a typical classroom, “making a presentation” often turns into a week-long odyssey of font choices, transitions, and image cropping. The actual thinking—the synthesis—gets buried under the formatting.

That’s why we built SlideCraft. It’s a new tool within Innovation Assessments designed for speed, accountability, and meaningful participation. It’s not a full-featured slide editor; it’s a structured workflow that turns a class’s collective research into a ready-to-present deck in minutes.

The Problem with “Death by PowerPoint” (and Canva, and Slides…)

In many EdTech tools, “engagement” is equated with gamification—points, music, and flashy animations. At Innovation, we believe real engagement is cognitive load. We want students focusing on the history, the science, or the literature, not the “rules of the game” or the aesthetic of a slide border.

SlideCraft is built for a specific, powerful classroom pattern:

1. The Hook: The teacher introduces a topic.
2. The Task: Students are assigned specific subtopics or “jigsaw” pieces.
3. The Build: Students research quickly and build exactly one slide.
4. The Share: The class presents the completed, unified deck immediately.

How It Works: Designed for the Live Classroom

SlideCraft lives in two places: your prep time and your live instruction.

Teacher Setup (The Prep) In configuration, you build the skeleton of the lesson. You can add up to five starter slides (intro, instructions, or framing) and then define the “prompts” students will receive. These prompts are reusable, meaning you can run the same activity with five different sections without rebuilding the wheel.

The Live Session (The Action) When class starts, you launch the Live Host from your course playlist. Students join via a link from their login page and are automatically assigned one of your prompts.

As they work, you can:

• Monitor incoming drafts in real-time.
• Set a countdown timer or stop the session manually.
• Autosave everything: Because this is built for real-school Wi-Fi and interruptions, student work is preserved constantly as they type.

What Students See: Focus over Frills

The student interface is intentionally lean. There are no menus for “WordArt” or background gradients. Students see:

• Their assigned title and specific instructions.
• A field for concise bullet points.
• An image upload (optional).
• A Source URL field: This is critical. By making the source a required part of the “Craft,” we reinforce academic integrity from the first click.

From “Building” to “Presenting” in One Click

The moment you stop the build session, the host view transforms into a presentation stage.

The finished deck is automatically assembled: your intro slides first, followed by the student-generated content. During the presentation, the teacher has access to a Presenter Timer and a Show Sources toggle. This allows you to pause the lesson and discuss source credibility or authority on the fly—turning a student slide into a teachable moment about information literacy.

Accountability and Scoring

SlideCraft isn’t just an “activity”—it’s an assessment. Once the presentation is over, the work doesn’t disappear. All student submissions are saved for review. Using the familiar Submissions and Score tools, you can:

• Evaluate slides using your existing rubrics.
• Score based on the quality of the bullets and the reliability of the sources.
• Provide written feedback and release evaluations to students.

A First Use Case: The French Revolution

Imagine a lesson on the causes of the French Revolution.

• Teacher Intro: 3 slides on the monarchy and the Three Estates.
• The Build: Students are assigned prompts like The Bread Crisis, Enlightenment Ideas, The American Influence, and Louis XVI’s Debt.
• The Result: Within 15 minutes, you have a 25-slide deck built by the class.

You aren’t just lecturing; the students are providing the evidence.

SlideCraft fills the gap between passive slide-viewing and time-consuming independent projects. It’s built for teachers who want their students to be active, collaborative, and accountable—without the “formatting fatigue.”

If you’re ready to turn your next research burst into a live class product, SlideCraft is ready for you in the Innovation dashboard.