Regulatory affairs teams live in two worlds.
In one, you are deep inside an eCTD package, reconciling a Module 3 change request against the latest CMC data and chasing down a missing Annex II reference. In the other, you have forty-five minutes to walk an executive sponsor, a clinical lead, and a finance partner through where the submission actually stands and what could blow up the timeline.
The first world is what the job is about. The second world is what keeps the first world funded.
Most regulatory leaders I talk to spend far more time than they would like on that second world the status decks, the milestone updates, the T-30 readiness reviews, the board slides for the IND or 510(k) program. Not because the work is hard, but because the tools for it were built for marketing teams, not for people whose source material is a 600-page submission package and a real-time readiness dashboard.
This post is about how I would close that gap if I were running a regulatory ops function today.
The hidden cost of status decks
If you have ever timed it honestly, you know how this goes.
You finish a working session on a submission package on Tuesday. By Wednesday morning, three people independently ask for "a quick update." One needs three slides for a steering committee. One needs a one-pager. One wants the full readiness picture for an external CRO partner call on Friday.
You open the deck from last cycle. You copy a slide. You paste in new numbers. You realize the chart is from a different program. You fix it. You change the footer. You change the date. You notice the executive summary still references a milestone you hit two weeks ago. You fix that. You send it. Forty minutes are gone, and the deck still looks like a deck from last cycle with new numbers pasted in.
Multiply that by every milestone, every governance review, every sponsor sync. For a five-person regulatory affairs team running two active submissions, this is easily a full day a week. For a CRO or regulatory consulting partner managing multiple sponsors, it is more.
The work is not strategic. It is translation - taking structured submission data and rewriting it as narrative slides for an audience that does not read eCTD.
What I would change
A workflow worth keeping has three properties.
It starts from the source of truth, not from last cycle's deck. If your readiness dashboard, your document workspace, and your status tracker already know where the submission stands, the deck should be derived from that - not retyped from it.
It separates structure from polish. The thinking - what story am I telling this audience, in what order, with what supporting evidence - is the part that needs a human. The visual rendering of that thinking into clean, on-brand slides is the part that does not.
It is fast enough that you actually do it before the meeting, not during it. The reason status decks are often half-rebuilt at 11 PM the night before a review is that they are too expensive to build from scratch. Make them cheap and the panic disappears.
Concretely, here is the loop I would run for a milestone review:
1. Export the readiness summary from your submission workspace - a short markdown or PDF with the current state per module, open items by owner, and projected dates.
2. Drop that into a tool that can turn structured notes into a structured deck. I have been using this free AI slides maker of for this, both for internal updates and for sponsor-facing material. You paste in an outline or a document, pick a template, and you get a deck with a real narrative arc, not a wall of bullet points.
3. Spend the time you saved on the part that actually matters - the executive summary slide, the "what could go wrong" slide, and the ask.
The first time I tried this with a colleague running a 510(k) program, the deck went from a Tuesday afternoon chore to a fifteen-minute task. The deck was also better, because she had time left over to think about what to say, not just what to put on the slides.
What to put on the slides (and what not to)
A short opinion, since this is where most regulatory status decks fall down.
Your audience does not want the eCTD table of contents. They want four things:
• Where are we against the planned filing date.
• What is the single thing most likely to slip it.
• What decision or resource do you need from this room today.
• What you will report next time.
Everything else is appendix. If a slide is not answering one of those four questions, it is probably hiding the answer instead of showing it.
This is also where a tool like ChatSlide earns its keep. When you feed it an outline organized around those four questions, it does not let you bury the lede in module-by-module trivia. When you feed it the full eCTD ToC, it cheerfully renders the whole thing and your audience checks out by slide six. Garbage in, garbage out - but the inverse is also true.
Where this fits with the rest of your stack
None of this replaces your submission workspace, your eCTD publishing tool, or your QMS. Those systems are the source of truth, and platforms like Assyro exist precisely because regulatory work needs purpose-built infrastructure, not generic project management.
What it does replace is the translation layer - the slow, manual, error-prone step of turning "what the submission workspace knows" into "what an executive sees in a Tuesday review." That translation is where regulatory teams quietly lose hours every week, and it is the most boring possible thing to be losing hours to.
If you are running a regulatory function today and you feel like your team spends too much time on status updates and not enough on the submission itself, start there. The two things are not unrelated. Every hour your team gets back from deck-building is an hour available for the actual work.
The submission is the product. The deck is the wrapper. The wrapper should be cheap.
Quan Lai Li builds tools at the intersection of AI and document workflows. He is the founder of ChatSlide, an AI presentation tool used by teams in regulated and unregulated industries to turn structured content into polished decks.
About the author
Assyro Team
Expert regulatory operations consultants helping pharmaceutical companies navigate complex compliance challenges.

