15Five check in error one on one notes saved to wrong direct report

TL;DR

Fix this in 15Five by acting on the exact problem first: in 15Five, find the check in note saved under the wrong report, confirm from its content and date which report it belongs to, move the note content into the correct report one on one record, delete the misfiled copy so no private note stays under the wrong person, and tell both the manager and the correct report what was moved. Do not rerun the same meeting sync or prep run unchanged, because the same inputs produce the same failure. Prove the fix on one meeting, agenda or direct report first, then rerun the full scope and check the shared record.

15Five check in error one on one notes saved to wrong direct report

Use this when

• The operation in 15Five fails with this exact problem: 15Five check in error one on one notes saved to wrong direct report.
• The same failure repeats on retry with unchanged inputs.
• A one on one agenda, talking point, action item or prep step is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The meeting completes and you only disagree with a people judgement such as a rating or a promotion call. That is a manager and people team decision, not this failure.

Steps

1. Reproduce the failure on one named meeting or direct report in 15Five and record the full problem text plus the meeting, participants and date involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: in 15Five, find the check in note saved under the wrong report, confirm from its content and date which report it belongs to, move the note content into the correct report one on one record, delete the misfiled copy so no private note stays under the wrong person, and tell both the manager and the correct report what was moved. Verify: the single failing meeting or agenda now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring meetings, reports or recurring occurrences that share the same template, calendar series or sync, because this class of failure rarely affects only one meeting. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in 15Five on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the shared agenda record, the calendar event or the meeting notes, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the meeting prep log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

15Five check in error one on one notes saved to wrong direct report

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single meeting proof, then the full rerun.

How to fix - 15Five check in error one on one notes saved to wrong direct report

The how to phrasing for the same failure in 15Five. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

15Five troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Check in notes attach to the report selected when the note was opened, and a manager with several similar report names can save into the wrong record, where the note is both lost and visible to the wrong conversation.

Edge cases

• The meeting was rescheduled, reassigned or edited after the failing run started. Refresh the meeting state and reapply the fix against the current agenda and attendees, not the values from the failed run.
• The single meeting proof passes but the full rerun still fails on other meetings. Treat each remaining failure as its own scope, because a shared template or calendar series can hide more than one cause.
• The source systems disagree on the correct value. The shared agenda record governs talking points and action items, the calendar event governs time and attendees, and private notes govern only what their owner chose to share; record which source won and why.

Compatibility: 15Five at current versions, plus the calendar, agenda or people tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_zEgMdnZbK6cnB03p7fTb7w