Faculty WizardFaculty Wizard

Methodology

How Faculty Wizard transforms rough notes into clear, fact-focused, dispute-resilient feedback.

What the tool does (and does not do)

  • Does: rewrite notes into professional, fact-focused feedback based on the facts present in your input.
  • Does not: assess student work, change grades, provide instruction, or store your input. It uses no context outside of the input.

The transformation flow (high-level, non-technical)

Input → (1) Normalization & structure → (2) Evidence-first framing → (3) Tone & compliance pass → Output

Output is structured into three sections:

  • Outcome / status label (e.g., Met Requirements / Not Yet)
  • Evidence-first rationale tied to observable criteria
  • Optional closing call to action (brief next-step suggestion)

To omit the closing call to action, include “no call to action”, “no action”, or “no action items” in your input.

Guardrails

Uses neutral language, avoids assumptions, focuses on observable criteria, and avoids overreach.

Privacy model

No storage of notes or output, with minimal technical logging only (e.g., word counts and timestamps). Faculty Wizard exists only as a tool to make faculty life easier by transforming rough thoughts into professional feedback; Faculty Wizard does not want your data. See the full details in the Privacy & Impressum.

When to use it / when not to

  • Use: when writing quick & messy assessment notes (e.g., while watching a video component), emotional drafts that might trigger a dispute, or under time pressure when expertise must be shared quickly & professionally.
  • Avoid: adding new claims you did not observe (the tool uses no context outside of input)

Examples

See real-world style transformations from raw notes to student-facing feedback.

View examples