# Monitoring and renewal calendar

TX-RAMP | Worked example with fictional data

Step: Monitor, report and renew
Owner: Security operations + incident lead + contract owner
When: After award and before expiry

## Gather first
- Award
- Manual 4.0
- Contract
- Vulnerability report
- Change register
- Incident policy

## How to prepare it
1. Record the award route, level, confirmed expiry, reporting cadence, contacts and backups. Schedule review of reporting dates and record each submission receipt.
2. Keep approved incident and significant change paths beside routine reporting. Assign the renewal lead and open a recertification task 12 months before expiry if the team is ready.
3. During each reporting cycle reconcile the included assets against the approved boundary, identify missing scan coverage and retain a review sign-off.

## Example

### Fictional calendar row
Standard Level 2. Security Operations owns quarterly reporting. The September report shows counts by severity and lists remediation or mitigation for high and critical findings.

### Fictional escalation
A significant change to covered hosting triggers a documented security impact review and the current DIR change request process.

## Review
Owners and backups can explain what goes to DIR, what goes to the agency and when each obligation is due.

## Handoff
Review with operations, counsel and procurement before each renewal.

Use the current rules and any prescribed forms for your engagement.
