Most weak ICT deferment applications are not weak because the reason is emotional. They are weak because the evidence does not let the reviewer understand the clash.
MINDEF guidance lists categories that may be considered, but approval still depends on the facts, timing, and documents.
This guide is a document-first companion to the broader ICT deferment guide.
Transport claims are small until they get rejected, held, or repeated enough times to become a monthly irritation.
The useful questions are practical: what can be claimed, what evidence is needed, why a payment might not appear, and how to handle extra trips or system rejections.
This guide stays within public claim guidance and uses OneNS checks as the starting point.
Telemedicine MCs create a very specific kind of confusion: people know they have an MC, but they are not sure whether the unit, OneNS, or public rules treat it the same way as an in-person clinic MC.
The official public guidance is clearest on medical leave submission and OneNS evidence. It is less explicit about every unit-level telemedicine scenario.
So the safe approach is to submit properly, update your unit promptly, and avoid inventing a universal rule where public guidance does not publish one.
ICT deferment feels messy mostly because people look it up late.
By then, the useful questions are not abstract anymore:
The cleanest way to handle deferment is to follow the admin sequence before the stress starts improvising for you.
Mobilisation manning sounds more mysterious than it actually is.
Most of the useful questions are straightforward:
Once those are clear, most of the unnecessary panic disappears.
Allowance questions feel much louder in NS because they usually show up exactly when you need the money.
That is why the same few questions keep appearing:
Most of the confusion is timing-related, not mysterious.
Getting an MC is usually the easy part. Closing the admin loop is where the avoidable problems start.
The common mess looks like this: the unit is informed halfway, the MC is photographed badly, the digital link is copied instead of uploaded properly, or someone assumes the system auto-approval means nobody needs to know anything else.
The cleaner route is simple once you treat the MC submission as its own short task.
Exit Permit gets confusing because most people hear three versions at once:
The easiest way to make sense of it is not by memorising random statements. It is by understanding the thresholds and then testing them against real situations.
The most annoying part of reporting sick is often not the illness. It is the admin around it.
Problems usually happen because someone disappears before informing the unit, assumes the MC alone settles everything, or forgets the OneNS follow-through entirely. The good news is that the low-drama version is very repeatable.
Inform early, follow the correct medical route, keep the paperwork, and close the admin loop before you switch off.