# Server Feedback Template

> **Do not include secrets or PII.** Never paste passwords, tokens, keys, cookies, `.env` values, database records, private user details, full request headers, or unredacted logs/screenshots. Use restricted evidence storage and provide only its approved reference.

Copy the structure below for each issue or acceptance response.

## Submission details

- Date/time (UTC):
- Reporter/team:
- Environment and active application URL:
- Server/region (non-sensitive identifier):
- Commit SHA:
- Artifact name:
- Artifact checksum:
- Related acceptance check number:
- Result (Accepted / Accepted with conditions / Rejected):

## Classification

- Category (access/TLS/runtime/database/mail/queue/storage/application/performance/other):
- Severity (Critical / High / Medium / Low):
- Frequency (Always / Intermittent / Once):
- Regression (Yes / No / Unknown):

## Summary

One concise sentence describing the issue or outcome.

## Steps to reproduce

1.
2.
3.

Use sanitized test data only.

## Expected result

Describe the intended observable behavior.

## Actual result

Describe the observed behavior, status code, and sanitized error text.

## Impact

State affected users/functions, operational risk, and whether deployment acceptance is blocked. Do not identify individual users.

## Evidence

- UTC timestamps:
- Sanitized log excerpt or restricted evidence reference:
- Browser/device or command used:
- Correlation/request ID (only if non-sensitive):

## Workaround

Document a safe temporary workaround, or `None known`.

## Follow-up

- Suggested next action:
- Owner:
- Target date:
- Retest result/date:
- Additional sanitized notes: