mirror of
https://github.com/opelly27/WinStudentGoalTracker.git
synced 2026-05-20 01:47:41 +00:00
ivan-pelly
996 lines
34 KiB
HTML
996 lines
34 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="UTF-8" />
|
||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||
<meta
|
||
name="description"
|
||
content="WIN Student Goal Tracker user manual for teachers and program staff."
|
||
/>
|
||
<meta name="theme-color" content="#111827" />
|
||
<title>WIN Student Goal Tracker - User Manual</title>
|
||
|
||
<style>
|
||
:root{
|
||
--bg:#f5f7fa;
|
||
--card:#ffffff;
|
||
--text:#111827;
|
||
--muted:#4b5563;
|
||
--border:rgba(17,24,39,.08);
|
||
--shadow:0 8px 24px rgba(17,24,39,.08);
|
||
--primary:#2563eb;
|
||
--primary-dark:#1d4ed8;
|
||
--header:#111827;
|
||
--success:#16a34a;
|
||
}
|
||
|
||
*{box-sizing:border-box;}
|
||
|
||
html{scroll-behavior:smooth;}
|
||
|
||
body{
|
||
margin:0;
|
||
font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Ubuntu,sans-serif;
|
||
background:var(--bg);
|
||
color:var(--text);
|
||
line-height:1.65;
|
||
}
|
||
|
||
header{
|
||
background:var(--header);
|
||
color:#fff;
|
||
padding:3rem 1.25rem 2.5rem;
|
||
text-align:center;
|
||
}
|
||
|
||
header h1{
|
||
margin:0;
|
||
font-size:clamp(2rem,4vw,2.6rem);
|
||
line-height:1.15;
|
||
}
|
||
|
||
header p{
|
||
margin:.85rem auto 0;
|
||
max-width:760px;
|
||
color:rgba(255,255,255,.88);
|
||
font-size:1.05rem;
|
||
}
|
||
|
||
.hero-actions{
|
||
display:flex;
|
||
flex-wrap:wrap;
|
||
justify-content:center;
|
||
gap:.75rem;
|
||
margin-top:1.5rem;
|
||
}
|
||
|
||
.btn{
|
||
display:inline-flex;
|
||
align-items:center;
|
||
justify-content:center;
|
||
padding:.8rem 1.05rem;
|
||
border-radius:12px;
|
||
text-decoration:none;
|
||
font-weight:700;
|
||
border:1px solid rgba(255,255,255,.08);
|
||
transition:.2s ease;
|
||
}
|
||
|
||
.btn-primary{
|
||
background:var(--primary);
|
||
color:#fff;
|
||
}
|
||
|
||
.btn-primary:hover{
|
||
background:var(--primary-dark);
|
||
}
|
||
|
||
.btn-secondary{
|
||
background:#fff;
|
||
color:var(--text);
|
||
}
|
||
|
||
.btn-secondary:hover{
|
||
background:#eef2ff;
|
||
}
|
||
|
||
main{
|
||
max-width:1100px;
|
||
margin:0 auto;
|
||
padding:1.25rem 1rem 3rem;
|
||
}
|
||
|
||
.layout{
|
||
display:grid;
|
||
grid-template-columns:1fr;
|
||
gap:1rem;
|
||
}
|
||
|
||
@media (min-width: 980px){
|
||
.layout{
|
||
grid-template-columns:280px 1fr;
|
||
align-items:start;
|
||
}
|
||
|
||
.toc{
|
||
position:sticky;
|
||
top:1rem;
|
||
}
|
||
}
|
||
|
||
.card{
|
||
background:var(--card);
|
||
border:1px solid var(--border);
|
||
border-radius:16px;
|
||
box-shadow:var(--shadow);
|
||
padding:1.25rem;
|
||
}
|
||
|
||
.toc h2,
|
||
.content h2{
|
||
margin-top:0;
|
||
}
|
||
|
||
.toc ul{
|
||
list-style:none;
|
||
padding:0;
|
||
margin:0;
|
||
}
|
||
|
||
.toc li + li{
|
||
margin-top:.55rem;
|
||
}
|
||
|
||
.toc a{
|
||
color:var(--text);
|
||
text-decoration:none;
|
||
}
|
||
|
||
.toc a:hover{
|
||
color:var(--primary);
|
||
}
|
||
|
||
.toc .small{
|
||
color:var(--muted);
|
||
font-size:.95rem;
|
||
margin-top:1rem;
|
||
}
|
||
|
||
.content section + section{
|
||
margin-top:1rem;
|
||
}
|
||
|
||
.section-title{
|
||
font-size:1.35rem;
|
||
margin:0 0 .5rem;
|
||
}
|
||
|
||
.muted{
|
||
color:var(--muted);
|
||
}
|
||
|
||
.grid{
|
||
display:grid;
|
||
grid-template-columns:1fr;
|
||
gap:1rem;
|
||
}
|
||
|
||
@media (min-width: 760px){
|
||
.grid.two{
|
||
grid-template-columns:1fr 1fr;
|
||
}
|
||
}
|
||
|
||
.info-list,
|
||
.content ol,
|
||
.content ul{
|
||
padding-left:1.2rem;
|
||
}
|
||
|
||
.info-list li,
|
||
.content li{
|
||
margin:.3rem 0;
|
||
}
|
||
|
||
.callout{
|
||
background:#eff6ff;
|
||
padding:1rem;
|
||
border-radius:12px;
|
||
margin-top:1rem;
|
||
}
|
||
|
||
.callout.success{
|
||
background:#f0fdf4;
|
||
}
|
||
|
||
.callout.warn{
|
||
background:#fffbeb;
|
||
}
|
||
|
||
code{
|
||
background:#eef2ff;
|
||
padding:.15rem .4rem;
|
||
border-radius:6px;
|
||
font-family:ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;
|
||
font-size:.95em;
|
||
}
|
||
|
||
.steps{
|
||
margin-top:.75rem;
|
||
}
|
||
|
||
.kpis{
|
||
display:grid;
|
||
grid-template-columns:repeat(2,1fr);
|
||
gap:.75rem;
|
||
margin-top:1rem;
|
||
}
|
||
|
||
@media (min-width: 760px){
|
||
.kpis{
|
||
grid-template-columns:repeat(4,1fr);
|
||
}
|
||
}
|
||
|
||
.kpi{
|
||
background:#f9fafb;
|
||
border:1px solid var(--border);
|
||
border-radius:14px;
|
||
padding:1rem;
|
||
text-align:center;
|
||
}
|
||
|
||
.kpi strong{
|
||
display:block;
|
||
font-size:1.25rem;
|
||
margin-bottom:.25rem;
|
||
}
|
||
|
||
.role-table{
|
||
width:100%;
|
||
border-collapse:collapse;
|
||
margin-top:1rem;
|
||
font-size:.95rem;
|
||
}
|
||
|
||
.role-table th,
|
||
.role-table td{
|
||
text-align:left;
|
||
padding:.5rem .75rem;
|
||
border:1px solid var(--border);
|
||
}
|
||
|
||
.role-table th{
|
||
background:#f3f4f6;
|
||
font-weight:600;
|
||
}
|
||
|
||
.role-table tr:nth-child(even) td{
|
||
background:#f9fafb;
|
||
}
|
||
|
||
.footer{
|
||
text-align:center;
|
||
color:var(--muted);
|
||
padding:2rem 1rem 3rem;
|
||
font-size:.95rem;
|
||
}
|
||
|
||
.back-link{
|
||
margin-top:1.25rem;
|
||
display:inline-flex;
|
||
align-items:center;
|
||
gap:.5rem;
|
||
}
|
||
</style>
|
||
</head>
|
||
<body>
|
||
<header>
|
||
<h1>WIN Student Goal Tracker</h1>
|
||
<p>
|
||
User manual for teachers, program staff, and administrators using the WIN
|
||
platform to manage students, goals, benchmarks, and progress events.
|
||
</p>
|
||
|
||
<div class="hero-actions">
|
||
<a
|
||
class="btn btn-primary"
|
||
href="https://win.opelly.me/login"
|
||
target="_blank"
|
||
rel="noopener noreferrer"
|
||
>
|
||
Open Live Application
|
||
</a>
|
||
<a class="btn btn-secondary" href="index.html">
|
||
Back to Project Home
|
||
</a>
|
||
</div>
|
||
</header>
|
||
|
||
<main>
|
||
<div class="layout">
|
||
<aside class="toc card">
|
||
<h2>Contents</h2>
|
||
<ul>
|
||
<li><a href="#overview">1. Overview</a></li>
|
||
<li><a href="#roles">2. User Roles</a></li>
|
||
<li><a href="#registration">3. Registering a New District</a></li>
|
||
<li><a href="#access">4. Accessing the Application</a></li>
|
||
<li><a href="#program">5. Selecting a Program</a></li>
|
||
<li><a href="#dashboard">6. Student Dashboard</a></li>
|
||
<li><a href="#add-student">7. Adding & Editing Students</a></li>
|
||
<li><a href="#goals">8. Managing Goals</a></li>
|
||
<li><a href="#benchmarks">9. Managing Benchmarks</a></li>
|
||
<li><a href="#events">10. Recording Progress Events</a></li>
|
||
<li><a href="#deleting">11. Deleting Records</a></li>
|
||
<li><a href="#reports">12. Reports</a></li>
|
||
<li><a href="#admin">13. Administration</a></li>
|
||
<li><a href="#mobile">14. Mobile Experience</a></li>
|
||
<li><a href="#workflow">15. Typical Workflow</a></li>
|
||
<li><a href="#tips">16. Usage Notes</a></li>
|
||
</ul>
|
||
|
||
<p class="small">
|
||
Prototype demo login:<br />
|
||
<code>opelly@gmail.com</code><br />
|
||
<code>1234</code><br />
|
||
(Teacher role — for demo use only)
|
||
</p>
|
||
</aside>
|
||
|
||
<div class="content">
|
||
<section id="overview" class="card">
|
||
<h2 class="section-title">1. Overview</h2>
|
||
<p class="muted">
|
||
The WIN Student Goal Tracker is a web-based application designed to
|
||
help teachers and program staff organize student progress in a
|
||
structured way. Users can review assigned students, create or review
|
||
goals, define benchmarks, and document progress events over time.
|
||
The application works on both desktop and mobile devices.
|
||
</p>
|
||
|
||
<div class="kpis">
|
||
<div class="kpi">
|
||
<strong>Students</strong>
|
||
Managed by teacher
|
||
</div>
|
||
<div class="kpi">
|
||
<strong>Goals</strong>
|
||
Tracked per student
|
||
</div>
|
||
<div class="kpi">
|
||
<strong>Benchmarks</strong>
|
||
Milestones per goal
|
||
</div>
|
||
<div class="kpi">
|
||
<strong>Progress Events</strong>
|
||
Documentation of progress
|
||
</div>
|
||
</div>
|
||
|
||
<div class="callout">
|
||
This manual covers teacher and program staff workflows as well as
|
||
district administration features including program management and
|
||
user provisioning.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="roles" class="card">
|
||
<h2 class="section-title">2. User Roles</h2>
|
||
<p class="muted">
|
||
Every user account is assigned a role when added to a program. The
|
||
role determines which actions that user can perform. There are five
|
||
roles in the system.
|
||
</p>
|
||
|
||
<table class="role-table">
|
||
<thead>
|
||
<tr>
|
||
<th>Role</th>
|
||
<th>Description</th>
|
||
<th>Key Permissions</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td><strong>Teacher</strong></td>
|
||
<td>Standard instructional staff member</td>
|
||
<td>
|
||
Full access to their own students — create, edit, and delete
|
||
students, goals, benchmarks, and progress events. Can run
|
||
reports and use AI suggestions.
|
||
</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Paraeducator</strong></td>
|
||
<td>Support staff assisting teachers</td>
|
||
<td>
|
||
Can view students and log progress events. Cannot create or
|
||
delete students, goals, or benchmarks, and cannot run reports
|
||
or use AI suggestions.
|
||
</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Program Admin</strong></td>
|
||
<td>Staff member who manages an entire program</td>
|
||
<td>
|
||
Same as Teacher but scoped across all students in the program,
|
||
not just their own. Can run reports.
|
||
</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>District Admin</strong></td>
|
||
<td>Administrator who manages a school district</td>
|
||
<td>
|
||
All Program Admin abilities plus access to the Administration
|
||
panel. Can create and edit programs and add users to any
|
||
program within the district.
|
||
</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Super Admin</strong></td>
|
||
<td>System-level administrator</td>
|
||
<td>
|
||
Full access across all districts and programs. Can assign any
|
||
role, including Super Admin. Reserved for platform operators.
|
||
</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
|
||
<div class="callout">
|
||
A user's role is set when their account is created by a District
|
||
Admin. If you are unsure of your role, contact your district
|
||
administrator.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="registration" class="card">
|
||
<h2 class="section-title">3. Registering a New District</h2>
|
||
<p class="muted">
|
||
If your school district is not yet set up in the system, a district
|
||
administrator can self-register to create the district account, an
|
||
initial program, and their own login in one step.
|
||
</p>
|
||
|
||
<div class="callout warn">
|
||
Registration creates a new, independent district. If your district
|
||
already exists, do not register again — contact your existing
|
||
district administrator to have a user account created for you.
|
||
</div>
|
||
|
||
<h3>How to register</h3>
|
||
<ol>
|
||
<li>
|
||
Go to <code>https://win.opelly.me/register</code> or click
|
||
<strong>Register</strong> from the login page.
|
||
</li>
|
||
<li>
|
||
Fill in <strong>Your Details</strong>: name, email address, and
|
||
password. This becomes your login.
|
||
</li>
|
||
<li>
|
||
Fill in <strong>District Details</strong>: district name and an
|
||
optional contact email for the district.
|
||
</li>
|
||
<li>
|
||
Fill in <strong>Your First Program</strong>: the name and optional
|
||
description of the first program in your district (e.g.
|
||
"Special Education").
|
||
</li>
|
||
<li>Click <strong>Create District & Account</strong>.</li>
|
||
</ol>
|
||
|
||
<div class="callout success">
|
||
After registration you will be directed to the login page. Sign in
|
||
with your new credentials. You will be assigned the District Admin
|
||
role automatically and can add more programs and users from the
|
||
Administration panel.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="access" class="card">
|
||
<h2 class="section-title">4. Accessing the Application</h2>
|
||
<p>
|
||
To begin, open the login page at
|
||
<code>https://win.opelly.me/login</code>.
|
||
</p>
|
||
|
||
<div class="steps">
|
||
<ol>
|
||
<li>Enter your assigned email address.</li>
|
||
<li>Enter your password.</li>
|
||
<li>Click <strong>Sign in</strong>.</li>
|
||
</ol>
|
||
</div>
|
||
|
||
<div class="callout success">
|
||
After a successful login, the system will take you to the program
|
||
selection screen.
|
||
</div>
|
||
|
||
<div class="callout">
|
||
If your account is locked after repeated failed attempts, you will
|
||
see a message indicating the account is temporarily unavailable.
|
||
Wait a few minutes before trying again or contact your administrator.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="program" class="card">
|
||
<h2 class="section-title">5. Selecting a Program</h2>
|
||
<p class="muted">
|
||
After authentication, the system displays the list of programs
|
||
available to the logged-in user. Each program card shows the
|
||
program name, your role (e.g. Teacher, District Admin), and whether
|
||
it is your primary program.
|
||
</p>
|
||
|
||
<ol>
|
||
<li>Review the available program cards.</li>
|
||
<li>Click the program you wish to work in.</li>
|
||
<li>The application will open the main dashboard for that program.</li>
|
||
</ol>
|
||
|
||
<div class="callout">
|
||
A user can belong to multiple programs with different roles in each.
|
||
Selecting a program loads a session scoped to that program — switch
|
||
programs by logging out and logging back in.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="dashboard" class="card">
|
||
<h2 class="section-title">6. Student Dashboard</h2>
|
||
<p>
|
||
The main dashboard displays the students assigned to the current
|
||
teacher or user.
|
||
</p>
|
||
|
||
<div class="grid two">
|
||
<div>
|
||
<h3>Sidebar</h3>
|
||
<ul class="info-list">
|
||
<li>
|
||
The left sidebar lists all students. Each entry shows the
|
||
student's <strong>name</strong> and <strong>IEP date</strong>.
|
||
</li>
|
||
<li>
|
||
Use the <strong>My Students / All</strong> toggle to switch
|
||
between viewing only your own students and all students in
|
||
the program.
|
||
</li>
|
||
<li>
|
||
Students may be organized into labeled groups if a Program
|
||
Admin or District Admin has configured groupings.
|
||
</li>
|
||
<li>Click a student to open their goal workspace.</li>
|
||
</ul>
|
||
</div>
|
||
<div>
|
||
<h3>Navigation</h3>
|
||
<ul class="info-list">
|
||
<li>
|
||
The sidebar provides links to <strong>Reports</strong>
|
||
and <strong>Log Out</strong>.
|
||
</li>
|
||
<li>
|
||
District Admins and Super Admins also see an
|
||
<strong>Admin</strong> link that opens the Administration
|
||
panel (see <a href="#admin">Section 13</a>).
|
||
</li>
|
||
<li>Click the edit icon next to a student to update their name or IEP date.</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<section id="add-student" class="card">
|
||
<h2 class="section-title">7. Adding & Editing Students</h2>
|
||
<p class="muted">
|
||
Teachers and Program Admins can add a new student record directly
|
||
from the dashboard, or edit an existing student's information.
|
||
Paraeducators cannot add or edit students.
|
||
</p>
|
||
|
||
<h3>Adding a student</h3>
|
||
<ol>
|
||
<li>Click <strong>+ Add Student</strong> at the bottom of the sidebar.</li>
|
||
<li>Enter the student's <strong>Name</strong> (initials or other non-personally identifiable label).</li>
|
||
<li>Enter the <strong>Next IEP Date</strong>.</li>
|
||
<li>Click the save button to create the record.</li>
|
||
</ol>
|
||
|
||
<p>
|
||
Once saved, the new student appears in the sidebar immediately.
|
||
</p>
|
||
|
||
<h3>Editing a student</h3>
|
||
<ol>
|
||
<li>Click the edit icon (pencil) next to a student's name in the sidebar.</li>
|
||
<li>Update the <strong>Name</strong> or <strong>Next IEP Date</strong> as needed.</li>
|
||
<li>Click <strong>Save</strong>.</li>
|
||
</ol>
|
||
</section>
|
||
|
||
<section id="goals" class="card">
|
||
<h2 class="section-title">8. Managing Goals</h2>
|
||
<p>
|
||
Selecting a student opens the goal workspace for that student.
|
||
Goals are the main tracking objects used to measure student
|
||
development and progress. Each goal appears as a tab along the top
|
||
of the workspace, labeled by its category.
|
||
</p>
|
||
|
||
<h3>Creating a goal</h3>
|
||
<ol>
|
||
<li>Click the <strong>+ Goal</strong> tab in the workspace.</li>
|
||
<li>Fill in the goal details:
|
||
<ul>
|
||
<li><strong>Category</strong> — a short label (e.g. Reading, Math, Behavior)</li>
|
||
<li><strong>Baseline</strong> — the student's starting point</li>
|
||
<li><strong>Goal</strong> — a description of the desired outcome</li>
|
||
<li><strong>Target Completion Date</strong> — automatically pre-filled from the student's next IEP date</li>
|
||
</ul>
|
||
</li>
|
||
<li>Click <strong>Add Goal</strong> to save.</li>
|
||
</ol>
|
||
|
||
<h3>Viewing a goal</h3>
|
||
<p>
|
||
Click a goal tab to view its details. The goal card shows the
|
||
category badge, description, and target completion date. Below the
|
||
card, two sub-tabs allow switching between
|
||
<strong>Benchmarks</strong> and <strong>Progress Events</strong>
|
||
for that goal.
|
||
</p>
|
||
|
||
<h3>Editing a goal</h3>
|
||
<ol>
|
||
<li>Click the edit icon (pencil) on the goal card.</li>
|
||
<li>Update any of the goal fields.</li>
|
||
<li>Click <strong>Save</strong>.</li>
|
||
</ol>
|
||
|
||
<h3>Closing a goal</h3>
|
||
<p>
|
||
When a student completes or exits a goal, the goal can be formally
|
||
closed from the goal edit screen.
|
||
</p>
|
||
<ol>
|
||
<li>Click the edit icon (pencil) on the goal card.</li>
|
||
<li>Set the <strong>Close Date</strong>.</li>
|
||
<li>Mark whether the goal was <strong>Achieved</strong> (yes or no).</li>
|
||
<li>Optionally add <strong>Close Notes</strong> summarizing the outcome.</li>
|
||
<li>Click <strong>Save</strong>.</li>
|
||
</ol>
|
||
<p>
|
||
Closed goals remain visible for reference and reporting but are
|
||
clearly distinguished from active goals.
|
||
</p>
|
||
|
||
<div class="callout">
|
||
Users can use this page to quickly review whether a student is making
|
||
progress and what supporting events have been documented.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="benchmarks" class="card">
|
||
<h2 class="section-title">9. Managing Benchmarks</h2>
|
||
<p>
|
||
Benchmarks break a goal into smaller, measurable steps. This makes it
|
||
easier to see incremental progress over time. Each benchmark has a
|
||
full description and an optional short name used for compact display.
|
||
</p>
|
||
|
||
<p class="muted">
|
||
Teachers and Program Admins can add and edit benchmarks.
|
||
Paraeducators can view benchmarks but cannot create or modify them.
|
||
</p>
|
||
|
||
<h3>To add a benchmark</h3>
|
||
<ol>
|
||
<li>Select the goal tab for the relevant goal.</li>
|
||
<li>Switch to the <strong>Benchmarks</strong> sub-tab.</li>
|
||
<li>Click <strong>+ Add Benchmark</strong>.</li>
|
||
<li>In the modal, enter the <strong>Benchmark</strong> description and optionally a <strong>Short Name</strong>.</li>
|
||
<li>Click <strong>Add</strong> to save.</li>
|
||
</ol>
|
||
|
||
<h3>AI-assisted suggestions</h3>
|
||
<p>
|
||
When adding a new benchmark, you can click the
|
||
<strong>✦ Suggest with AI</strong> button. The system will analyze
|
||
the student's goal and generate a recommended benchmark that you
|
||
can accept, modify, or discard before saving. This feature is
|
||
available to Teachers and Program Admins only.
|
||
</p>
|
||
|
||
<h3>Editing a benchmark</h3>
|
||
<ol>
|
||
<li>Click the edit icon (pencil) next to the benchmark.</li>
|
||
<li>Update the description or short name.</li>
|
||
<li>Click <strong>Save</strong>.</li>
|
||
</ol>
|
||
|
||
<h3>Example benchmark</h3>
|
||
<p><code>Complete Computing for Good</code></p>
|
||
</section>
|
||
|
||
<section id="events" class="card">
|
||
<h2 class="section-title">10. Recording Progress Events</h2>
|
||
<p class="muted">
|
||
Progress events document meaningful activities, milestones, or notes
|
||
related to a student's goal. All roles (including Paraeducators) can
|
||
log progress events.
|
||
</p>
|
||
|
||
<h3>To log a progress event</h3>
|
||
<ol>
|
||
<li>Select the goal tab for the relevant goal.</li>
|
||
<li>Switch to the <strong>Progress Events</strong> sub-tab.</li>
|
||
<li>Click <strong>+ Log Progress Event</strong>.</li>
|
||
<li>Enter a <strong>Description</strong> of the activity.</li>
|
||
<li>
|
||
Optionally, select one or more <strong>Related Benchmarks</strong>
|
||
to link the event to specific milestones. Benchmarks appear as
|
||
clickable chips that toggle on and off.
|
||
</li>
|
||
<li>Click <strong>Log</strong> to save.</li>
|
||
</ol>
|
||
|
||
<h3>Each progress event captures</h3>
|
||
<ul>
|
||
<li>A description of the activity</li>
|
||
<li>The user who recorded the event (recorded automatically)</li>
|
||
<li>The date of the event (recorded automatically)</li>
|
||
<li>Any linked benchmarks</li>
|
||
</ul>
|
||
|
||
<p>
|
||
Progress events are displayed in a timeline view, with linked
|
||
benchmark tags shown beneath each entry.
|
||
</p>
|
||
|
||
<h3>Editing a progress event</h3>
|
||
<ol>
|
||
<li>Click the edit icon (pencil) on the event card in the timeline.</li>
|
||
<li>Update the description and/or benchmark selections.</li>
|
||
<li>Click <strong>Save</strong>.</li>
|
||
</ol>
|
||
|
||
<h3>Example</h3>
|
||
<p><code>Took C4G – loved it!</code></p>
|
||
|
||
<div class="callout success">
|
||
Progress events create a historical record that can support follow-up,
|
||
reporting, and program evaluation.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="deleting" class="card">
|
||
<h2 class="section-title">11. Deleting Records</h2>
|
||
<p class="muted">
|
||
Students, goals, benchmarks, and progress events can all be deleted
|
||
by Teachers and Program Admins. Paraeducators cannot delete records.
|
||
Deletions are permanent and cannot be undone.
|
||
</p>
|
||
|
||
<h3>How to delete</h3>
|
||
<ul>
|
||
<li>
|
||
<strong>Student</strong> — Click the delete icon (trash) in the
|
||
student header area. A double-confirmation dialog will appear
|
||
because this deletes the student and all their goals, benchmarks,
|
||
and progress events.
|
||
</li>
|
||
<li>
|
||
<strong>Goal</strong> — Click the delete icon on the goal card.
|
||
A double-confirmation dialog will appear because this also
|
||
deletes all benchmarks and progress events under the goal.
|
||
</li>
|
||
<li>
|
||
<strong>Benchmark</strong> — Click the delete icon next to
|
||
the benchmark. A double-confirmation dialog will appear.
|
||
</li>
|
||
<li>
|
||
<strong>Progress Event</strong> — Click the delete icon on
|
||
the event card in the timeline. A confirmation dialog will appear.
|
||
</li>
|
||
</ul>
|
||
|
||
<div class="callout">
|
||
Deleting a student or goal is a cascading operation — all child
|
||
records (goals, benchmarks, and progress events) are permanently
|
||
removed. Use with caution.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="reports" class="card">
|
||
<h2 class="section-title">12. Reports</h2>
|
||
<p class="muted">
|
||
The Reports section provides tools for extracting and summarizing
|
||
student progress data. Access it from the <strong>Reports</strong>
|
||
link in the sidebar. Reports are available to Teachers and Program
|
||
Admins. Paraeducators do not have access to the Reports section.
|
||
</p>
|
||
|
||
<h3>Student Progress Report</h3>
|
||
<p>
|
||
Generates a formatted progress report for a selected student over
|
||
a date range. This is useful for IEP meetings, program reviews, or
|
||
external reporting.
|
||
</p>
|
||
|
||
<ol>
|
||
<li>Click <strong>Reports</strong> in the sidebar, then select <strong>Student Progress Report</strong>.</li>
|
||
<li>Select a <strong>Student</strong> from the dropdown.</li>
|
||
<li>Set the <strong>From Date</strong> and <strong>To Date</strong> for the reporting period.</li>
|
||
<li>Check or uncheck which <strong>Goals to Include</strong> in the report.</li>
|
||
<li>
|
||
Optionally, edit the <strong>Prompt</strong> to customize the
|
||
report instructions. The prompt auto-saves as you type.
|
||
</li>
|
||
<li>Click <strong>Run</strong> to generate the report.</li>
|
||
</ol>
|
||
|
||
<div class="callout success">
|
||
The generated report aggregates goals, benchmarks, and progress
|
||
events into a structured summary that can be copied or used in
|
||
external documents.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="admin" class="card">
|
||
<h2 class="section-title">13. Administration</h2>
|
||
<p class="muted">
|
||
The Administration panel is available to District Admins and Super
|
||
Admins. It is accessed via the <strong>Admin</strong> link in the
|
||
sidebar, which is only visible to users with those roles.
|
||
</p>
|
||
|
||
<p>
|
||
The Admin panel has two tabs: <strong>Programs</strong> and
|
||
<strong>Users</strong>.
|
||
</p>
|
||
|
||
<h3>Programs tab</h3>
|
||
<p>
|
||
Lists all programs in your district. District Admins can create new
|
||
programs and edit existing ones.
|
||
</p>
|
||
|
||
<h4>Adding a program</h4>
|
||
<ol>
|
||
<li>Click <strong>+ Add Program</strong>.</li>
|
||
<li>Enter a <strong>Program Name</strong> (required) and an optional <strong>Description</strong>.</li>
|
||
<li>Click <strong>Create</strong>.</li>
|
||
</ol>
|
||
|
||
<h4>Editing a program</h4>
|
||
<ol>
|
||
<li>Click <strong>Edit</strong> next to the program.</li>
|
||
<li>Update the name or description.</li>
|
||
<li>Click <strong>Save</strong>.</li>
|
||
</ol>
|
||
|
||
<h3>Users tab</h3>
|
||
<p>
|
||
Lists all users across all programs in your district, showing each
|
||
user's name, email, role, and assigned program.
|
||
</p>
|
||
|
||
<h4>Adding a user</h4>
|
||
<ol>
|
||
<li>Click <strong>+ Add User</strong>.</li>
|
||
<li>Enter the user's <strong>Name</strong>, <strong>Email</strong>, and a temporary <strong>Password</strong>.</li>
|
||
<li>Select the <strong>Program</strong> to assign the user to.</li>
|
||
<li>Select the user's <strong>Role</strong> (see <a href="#roles">Section 2</a> for role descriptions).</li>
|
||
<li>Click <strong>Create User</strong>.</li>
|
||
</ol>
|
||
|
||
<p>
|
||
The new user can immediately log in with the email and password you
|
||
provided. Share the credentials with them securely.
|
||
</p>
|
||
|
||
<div class="callout">
|
||
District Admins cannot assign the Super Admin role. Only a Super
|
||
Admin can elevate another user to Super Admin.
|
||
</div>
|
||
|
||
<div class="callout warn">
|
||
There is currently no in-app password reset. If a user forgets their
|
||
password, a District Admin will need to create a new account or
|
||
contact the platform operator for assistance.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="mobile" class="card">
|
||
<h2 class="section-title">14. Mobile Experience</h2>
|
||
<p class="muted">
|
||
The application automatically detects whether you are using a
|
||
touch-based mobile device and presents a touch-optimized interface.
|
||
</p>
|
||
|
||
<h3>Mobile capabilities</h3>
|
||
<ul>
|
||
<li>
|
||
<strong>Student list</strong> — browse your students, with the
|
||
same My Students / All toggle available on desktop.
|
||
</li>
|
||
<li>
|
||
<strong>Student goals</strong> — tap a student to view their
|
||
goals and benchmarks.
|
||
</li>
|
||
<li>
|
||
<strong>Log progress events</strong> — tap a goal to open a
|
||
touch-friendly form for entering notes and selecting benchmarks
|
||
via large, tappable tiles.
|
||
</li>
|
||
</ul>
|
||
|
||
<div class="callout">
|
||
Some management features — such as adding students, creating goals,
|
||
editing benchmarks, running reports, accessing the Admin panel, and
|
||
deleting records — are only available in the desktop interface. Use
|
||
a desktop browser for full administrative access.
|
||
</div>
|
||
</section>
|
||
|
||
<section id="workflow" class="card">
|
||
<h2 class="section-title">15. Typical Workflow</h2>
|
||
|
||
<h3>For a Teacher or Program Admin</h3>
|
||
<ol>
|
||
<li>Log into the application and select your program.</li>
|
||
<li>Review the list of assigned students in the sidebar.</li>
|
||
<li>Add a student if needed.</li>
|
||
<li>Open a student record and review or create goals.</li>
|
||
<li>Add benchmarks to define milestones (use AI suggestions when helpful).</li>
|
||
<li>Record progress events as the student advances, linking relevant benchmarks.</li>
|
||
<li>Run reports as needed for IEP meetings or program reviews.</li>
|
||
</ol>
|
||
|
||
<h3>For a Paraeducator</h3>
|
||
<ol>
|
||
<li>Log into the application and select your program.</li>
|
||
<li>Browse students using the sidebar.</li>
|
||
<li>Open a student record and select a goal.</li>
|
||
<li>Switch to the <strong>Progress Events</strong> sub-tab and log a new event.</li>
|
||
</ol>
|
||
|
||
<h3>For a District Admin (initial setup)</h3>
|
||
<ol>
|
||
<li>Register at <code>/register</code> to create your district and first program.</li>
|
||
<li>Log in and open the <strong>Admin</strong> panel from the sidebar.</li>
|
||
<li>Create additional programs if needed.</li>
|
||
<li>Add teacher and paraeducator accounts under the Users tab.</li>
|
||
<li>Share login credentials with each user.</li>
|
||
</ol>
|
||
</section>
|
||
|
||
<section id="tips" class="card">
|
||
<h2 class="section-title">16. Usage Notes</h2>
|
||
<ul>
|
||
<li>Keep student names consistent (use initials or a non-identifying label) to avoid duplicate entries and to protect student privacy.</li>
|
||
<li>Update progress events regularly so the record stays current.</li>
|
||
<li>Use benchmarks to make large goals easier to track.</li>
|
||
<li>Link progress events to benchmarks for richer reporting.</li>
|
||
<li>Review student cards often to spot inactivity or missing updates.</li>
|
||
<li>Use the mobile app for quick progress logging in the field.</li>
|
||
<li>Log out when finished using the system on a shared device.</li>
|
||
<li>If your login is locked, wait a few minutes and try again, or contact your district administrator.</li>
|
||
<li>District Admins: share newly created passwords with users through a secure channel and advise them not to share their credentials.</li>
|
||
</ul>
|
||
|
||
<a href="index.html" class="btn btn-primary back-link">Back to Project Home</a>
|
||
</section>
|
||
</div>
|
||
</div>
|
||
</main>
|
||
|
||
<div class="footer">
|
||
© 2026 WIN Student Goal Tracker.
|
||
</div>
|
||
</body>
|
||
</html>
|