Changes · New change event

Record a change event

Saves as draft
Cancel
Record an organizational change that may affect scope, controls, or affirmation readiness. The event is saved as a draft and requires review before a decision is recorded.

Evidence boundary

Safe metadata only

Record coordination information, not raw CUI. Do not paste system exports, account credentials, or controlled technical data into any field. Evidence references belong in external document management systems.

Event identification

Classify the change and record when it occurred. Category and date drive the review priority.

Brief, factual description of the change — safe metadata only.

When the change took effect, not when it was logged.

Select the assessment scope whose boundary this change may affect.

Description

Summarize what changed and the known impact. Use safe coordination language — no raw data, credentials, or CUI.

Describe the change in plain terms. Focus on what affected the scope boundary, controls, or personnel with CUI access.

Comma-separated NIST SP 800-171 control IDs, e.g. 3.1.1, 3.5.3

Review and decision path

After saving, submit for review from the event detail page. The reviewer records the decision outcome and any scope or affirmation impact.

No scope update recorded here

Whether this change requires a scope document revision is determined during the reviewer decision step — not when the event is first logged. Affirmation impact is also set at that stage.
Cancel