# NIST AI RMF Drafter — MANAGE
Draft MANAGE.1 through MANAGE.4 for an AI system.

_Generate the MANAGE function write-up for an NIST AI RMF profile. One paragraph per subcategory, focused on prioritization and response._

Used in: Lesson expert/07 — https://vetslearn.com/lessons/expert/07
Source: https://vetslearn.com/resources/templates/prompts#t-nist-ai-rmf-section-drafter-manage

---

## Context
You are an AI governance lead writing an NIST AI RMF 1.0 profile. The MANAGE function covers risk prioritization, response, third-party risk, and continuous improvement. You write for an evaluator who wants to see real decisions, not aspirations.

The AI system is [SYSTEM NAME], owned by [ORG NAME].
Intended use: [INTENDED USE]
Potential harms: [POTENTIAL HARMS]
Who uses it: [WHO USES IT]
Incident response owner: [INCIDENT RESPONSE OWNER]

## Task
Draft one paragraph for each MANAGE subcategory, MANAGE.1 through MANAGE.4. Use the official NIST AI RMF subcategory names as the paragraph headers.

## Standards
- One paragraph per subcategory. 4 to 7 sentences.
- Name the response owner, escalation path, and decision threshold where I gave you enough. Where I did not, write [TO BE NAMED].
- Show how risks are ranked, not just listed.
- Reference the rollback or shut-off path. If there is no rollback, say so.
- Cite NIST AI RMF 1.0 (2023) once at the top.

---

**Why this works**

MANAGE is the function that proves the rest of the profile is real. An evaluator wants to see an owner, a threshold, and a shut-off path. Forcing the AI to name those three keeps the paragraphs from sounding like a policy template. Saying "there is no rollback" out loud is better than pretending one exists.

## Check before you use it

- Check subcategory names and numbering against NIST AI RMF 1.0. The AI misnumbers them.
- The response owner and escalation path must be people and channels that exist. Confirm with them.
- If it described a rollback path, test that the path works.