> For the complete documentation index, see [llms.txt](https://docs.flylogs.com/fcom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flylogs.com/fcom/training-courses/missed-classes-and-class-work.md).

# Missed classes and class work

What happens when a student misses an onsite class — the email, class work, justifications and how it's reported.

Onsite classes and exams track attendance as part of the training record, and follow up automatically when a student misses one. This page walks through the whole flow, from an unmarked register to a resolved, reported outcome. For where each of these actions lives on screen, see [Teacher tools](/fcom/training-courses/teacher-tools.md), [Student evaluation](/fcom/training-courses/student-evaluation.md) and [Student management](/fcom/training-courses/student-management.md).

<figure><img src="https://3907986352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMT7uFw9SCqEw2vqrAnQg%2Fuploads%2Fgit-blob-4f666e296acc886cf43a64c07ca92a5d031e0108%2FtrainingsAttendanceWorkflow.png?alt=media" alt=""><figcaption><p>The full flow: class session, attendance, signature, class work and absence justification.</p></figcaption></figure>

### The four attendance statuses

Each student on a class register is set to one of:

* **Attended**
* **Attended (post-class)** — attended after the fact, see below.
* **Absent**
* **Absent (justified)** — an approved justification, see below.

Before the teacher signs the class, students can be left **unmarked** — nothing has been decided yet. Nothing is saved to the training record until the class is **signed**: signing is the moment the register becomes a record, and it turns every student still unmarked into **Absent**.

A signed register is locked. A training manager can reopen it with **Modify signed attendance**, make corrections, and sign again with **Update attendance** — every signature is kept as history, so nothing is overwritten. Both **Attended** and **Attended (post-class)** count as present; **Absent (justified)** does not.

<figure><img src="https://3907986352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMT7uFw9SCqEw2vqrAnQg%2Fuploads%2Fgit-blob-efa137cc4533f0def224801cc6d75426335b7c18%2FtrainingsAttendanceStatuses.png?alt=media" alt=""><figcaption><p>The four attendance statuses on a class register.</p></figcaption></figure>

<figure><img src="https://3907986352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMT7uFw9SCqEw2vqrAnQg%2Fuploads%2Fgit-blob-43703cbde363df9d3fa75b25b55db6d3e3844869%2FtrainingsAttendanceSigned.png?alt=media" alt=""><figcaption><p>A signed register: statuses are read-only, the totals are summarised, and only "Modify Signed Attendance" reopens it.</p></figcaption></figure>

\### Signing your own attendance

Some courses ask students to countersign their attendance — the setting is **Require students to sign assistance** on the training, off by default. On those courses, a student recorded as **Attended** or **Attended (post-class)** is asked, once per class, to confirm it themselves.

The student opens the class page, presses **Sign my attendance** and enters their password. The signature is stored with the date and time, and shown on the register and on the class report PDF next to their name.

<figure><img src="https://3907986352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMT7uFw9SCqEw2vqrAnQg%2Fuploads%2Fgit-blob-c3eee8b62b0182200659c4dccd6be0434ba06a53%2FtrainingsStudentSignPrompt.png?alt=media" alt=""><figcaption><p>The prompt on the student's class page.</p></figcaption></figure>

<figure><img src="https://3907986352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMT7uFw9SCqEw2vqrAnQg%2Fuploads%2Fgit-blob-3a10957efb2fbe7297d6c5f0967b87ffc840c00e%2FtrainingsStudentSigned.png?alt=media" alt=""><figcaption><p>Once signed, the same banner confirms when it was done.</p></figcaption></figure>

The window runs from four hours before the class until **seven days after** it. The teacher signing the register does not close it — that signature says who was there, the student's says they were, and the two are independent. Students who were absent are never asked to sign.

If a student can't sign, the class page says why: the class hasn't started, the seven days have passed, their attendance isn't recorded as attended, or they've already signed.

### The missed-class email

When the register is signed, Flylogs automatically emails every student marked **Absent**. The email names the class, its date and location, a summary of the content, and links straight to the class page. It also tells the student whether class work has been requested and how to justify the absence, with the relevant deadlines if set.

Each student receives this email once per class — even if the register is later reopened and signed again, a student already emailed isn't emailed a second time.

<figure><img src="https://3907986352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMT7uFw9SCqEw2vqrAnQg%2Fuploads%2Fgit-blob-328b39a5a56af3da2060fe4ac459e0502a41e568%2FtrainingsMissedClassEmail.png?alt=media" alt=""><figcaption><p>The missed-class email sent to an absent student.</p></figcaption></figure>

\### Uploading class work

A teacher can request class work (homework) from the class page's **Documents** tab — turned on there, not while scheduling the class. They set a deadline and write a description of what students need to do; students are notified and see a banner on the class page until they've dealt with it.

Once the register is signed, the request itself is frozen — it can't be turned on, changed or cancelled after that point. Students can still upload their work after signing, which is the point: class work is often finished after a missed class, not before it's caught up with. Each student only ever sees their own submissions; the teacher and any training manager see everyone's, to evaluate.

**One file, replaceable until the deadline — or until it's graded.** Class work is a single file. A student who wants to hand in something different deletes what they uploaded and uploads again, as often as they like. Two things close that window, whichever comes first: the deadline passing, or the teacher grading the work. After either, the file is locked — what the teacher graded is what stays. The teacher and any training manager can still remove it if something has to go.

While a class work request is open, the student's class page shows a yellow banner asking for the work. Once they've submitted, it turns green and says so instead of nagging — the banner reports the state rather than demanding an action.

A student who submitted **nothing** by the deadline can still upload afterwards — that's the whole point of the missed-class flow. Work that arrives after the deadline is accepted and marked **Late** wherever it's shown, to the student and to the teacher alike. Extending the deadline afterwards removes the mark from anything the new deadline covers.

<figure><img src="https://3907986352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMT7uFw9SCqEw2vqrAnQg%2Fuploads%2Fgit-blob-324cef84fe5ca76715ef3963a182486654e6c5a2%2FtrainingsClassworkRequest.png?alt=media" alt=""><figcaption><p>Requesting class work from the Documents tab.</p></figcaption></figure>

<figure><img src="https://3907986352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMT7uFw9SCqEw2vqrAnQg%2Fuploads%2Fgit-blob-4e191145647c0e2dc5a284146e1a622a0b27c8a0%2FtrainingsStudentsHomework.png?alt=media" alt=""><figcaption><p>What the student sees: the brief, the deadline, and their own upload area. Students never see another student's file.</p></figcaption></figure>

### Grading class work

The teacher — or the subject's teacher, or any training manager — grades from the same **Documents** tab. The class work box lists every student on the register: their file (with who uploaded it, when, and a **Late** mark if it applies), a score out of 10, and a comment for the student.

Students who handed nothing in still get a row, so a zero with an explanation is possible. Either the score or the comment is enough — an entirely empty grade isn't saved. Re-grading overwrites the previous mark rather than adding a second one.

Saving a grade sends the student an in-app message with the score and the comment, linking back to the class. It's a message only — no email, no phone notification. The student also sees their grade on the class page, under their own submission. Nobody sees anyone else's mark.

### Justifying an absence

A student marked **Absent** can submit a justification from the class page's **Attendance** tab — an explanation, a document, or both.

### How a justification is decided

The class's teacher, or any training manager, reviews pending justifications from the same tab and either **approves** or **rejects** them, with an optional note. Approving sets the student to **Absent (justified)**. Each submission gets one decision — if the student wants to try again, they submit a new justification rather than reopening the old one.

{% hint style="info" %}
A class work file can be deleted by the student who uploaded it, but only until the deadline passes or a teacher grades it — after either, it's locked. Justification documents can never be deleted by the student who submitted them, deadline or not: they're the evidence behind an attendance decision, so the record stays intact. The class's teacher, the subject's teacher and training managers can remove either kind at any time, for the cases where something has to go — a corrupt file, or work posted to the wrong class. No file can ever be moved to a different record.
{% endhint %}

### Attended after the fact

If a student makes up a missed class — for example by working through the content and any requested class work — a training manager can reopen the signed register and change that student's status to **Attended (post-class)** instead of leaving them **Absent** or **Absent (justified)**. It counts as attendance, but stays visible in reports as credit given after the fact rather than attendance on the day.

### Recovering a class in another sitting

When the same lesson is taught more than once — a morning and an afternoon cohort, or a repeat a few weeks later — a student who misses their own sitting can simply attend the other one. Nothing needs to be done by hand: as soon as the student is marked **Attended** in the other sitting (the teacher adds them to that class's register if they are not on it), the missed sitting is credited automatically as **Attended (post-class)** and the lesson counts as attended in the student's progress.

The record keeps the whole story. The missed sitting still shows that it was missed and which class recovered it — the register reads *Attended (post-class) — recovered in the class of {date}*, the same line appears on the printed class report, and the student's attendance breakdown counts it under **Credited after class**, with the number of those that were recovered in another sitting shown separately. The status the row had before (**Absent** or **Absent (justified)**) is remembered too.

Two limits keep this honest:

* The other sitting must be within **90 days** of the missed one, and within the student's current enrollment. Last year's run of the same lesson, or a previous enrollment, never excuses a new absence.
* If the attendance that earned the credit is later corrected to **Absent**, the credit is withdrawn and the missed sitting goes back to what it was — or moves to another sitting the student did attend.

A credit is only given for a sitting that has actually been marked absent. A sitting nobody has signed yet stays **Not marked** until the teacher decides it.

### Students invited but not enrolled

Someone can be invited to a class without being enrolled in the training. They can open the class page, but no attendance or evaluation can be recorded for them: the register shows them read-only with a **Not enrolled** label, and they're excluded from the attendance ratio, the missed-class email and the class work notification. Enrol them in the training to start recording their results.

### How it's reported

The student's training record, the training report and its PDF all split missed sessions into three outcomes: **justified**, **not justified**, and **credited after class**. See [Student management](/fcom/training-courses/student-management.md#attendance-breakdown) for where this appears.
