How to Fix Duplicate Assignments and Conflicting Calendar Entries

Duplicate assignment entries usually come from a reasonable action repeated in several systems:

• manual entry;
• syllabus import;
• LMS calendar feed;
• personal reminder;
• shared group calendar;
• changed deadline.

The fix is not “delete whichever looks older.”

First decide what each entry represents.

Use the identity test

Compare:

1. course;
2. task name;
3. task type;
4. due date and time;
5. submission destination;
6. source;
7. milestone versus final deliverable;
8. personal reminder versus official deadline.

Two records are likely duplicates when they refer to the same course requirement and the same completion event.

They are not duplicates merely because their names are similar.

Common look-alikes

Official deadline and personal work block

• “Essay due”
• “Finish essay draft”

Keep both. Rename them so their roles are clear.

Draft and final submission

• “Project draft”
• “Final project”

Keep both when the course requires both.

Old and changed deadline

• “Problem Set 3 — Oct. 8”
• “Problem Set 3 — Oct. 9”

These may represent one task after a date change. Confirm the current source, keep one canonical deadline, and record the old date in history. If the sources disagree, use the syllabus-versus-LMS deadline guide before deleting either entry.

Same task name in different courses

• Quiz 4 — ECON
• Quiz 4 — MATH

Keep both. Course identity prevents a false merge.

LMS feed plus manual entry

If both represent the same official due date, choose one canonical entry and decide which system remains responsible for future updates.

Create a canonical record

The canonical record should contain:

• current official name;
• course;
• current due date/time;
• verification status;
• primary source;
• previous date if changed;
• notes or secondary source links;
• planning status.

Other systems may display or reference the task, but one record should own its academic meaning.

Choose which duplicate to keep

Prefer the entry that has:

• the strongest source traceability;
• the current confirmed date;
• the most useful task history;
• existing notes or work blocks;
• stable connection to the system you actually maintain.

Do not choose solely by which calendar created it automatically.

Worked example: three entries for one lab

A student sees:

1. Google Calendar: “Lab 3 — Oct. 12”
2. Personal task app: “Finish Lab 3 — Oct. 11”
3. LMS feed: “Lab 3 — Oct. 13 at 5 p.m.”

Investigation:

• The task app item is a personal target, not the official deadline.
• The manual calendar event used the original syllabus date.
• The LMS task page and instructor announcement confirm Oct. 13 at 5 p.m.

Final system:

• Official task: Lab 3 — Oct. 13, 5 p.m.
• Personal target: Finish Lab 3 — Oct. 11
• Previous official date: Oct. 12
• Remove the stale Oct. 12 event.

Nothing important is lost because the roles are distinguished.

When calendar subscriptions duplicate each other

Duplication can occur when:

• the same feed is subscribed twice;
• one feed is imported as a snapshot and also subscribed;
• two calendars display the same course feed;
• a manual calendar copies the feed’s events;
• an integration recreates events instead of updating them.

Before deleting events individually:

1. identify the source calendar;
2. check whether it is a subscription or imported copy;
3. disable one source temporarily;
4. confirm which events disappear;
5. keep the source with the intended update behavior;
6. repair manual exceptions afterward.

Deleting each duplicate event may be wasted effort if the source imports them again.

Preserve source differences that matter

Sometimes two records should remain linked rather than merged.

Example:

• Official deadline in LMS
• Group-internal deadline two days earlier

Store both, but name the second:

Group internal draft deadline

The official record answers compliance.

The internal record answers coordination.

Use a duplicate-resolution log

For recurring problems, record:

This helps when the same integration creates the problem again.

Do not lose changed-date history

The College Assignment Tracker Template includes Current Due Date, Previous Due Date, Source, and Verification Status.

Use those fields before deleting a stale entry from the visible calendar.

A safe cleanup checklist

• [ ] Course and section match.
• [ ] Task names refer to the same deliverable.
• [ ] Milestone versus final checked.
• [ ] Official versus personal date checked.
• [ ] Current source verified.
• [ ] Canonical record chosen.
• [ ] Previous date preserved if useful.
• [ ] Source subscription identified.
• [ ] Stale duplicate removed.
• [ ] Group or shared-calendar users informed.
• [ ] Reappearance checked after refresh.

A clean calendar is useful.

A clean calendar that erased a real milestone is not.

Verify the role of each record before you merge or delete it.