Proctoring Acs Log

This topic lists Data Explorer and API fields (and their descriptions) associated with a query on actions taken by a proctor, test-taker, or system component. The entities described in this topic are considered to be the most meaningful when performing a query of a delivery’s data - not all entities returned with a query are listed.

Note that though these logs are mainly designed for proctoring analysis, they may also include test-taker and system level actions depending on the value of the actor field.

Proctoring logs track key events throughout the assessment lifecycle. These logs capture interactions between test-takers, proctors, and the system, allowing monitoring of assessment execution, analysis of test-taker behavior, and a detailed overview of the lifecycle of specific sessions.

These logs include:

Log Categories: Classification of events (environment, test-taker, proctor, etc.)
Reason Codes: Predefined numeric identifiers for event types.
Reason Messages: Descriptive messages or data providing event context.

Data Explorer	API	Description
Delivery Id	`deliveryId`	Delivery identifier as provided by the delivery tool.
Delivery Execution Id	`deliveryExecutionId`	Unique identifier for the delivery execution (the session for a given test taker/delivery combination).
Test Taker	`testTaker`	The test taker’s login ID.
Login	`login`	The test taker’s ID/username (not name).
Name	`name`	The display name of the actor generating the log entry.
Actor	`actor`	Defines who performed the action. Possible values: `test-taker`, `proctor`, `system`, `deliver-fe`.
Action	`action`	Describes the action taken. Possible values: `start`, `pause`, `resume`, `terminate`, `submission`, `flag`, `log`, `navigation` (if enabled), `termination`.
Action Status	`actionStatus`	Whether the action was successful or resulted in an error. Possible values: `succeeded`, `closed`, `initial`, `interacting`, `suspended`.
Reason Code	reasonCode	Numeric identifier describing the category of the event. For more information, see the section on Categories and Reason Codes below.
Reason Message	`reasonMessage`	Provides additional context for the logged events, either in the form of the text comment left by proctors on their actions, or in the form of a data structure, when the `Action Code` is `40999`
Extra Time	`extraTime`	Additional minutes assigned by a proctor (when `action = update`).
Incident Time	`incidentTime`	The time of the action (provided as a unix timestamp).
Last_Update_Date	`last_update_date`	The date the session was last updated (provided as a unix timestamp).
Item Id	`itemId`	The unique identifier of the item within the scope of the action.
Resource Link	`resourceLink`	Test session ID or test context ID.
Status	`status`	Session status at time of logging. Possible values: `initial`, `interacting`, `suspended`, `terminated`, `closed`.
Tenant Id	`tenantId`	The unique identifier for the TAO environment on which the action was executed.
User Agent	`userAgent`	Browser and system details.
IP	`ip`	Internet Protocol address.
Message Id	`messageId`	The unique identifier for a message or transaction between the client and the API.
	`_id`	Internal system identifier for the log entry (identical to the delivery execution ID).

Proctoring ACS logs in TAO Insights can now include information about various actions the test-taker took within the test, such as navigating, submitting, or interacting in different ways with the test (such as entering or exiting full-screen mode, or copy / pasting content). This information is provided in the values of navigation and interaction (Reason Code 40999) fields. To enable this feature, please contact your Account Manager.

Clarified field definitions

Actor

Defines the source of the event:

Value	Description
`test-taker`	Assessment participant (disabled by default).
`proctor`	User supervising the assessment.
`system`	Automated or scheduled TAO process (e.g., auto-submission).
`deliver-fe`	Client-side (front-end) errors or browser-generated logs.

Action

Represents the event type:

Action	Description
`start`	The test-taker started the delivery execution (session). Disabled by default.
`pause`	The session was paused (by a proctor or a security trigger).
`resume`	The session was resumed. Disabled by default.
`terminate`	The proctor terminated the session.
`reset`	The proctor erased the test-taker’s attempt and reopened it.
`submission`	The test-taker submitted the assessment. Disabled by default.
`update`	The proctor added time to the session (`extraTime` field).
`flag`	A noteworthy/additional security plugin event logged without changing delivery state (even if security was breached).
`log`	Generic event, often for client-side or network messages.
`navigation`	A test taker submitted a response and navigated to another item.

Action Status

Indicates the result of the attempted action:

Value	Description
`succeeded`	Action was completed successfully.
`failed`	Action failed or was interrupted.

Status

Reflects the delivery execution (session) state:

Status	Description
`initial`	Test ready but not yet started.
`authorized`	Authorized by administrator but not started.
`interacting`	Test-taker interacting with test.
`suspended`	Paused by proctor or system.
`terminated`	Ended by proctor.
`closed`	Submitted and closed.
`canceled`	Canceled by test-taker.

Cause and Reason Codes

When a proctor takes an action (such as reporting or terminating a session), they must specify a Cause and a Reason for taking that action. These specifications display as a Reason Code in a proctoring log.

Cause category	Reason Code	Exact Cause	Description
Environment	10010	COMFORT	N/A
	10020	DISTURBANCE	N/A
	10030	NOISE	N/A
	10040	POWER OUTAGE	N/A
	10050	WEATHER	N/A
	10999	OTHER	N/A
Examinee	20010	BEHAVIOUR	N/A
	20020	COMPLAINT	N/A
	20030	ID/AUTHORIZATION	N/A
	20040	ILLNESS	N/A
	20050	LATE	N/A
	20060	NAVIGATION	Events related to full-screen mode or tab changes.
	20999	OTHER	e.g., keyboard shortcuts or forbidden actions.
Proctor/Staff	30010	BEHAVIOUR	N/A
	30020	COMPLIANCE	N/A
	30030	ERROR	N/A
	30040	LATE	N/A
	30999	OTHER	N/A
Technical	40010	FREEZING	N/A
	40020	LAUNCHING	N/A
	40030	NETWORK	N/A
	40040	PRINTING	N/A
	40050	TESTING WORKSTATION	N/A
	40999	OTHER	May contain structured XML describing navigation events.

Actor-specific actions

This section outlines and describes the possible values of the Action field.

Proctor actions

This section describes the possible values for the Action field when the Actor field is set to proctor.

Commonly logged proctor operations:

pause: temporarily suspend a session
resume: continue a suspended session
terminate: end a session
reset: restart a test-taker’s session attempt
update: assign additional time (extraTime)
flag: log a non-critical event

Each may include a reason code and/or a reason message entered by the proctor.

Test-taker actions

This section describes the possible values for the Action field when the Actor field is set to test-taker.

When enabled, test-taker events may include:

start, resume, pause, submission, log
Reason Code 20060 or 40999 (navigation or fullscreen-related events)

System and Client Logs

This section describes the possible values for the Action field when the Actor field is set to deliver-fe or system.

System actions include auto-submissions, timeouts, or session finalization.
Client (deliver-fe) logs capture browser or network-level messages, often with action = log and reasonMessage containing diagnostic details.

Reason Messages by Actor

Actor	Reason Code	Example Reason Message
Proctor	10010–40999	`Comment by the proctor`
Test-taker	20060	`[Full Screen] Test-taker exited full screen.`
	20060	`[Pause On Blur] Test-taker switched tab or window.`
	20999	`[Disable Right Click] Test-taker used right-click menu.`
	20999	`[Disable Commands] Attempted forbidden command: copy / cut / paste.`
System / Technical	40999	Structured navigation data (XML/JSON).

Example scenarios

Example 1: Test-Taker navigation and submission

Step	Action	Details
1	`start`	Session begins (`actor = test-taker`).
2	`move` (`40999`)	Navigation between items.
3	`pause`	Triggered by leaving full screen or browser focus.
4	`submission`	Final test submission event.

Example 2: Proctoring

Step	Action	Description
1	`pause`	Proctor pauses a test session.
2	`resume`	Session is resumed.
3	`update`	Extra time granted.
4	`terminate`	Delivery terminated by proctor.

Each proctor action includes:

A corresponding reason code (e.g., 30030 ERROR, 30040 LATE)
A reason message (proctor’s comment or system text)