> For the complete documentation index, see [llms.txt](https://academy.synap.ac/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.synap.ac/doc/exams/proctoring-with-synoptic/synoptic-ai-review/synoptic-ai-live-in-the-loop.md).

# Synoptic AI Live in the Loop

Coming soon

AI in the Loop watches candidates live during video and audio recorded exams and prompts them to correct issues as they happen, rather than only flagging them after submission. It runs on the candidate's own device and checks six things continuously: face visibility, positioning, where they are looking, whether anyone else is in view, camera clarity, and whether a phone or other device is in view.

<div><figure><img src="https://3316915154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkgvUeCmTPeNouRxGPC%2Fuploads%2F08NXf3TAehGsxEnIFWwn%2Flookingawayboxes.gif?alt=media&amp;token=cd4d38bb-9003-4604-b0c1-4fa677612103" alt=""><figcaption></figcaption></figure> <figure><img src="https://3316915154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkgvUeCmTPeNouRxGPC%2Fuploads%2F2zYFjfMrqVTBaNvWWEQj%2FaiInTheLoopLookingaway1.gif?alt=media&amp;token=53af39ca-92eb-46ef-84da-a45c269ecc96" alt=""><figcaption></figcaption></figure></div>

{% embed url="<https://www.youtube.com/watch?v=WNRYxIyRo-Q>" %}

When a check fails, the candidate sees a status change and a short instruction. If the issue continues, they get a warning, and persistent issues are recorded as a breach for the exam team to review. The exam and timer keep running throughout.

<figure><img src="https://3316915154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkgvUeCmTPeNouRxGPC%2Fuploads%2FA8I5WDIcV2SJ5Gpf6gBA%2FScreenshot%202026-10-29%20at%2013.19.46.png?alt=media&amp;token=6cf4a7cd-2496-4e04-a0d6-69f0c8586e14" alt=""><figcaption></figcaption></figure>

### AI Checks

Each check shows a tick when passing and a cross when failing. When the camera can't see a face, checks that depend on it show a dash rather than a result.

| Check                      | Passes when                                         | Status shown on failure                    |
| -------------------------- | --------------------------------------------------- | ------------------------------------------ |
| Face visible               | One face is detected in the camera picture          | Camera blocked (with Camera picture clear) |
| Well positioned            | The candidate is centred and at a suitable distance | Not shown in demo                          |
| Facing your screen         | The candidate's gaze is directed at the screen      | Facing away                                |
| Only you in view           | Only one person is detected                         | Not shown in demo                          |
| Camera picture clear       | The picture isn't covered, too dark or obscured     | Camera blocked                             |
| No phone or device in view | No phone, laptop or remote is detected              | Suspicious device detected                 |

Gaze is tracked from eye and iris position and works with or without glasses. Looking down at the screen, for example to read smaller text, does not fail the check.

### Candidate experience

Candidates see a status button in the exam header, next to the start time and timer. The button changes colour first when something needs attention; clicking it opens the **Camera checks** panel with a live camera preview and the six checks.

<figure><img src="https://3316915154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkgvUeCmTPeNouRxGPC%2Fuploads%2FVhKMnuM7tp7M6xrQphVN%2FScreenshot%202026-10-29%20at%2013.19.46.png?alt=media&amp;token=fa7c63c8-3ada-4ba3-9be0-d0b3e4df150b" alt=""><figcaption></figcaption></figure>

| Status                              | Colour          | Trigger                              | Message to candidates                                                                                                       |
| ----------------------------------- | --------------- | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- |
| Camera live                         | Green           | All checks passing                   | All checks passing. Keep going.                                                                                             |
| Facing away                         | Blue (info)     | Candidate looks away from the screen | Facing away                                                                                                                 |
| Suspicious device detected          | Amber (warning) | Phone, laptop or remote in view      | Please move any phone, laptop or remote out of your camera's view. If you think this is a mistake, carry on with your exam. |
| Camera blocked                      | Amber (warning) | Camera covered or room too dark      | Check nothing is covering your camera and that the room is lit. Your exam and timer are still running.                      |
| Suspicious device logged for review | Orange          | Device stays in view after a warning | Suspicious device logged for review                                                                                         |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.synap.ac/doc/exams/proctoring-with-synoptic/synoptic-ai-review/synoptic-ai-live-in-the-loop.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
