Logged dates
When Junipa shows a logged-date badge, it means the date of the activity and the date the record was entered are different.
This is normal for many school workflows. A teacher might provide an adjustment during class, attend a meeting, speak with a parent, or support a student in the playground, then record the evidence later when they are back at a computer.
The two dates
Junipa keeps the date of the support separate from the date the record was entered.
| Date | What it means |
|---|---|
| Activity date or Evidence date | The date the support, meeting, adjustment, observation or evidence event happened. |
| Logged | The date and time the staff member saved the record in Junipa. |
If both dates are on the same calendar day, Junipa usually shows only one date. If they are on different days, Junipa shows both dates and adds a compact timing badge.
What the badge means
Junipa uses a compact badge when the activity date and logged date are separated enough to notice:
In this example, the record was logged nine days before the activity or evidence date shown beside it. If the badge says the record was logged later, the record was entered after the support happened.
The important date for understanding when support happened is the Activity date or Evidence date. The Logged date tells you when Junipa received the record.
Is backdating evidence allowed?
Schools can record evidence after the fact when recording at the time was not practical. The record should still describe what actually happened and use the real date of the support.
Delayed logging can still support accurate resourcing and help explain staff time spent providing adjustments. It is strongest when the entry is clear enough for another staff member to understand without asking the original teacher to reconstruct it later.
What to check
When you see a logged-date badge, check the record in this order:
- Activity date or Evidence date: Confirm this is the real date the support happened.
- Case note: Check that the note explains what changed for the student.
- Attachments: Add or check files when the entry refers to a task, meeting note, plan, photo or work sample.
- Staff member: Confirm the person who logged the record can explain it if needed.
- Large gaps: Follow up if the record was logged much later and the note is too brief.
Do not edit a record only because it was logged later. Edit it when the activity date, evidence date, case note, attachment or student record is wrong or unclear.
How to use logged dates in reports
Use the Activity date or Evidence date when you are asking:
- Did the support happen inside the period being reviewed?
- Does the evidence show ongoing adjustment over time?
- Which term, week or reporting window does this record belong to?
Use the Logged date when you are asking:
- When did Junipa receive the record?
- Was evidence entered soon after the support happened?
- Are there staff or teams that need help recording evidence closer to the point of action?
The Evidence Log is useful when you need the school-wide evidence trail. Student Activity is useful when you want to check whether a student has activity that needs a clearer reporting decision.
When to follow up
Follow up with the staff member or case manager when:
- The activity date looks like the wrong day, term or year.
- The badge shows the record was logged before the activity date, and the future date was not intentional.
- The entry was logged much later and does not explain the adjustment clearly.
- The note refers to a file, meeting or plan but nothing is attached.
- The logged delay could affect an NCCD review, audit trail or resourcing discussion.
For guidance on writing strong entries, see Adding evidence and Attaching files.