TL;DR: Wrong output usually means wrong input meridiem, timezone offset applied twice, browser autofill corrupting field, or confusing duration with clock time. Reset form and re-enter manually.
AM/PM toggle inverted
User selects PM for morning appointment—converter faithfully outputs 1300 for 1:00 mislabeled. Clear fields, reselect meridiem carefully.
Timezone checkbox hidden
Some advanced tools apply UTC offset—disable if converting local wall time only for personal schedule.
Autofill inserting old value
Browser autofill drops previous search “3:00” without PM—always visually confirm fields before submit.
Duration mistaken for timestamp
Entering 0230 meaning two hours thirty minutes duration into time-of-day converter yields nonsense clock—use duration tool instead.
Locale parsing 03/04/2026
Date ambiguity affects datetime combo tools—use ISO date in advanced mode when testing.
Mobile keyboard AM/PM missing
iOS time picker wheels hide meridiem when 24h system setting on—switch input mode or use dedicated 12h entry.
Compare trusted source
Second opinion on military-time-chart.org—if two clean tools agree, error was input; if disagree, screenshot for bug report.
Cache stale JavaScript
Hard refresh Ctrl+F5 after site update—old client bundle rare but possible on corporate proxy cache.
Spreadsheet link stale
Embedded web query pulling old API—relink rather than blaming mental math.
Document bug properly
Report steps: input screenshot, expected, actual, timezone, browser—maintainers reproduce faster.
Fallback manual method
Paper chart on wall never fails API—hybrid redundancy for mission-critical scheduling desk.
Autofill meridiem trap
Browser drops 3:00 without PM—visual confirm fields every submit.
Duration vs timestamp mode
0230 duration entered in clock converter yields nonsense—pick correct tool mode.
Hard refresh after JS update
Ctrl+F5 if two clean tools disagree—proxy cache rare culprit.
Spreadsheet stale web query
Relink embedded query rather than blaming mental math.
Paper chart fallback
Wall chart never fails API—hybrid redundancy on dispatch desk.
Autofill that saved 1:00 AM over a 1300 job
A browser that autofills 1:00 AM because that was yesterday’s test will feed a converter a true morning instant. The converter’s output, 0100, is then correct for the input and wrong for the job you meant, which was 1:00 PM, or 1300. Clear the field, type 13:00 or select PM yourself, and look at the preview before you save. A correct converter cannot rescue a wrong meridiem. Blame the field after you have looked at it, not before.
Disable autofill on that form if you can. If you cannot, tab through the meridiem control every time and say the half-day out loud. “PM, expecting thirteen hundred.” When the preview shows 0100, your sentence and the preview disagree, and you do not save. The spoken sentence is the check the autofill cannot satisfy by accident.
Hidden zone box that shifts 1300 to 1200
A timezone control set to “UTC” while you thought you were entering local 13:00 will store an instant one or more hours away. The preview might still say 13:00 because it is previewing the wall time you typed, not the stored instant. Open the stored value. For a minus-one offset you might see 12:00 UTC when you meant 13:00 local. The bug is the hidden box, not the arithmetic you did in your head. Make the box visible. A hidden control with a sticky default is a loaded mistake.
Test the form with a known pair and write the expected stored instant on a card. “Typed 13:00 local, zone named, stored 12:00Z” is an example only if your zone is minus one. Use your real zone on the card. A card copied from another office is another hidden control.
Duration field that accepted 1300 as a length
Some tools have a mode switch between “time of day” and “duration.” A duration of 1300 minutes is a long maintenance window. A time of day of 1300 is one in the afternoon. If the mode was duration, the tool did not malfunction when it scheduled a huge block. Look at the mode label before you clear the database. Fixing the data without fixing the mode will create the next huge block tonight.
Put the mode in the page title, not in a tooltip. “Clock time, not duration.” Tooltips do not survive fatigue. A title does. If the product will not change the title, tape a label to the monitor that says which mode this bookmark is. The bookmark should include the mode in its name.
Hard refresh after the preview script changes
If engineering ships a new preview script, your browser may run the old one until you hard-refresh. The symptom is a preview that still shows 0100 for a PM selection you just fixed in the code. Refresh, then retest the 13:00 case. Do not file a regression on a stale tab. Do not ignore a real regression because you assume the tab is stale. Refresh once, retest once, then believe what you see. Write the result next to the release number.
Bookmark title that includes the words clock time
Name the bookmark “Yard form — clock time, not duration” if that is what the form is. The title is visible when the tab is wrong. A bookmark called “Yard” will be clicked for duration entries and for clock entries, and the hidden mode will do the rest. If there are two forms, there are two bookmarks, and their titles disagree on purpose. The disagreement is the safety feature.
Once a month, click the bookmark and read the page title before you type. If engineering renamed the page and dropped the mode, update the bookmark the same day and retest the 13:00 case. A bookmark that promises clock time and opens a duration form is a trap you built yourself. Retire it until the titles match again.