How to reschedule a missed study session in Vithi
A missed study block leaves two decisions: what work still matters and where it can realistically fit. Moving everything to tomorrow usually hides the capacity problem. This guide is written by Vithi and uses its calendar editing fields to describe a more deliberate rescheduling process.
Separate the missed session from the actual deadline
Your intended revision time and the deadline set by a teacher are different commitments. If you planned to practise on Tuesday and did not, Tuesday’s study block can change. That does not move a Friday hand-in or an exam date. Check the original instructions before editing any event that represents an external commitment.
Write down the unfinished output: two source comparisons, one essay outline or a set of corrections. If part of the session was completed, identify only the remaining work. The replacement should not silently restart the whole task.
Find space before choosing a new time
Look at classes, travel, meals and existing commitments for the proposed day. Count the usable time rather than assuming an empty-looking evening is completely available. Leave a margin for preparing the materials and checking the result.
Suppose a hypothetical 60-minute revision block was missed and the next day has only 30 usable minutes. Move a 25-minute task with five minutes to check it, or choose a later slot that can hold the original work. Do not squeeze an hour of work into half an hour by changing the calendar label.
If the work cannot fit before the real deadline, reduce scope where the assignment permits it or seek help with the constraint. A calendar edit records your plan; it cannot change the amount of work required.
Edit the existing block rather than adding a confusing copy
Vithi’s calendar supports editing an event’s title, date, start time and end time, as well as an all-day setting. Open the missed event for editing and use the new date and time you have chosen. Check the calendar date itself, especially when moving between weeks.
Give the replacement a concrete title such as “correct two source-comparison answers”. A title like “catch up everything” gives you no reliable finishing point. If you split the work across two blocks, name the separate outputs so the same task is not counted twice.
For a timed session, use a start and end time rather than an all-day entry. The current form requires the end time to be later than the start time. This guide describes manually editing the event, not automatic conflict resolution or a recurring-event migration.
Check the saved calendar before relying on it
Save the change and inspect the destination day. Verify the title, date and both times. Reopen or reload the calendar to check that the change persisted. If a save reports an error, review the visible event before trying again so you do not create a duplicate.
Also check the old day. You should be able to tell whether the session moved or whether you accidentally left the original and created another event. If you use an external calendar too, check its displayed state separately rather than assuming the edit propagated.
The revised event is a future intention. It does not show that the work was completed or that the topic is understood. Keep the completed work or correction notes where you can review them afterwards.
Use a smaller recovery block when attention is limited
A hypothetical missed essay session might have aimed to produce a full draft. A useful replacement could be “choose the evidence for paragraph two and write its claim”, followed by a separate drafting block. The smaller task should still contribute to the same assignment.
For exam revision, prefer a bounded attempt and feedback cycle: answer two questions, compare with the marking guidance and retry the weakest part. A short session spent only copying notes may leave the original uncertainty untouched.
Use this rescheduling record outside the app if helpful: unfinished output; fixed deadline and source; available slot; revised output; time for checking; event verified; next decision after the work. These are planning notes, not a claim that Vithi stores each field.
Respond differently if the same block keeps moving
If the task is postponed repeatedly, inspect the cause. It may be too large, unclear, dependent on missing material or scheduled during an unreliable part of the day. Change the condition that blocks it rather than repeatedly changing the date.
For a blocked task, write a first action you can perform, such as finding the question sheet or asking which feedback comment needs attention. Once that dependency is resolved, schedule the actual study output. Keep a truthful distinction between organising the work and doing it.
