The HSA Just Changed What "Submission-Ready" Means: Inside the New CMC Quality Declaration

The HSA Just Changed What "Submission-Ready" Means: Inside the New CMC Quality Declaration

Jun 04, 2026

If you file therapeutic product dossiers in Singapore, a quiet but important change took effect on 1 June 2026, and it has nothing to do with new science and everything to do with discipline. The Health Sciences Authority (HSA) now expects you to certify, in writing, that your CMC package has no known quality defects at the moment you hit submit. Not when you compiled the data. Not when the batch was released. At submission.

It sounds like a small administrative tweak. It isnt. It quietly shifts the burden of "is this data still valid?" from the reviewers desk back onto yours, and it rewards the companies who already run tight change control while exposing the ones who dont.

At Valina Services, we spend our weeks helping APAC pharma, biotech, and medical device companies keep their submissions clean and their systems audit-ready. So heres a practical, no-jargon breakdown of what changed, why HSA did it, and what you should actually do about it.

First, What Actually Changed

On 1 April 2026, HSA rolled out two updates to therapeutic product registration. The first made the Electronic Common Technical Document (eCTD) format, using SG-HSA eCTD version 1.1, the official standard for dossier submissions. The second is the one that quietly bites: from 1 June 2026, applicants must include an official letter declaring that there are no known quality defects or critical issues that would require an amendment to the submitted Chemistry, Manufacturing & Controls (CMC) package.

HSA frames this under the banner of "Good Submission Practice." The stated aim is to reduce the inadvertent submission of superseded technical data and to improve overall regulatory efficiency. In plain terms, they dont want to spend review cycles on a CMC dossier that the applicant already knows is out of date.

You can read HSAs own announcement here: https://www.hsa.gov.sg/announcements/regulatory-updates/regulatory-updates-on-therapeutic-product-registration-(1-april-2026)

Why This Matters More Than It Looks

Plenty of teams will read "submit a declaration letter" and file it under paperwork. Thats the wrong instinct. Heres why this change has teeth:

It moves the validity checkpoint. Previously, the unspoken assumption was that a reviewer might catch a stale specification or a superseded method during evaluation. Now you are formally attesting, up front, that nothing in the package is known to be defective. The responsibility is explicitly yours.
It creates an accountability trail. A signed declaration is a document with a name on it. If a known defect later surfaces that should have triggered an amendment before submission, that letter exists. This is exactly the kind of artefact an inspector or reviewer can point to.
It exposes weak change control. The whole point of the declaration is to confirm your CMC data is current at submission. If your internal change-control and document-control processes are slow or fragmented, you genuinely may not know whether a specification, method, or stability commitment has moved since the dossier was compiled. This requirement turns that blind spot into a compliance risk.

The companies that already run disciplined change control will sign this letter with confidence. The companies that treat compilation as a one-time event and then look away will feel the pressure.

What "No Known Quality Defects" Really Asks of You

To sign that declaration honestly, you need to be able to answer "yes" to questions like these, on the day you submit:

Are all specifications in the dossier the current, approved versions?
Have any analytical methods been revised, superseded, or invalidated since the package was assembled?
Are there any open deviations, OOS results, or investigations affecting the data in the submission?
Have stability commitments from prior applications produced results that change the picture?
Has any manufacturing change occurred between compilation and submission that the CMC package doesnt reflect?
Is there any known issue at a drug substance or drug product manufacturing site that would require an amendment?

If you cant answer those confidently, the declaration isnt your problem. Your change-control process is.

A Practical 5-Step Readiness Checklist

Heres the approach we walk clients through when a new submission is on the horizon.

Step 1: Freeze and Reconcile Before You Sign

Set a clear "data lock" point ahead of submission and reconcile the dossier against your live document management system. Confirm that every specification, method, and report in the package matches the currently effective version. Mismatches between "whats in the dossier" and "whats in the system" are exactly what this requirement is designed to catch.

Step 2: Sweep Your Open Items

Pull the current list of open deviations, OOS/OOT investigations, change controls, and CAPAs touching the products in scope. Any open item that could affect the CMC data needs a documented assessment before you can honestly declare "no known defects."

Step 3: Check Your Stability Commitments

Stability commitment batches from earlier variations are a classic source of superseded data. Confirm no results are outstanding or trending in a way that would require you to amend what youre about to submit.

Step 4: Build the Declaration Into Your SOP

Dont treat the letter as a last-minute formality drafted by whoever is free that afternoon. Add it to your submission SOP as a controlled step, with a defined owner, a defined sign-off, and a defined evidence trail showing the checks above were actually performed.

Step 5: Get eCTD-Ready in Parallel

Since eCTD (SG-HSA v1.1) is now the official format, use this moment to confirm your dossier publishing process, validation profiles, and lifecycle management are aligned. Companies can still use existing submission modes for now, but HSA is strongly encouraging the transition, and early adopters will be in better shape as further phases roll out.

The Bigger Picture: Where APAC Regulation Is Heading

This change is small on its own, but it fits a clear pattern weve been seeing across the region: regulators are pushing accountability upstream, toward the applicant, and rewarding companies whose quality systems are genuinely live rather than periodically dusted off. eCTD adoption, tighter submission practices, and reliance arrangements between authorities all point the same way, more structure, more traceability, and less tolerance for stale or disconnected data.

The teams that build these checks into how they work, rather than scrambling at each filing, are the ones wholl move faster when speed actually matters.

How Valina Helps

This is the work we do every week. If the new CMC declaration has you wondering whether your submissions would survive scrutiny, heres how we can help:

Submission Readiness Reviews. We assess your CMC package and the change-control processes behind it the way a reviewer would, and hand you a clear, prioritised gap list before you sign anything.
Process and SOP Strengthening. We help you embed the declaration, data-lock, and reconciliation steps into your submission and quality SOPs, so "submission-ready" becomes a repeatable process rather than a last-minute scramble.
eCTD and Compliance as a Service (CaaS). From eCTD publishing readiness to fully managed compliance support, we help APAC pharma, biotech, and medical device companies keep their data current and their submissions clean, so the next regulatory change is one less thing to worry about.

Final Thoughts

The new CMC declaration is, in the end, a test of one simple question: do you actually know whether your data is current when you submit it? For companies with disciplined change control, signing the letter is a non-event. For companies that compile a dossier and then stop watching, its a quiet new risk with their name on it.

You dont have to wait for a submission to find out which one you are. If youd like an honest read on where your CMC and submission processes stand, thats exactly the conversation we like having. Contact us for a consultation, and well help you get there.

This blog provides general information and should not be considered regulatory advice. Always consult qualified professionals and refer to the latest HSA guidance regarding your specific compliance requirements.

Posted by Dr Suhanya Parthasarathy.PhD