OJK regulatory monitoring: a practical checklist
Ever heard about a new OJK rule from a colleague first? Track OJK changes, confirm what's really in force and get each one to the right reviewer.
Have you ever heard about a new OJK rule from a colleague or a headline, then spent the afternoon working out whether it's a draft, a proposal or something already in force?
Regulatory news rarely arrives clean. A headline says "OJK to require…", someone shares a screenshot in a group chat, and the product team asks whether they need to change a launch. Before anyone can answer, you need to know what was actually published, whether it applies to you yet, and who should look at it.
This checklist turns that into a steady weekly routine. It helps you find and sort regulatory news, and it doesn't replace legal advice.
1. Decide what you're responsible for watching
Write down the product lines, legal entities and topics you must cover, such as product requirements, tariffs, distribution, governance and reporting.
Then list the sources you can't miss, starting with OJK's own publications. Compare that list with what your current feed or tool actually sends you, so you know where the gaps are.
Finally, name one owner for the feed, and the people who review each kind of change: legal, compliance, product or actuarial.
2. Keep each feed focused
When one feed covers all regulatory news, the important items get buried. Start with one product line or topic, and keep these apart so they don't blur together:
- OJK's own publications, and news about OJK
- proposals still under discussion, and rules already in force
- changes for the whole industry, and news about one company
If irrelevant or duplicate items keep showing up, tighten the keywords or drop the source.
3. Work out what stage it's at
Not every headline is a "new regulation." Most regulatory news sits at one of four stages, and the words you use with your team should match:
| Stage | What to find out | How to describe it |
|---|---|---|
| Proposal or consultation | Who proposed it, what it covers, when feedback closes | "Proposed" or "under consultation" |
| Under review | What OJK is looking at, and what's still undecided | "Under review" |
| Issued | The regulation number, the issue date and the date it takes effect | "Issued, takes effect on…" |
| In force | Who it applies to, and what they must do now | "In force" |
A news report that OJK "plans to" cap a tariff tells you to look for the source. It doesn't tell you the cap exists. Imagine telling your product team a tariff cap is coming, watching them pause a launch, then learning it was one official's comment at a conference.
4. Find the original document
For anything that could affect your products, find the OJK publication itself. Headlines and summaries often drop the details that matter most, like exceptions and transition periods. Once you have it, check:
- the regulation number, title and publication date
- when it takes effect, and any transition period
- which products, companies and activities it covers, and any exceptions
If you can't find the original, mark the item "needs verification" and say so when you share it. Don't fill the gap with a guess.
5. Send it to the right person
Give each item one label:
- Review now: it could create an obligation, set a deadline or affect a product.
- Monitor: a proposal or review that may still change.
- Reference: useful background, nothing to do yet.
- Out of scope: outside what you're responsible for watching.
For anything marked Review now, note who is reviewing it, by when, and why you flagged it. Spotting a change and deciding what it means legally are separate steps, often done by different people.
6. Keep a record you can trace
A simple log lets anyone see later what was found, what it's based on and what was decided. Copy this table and fill in the middle column for each item. The example shows one filled-in entry.
| Field | What to write | Example |
|---|---|---|
| What happened | One sentence, including its stage | Draft OJK regulation on health product distribution, open for comments |
| Source | A link to the original publication | The OJK consultation page |
| Dates | When it was published, and when it takes effect or closes | Published 3 March, feedback closes 31 March |
| Who it affects | The products, entities and activities in scope | Our individual health products sold through banks |
| Reviewer and due date | Who looks at it, and by when | Compliance lead, by 20 March |
| Decision | What was decided, and when to look again | Send feedback through the association, check again when the final rule is issued |
Keep the source's own words apart from your reading of them, so a reviewer can tell which is which.
7. Share it without overclaiming
Whether you're briefing your team or making the call yourself, a short update covers what happened, why it may matter, what's still unclear and who is reviewing it. Hold back on "we must comply by…" until the reviewer has looked at it.
Take care with numbers in regulatory stories too. One article might quote a projection, a half-year result and a year-to-date figure in the same paragraph. They measure different things, so don't compare them as if they were the same.
8. Look back every few weeks
- Did we miss a source or a change we should have caught?
- Did important items reach the right reviewer in time?
- Which keywords or sources mostly brought noise?
Change one thing after each review, and see whether the next few weeks run smoother.
Where Flowy fits
Flowy keeps your feeds focused (step 2) and gets you to the original document faster (step 4). It watches regulator, industry association and news sources, files regulatory news under Regulatory Watch by product line, and links each item to its source.
See how compliance teams set it up in regulatory monitoring, and run the two-minute fact check before you escalate anything.
Catch OJK changes early
Set up a regulatory watchlist in Flowy and see what it surfaces this week. Free, no credit card.