diff --git a/.github/workflows/test-coverage.yaml b/.github/workflows/test-coverage.yaml
index 89c9612..fefc52e 100644
--- a/.github/workflows/test-coverage.yaml
+++ b/.github/workflows/test-coverage.yaml
@@ -8,6 +8,8 @@ on:
 
 name: test-coverage
 
+permissions: read-all
+
 jobs:
   test-coverage:
     runs-on: ubuntu-latest
@@ -23,18 +25,27 @@ jobs:
 
       - uses: r-lib/actions/setup-r-dependencies@v2
         with:
-          extra-packages: any::covr
+          extra-packages: any::covr, any::xml2
           needs: coverage
 
       - name: Test coverage
         run: |
-          covr::codecov(
+          cov <- covr::package_coverage(
             quiet = FALSE,
             clean = FALSE,
             install_path = file.path(normalizePath(Sys.getenv("RUNNER_TEMP"), winslash = "/"), "package")
           )
+          covr::to_cobertura(cov)
         shell: Rscript {0}
 
+      - uses: codecov/codecov-action@v4
+        with:
+          fail_ci_if_error: ${{ github.event_name != 'pull_request' && true || false }}
+          file: ./cobertura.xml
+          plugin: noop
+          disable_search: true
+          token: ${{ secrets.CODECOV_TOKEN }}
+
       - name: Show testthat output
         if: always()
         run: |
@@ -48,4 +59,3 @@ jobs:
         with:
           name: coverage-test-failures
           path: ${{ runner.temp }}/package
-
diff --git a/inst/rmarkdown/templates/scenario-report/skeleton/skeleton.Rmd b/inst/rmarkdown/templates/scenario-report/skeleton/skeleton.Rmd
index c76fbd8..a8a2112 100644
--- a/inst/rmarkdown/templates/scenario-report/skeleton/skeleton.Rmd
+++ b/inst/rmarkdown/templates/scenario-report/skeleton/skeleton.Rmd
@@ -119,13 +119,4 @@ tbls <- split(
 
 There are limitations with this approach and it is recommended to use this information in combination with other information sources. The main limitation is the availability of data combined with the data driven approach. There may not be related, publicly available information for a performance metric. The model may, therefore, end up either selecting other unrelated metrics to determine its prediction, or even base the prediction largely on the previous value for that performance metric.
 
-## Input scenario data
-
-The table below contains the inputs used to create the charts above.
-
-```{r}
-#| label: data-tables
-
-print(names(params$scenario_data))
-```