{"id":14640,"date":"2026-06-06T20:41:53","date_gmt":"2026-06-06T18:41:53","guid":{"rendered":"https:\/\/www.leaplytics.de\/?page_id=14640"},"modified":"2026-06-06T20:41:55","modified_gmt":"2026-06-06T18:41:55","slug":"risk-register","status":"publish","type":"page","link":"https:\/\/www.leaplytics.de\/fr\/services\/risk-register\/","title":{"rendered":"Registre des risques"},"content":{"rendered":"<p><!-- SEITEN-TITEL (WordPress Page Title):\n     \"Your Corporate Risk Register. Built on Microsoft 365.\"\n     \n     SEITEN-UNTERTITEL \/ Intro (erster Absatz nach dem Titel):  --><\/p>\n<p>We design, build, and maintain corporate risk registers on <a href=\"\/fr\/services\/sharepoint\/\">SharePoint<\/a> et <a href=\"\/fr\/services\/power-bi\/\">Power BI<\/a> \u2013 fully automated, ERM-aligned, and appetite-driven. From a single list to a full board-level dashboard, delivered remotely within your existing Microsoft 365 environment.<\/p>\n<p><!-- \u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n     SECTION 1: PROBLEM\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550 --><\/p>\n<h2>Most risk registers aren&#8217;t working for you.<\/h2>\n<p>Many organisations still manage risk in spreadsheets or generic SharePoint lists \u2013 disconnected from their ERM framework, hard to maintain, and impossible to report from meaningfully. The result is a register that gets filled in because it has to be, not because it helps anyone make better decisions.<\/p>\n<h3>No automated scoring<\/h3>\n<p>Probability \u00d7 impact is calculated manually, copied between sheets, and never version-controlled. When the methodology changes, someone has to update every row by hand.<\/p>\n<h3>No real-time dashboard<\/h3>\n<p>Risk appetite is invisible at board level. Reports take days to compile, are outdated before they land, and don&#8217;t show whether risks are within or out-with appetite.<\/p>\n<h3>No workflow<\/h3>\n<p>Mitigations are tracked in email threads and status meetings, not in the system where the risk lives. Overdue actions go unnoticed. Stakeholders don&#8217;t know they&#8217;re involved.<\/p>\n<p><!-- \u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n     SECTION 2: WHAT WE BUILD\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550 --><\/p>\n<h2>A risk register that actually works.<\/h2>\n<p>We build risk registers directly in your Microsoft 365 environment \u2013 no new licences, no new tools. <a href=\"\/fr\/services\/sharepoint\/\">SharePoint<\/a> as the data backbone, <a href=\"\/fr\/services\/power-bi\/\">Power BI<\/a> for reporting, <a href=\"\/fr\/services\/power-apps\/\">Power Apps<\/a> for smart forms, and <a href=\"\/fr\/services\/power-automate\/\">Power Automate<\/a> for alerts and notifications. Everything stays in your tenant.<\/p>\n<h3>SharePoint Risk Register<\/h3>\n<p>A properly structured SharePoint list with all required fields \u2013 not just a generic list with a few columns added. Typical field coverage includes:<\/p>\n<ul>\n<li>Risk type dropdown (Risk \/ Opportunity \/ Issue) with conditional response options<\/li>\n<li>Risk appetite categories aligned to your ERM framework<\/li>\n<li>Pre- and post-mitigation probability and impact scores (automatically calculated)<\/li>\n<li>Risk velocity \/ timing (how quickly the risk could materialise)<\/li>\n<li>Corporate objective alignment<\/li>\n<li>Stakeholder tagging with automated notifications<\/li>\n<li>Mitigation sub-items with control owner, target date, and status<\/li>\n<li>Lesson learned field (Issue type only)<\/li>\n<li>Financial value at risk<\/li>\n<\/ul>\n<h3>Power Apps Smart Form<\/h3>\n<p>The default SharePoint form can&#8217;t show or hide fields based on what the user selects. Our Power Apps replacement can. It adapts dynamically based on risk type \u2013 so a Risk shows Mitigate \/ Accept \/ Transfer \/ Avoid, while an Opportunity shows Exploit \/ Enhance \/ Transfer. Guided input, built-in validation, and no training needed.<\/p>\n<h3>Power BI Dashboard<\/h3>\n<p>A live, multi-page dashboard connected directly to your SharePoint risk register. Typical pages include:<\/p>\n<ul>\n<li><strong>Risk Matrix:<\/strong> heatmap of all open risks by probability and impact, colour-coded by appetite<\/li>\n<li><strong>Stats &amp; Risk Detail:<\/strong> scores, ratings, velocity, and filter by function, category, and status<\/li>\n<li><strong>Mitigation Status:<\/strong> progress by function and appetite category \u2013 Not Started \/ In Progress \/ Completed \/ Overdue<\/li>\n<li><strong>Top 10 Risks:<\/strong> filterable by rating, appetite, function, and velocity<\/li>\n<\/ul>\n<h3>Power Automate Alerts<\/h3>\n<p>Automated email notifications that remove the need for manual chasing. Included flows typically cover:<\/p>\n<ul>\n<li>Overdue mitigation alert \u2013 notifies the risk owner when a mitigation hasn&#8217;t been updated after one month<\/li>\n<li>Stakeholder assignment notification \u2013 emails the stakeholder automatically when tagged on a risk<\/li>\n<li>Status change alerts \u2013 notifies owners when a risk status changes in the register<\/li>\n<\/ul>\n<p><!-- \u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n     SECTION 3: PROCESS\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550 --><\/p>\n<h2 id=\"how-it-works\">How it works.<\/h2>\n<h3>1. Kickoff &amp; Walkthrough<\/h3>\n<p>We review your existing setup, requirements document, and open items together. Nothing gets built until scope is agreed. You get a written summary of what&#8217;s in scope, what&#8217;s out, and what we need from you before we start.<\/p>\n<h3>2. Build<\/h3>\n<p>SharePoint, Power Apps, Power Automate, and Power BI are configured directly in your Microsoft 365 tenant. We work in a staging area where available, promote to live only after your sign-off. Weekly written status updates every Friday.<\/p>\n<h3>3. UAT Management<\/h3>\n<p>We manage the full testing process \u2013 test case creation based on the agreed scope, test programme design, execution coordination, and defect tracking. Your nominated UAT contact reviews and confirms. We fix, you sign off.<\/p>\n<h3>4. Go-Live &amp; Handover<\/h3>\n<p>Data migration from your existing register, final checks, and full handover with documentation. Includes 3 months of defect remediation after go-live at no extra cost.<\/p>\n<p><!-- \u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n     SECTION 4: WHAT'S INCLUDED\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550 --><\/p>\n<h2>What&#8217;s included.<\/h2>\n<h3>Core engagement typically includes:<\/h3>\n<ul>\n<li>SharePoint list design with all required fields (typically 30\u201340 field-level configurations)<\/li>\n<li>Power Apps custom form replacing the standard SharePoint form<\/li>\n<li>Conditional logic: dynamic dropdowns, field visibility, type-dependent response options<\/li>\n<li>Pre- and post-mitigation scoring (automatic calculation: probability \u00d7 impact)<\/li>\n<li>Risk appetite representation \u2013 automated within \/ out-with appetite indicator<\/li>\n<li>Power Automate flows: overdue mitigation alerts, stakeholder notifications<\/li>\n<li>Power BI dashboard (typically 3\u20135 pages: heatmap, stats, mitigation status, Top 10)<\/li>\n<li>Full UAT management: test cases, execution, defect resolution<\/li>\n<li>Data migration from existing register<\/li>\n<li>3 months defect remediation after go-live<\/li>\n<\/ul>\n<h3>Available as optional add-ons:<\/h3>\n<ul>\n<li>End-user training sessions and training materials<\/li>\n<li><a href=\"\/fr\/services\/erm-consulting\/\">ERM framework consulting<\/a> \u2013 risk appetite definition, category design, scoring methodology<\/li>\n<li>Ongoing maintenance retainer after the warranty period<\/li>\n<\/ul>\n<p><!-- \u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n     SECTION 5: PRICING\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550 --><\/p>\n<h2>Transparent pricing.<\/h2>\n<p>We work on a Time &amp; Material basis. You pay for days actually worked at a fixed day rate \u2013 no fixed-price guesswork, no hidden costs. If it takes fewer days than estimated, you pay less.<\/p>\n<ul>\n<li><strong>Day rate:<\/strong> from \u20ac800\/day (net)<\/li>\n<li><strong>Typical engagement:<\/strong> 10\u201315 man-days<\/li>\n<li><strong>Typical budget:<\/strong> \u20ac7.500\u2013\u20ac11.250 (net)<\/li>\n<li><strong>Delivery:<\/strong> 100% remote<\/li>\n<li><strong>Invoicing:<\/strong> after agreed milestones (typically 2 invoices)<\/li>\n<\/ul>\n<p>Preferential rates available for existing clients and multi-year engagements.<\/p>\n<p><!-- \u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n     SECTION 6: SOCIAL PROOF\n     \u2192 Use theme's Testimonial widget section\n     OR paste as blockquotes\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550 --><\/p>\n<h2>Trusted by risk teams across Europe.<\/h2>\n<blockquote>\n<p>LeapLytics built and maintains our corporate risk register on SharePoint and Power BI. The setup covers 37 field-level configurations, a custom Power Apps form, automated alerts, and a full Power BI dashboard \u2013 all within our Microsoft 365 environment. Exactly what we needed.<\/p>\n<p>  <cite>\u2014 Risk &amp; Compliance Team, Transportation, Germany<\/cite>\n<\/p><\/blockquote>\n<blockquote>\n<p>Excellent tool to visualise the full risk portfolio.<\/p>\n<p>  <cite>\u2014 Rail Baltica<\/cite>\n<\/p><\/blockquote>\n<blockquote>\n<p>Convinces us across the board.<\/p>\n<p>  <cite>\u2014 VELUX Commercial<\/cite>\n<\/p><\/blockquote>\n<p><!-- \u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n     SECTION 7: WHY LEAPLYTICS\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550 --><\/p>\n<h2>Why LeapLytics?<\/h2>\n<h3>Microsoft 365 specialists<\/h3>\n<p>We work exclusively within your existing M365 environment. No new tools, no new licences, no data leaving your tenant. Everything we build is yours and stays in your environment after handover.<\/p>\n<h3>We own the Risk Matrix visual<\/h3>\n<p>Our AppSource-certified Risk Matrix visual powers the heatmap in your Power BI dashboard. It&#8217;s used by risk teams across Europe \u2013 including Rail Baltica and Velux \u2013 and is available separately on Microsoft AppSource. When we build your dashboard, we bring platform-level expertise that goes beyond standard report development.<\/p>\n<h3>ERM experience, not just IT<\/h3>\n<p>We understand risk appetite, ERM frameworks, ISO 31000, and risk scoring methodology \u2013 not just how to configure SharePoint. That means the system we build reflects how your organisation actually thinks about risk, not just what the tool can do out of the box.<\/p>\n<p><!-- \u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n     SECTION 8: FAQ\n     \u2192 Use theme's FAQ widget section\n     OR Yoast\/RankMath FAQ block (for FAQPage schema)\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550 --><\/p>\n<h2>Frequently asked questions.<\/h2>\n<h3>Do we need additional Microsoft licences?<\/h3>\n<p>No. Power Apps (standard SharePoint connector) and Power Automate are included in most Microsoft 365 plans including Business Standard, E3, and E5. No additional licences are required for a standard risk register engagement. We confirm your licence entitlement before starting.<\/p>\n<h3>Can you work with our existing SharePoint setup?<\/h3>\n<p>Yes. We work directly within your existing Microsoft 365 tenant and adapt to your current environment. We assess your setup during the kickoff and design the solution around what you already have.<\/p>\n<h3>How long does it take?<\/h3>\n<p>A typical risk register engagement runs 6\u20138 weeks end to end, covering build, UAT, data migration, and go-live. Timelines depend on scope, feedback cycles, and how quickly access can be provisioned.<\/p>\n<h3>Do you work on-site?<\/h3>\n<p>All work is delivered remotely as standard from Germany. On-site visits can be arranged by mutual agreement \u2013 for example for kickoff, UAT, or go-live. Travel costs are invoiced at cost with prior written approval.<\/p>\n<h3>What happens if requirements change mid-project?<\/h3>\n<p>Any changes beyond the agreed scope are handled via a formal change request process \u2013 assessed for timeline and cost impact, and agreed in writing before any additional work begins. Nothing is added to scope without your sign-off.<\/p>\n<h3>What if we don&#8217;t have an ERM framework yet?<\/h3>\n<p>We can help with that too. Our <a href=\"\/fr\/services\/erm-consulting\/\">ERM Consulting<\/a> service covers risk appetite definition, category design, and scoring methodology \u2013 and we implement it directly into the register as part of the same engagement.<\/p>\n<p><!-- \u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n     SECTION 9: CTA\n     \u2192 Use theme's CTA widget section\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550 --><\/p>\n<h2>Ready to build your risk register?<\/h2>\n<p>Tell us about your current setup and what you&#8217;re trying to achieve. We&#8217;ll come back with an indicative scope and estimate within 24 hours \u2013 no commitment required.<\/p>\n<p><a href=\"\/fr\/contact\/\" class=\"btn-readmore\">Get in touch<\/a><\/p>\n<p>Or email us directly at <a href=\"\/fr\/&\/#x6d;&#x61;&#x69;&#x6c;&#x74;&#x6f;&#x3a;&#x69;&#x6e;&#x66;&#x6f;&#x40;&#x6c;&#x65;&#x61;&#x70;&#x6c;&#x79;&#x74;&#x69;&#x63;&#x73;&#x2e;&#x64;&#x65;\">info@leaplytics.de<\/a><\/p>\n<hr>\n<p><strong>Related services:<\/strong> <a href=\"\/fr\/services\/sharepoint\/\">SharePoint Development<\/a> &middot; <a href=\"\/fr\/services\/power-apps\/\">Power Apps<\/a> &middot; <a href=\"\/fr\/services\/power-automate\/\">Power Automate<\/a> &middot; <a href=\"\/fr\/services\/power-bi\/\">Power BI Consulting<\/a> &middot; <a href=\"\/fr\/services\/erm-consulting\/\">ERM Consulting<\/a><\/p>","protected":false},"excerpt":{"rendered":"<p>We design, build, and maintain corporate risk registers on SharePoint and Power BI \u2013 fully automated, ERM-aligned, and appetite-driven. From a single list to a full board-level dashboard, delivered remotely within your existing Microsoft 365 environment. Most risk registers aren&#8217;t working for you. Many organisations still manage risk in spreadsheets or generic SharePoint lists \u2013 &hellip; <\/p>","protected":false},"author":2,"featured_media":0,"parent":14654,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-14640","page","type-page","status-publish","hentry","latest_post"],"_links":{"self":[{"href":"https:\/\/www.leaplytics.de\/fr\/wp-json\/wp\/v2\/pages\/14640","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.leaplytics.de\/fr\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.leaplytics.de\/fr\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.leaplytics.de\/fr\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.leaplytics.de\/fr\/wp-json\/wp\/v2\/comments?post=14640"}],"version-history":[{"count":9,"href":"https:\/\/www.leaplytics.de\/fr\/wp-json\/wp\/v2\/pages\/14640\/revisions"}],"predecessor-version":[{"id":14680,"href":"https:\/\/www.leaplytics.de\/fr\/wp-json\/wp\/v2\/pages\/14640\/revisions\/14680"}],"up":[{"embeddable":true,"href":"https:\/\/www.leaplytics.de\/fr\/wp-json\/wp\/v2\/pages\/14654"}],"wp:attachment":[{"href":"https:\/\/www.leaplytics.de\/fr\/wp-json\/wp\/v2\/media?parent=14640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}