Connect evidence, decision, execution, and record
Follow the audit lifecycle while preserving visibility and redaction boundaries.
- Audience
- moderator · senior reviewer · team lead
- Availability
- private beta access
- Maturity
- alpha
Last reviewed
On this page
Outcome
You will distinguish the source material, moderator decision, separately authorized execution, and durable audit record in one review workflow.
Set up the lesson
- An authorized case or moderation record.
- Access to the source evidence required for the review.
- The reviewer or executor permission appropriate to the next step.
Practice the workflow
Open a case
Run /case create with the member, a concrete reason, and an appropriate priority. Keep the returned case number.
Check: You have one open case to receive evidence and later decisions.
Attach the source
Right-click the source message and choose Apps → Add to Active Case, or use /evidence add for an external archive URL. Confirm the destination case and visibility.
Check: The case has a source-aware evidence item rather than a pasted claim with no origin.
Review before deciding
Use /evidence view and the case room or dashboard timeline. Write what the evidence supports and what it does not support.
Check: The decision is attributable to a human reviewer and grounded in visible material.
Execute only the chosen action
If the decision calls for a warning, mute, jail, or ban, run that command separately and include the case number in the reason.
Check: The case decision and Discord execution are distinct, traceable events.
Check the timeline
Open the case after execution and verify the evidence, moderator decision, action result, and any error or redaction state.
Check: A later reviewer can reconstruct the work without broader access than their role allows.
/case create user:@Maya reason:Review repeated harassment priority:High type:Harassment/evidence add case_number:104 title:Message archive description:Messages reported from #general url:https://example.org/archive/104 visibility:Staff/evidence view case_number:104/mute user:@Maya duration:2h reason:Case #104 — repeated harassment after warningVerify your result
The record shows a traceable separation between evidence, decision, execution, and outcome, including safe failure or redaction states.
Use the canonical server-scoped Case
| Field | Use | Warning |
|---|---|---|
| Case ID | Internal links, APIs, buttons, and related records. | Do not substitute a display number across servers. |
| Case number | Human-facing reference allocated within one server. | Case #104 in one server is unrelated to Case #104 elsewhere. |
| Occurred at | Chronological placement of the incident/action. | An imported/backfilled record can be stored later than it occurred. |
| Created at | When ModFlow stored the Case. | Creation time is not always incident time. |
| Activity/timeline | Attributable changes, comments, decisions, execution, and closure. | Visibility can redact content while preserving a safe event summary. |
Native moderation actions create or reuse a Case and link the concrete action. Follow-up unmute, unban, unjail, scheduled execution, appeal, evidence, transcript, or rejoin work should reuse the original Case when the workflow provides that link.
Classify evidence and context correctly
| Type | Examples | How to record it |
|---|---|---|
| Source message | Reported message, jump URL, author, channel, timestamp. | Use message Apps so source identity and visibility checks stay attached. |
| Conversation window | Messages around a key source. | Capture only the supported window and preserve each source identity. |
| External reference | Approved archive URL or report. | Add title, description, URL, and why it matters; do not imply ModFlow controls its availability. |
| Uploaded artifact | Image, document, or other supported Case evidence. | Describe origin, integrity, audience, and any local-storage limitation. |
| Transcript/recording | Jail or Soundcheck artifact actually produced. | Preserve session identity, consent/status, visibility, and processing limits. |
| Staff observation | What a moderator directly observed. | Label it as staff-authored context, not an original source artifact. |
| Imported record | Normalized external moderation entry. | Keep provider, actor, source message, confidence, and occurrence time distinct. |
Preserve evidence visibility and redaction
| Question | Safe practice |
|---|---|
| May this viewer open the Case? | Case visibility is the first check, not the final evidence check. |
| May this viewer open this evidence item? | Respect staff/senior or team-specific visibility. |
| Can the viewer still access the source channel/message? | A Case link does not grant hidden-channel access. |
| Is a local file still available? | Treat missing storage as unavailable; do not reconstruct from unauthorized copies. |
| What may be included in a handoff/export? | Use the visible summary and omit/redact restricted fields. |
Record the decision, execute, and close
State the review question
Write the decision the Case is trying to answer.
Check: The evidence is evaluated against a concrete issue.
Summarize evidence fairly
Record supporting, conflicting, missing, and restricted material.
Check: Uncertainty is visible.
Record the human decision
Choose the supported outcome and explain the policy/reasoning.
Check: The reviewer and decision time are attributable.
Execute separately
Use the authorized action control and read its own result.
Check: Approval is not confused with external action.
Resolve follow-up
Assign notification, reversal, role cleanup, evidence request, or retry work.
Check: Partial outcomes have an owner.
Close with a durable summary
Confirm the final timeline, status, linked records, and remaining limitations.
Check: Another authorized reviewer can reconstruct the lifecycle.
| Condition | Why |
|---|---|
| Execution is pending or uncertain | The decision exists, but the requested action is not verified. |
| Required evidence is still requested | The review question remains open. |
| A reversal or appeal side effect failed | The outcome is only partial. |
| Visibility or redaction is disputed | Closing can hide an unresolved access problem. |
| The target/incident identity is uncertain | The Case can be attached to the wrong person or event. |
Avoid these mistakes
- Copying restricted evidence into a wider audience.
- Assuming approval means execution succeeded.
- Removing the reason or actor from a handoff.
- Using hidden material to justify a decision to someone who cannot inspect it.