How to Merge School Calendars Without Creating Duplicate Assignments

To merge school calendars without creating duplicate assignments, do not copy every event into one calendar.

Instead, give each calendar a clear job:

• source calendar: dates supplied by an institution, course, or LMS;
• planning calendar: your study sessions and work blocks;
• personal calendar: work, appointments, travel, and commitments;
• master task system: verification, TBD work, status, and changes.

You can view the layers together without making them all own the same event.

Step 1: inventory every calendar

List:

• Canvas, Brightspace, Moodle, or Classroom feeds;
• institutional academic calendar;
• course-specific calendars;
• Google, Apple, or Outlook personal calendar;
• work schedule;
• planner or task app;
• manually imported .ics files.

For each, record whether it is:

• subscription;
• one-time import;
• manually maintained;
• automatically generated;
• authoritative or only convenient.

Step 2: choose one owner for every event type

Example:

An event can be visible in several places while having only one authoritative owner.

Step 3: distinguish subscription from copy

A subscription points to another calendar's feed. A copy creates a separate event you must maintain.

Manual copies are useful when you need:

• personal notes;
• a study block;
• a preparation milestone;
• an offline fallback.

Do not copy an official deadline merely to create a second identical deadline. Create preparation sessions around it instead.

Step 4: use names that reveal the source

Examples:

• Canvas — All Courses
• University Academic Dates
• Work Shifts
• Personal
• Study Blocks

Avoid naming every calendar “School.”

Source names make duplicates easier to diagnose.

Step 5: check before adding a new feed

Before subscribing or importing:

1. search for the assignment title;
2. inspect existing calendars;
3. check whether the current source is already included;
4. determine whether the new source is a subscription or one-time import;
5. decide which version will remain visible.

Step 6: separate deadlines from work sessions

Suppose a paper is due October 18.

Keep:

• one official deadline event;
• separate personal blocks for topic, sources, draft, and revision.

Do not label every block “Paper due.” The deadline and work plan serve different jobs.

Step 7: handle changed dates

When a date changes:

• verify the authoritative source;
• update manual planning blocks;
• leave the source subscription to reflect its own data;
• remove stale manual duplicate deadlines;
• record the prior date where history matters.

Use What to Do When a Professor Changes a Deadline for the complete workflow.

Step 8: handle TBD items outside the dated grid

A calendar date is the wrong place for work with no confirmed date.

Keep a separate list containing:

• task;
• course;
• source;
• current wording;
• verification status;
• next check.

The one reliable assignment-system guide explains this source-linked maintenance layer.

Weekly duplicate check

During the weekly review:

• search near deadlines for duplicate titles;
• compare old and new dates;
• inspect newly added feeds;
• verify manual copies;
• remove canceled or stale events;
• keep planning blocks even when the official deadline is subscribed elsewhere.

Duplicate-resolution checklist

When two entries look identical, compare:

1. title;
2. course;
3. source;
4. due time;
5. last update;
6. whether one is a work session;
7. whether one is a manually copied deadline.

Then choose:

• keep both because jobs differ;
• hide one calendar;
• delete a manual duplicate;
• preserve one as historical;
• mark unresolved until the source is confirmed.

What one-calendar planning does not mean

It does not require putting every event into one database or one color.

It means you can answer:

• What is official?
• What must I do?
• When will I do it?
• What changed?
• Which copy should I trust?

A well-merged calendar gives you one combined view without creating several independent versions of the same deadline.