Documentation/Faculty

Faculty Documentation

Run classroom-aligned AI teaching workflows using topic progress, student signals, and intervention-oriented course monitoring.

Audience: Faculty members, course owners, and department coordinatorsLast updated: February 2026Format: Step-by-step procedures

At A Glance

  • Operate topic pacing with high fidelity to classroom progression.
  • Interpret student learning signals and react at the right time.
  • Use quizzes and trends to close understanding gaps faster.
  • Maintain consistent weekly rhythms across all assigned courses.

1. Course Readiness

Before teaching starts, validate that course assignments, syllabus quality, and operational dependencies are stable.

Validate assigned courses

Objective: Confirm your working set and student coverage.

Procedure

  1. Open `/faculty` and review cards under Your Courses.
  2. Check each card for course code, course name, student count, and activity badge.
  3. Use the dashboard search box to quickly find expected assigned courses.
  4. Open each course and verify header details match the intended teaching allocation.
  5. If a course is missing or incorrect, share the exact course code/id with Admin for reassignment.
  6. Do not update progress or content for courses that are not officially assigned to you.

Verify syllabus completeness

Objective: Ensure topic structure supports reliable AI support.

Procedure

  1. From course page, open Topic Content to inspect unit/topic list in the left sidebar.
  2. Verify all expected units and topics exist and are named clearly.
  3. Select key topics and confirm content loads in editor (or generate if missing).
  4. Use Progress page to confirm the same topic set is available for pacing updates.
  5. If syllabus order or topic set is incorrect, request Admin correction in course Syllabus Editor.
  6. Start teaching workflow only after topic structure is usable and consistent.

Confirm operational readiness before first class

Objective: Prevent mid-session blockers caused by unresolved setup gaps.

Procedure

  1. Open one assigned course and verify these pages load: Trends, Notes, Progress, and Topic Content.
  2. In Progress page, confirm you can toggle topic statuses and that Save Changes is available.
  3. In Notes page, create one test note and verify it appears in History.
  4. In Topic Content page, open a topic and verify content can be edited/saved.
  5. In Trends page, verify weekly trend card loads (Stable, Needs Attention, or Improving).
  6. If any route fails with authorization or assignment errors, escalate to Admin before class starts.

2. Topic Coverage Workflow

Topic status drives what depth students can access.

Update topic progression

Objective: Keep AI pacing synchronized with actual instruction.

Procedure

  1. Mark topics as not started, in progress, or covered after class.
  2. Apply updates in sequence to avoid progression gaps.
  3. Re-check status before major assessments.

Correct pacing drift

Objective: Prevent confusion from stale or premature topic states.

Procedure

  1. Review course-level progress timeline weekly.
  2. Identify skipped or out-of-order topics.
  3. Realign statuses and notify students of corrected pacing.

3. Student Learning Signals

Use engagement, misconception, and progression signals to prioritize instructional effort where learning impact is highest.

Analyze weak-topic patterns

Objective: Spot repeated confusion before it compounds.

Procedure

  1. Open course home and review Topic Analysis (Last 14 Days).
  2. Focus on topics with higher Questions and Examples Req. counts.
  3. Use status badges (Struggling, Learning, Stable) to prioritize support effort.
  4. Open Trends page and compare current week count vs previous week count.
  5. Treat sustained high interaction load as a signal to reinforce that topic in class.
  6. After intervention, revisit Topic Analysis and Trends to confirm load is reducing.

Use notes for intervention

Objective: Turn observation into repeatable remediation actions.

Procedure

  1. Open Notes page and add a short observation after class or doubt sessions.
  2. Keep note format consistent: topic, observed issue, and planned teaching correction.
  3. Use notes as your intervention queue for the next teaching slot.
  4. Keep notes private and course-specific; they are not visible to students.
  5. Review historical notes weekly to see repeated misconceptions.
  6. Close a note item only after Topic Analysis or class feedback shows improvement.

Prioritize interventions by severity

Objective: Allocate limited teaching time to the highest-impact student needs.

Procedure

  1. Rank topics by combined signal strength: high question count, repeated example requests, and `Struggling` status.
  2. Prioritize prerequisite topics first because they block downstream units.
  3. Address medium-severity items with focused recap rather than full reteach.
  4. Handle low-severity items through quick clarification in regular class flow.
  5. Track what action you took in Notes so follow-up is measurable.
  6. Escalate to Admin when root cause is syllabus/content structure, not just teaching pace.

Close the signal-to-action loop

Objective: Ensure analytics insights are converted into verified learning improvements.

Procedure

  1. For each high-signal topic, define one specific classroom intervention.
  2. Execute the intervention and re-check Topic Analysis after enough student interactions accumulate.
  3. If Trends remains Needs Attention, adjust method and repeat with narrower topic focus.
  4. Use Notes history as your evidence log of signal -> action -> outcome.
  5. Share persistent blockers with Admin when content-level fixes are needed.

4. Quiz and Mastery Loop

In Cognicampus, quizzes are student-driven (`Practice` button). Faculty mastery work is to use those attempts plus trend signals to guide remediation.

Drive student quiz attempts at the right time

Objective: Use student practice behavior as a learning checkpoint.

Procedure

  1. After marking a topic as in progress or covered, ask students to run Practice from their learning workspace.
  2. Remember: Practice is disabled for students when a topic is still `not_started`.
  3. Use this behavior to time checks after class completion, not before topic start.
  4. Track follow-up signal changes on faculty Topic Analysis and Trends pages.
  5. If load remains high after practice, treat topic as not yet mastered at cohort level.

Close the mastery loop

Objective: Move students from clarification to competence.

Procedure

  1. Identify topics with persistent `Struggling` status or increasing weekly interaction counts.
  2. Deliver focused recap in class, then request a second student Practice attempt.
  3. Re-check Topic Analysis to confirm question/example pressure is reducing.
  4. Mark remediation as effective only when signals stabilize to Learning or Stable.
  5. Keep unresolved topics in Notes and carry them into next teaching cycle.

Design practice-to-intervention pathways

Objective: Convert student practice behavior into repeatable teaching actions.

Procedure

  1. Define simple rules: repeated Struggling topics -> deep reteach; moderate spikes -> targeted recap; stable topics -> continue pacing.
  2. Use Trends page for weekly direction and Topic Analysis for topic-level specificity.
  3. Apply same intervention pattern for repeated topic failures across batches.
  4. Document effective patterns in Notes so they can be reused next term.
  5. Escalate to Admin if intervention is blocked by missing/incorrect topic content.

Validate mastery over time

Objective: Confirm that gains persist beyond immediate post-remediation checks.

Procedure

  1. Revisit previously weak topics in later classes and observe whether signal load stays controlled.
  2. If topic pressure relapses in Trends/Topic Analysis, revisit prerequisites.
  3. Do not mark long-term mastery on one good day; confirm stability across multiple sessions.
  4. Use Notes history to compare before/after patterns per topic.
  5. Keep a short end-of-week summary of stable vs unstable topics for planning.

5. Weekly Operating Rhythm

A fixed weekly operating cycle keeps teaching delivery, student progress, and intervention quality aligned.

Run weekly review cycle

Objective: Keep delivery, engagement, and governance aligned.

Procedure

  1. Set one weekly review slot and open each assigned course.
  2. Review Progress page first: confirm topic statuses reflect actual teaching coverage.
  3. Review course home Topic Analysis table for top weak topics.
  4. Open Trends page to determine whether interaction pressure is improving or worsening.
  5. Check Notes page and close completed intervention items.
  6. List blockers requiring Admin action (assignment/content/syllabus access issues).

Plan next-week instructional priorities

Objective: Convert review findings into an executable weekly teaching plan.

Procedure

  1. Build a short list of high-priority topics per course from this week’s signals.
  2. Reserve time for both forward coverage and remediation of Struggling topics.
  3. Schedule when students should run Practice after each remediation segment.
  4. Keep plan realistic: resolve prerequisites before advancing difficult downstream units.
  5. Capture the plan in your own teaching tracker or Notes workflow.

Track execution and adaptation

Objective: Ensure weekly plans are executed and adjusted based on evidence.

Procedure

  1. Mid-week, verify planned progress updates were actually applied in the Progress page.
  2. If high-severity signals appear, re-order the week plan immediately.
  3. Use Notes to record deviations and what corrective action you took.
  4. At week end, compare expected vs actual trend movement.
  5. Carry forward unresolved topics explicitly into next week’s first class slot.

Maintain faculty-admin escalation loop

Objective: Close operational gaps quickly through structured communication.

Procedure

  1. Escalate with concrete detail: course id/code, affected page, and observed issue.
  2. Include whether issue blocks Progress, Topic Content, Notes, or Trends workflow.
  3. Confirm fixes directly in the product before marking escalation closed.
  4. If issue repeats weekly, raise severity and request structural fix from Admin.
  5. Keep a short weekly closure note so unresolved issues stay visible.

Related Links

Go to Platform LoginHow It WorksAI AgentsContact Team