Welcome to our Q3 2026 product update. Before we get started for real here, just a few good things to know. This webinar here is being recorded. We will share it with you afterwards in an email, but it will also be available in our help center. Please feel free to use our Q and A button if you have any questions as we go. We will, again, collect them as we go, and then we will address them towards the end of the webinar. Today it is going to be Kristian, Raquel, and myself. Kristian, can you put a few words on who you are?
Thank you, Morten. Yes. My name is Kristian Jensen. I am the Lead Product Manager here at Impero, and I have the pleasure of talking a little bit about recent highlights in some of the releases we have done, but also talking a little bit about what is to come. I am really excited to do that.
I will just go ahead.
Yeah.
My name is Raquel. I am Product Manager here at Impero as well, and today I will be doing a deep dive into our new Control Health feature.
Thank you both. My name is Morten Christensen. I am customer experience director here at Impero, and today my role is trying to moderate the things here. Hopefully everything will go smooth. What you can expect for today or for this webinar is a recap of our latest releases, highlights, recent product updates, et cetera. We are going to do a feature and focus on our newly released Control Health, and we will again see a little bit on how that looks live and also a little bit on what our plans are for the future, both within Control Health but also within other areas.
Then, as mentioned, we will do a live Q and A towards the end. Should you have any questions, anything throughout the webinar, please address it in the Q and A feature. Final thing before we get started for real, your feedback really matters to us. We are doing an NPS survey. We are doing that continuously within the platform, but we are also doing another round through our email channel.
You might have received it earlier, like half a year ago. You could see how it looks here on the right side of the screen. It is a classic NPS survey that we are doing. It is really simple to do. You click on a number, depending on how good you believe that we are. As the official term is, how likely it is that you will recommend Impero to friend or colleague. It goes from 0 to 10. One thing to note is when you click the number in the link, it will actually be a pop-up window where you just have to confirm the answer and click submit in the end.
You will be able to do that with a comment as well. It is really important for us that we get as much feedback as possible, both the customer-facing team that I am a part of, but also for our product team, for Kristian and Raquel and the rest of the team over here, so we can be as good as we possibly can. With that out of the way, let us get started for real. I will leave it to you, Kristian.
Thank you, Morten. I have the pleasure of spending a bit more time on highlighting some of the recent releases on the platform. Without further ado, let us dive straight into it. Entity Management allows you to run one set of controls across your whole organization, while each entity or department only sees and manages the data related to its own entity. Entity Management is something that we have now upgraded even further, so that we have enabled local entity access to be able to work with the dashboard and the reports module. This enables the local entity owner to pull reports, set up dashboards without needing to involve a global admin to every change or request.
We're, of course, very eager to hear your feedback on this, but we will also continue to add more functionality to Entity Management and any feedback or potential improvements that you have, we're really happy to listen to them and see how we can help you get the most out of the platform. We also want to make it easier for you to complete and review controls. So instead of having inbox rules or similar that filters out not relevant emails, you're now able to be a bit more specific around which emails you want to receive from Impero.
It's important to stress here that critical emails will still always be sent out, but beyond that, we want to make sure that we are only sending you the emails that you deem relevant, and that helps you basically complete your controls and so on. If you're already using Impero Assist, you may already be familiar with this, but we have now added an AI summary to the residual risk within the risk module. So if you ran a mitigation plan on your top risk last quarter, how did that actually turn up? How did that change your risk picture? Impero Assist is now enabling you to get a quick summarized view on how that has been performed. Of course, it's important to stress here that this is only a summary, and there may be errors and so on.
It's just a way to get you started with the work. We have upgraded our activities page, which is something that I believe most of you are using on the daily, but we have added some more functionality for all users, and we've also made it possible for entity users. So if you're using Entity Management, then the local entity admin or entity viewer and so on can now also work with the activities page, and filter, of course, on entities and so on. It's now also possible to adjust the view to define where each column should be or which column should be visible. Hopefully with this upgrade, you should also now experience a significantly faster reaction time from when you set a filter or start searching when using the activities.
We've also added the ability for you to send personalized reminder to really get those controls over the finish lines and encourage performers and reviewers of completing a control. It is now also possible to unarchive activities yourself instead of needing to reach out to support, so that if you, let's say, accidentally archive the control activity that shouldn't have been archived, now it's easy for you to undo that. Finally, from the screenshot here, you can also see the possibility to extend the due date, which is something that I will return a little bit later to in this webinar.
That's just a little bit of a tease. We have introduced a way for you to go beyond whether a control was completed in time or not by releasing our Control Health functionality. This is a natural segue into our feature and focus with Raquel, who will be presenting our feature of Control Health and speaking a bit more about some of the amazing things that we have planned for this area. But first, I believe that we have a little bit of a poll.
We do. What we want to know here is a little bit on when one of your control activities is running behind, what's your first question? Is that who's currently holding it up? Is it responsible? Is it reviewer? Is it a little bit more of what actually happened along the way? Is something needs some rework? Is it going back and forth or is it just sitting with someone overdue? Is this a recurring pattern for this control, or is it just something that you usually just note and then move on. I'll just give everyone a few seconds here to vote on this. But it's something that's quite important for us also when we look at, okay, how should Control Health also look a bit in the future, then we are super interested in what's actually important for you guys.
Just leave it here for another 5-10 seconds, then we can see the result. Right. So, yeah, it was mainly the first option here. So who is actually currently holding it up? Is it responsible? Is it reviewer? But also a little bit on, okay, what actually happened along the way, so a little bit more in the detail on something needs some rework or something that's going back and forth. So that's super interesting and something I'm sure that Kristian and Raquel can use going forward. With that, I'll leave the scene to you, Raquel.
Yes. Thank you very much, Morten. Staying on the same topic as the poll as well, I'll share a bit more about Control Health, which we launched a few weeks ago, and I know that many of you have already been using intensively. If we go to next slide. Starting by the origin of it. The reality is that Control Health was not really invented by us. It was actually something that was invented by some of our customers. Through conversations with them, we kept seeing the same pattern, that was that people were trying to understand what had happened with specific activities, because the reality is that there was no easy way of seeing the full life cycle in the platform. So questions like, as you said in the poll, like who was the current bottleneck?
If it was the responsible who was taking a lot of time, maybe it was the first or second reviewer who was the one blocking the way, or whether the activity had been rejected or reopened. What we realized was that this was usually a reactive approach, this meaning that people were usually investigating an activity only once they already knew that there was a problem with this was usually because it was already overdue or because it was flagged some way. A good example of that is what you can see on the screen. Here we have two activities. Both of them share the same status, the completed status. Until now, at first glance, that was pretty much all you could see.
But if you look at the Control Health column, this is the new column that we just implemented, the story is quite different. The first activity seems that had no friction, but then the second activity was rejected and reopened along the way. This doesn't believe in that one is necessarily better than the other, but at least it gives you more context on what happened before the activity was completed. If we go to the next slide, what is exactly Control Health? Control Health basically tells you the story of the activity. First, as I just mentioned, status tells you where an activity is, but Control Health tells you how it got there. What happened along the way for the activity to get there. Control Health helps you as well to spot signals early.
You can see issues building before an activity becomes overdue or closes, so you can act or fix it sooner. Then it helps you as well understand performance across your portfolio, so you're able to identify patterns across programs, controls or entities or know where to focus. If we go to next slide. Exactly what is it that we consider a friction event? Based on conversations with many of you, with focus on two main dimensions. First of all is completion cycle. Was the activity completed in one go, or was there any back and forth through rejections or reopens? The second dimension is punctuality. That shows first on screen. Was the activity completed on time? If it was not completed on time, who is the bottleneck, or what was the bottleneck that was causing the overdue?
The combination of both dimensions showing up on an activity will show as high friction. Just one dimension will show just as friction. Another dimension will just show as clean. It's good to mention here as well that this is what we're showing today. Going forward, the goal is to understand whether there are other signals that would be useful to track and make Control Health even more insightful. Next slide. One very important thing to keep in mind here is that Control Health tells you what happened, but it doesn't tell you whether this was good or bad. Basically, it helps you understand how an activity moved from X to Y, and where friction happened along the way. But the interpretation of all these events should just be yours.
We had examples of customers having back and forth in an activity with a reviewer. Maybe this is something that might look like friction, because it shows as friction. Then, at the end of the day, the result was that this was actually good because it meant that the review was thorough and intense, so it improved the final result. So it's good to keep in mind that this gives you the tools to better understand what was going on with the activities, but then the interpretation is just really something that you need to consider. Okay. So far, so good. Hopefully. A lot of theory. I'm going to be showing a real example in the platform because I think that it will just help everybody understand the feature better. Okay. Perfect. Hopefully, you're seeing my screen now, right? Good. Okay.
I'm sitting right now on the activity page and just going back so everybody really knows where it is. We're going to the activity table, the activity page. This is the information that you until now were able to see. For example, I see these two activities that are both completed after due date in terms of the status. The new Control Health feature that we've developed is something that it should show by default on your activity table. But if it doesn't, we have, as Kristian mentioned before, this new adjust view functionality here that's actually off-topic, but something super cool that will allow you to just drag and move columns around or deselect columns if you're not interested in seeing a specific column, or just focus on something specific. But here you should be able to see a column that says Health.
As I said before, Health basically tells you the friction or the life cycle of that specific activity. So status is telling me that these two activities are both completed after due date, but then the Health column is telling me that the second activity, apart from being overdue, it has been rejected along the way as well. So, this is the first thing that you will be seeing, and then you can sort by the different activities to see exactly which ones have no friction or high friction. But then if you click in this cell over here comes a bit of magic that basically is the full compilation of events of what was going on with that activity from when it was created until the current status right now.
We have a summary box up here that basically tells you who is currently involved into performing this activity, and then the due date that right now I can see that, for example, this activity is overdue because it's showing red, so it's just easy to spot. Then we go to the activity timeline, and as I said before, this is like the storybook of the activity. So you can see that the activity was created, and it was assigned to me. Something that will allow you to spot the bottlenecks, and I'm very happy that the whole turned out to be like that because the bottlenecks is something that you will be able to spot easier with Control Health. You see these waiting on boxes that basically tell you who was the bottleneck at that specific stage.
For example, the activity was created, and you can see that I was the bottleneck because I was the responsible, and this was my personal due date. Then you can see that the activity was in, I submitted the activity for review, and then the activity was waiting on Morten, who was the bottleneck with his individual due date. Then he saw the activity, and then this activity due date timeline bar tells you that after he had seen the activity, then it got overdue. Again, this can be because maybe he didn't have enough time, or maybe he just took a lot of time in reviewing it before doing it. Then we can see that the activity was rejected and back to the responsible, with the comment that it was left.
Then the bottleneck boxes turn orange because me, as a responsible, I'm doing my step after the due date. So you can easily spot what's after or who was the bottleneck at the specific point in time. That with the next of events. So it was in, then it was submitted for review, and then after that, you can see that it was finally completed and reviewed. As I said before, this is something that you can sort. For example, if you want to focus on the activities that are currently in progress right now, you can just sort by the health column, so they pop up before. So you can just take action before they become a real problem. Okay. I think that we can share the screen again, the presentation.
I'll go back.
We're back.
Bit of luck.
Okay. Then in the next one. So far we've looked at what's already been released. Now we're going to be shifting gears to what's coming next, and continuing as well with Control Health. The first release, as I just showed, gives you the most granular view. So basically, in the activity table, you're able to see the overview per activity of what's going on, friction events, and so on. The next release will introduce a dashboard that gives you an overview of how friction is affecting your organization. This means you're going to be able to see how activities are performing, like all your activities are performing over time. You're going to be able to focus maybe on a specific entity, or a specific program, or a specific tag.
With another widget as well, you will be able to spot patterns and current bottlenecks on specific programs and ongoing activities. So you know what you need to focus on first. Just something that I want to mention here as well, that it is fair to say that this feature is still evolving. I think that we're really only scratching the surface of it. So it will become much richer as more of you use it and we just share feedback and get more feedback from you.
Okay, on the next slide. On future developments as well. For the next release, we've been working on a new public API endpoint that lets external systems basically to pull evidence files, that this is the attachments on a control activity directly from Impero, as this is something that has been highly requested by some of you. Now over to you, Kristian, with more exciting features.
Thank you. I have the pleasure of talking a little bit more about some other things that are also coming soon. I hinted at earlier, we are adding the functionality to enable organizations to decide whether they allow for postponing of due dates. This will enable you to either update a due date in the case of a reopen or in a situation where other factors cause the due date to be in a need of an update of some sort. In this way, an agreed delay becomes a logged, attributed decision, instead of a silent overdue of the record, and maybe it is leading into some Control friction as well. We do acknowledge, of course, that this is something that not all organizations want to have made possible. The default will be that this functionality will be toggled off.
But if this sounds like something that you are interested in, you are more than welcome to reach out or if you have any questions or concerns or similar, reach out and we will answer them. If you just want this enabled as soon as possible, reach out and we will have it enabled as soon as this goes live. If you jump to the next slide. We had the pleasure of hosting our networking event here in Copenhagen called Compliance. Curated. At this point, I told a story about a change that we see in the market across many industries. In short, we shared that we are working on capabilities that will let people work with Impero in their favorite AI client and connect with Impero to workflows outside of Impero.
This slide shows how the change will be and how we see the changes is happening right now in the industry. People and organizations are moving outside of the classic UI, and they are doing more and more work using either Claude or Microsoft Copilot or similar. Next slide. For this would mean that you would be able to go to Copilot or any other AI client, and you would be able to ask it something. It could be something simple, like, do I have any open controls? Or, what do I need to review? Or it could be, take the evidence from over here and add it to this specific control.
This was just a short sneak peek, and we are going to follow up in the future and have more dedicated sessions specifically on this and share much more. But if this sounds interesting to you or if this is something that you have already been working a little bit with on your own side, then please reach out. Or if you have any questions or concerns, as always, please feel free to reach out to us and we will tackle that. But I think that is all from us from now on. I will pass it back to Morten.
Thank you both to Kristian and Raquel for the update. As usual, a lot of things are happening, and things are speeding up also for us. You can always keep exploring Impero, and we will have all the releases, updates, everything that we do in our help center. It is at support@impero.com, as you can see on the screen here as well. In here, we also have some of our Control Health tutorials. Again, Raquel did an awesome job today showcasing how it works, but you can also see it is slow-paced. You can pause and play. You can follow a bit along, and it is both available in English and in German. Keep following us on LinkedIn.
There is a lot of fun stuff on what is going on behind the scenes, but also a way to get the news when something, new features we are working on, et cetera, that will always be posted on LinkedIn as well. Follow us here as well. Then a few more practical things here. We are doing a product update webinar again towards the end of the year. It is going to be December 15th. It is going to be super good. We are going to round the year off, hopefully, with a lot of exciting things. We got a little bit of a sneak peek on it here today. You should please sign up for our newsletter as well. You can scan the QR code here on the screen.
There is both one for marketing and there is one for product, left and right here, and so you can also obviously subscribe to both of them. It is an easy way for us to communicate all the good things that are going on in our world towards you guys. Then before we go to the Q and A session, there is a second poll, and now we talked a little bit about Entity Management, or you did today, Kristian, on how that actually works, or how the improvements have actually went, is probably a bit more accurate. It is something that has been enabled for a few of our clients already, and we see actually a lot of value here in data segregation, et cetera.
We are just really interested in learning where you stand on this and whether it is something you are interested in learning a bit more about in Impero, and we have a few options here. You can obviously explore this a little bit on your own. Again, as mentioned, we have a lot of awesome resources in our help center. It is also something we can tailor a little bit more to your world.
Then please select the customer success option here because then we can, in my teams, reach out and we can schedule something where we can showcase what does that actually look like for you. If you are already using it, then you already know how it works, and it might be that the timing is not right now. But there is really a lot of good things that comes with Entity Management. You can assign more local ownership.
A lot of clients where it is piling a little bit up on who is performing what is controlled very centrally. But also when it comes to access rights to auditors, et cetera, then now we actually have a better way of actually assigning the access rights and granting a view access all the way down to a single entity. Really awesome feature. Please select the option here that makes the most sense for you. But obviously, we want to showcase it to as many of you as possible. Let's see how my sales pitch here went. Then we can see that a lot of you want to explore this on your own.
Again, totally makes sense. There is a lot that is available on our website on this. Then we will find the right timing for when we need to know more. If you are interested in having a chat with us, we will obviously set that up. Luckily, a bunch of you are using it already. As always, there is a timing issue. We obviously also understand that, so respect that. Hopefully, we can have a look at that later on, either this year or at the beginning of next year.
With that, we will open the Q and A session. I will just find it so I have it on my screen here as well. I see there is a bunch of questions available here already. I think this one goes to you, Raquel, but you know if I make a swing and a miss, then you can also pitch in here Kristian. But in the Health check, when an activity is listed as seen, will that be tracked for all the times our preparer or reviewer insert into or open the activity?
Yeah. That is actually a very good and detailed question. When we were building the activity timeline, we didn't really want to pollute the timeline with all the seen events, for example, for when a responsible reviewer was opening the activity. So what we decided here is that the seen event will only show the first time that the person that is holding the current step sees the activity for the first time. So this means the first time that the responsible, when it is their time opens activity, it will show as seen, and then the same for first reviewer and second reviewer.
Perfect. Thank you, Raquel, and I think I have a few questions for you, Kristian. It is regarding this deadline or postpone due date, it is probably more accurate to say, but who will actually be able to postpone the deadline in the new features? Is it admins, or is it regular users who can do that?
That will be admins. That will be the people sitting typically with the responsibility, but not the performer or the reviewer, typically. It is the same people that in many cases would sit the responsibility of the overall performance of it, that would be sitting and updating or postponing the due date in case that something came up. If the person that asked the question is curious about or want to have the functionality for regular users, I would love to chat with them and understand a little bit more around their use case.
Perfect. This might be a twofold question here. I think the first part is as a follow-up to the postponed deadline thing here, but when postponed deadlines is activated, will that change the completion status? Let us say that the initial task was completed after due date, but then upon reopening or postponing the due date, will then that task then actually be completed within the updated deadline?
That is a very good question, and something that I will need to double-check. My understanding is that if you extend the due date, that the due date will then, or the activity will then be completed within the due date. So, yeah. It will be tracked as a point of friction as far as I understand from the Control Health project as well, because there is a need for some sort of interference here, but it will still be a situation where the, what is it called, where the activity will now be completed within the due date. Raquel?
Yeah, I think that I can help you with the health and friction there. On the health side of it, we are going to be tracking every time that an activity has been reopened. So in the timeline, you are going to be able to see, same as the other events, when that happened, and then the previous due date. So, what was the previous due date compared to the new due date.
So you will always be able to track that. In terms of whether this is affecting the friction label or not, this is something that we are still exploring because this is a feature, so we just need to understand exactly how our customers think of whether postponing a due date is something that they would still consider as friction or not. So yeah, this is something that we are still working on right now.
Thank you.
Perfect. Thanks to both of you. A question actually also related to this part here. I think there is a lot of interest in the extended due date, but is the extended deadlines, is that a feature that is only when reopening things, or is it actually also something that can be used for tasks not completed yet?
It is both for active tasks, so tasks that are activities that are not been completed yet, but also when reopening an activity. We do currently not allow for completed activities to have their due date extended, because it shouldn't become a situation where everything just becomes green and you can extend the due date of completed things. But if there is a need for either an ongoing activity to extend the due date or for an activity to be reopened, could be that there is still some work there to be done. We do allow for the due dates to be extended.
Perfect. Let's just take two more questions here, and then we can we'll answer the rest afterwards. There's one here, the Entity Management and whether the company should have access to Entity Management before external auditors are granted access. I think I can maybe answer that question here and maybe
Yeah
a little bit on how it actually works. The short version would be that when we enable Entity Management, we can create the entities, and on each of those, we can set the access rights. So you can still continue to have everything governed centrally, but you actually also have the option of saying, "Okay, this entity here that we have in Spain is actually also governed locally by an admin down here." So, that'll be fairly easy to do that. You need all of that enabled and set up before it would make sense at least to grant your external auditors access to the entity. Unless you're doing everything centrally today anyway, and your objective would be on access rights towards the external auditors, then we can do that fairly easy.
Again, reach out to us, then we can set up a session where we can showcase exactly how it is. Final question here. It's been a little bit on the AI, so Impero exploring AI in the upcoming months. Is there any possibility to see sort of control process effectiveness and percentage, like completion percentage based on data loaded and control set up available in Impero automatically in the future?
I'm not sure I fully understood that question, but if my understanding is correct, I assume that the person asking for the question would like to process large amount of data with AI and have AI give a first assessment of how well the ongoing control processes are going. I could share that with an MCP connector, for an example, being able to use your own client, so your Copilot or Claude or whatever. That's definitely something that could be done relatively easily around pulling the data from Impero into your own AI assistant and then giving them the prompts and the input that you're asking for. Of course, it's a matter of asking the right questions and also kind of like not just trusting whatever the AI would spit out completely. But something like what the person is describing is definitely possible with using those tools.
Thank you, Kristian. Let's close the Q and A for now. There's still a few open questions here. We'll come back to those and address these with you guys afterwards. Thank you so much for joining. We'll see you at the next product update webinar on December 15th. My final words of today will be, remember the NPS that we're going to send out tomorrow. Again, it really, really, really, really means a lot to us to get your feedback. It's something that we highly value, both in the customer-facing team, as I mentioned, but also in the product team. So we are familiar with the direction we need to go into in the future as well. Once again, thank you for joining. Thank you to Kristian and Raquel for a fantastic presentation on all the good things that has happened and is currently happening.
Thank you so much.
Thank you. Thank you all.
Bye guys.