Change Request Form

No. It records a proposal for human review. A responsible owner must communicate a separate decision and any conditions, owner, budget, schedule, testing, rollback, communication, and verification requirements through the approved process.

No. It does not amend a contract, authorize spending, approve a policy, grant access, waive a control, or create a binding commitment. Use reviewed legal, procurement, finance, governance, signature, and recordkeeping processes where they apply.

No. Priority and timing are requester-provided context. The receiving team should assess impact, authority, dependencies, capacity, risk, legal obligations, and existing commitments before setting an actual priority, owner, change window, or delivery date.

No. Keep secrets, credentials, vulnerability details, private keys, payment data, government identifiers, medical records, personnel files, regulated records, production data, and unnecessary third-party information out of a general intake. Use an approved restricted channel when specialist evidence is genuinely needed.

Do not rely on this form for an active outage, suspected security event, immediate danger, urgent safety issue, or time-critical legal or regulatory notice. Publish and use the organization's monitored incident, security, emergency, safeguarding, legal, or regulatory route instead.