Internal comments and follow-up
Skolar allows internal comments on both students and employees. These are operational notes for the school team, not messages for families and not public notices.
Where comments are used
You can add comments from:
- the student record
- the employee profile
- time clock incidents when staff attendance follow-up is active
In each case the comment stays attached to the corresponding record and keeps the author reference.
When comments are useful
Use comments to:
- leave context before handing a case to another area
- record agreements or internal follow-up
- explain an operational exception
- summarize background before contacting a family or staff member
They should not replace:
- discipline incidents
- invoices or reconciliations
- newsletters or external communication
- workstream, when what matters is system event history
Comments on students
In the student record, comments help connect:
- academic context
- guardian follow-up
- relevant finance notes
- discipline situations that do not yet require a formal incident
Since the record also shows debts, enrollments, and grade cards, a well-written note saves the next admin from rebuilding the case from scratch.
Comments on employees
For employees, comments are useful for:
- Skolar access follow-up
- role or function changes
- time clock observations
- context before rehiring or dismissal
Comments on time clock incidents
Here it helps to distinguish between:
- the initial justification submitted by the employee
- the follow-up comments added later by the employee or admin team
Both document the incident, but the final resolution still depends on admin review and status change.
Good practices
- write notes that are concrete, dated, and actionable
- avoid vague judgments or emotional language
- do not duplicate sensitive information if it already exists in a formal flow
- prefer one clear note over many fragmented comments
- delete comments only when they were truly entered by mistake
Common issues
There are too many notes and nobody understands the case
This usually happens when several teams leave short comments without context, next action, or owner.
The comment is not showing where expected
Confirm whether it was saved on the student, the employee, or the attendance incident. Each flow stores comments separately.
A useful note was deleted
Comments can be removed, so major decisions should also be reflected in the team process and not live only in one note.