FedRAMP Notices¶
FedRAMP rules require you to notify agencies and FedRAMP at set points in an incident, a significant change and a Trust Center access denial. GRC-ITSM puts each notice on its own workflow step, sends it from a templated email you review before it goes, and scores it against the rule's window. This page lists every notice, explains how sending and scoring work, and covers the edge cases: emergencies, changes closed by status, and exercises.
Quick Summary
- Each notice has a Send action on a notice-due step. Send opens the email in preview; nothing goes until you press Send in the preview.
- Send is what moves the ticket on. The fill-in actions record report content only.
- No AI or API tool sends a notice. A person sends every one.
- Each send writes a dated Pass or Fail row on the rule's validation record. The newest row sets the check's status.
- A daily sweep at 06:00 UTC writes an
OWED (sweep):Fail for any notice past its window. A later send replaces that row. - Business-day windows count weekdays. Federal holidays are not excluded.
Notices at a glance¶
| Notice | Rule | Classes | Step where it is due | Action | Window | Scored when | Daily sweep |
|---|---|---|---|---|---|---|---|
| Initial Incident Report (IIR) | IEC-CSO-IIR | MUST B-D, SHOULD A | Initial Report Due | Send FedRAMP Initial Incident Report | PAIN-rated timeframe from the first reportable evaluation | At the send | Yes |
| Ongoing Incident Report (OIR) | IEC-CSO-OIR | MUST B-D, SHOULD A | Ongoing Report Due (also offered on Final Report Due) | Send FedRAMP Ongoing Incident Report | PAIN-rated interval between reports, until recovery is complete | At each send, for the gap since the previous report | Yes |
| Final Incident Report (FIR) | IEC-CSO-FIR | MUST A-D | Final Report Due | Send FedRAMP Final Incident Report | PAIN-rated timeframe after recovery is complete | At the send | Yes |
| SCN: Transformative Initial Plans | SCN-TRF-NIP | MUST B-D | Initial Plans Due | Send SCN: Initial Plans | At least 30 business days before the change starts, checked as 42 calendar days | At Initiate Change | No |
| SCN: Transformative Final Plans | SCN-TRF-NFP | MUST B-D | Final Plans Due | Send SCN: Final Plans | At least 10 business days before the change starts, checked as 14 calendar days | At Initiate Change | No |
| SCN: Transformative Change Complete | SCN-TRF-NAF | MUST B-D | Completion Notice Due | Send SCN: Complete | Within 5 business days after Complete Change | At the send, and at close | Yes |
| SCN: Transformative Verification Complete | SCN-TRF-NAV | MUST B-D | Verification Notice Due | Send SCN: Verified | Within 5 business days after Verification Completed On | At the send, and at close | Yes, open changes |
| SCN: Adaptive Change Complete | SCN-ADP-NTF | MUST B-D | Adaptive Notice Due | Send SCN: Adaptive | Within 10 business days after Complete Change | At the send, and at close | Yes |
| SCN: Emergency Change (Retroactive) | SCN-CSO-EMG | B-D; MAY to use, its MUSTs bind once used | Emergency Notice Due | Send SCN: Emergency | The rule sets no deadline | At close | No |
| Trust Center agency-denial notice | CDS-UTC-AAD | MUST A-D | Denial Notice Due | FedRAMP Notified (records the notice) | Within 5 business days of denying an agency request | At FedRAMP Notified, and at close | Yes |
The PAIN-rated incident timeframes are in the organization-defined values of the Incident Response policy. A reportable incident with no PAIN estimate is timed as PAIN 5 (IEC-CSO-DPR).
Other checks scored alongside the notices
| Check | Rule | Classes | What it tests | Scored when |
|---|---|---|---|---|
| Reportability evaluation | IEC-CSO-EFR | MUST A-D | The incident was evaluated within 1 day of detection, with a reason opening Reportability (IEC-CSO-EFR):. The rule says "promptly"; 1 day is a house threshold. |
At evaluation and each incident send; daily sweep |
| PAIN estimate | IEC-CSO-EFI | SHOULD B-D | A PAIN rating was estimated before the IIR went out | At the IIR send |
| FedRAMP ID | CDS-CSO-FID | MUST B-D | The FedRAMP ID (or the placeholder before one is assigned) was set at the send | At each incident and SCN send |
| Change evaluation | SCN-CSO-EVA | MUST B-D | Description, Change Type and Change Type Explanation were set | At Request Approval |
| Notice content | SCN-CSO-INF | MUST B-D | The required notification information was set on the change | At each SCN send |
| Documentation update | SCN-TRF-UPD | MUST B-D | The "Publish updated service documentation" to-do was completed within 30 business days after Complete Change | At completion and close; daily sweep |
| Post-emergency assessment | SCN-CSO-EMG | B-D, once used | Complete Review was taken with a note opening Post-emergency assessment (SCN-CSO-EMG): |
At close |
How Send works¶
flowchart LR
A["Notice-due step"] --> B["Press the Send action"]
B --> C["Fill required fields"]
C --> D["Email preview"]
D -->|"Press Send"| E["Notice sent<br/>ticket moves on"]
E --> F["Pass or Fail row<br/>on the rule's record"]
D -->|"Close without sending"| A
- Open the ticket on its notice-due step and press the Send action for that notice.
- Complete the required fields. Incident sends require Reported To and the matching Sent At date. Send SCN: Verified requires Verification Completed On, which anchors the verification window.
- Review the email in the preview. The template fills in the notice content from the ticket. Confirm the recipients in the preview before you send.
- Press Send in the preview. Nothing goes out, and the ticket does not move, until you do.
Send is what moves the ticket off a notice-due step. The fill-in actions (Initial Report, Ongoing Report, Final Report) record report content on the ticket only; they do not send anything or change the step. Recovery Complete is the one non-send move in the incident chain: it takes the ticket from Ongoing Report Due to Final Report Due.
No AI or API tool sends a notice
The AI and API record tools fill in report fields only. Every FedRAMP notice is sent by a person pressing Send in the preview.
Before you send a Significant Change Notification
Attach the business or security impact analysis before you press Send; the template states that it is attached. Check the Approved by row: it prints each approver as Name, Title from the agent's Job Title, or the name alone where Job Title is blank. Add any missing title before you press Send, and keep Job Title filled on approver agents. See Change Management.
The Trust Center agency-denial notice is the exception to the email pattern. FedRAMP takes it through its own form; you record it with FedRAMP Notified (a note is required), and that action is what the check scores. The platform does not read the form submission.
Scoring¶
Each notice rule has a validation record under Compliance > Validations, category Validation>Rule. Every scoring writes a dated row on that record.
- The newest row sets the check status. Pass sets Satisfied; Fail sets Not Satisfied.
- A row is written only when a notice is owed. A non-reportable incident, a change type with no notice, or a class the rule does not cover writes nothing. A re-fire that finds the same result writes nothing.
- Scope comes from the customer's highest FedRAMP class.
- Track start dates. Rows are written for 20x from 2026-07-04 and for Rev5 from 2027-01-01.
- Class A. IIR and OIR are scored as SHOULD, and their rows say so in the note. FIR and the reportability evaluation are MUST. Class A has no Significant Change Notification checks and no FedRAMP ID checks.
- Significant Change Notifications apply to Classes B, C and D.
See KSI Tracking for how validation records and their rows roll up.
Error and Not Applicable¶
The notice checks write Pass or Fail rows only.
| Record status | What the notice checks and sweeps do |
|---|---|
| Not Applicable | Leave the record alone. No new rows are written, and the status stays Not Applicable. |
| Error | The next Pass or Fail row replaces Error. |
Daily sweeps¶
Three sweeps run every day at 06:00 UTC: one for incidents, one for Significant Change Notifications and one for the Trust Center denial notice. Each looks for notices that are past their window with nothing sent.
| Sweep | Writes owed rows for |
|---|---|
| Incidents | Reportability evaluation, IIR, OIR (the open gap) and FIR |
| Significant Change Notifications | Change Complete, Verification Complete (open changes), Adaptive Change Complete, and the documentation update |
| Trust Center | The agency-denial notice, for open requests |
- An owed row is a Fail whose note opens
OWED (sweep):, orEXERCISE: OWED (sweep):on an exercise ticket. - While the notice stays owed, the sweep rewrites the same row with each run's time.
- When someone sends the notice, the send's result replaces the owed row in place.
- A sweep never overwrites a Pass.
- A sweep skips a record at Not Applicable.
The Emergency Change notice has no sweep because SCN-CSO-EMG sets no deadline. The initial and final plans notices are scored at Initiate Change, so nothing is left for a sweep to find. Use the Transformative Change Notice Windows report to see changes on Initial Plans Due or Final Plans Due whose planned start is within 42 or 14 calendar days.
Windows¶
- "Within N business days after" counts N weekdays from the anchor date. Federal holidays are not excluded.
- Initial and final plans are checked on calendar days: the initial plans send must come at least 42 calendar days, and the final plans send at least 14 calendar days, before Initiate Change.
- Incident windows follow the PAIN rating in force: at the first reportable evaluation for the IIR, at the start of each gap for the OIR, and at recovery complete for the FIR.
Holidays can shorten a plans window
42 and 14 calendar days equal 30 and 10 weekdays. A federal holiday inside the window leaves fewer than 30 or 10 business days, and the check still passes. Send plans early when a holiday falls in the window.
Emergency changes¶
Emergency is a Yes/No field on the Change Request, not a change type.
- Emergency = Yes skips the advance-notice steps. The initial and final plans notices are not owed. If Emergency is set late with Proceed as Emergency, the plans rows are rewritten as Pass with a "not owed: emergency" note.
- A significant emergency goes to Emergency Notice Due after Complete Change. Send SCN: Emergency sends the notice retroactively.
- Finish and adaptive notices still bind. An emergency Transformative change still owes Change Complete, and an emergency Adaptive change still owes Adaptive Change Complete. A Send SCN: Emergency taken inside that notice's window satisfies it.
- A Transformative emergency still owes the verification notice. After the emergency send it moves on to Verification Notice Due.
- The emergency notice and the post-emergency assessment are scored at close. The assessment is the Complete Review note, which must open
Post-emergency assessment (SCN-CSO-EMG):. - A non-significant emergency change goes to Review with no Send button.
Closing a change by status¶
Closing a Change Request by setting its status skips the workflow, and the checks catch it.
- A Transformative or Adaptive change closed by status without Complete Change Fails the after-change notices it owed: Change Complete, Verification Complete and the documentation update for Transformative, Adaptive Change Complete for Adaptive. This applies whether or not the change was an emergency.
- A cancelled change owes no after-change notices and writes no close-time rows. Cancel Change is offered only before the change is initiated.
Exercises¶
Tick Is Exercise on any ticket raised for a tabletop or exercise.
- Reports. Exercise tickets stay out of the Trust Center (Agency) reports and the POA&M reports.
- Scoring. Exercise tickets are still scored like real ones. Their rows carry an
EXERCISE:prefix and set the check status like any other row. - Emails. Notice emails show an Exercise Status row. The template cannot change the subject or recipients for an exercise, so the sender types
EXERCISE:at the start of the subject and addresses the internal mailbox before pressing Send.
Dates in notice emails¶
Notice emails print dates in UTC and label each one (UTC). Incident notices label the incident start, detection, reportability evaluation and recovery dates; Significant Change Notifications label the planned start and planned completion. A UTC date can be a day later than the same moment in a United States time zone, so convert before you quote a date.
Related pages¶
- Incident Response policy: reportability, PAIN timeframes and the reporting chain
- Change Management policy: change types, the Significant Change Notification steps and emergency changes
- Certification Data Sharing policy: Trust Center access and the agency-denial notice
- Data Removal policy: agency removal requests and spills
- KSI Tracking: validation records, rows and status rollup
- Trust Center Access and Data Removal Request ticket types