COPRSETR WORKSHEET
Monitoring and renewal calendar
TX-RAMP · Step 5 · Monitor, report and renew- Who prepares it
- Security operations + incident lead + contract owner
- When to prepare it
- After award and before expiry
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- 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.
Gather first
- Award
- Manual 4.0
- Contract
- Vulnerability report
- Change register
- Incident policy
How to prepare it
- Record the award route, level, confirmed expiry, reporting cadence, contacts and backups. Schedule review of reporting dates and record each submission receipt.
- 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.
- During each reporting cycle reconcile the included assets against the approved boundary, identify missing scan coverage and retain a review sign-off.
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.