Why is My Update Marked Late?

An update is marked Late when it's posted after your team's DSM cutoff time and grace period have both passed. Here's how to diagnose the cause.

Check What Time the Cutoff Is

1. Go to Settings → Profile.
2. Look at your working schedule — this shows the org or team cutoff time in your local timezone.

If you don't see this, ask your admin for the org cutoff time.

Common Reasons for Late Marks

You submitted after the cutoff time

The most common reason. If your team's cutoff is 11:00am and you submitted at 11:45am (outside the grace period), the update is Late. Aim to submit before the cutoff.

Your timezone is set incorrectly

If your timezone is wrong, the cutoff time may display incorrectly — you might think you're submitting before the cutoff when you're actually after it.

Fix: Go to Settings → Profile and verify your timezone is correct. See Setting your personal timezone.

Your org uses org timezone mode

If your org's cutoff is set to org timezone mode, the cutoff applies in the org's timezone regardless of yours. If the org is in London and the cutoff is 11:00am BST, members in New York need to submit before 6:00am ET — which may not be realistic.

Fix: Ask your admin to switch to user timezone mode, or set a team-level schedule override with a later cutoff for your timezone. See Team-level schedule overrides.

The grace period is very short

If the grace period is only 5–10 minutes, even slight delays result in a Late mark. Ask your admin to increase the grace period if this is causing issues.

Can a Late Mark Be Reversed?

No — timeliness scores are finalized at submission time and cannot be changed retroactively. Focus on preventing future late marks rather than disputing past ones.