Skip to main content

OneNS Not Updated After a Status Change

· 12 min read
NSVault Editorial Team
NSVault Editorial Team
Practical guides for Singapore NSFs and NSMen

OneNS can become more confusing after a real change than before it. You may have a new posting order, a transfer between services, an updated medical status, or an active call-up, while the app still shows the old unit, a blank field, or a record that does not match what you were told.

The safe response is not to guess which screen will eventually win. Separate the official instruction from the digital display, preserve evidence of the mismatch, and contact the office that owns the underlying record.

This guide is unofficial. Your posting order, SAF100, medical record, current and receiving units, Personnel Admin Centre, and written MINDEF instructions override anything here.

Editorial desk scene with a phone showing abstract status cards beside record folders, a clock, and a reconciliation checklist
Quick version
  • A blank or stale OneNS field does not cancel a posting order, reporting instruction, medical restriction, SAF100, or IPPT obligation.
  • Compare the app with the OneNS website, the document that created the change, and any direct unit instruction.
  • MINDEF says some portal updates, such as profile or deferment changes, can take up to 48 hours to appear in the app. It does not publish a 48-hour deadline for unit transfers or posting updates.
  • If reporting, medical safety, a booking deadline, pay, or a call-up is affected, contact the responsible unit or admin route immediately instead of waiting for the display to fix itself.
  • Save screenshots, timestamps, the exact incorrect field, and the reference document before asking for verification.

What This Applies To​

  • NSFs whose unit is blank or still shows the old unit after posting or transfer.
  • NSFs returning from BMT recourse or handling an OOC-related posting instruction.
  • NSmen whose unit attachment, call-up, or ICT information looks missing or inconsistent.
  • Pre-enlistees, NSFs, or NSmen whose medical fitness information is absent or appears incorrect in OneNS or eHealth.
  • Anyone blocked from an important eService because the displayed record has not caught up with an official change.

This is not a guide to editing unit, posting, PES, medical, or call-up data yourself. Public guidance does not provide a self-service control for changing those underlying decisions.

First Separate The Record From The Display​

Not every mismatch is the same problem. Identify which layer is wrong before escalating it.

The controlling record​

This is the document or instruction that tells you what currently applies. Depending on the situation, it may be:

  • a posting order;
  • a direct reporting instruction from the current or receiving unit;
  • a SAF100 or call-up record;
  • an official medical fitness or exemption record;
  • a written deferment outcome;
  • an IPPT or NS FIT window and booking record.

The portal record​

This is what the OneNS website or a linked eService shows after you log in. eHealth may open as a separate portal even when you enter through OneNS.

The app display​

This is the mobile view. It is useful, but it can be a display layer rather than the source that created the posting, medical decision, or call-up.

If the app and website disagree, do not choose the more convenient answer. Record the difference and check the controlling document or official contact.

The 48-Hour Note Has A Limit​

MINDEF says updates made on the OneNS Portal, with profile and deferment status given as examples, will be reflected in the OneNS app. It also asks users to allow up to 48 hours for those updates to appear.

That is useful when you changed a self-service profile field or received a portal update and the app has not caught up yet.

It is not a published service-level promise for:

  • a new unit after posting;
  • an inter-service transfer;
  • a BMT recourse or OOC movement;
  • a PES or medical-board result;
  • a new NSman attachment;
  • a cancelled or amended call-up.

For those records, public guidance does not give one universal update time. Use the official instruction and the responsible admin route instead of telling yourself that every mismatch will disappear after 48 hours.

If Your Unit Is Missing After Posting Or Transfer​

Start with the posting order, not the unit tile in the app.

MINDEF says your commander or training institute will tell you when the posting order is available in OneNS. If you have the posting order, capture:

  • the new unit or course;
  • reporting date and time;
  • reporting location;
  • attire or packing instruction;
  • any named contact route.

If the app still shows the old unit or no unit, tell the current and receiving units what the posting order says and what the app shows. MINDEF's posting guidance says an NSF who cannot report to a new unit should contact both the current and new units and explain the reason.

Do not skip reporting because the profile tile is blank. Ask this instead:

My posting order dated [date] tells me to report to [unit/location] on [date and time], but OneNS currently shows [old unit/blank]. Which instruction should I follow, and can the underlying unit record be checked?

That question gives the admin team a document, a mismatch, and a deadline.

Special Cases After BMT, OOC, Or Recourse​

MINDEF publishes separate routing for some posting-order cases:

  • NSFs who attended BMT recourse are told to return to their previous unit and wait for further instructions.
  • NSFs who are OOC from BMT are told to return to their BMT unit and wait for further instructions.
  • Military Regulars are directed to their Recruitment Centre.
  • Other missing posting-order cases are directed to the BMT unit.

Follow the route that matches your actual status. A blank OneNS unit field does not prove that you were released from the old unit, permanently assigned to the new one, or free to choose where to report.

If You Are An NSman With No Unit Showing​

MINDEF says NSmen can check their current ICT unit through the My Personal Information eService on OneNS and contact the unit directly for more information.

If that field is blank, stale, or inconsistent with a SAF100:

  1. open the ICT and Manning eService;
  2. check the SAF100, reporting venue, and acknowledgement status;
  3. check My Personal Information for the unit attachment;
  4. use the contact details in the call-up or the known unit route;
  5. contact the NS Contact Centre if the unit cannot be identified or the portal itself is failing.

A missing profile field does not erase an issued SAF100. MINDEF describes SAF100 as the official Order to Report for National Service. If a call-up is active, resolve the mismatch before the reporting date.

If PES Or Medical Information Looks Wrong​

Treat a medical-record mismatch as its own lane. Do not combine it with a posting question unless both records are actually affected.

MINDEF says medical fitness and exemptions can be viewed in the Medical Fitness Info tab of Manage Medical Matters. It also provides a route for incorrect eHealth information: email the NS Contact Centre with identification, contact details, and the nature of the error so the record can be verified and amended where appropriate.

Prepare:

  • the current OneNS or eHealth screenshot;
  • the date and time viewed;
  • the medical review or board date, if known;
  • any written outcome or appointment record;
  • the exact booking or activity that the mismatch affects;
  • the upcoming deadline.

Do not assume an old displayed PES gives permission to ignore a current medical instruction. Do not assume a verbal medical update has changed your official record either. Until the mismatch is reconciled, ask the Medical Officer, unit, Personnel Admin Centre, or NS Contact Centre how to handle the specific activity safely.

When To Wait And When To Escalate​

Waiting can be reasonable when all of these are true:

  • you made a profile or portal change recently;
  • the official instruction is already clear;
  • there is no reporting, medical, pay, booking, or legal deadline approaching;
  • the mismatch does not affect safety or attendance;
  • you have saved evidence of the change.

Escalate immediately when any of these applies:

  • reporting is within the next few days;
  • the old and new units give different instructions;
  • a SAF100 is active but the unit field is blank;
  • a medical restriction or status may affect a booked activity;
  • OneNS blocks IPPT, NS FIT, medical, deferment, pay, or call-up action;
  • the website and app show different outcomes;
  • the record remains wrong after the relevant office says it was updated;
  • you cannot identify who owns the current record.

Do not let a display problem become an attendance, safety, or deadline problem.

Build A Clean Escalation Message​

MINDEF asks users reporting OneNS technical difficulties to provide their name, user profile, and the point at which the error happened. A useful record-mismatch message should also include:

  • current NS status: pre-enlistee, NSF, NSman, or Regular;
  • service and current known unit;
  • the field that is wrong or missing;
  • what the website shows;
  • what the app shows;
  • the official document that conflicts with it;
  • when the change was supposed to take effect;
  • the next deadline or reporting date;
  • a screenshot with sensitive details shared only through the official channel.

Keep the request narrow:

OneNS shows [incorrect field] as of [date and time]. My [posting order/SAF100/medical record] dated [date] shows [different status]. This affects [reporting/booking/activity] on [date]. Please confirm which instruction controls and which office can verify the underlying record.

Do not post screenshots containing NRIC, unit details, medical information, call-up information, or contact numbers publicly.

Who To Contact​

Use the route closest to the source of the change:

  • Posting after BMT: BMT unit, commander, or training institute.
  • Unable to report to a new unit: current and receiving units.
  • In-service personnel record: unit S1, Personnel Admin Centre, or PERS Centre.
  • NSman unit attachment or call-up: unit contact in the call-up, then NS Contact Centre if the unit cannot be identified.
  • Medical or eHealth error: unit medical/admin route and the official eHealth error channel.
  • OneNS technical failure: NS Contact Centre with the exact failure point and user profile.

The NS Contact Centre can help route or verify a portal problem. It cannot safely be replaced by Reddit speculation about what a blank field "usually" means.

Common Mistakes​

  • Treating the app's unit tile as more authoritative than a current posting order.
  • Assuming every backend record has a published 48-hour update deadline.
  • Waiting until reporting day to mention a mismatch first seen days earlier.
  • Asking only one unit when the current and receiving units disagree.
  • Combining posting, PES, IPPT, call-up, and pay issues into one vague message.
  • Sending no screenshot, timestamp, document date, or deadline.
  • Posting personal or unit-sensitive screenshots publicly.
  • Assuming a blank record cancels an obligation.

Frequently Asked Questions

How long does OneNS take to update after a posting?

MINDEF does not publish one universal posting or unit-transfer update time. Its 48-hour note applies to portal-to-app updates such as profile or deferment changes, not every backend unit record. Follow the posting order and contact the responsible units if reporting is affected.

Which should I follow if OneNS shows the old unit?

Use the current posting order and direct official reporting instructions, then ask the current and receiving units to reconcile the mismatch. A stale app display is not permission to miss reporting.

What should I send when reporting wrong OneNS information?

Send the official channel your status, the exact wrong field, website and app screenshots, timestamp, conflicting document, effective date, and any reporting or booking deadline. Share sensitive details only through official channels.

Official References​

Bottom Line​

When OneNS looks stale after a real change, separate the instruction from the display. Preserve the posting order, SAF100, medical record, or written outcome; compare the website and app; record the mismatch; and contact the office that owns the underlying record. Wait only when the official instruction is clear and no deadline or safety issue is affected.