SECAP management platform for municipalities
The SECAP Management Platform manages the municipal emission inventory, risk and vulnerability assessment, energy poverty indicators, targets and actions inside one tenant boundary. Every result traces back to its source data version, evidence, method and approval.
It does not submit to MyCovenant automatically; it produces a package ready for manual upload. Official acceptance belongs to the Covenant of Mayors process.
Recent activity
The municipal profile, plan cycle, roles and users are defined; all working data is bound to the municipality and the plan cycle.
Requests go to departments and data owners; Excel/CSV files and evidence are uploaded, graded for quality and technically reviewed.
The BEI calculation runs on the server with versioned factors; once through technical review and approval, the result is locked and carried into the report package.
Features
From the first data request to the final report package, every step runs in one application under one evidence and approval discipline.
Each data item moves from request to lock through explicit states; files pass a quarantine scan, and an A–E quality grade and source trail stay on the record.
grade A · scan clean · public-buildings-electricity-2024.xlsx
Compliance findings are raised and closed before the final SECAP; no final package is produced until the council decision gate is passed.
Workspaces bound to the same plan cycle:
Each role sees only what its work needs; backend authorization and database row-level security apply together.
Sign-ins, data changes, approvals and locks are recorded with actor, time and reason.
The pilot SECAP draft and the final report are produced in Turkish and English from the same locked snapshot.
Each municipality’s data lives in its own tenant, protected by backend authorization and PostgreSQL row-level security.
Every user signs in with e-mail, password and a second factor; the workspace stays closed until it is enrolled.
Calculations run deterministically on the server with versioned factors; a locked result is never edited in place.
The interface and the per-language narrative fields offer the same functional scope in both languages.
Neighbourhood and risk layers are processed with PostGIS; externally prepared maps are linked with their source trail.
Energy poverty surveys run without directly collecting identity, and their results feed the indicators.
Answer an audit question without hunting for files: the value, source data version, factor used, evidence and approver sit on the same trail.
Benefits
The goal is not another dashboard; it is less data-collection effort, figures tied to evidence and a plan process that can be audited.
Data is collected in one workspace instead of scattered files; who uploaded which version, and when, is always clear.
Which department owes which data, what is late and what needs correcting is visible on screen.
Inventory results trace back to the underlying document, factor and approver.
The same method and versioned factors give reproducible results in every monitoring period.
Missing sections and open findings against the guidebook sit in one list before the final report.
Even when the team changes, data, evidence and decision history stay with the municipality.
Modules
Every module uses the same evidence, technical review, approval and lock flow; monitoring and assurance draw on the same records.
01 · BEI inventory
Consumption and emissions by sector and energy carrier are calculated with versioned factors and locked after technical review.
Reporting
Request status, quality grade and review outcome per data item in one table. Close the items that need correction before the deadline.
| Unit | Data item | Status |
|---|---|---|
| Public Works Department | Public building electricity2024 | Locked |
| Support Services Department | Municipal fleet fuel2024 | Approved |
| Natural gas distributor | Residential natural gas use2024 | Correction requested |
| Transport Planning Department | Public transport fuel2024 | In technical review |
| Electricity distributor | Street lighting2024 | Requested |
| Climate Change Department | Waste disposal volume2024 | Correction requested |
No records in this status.
States are shown in text as well as colour; unit names and values are synthetic.
FAQ
If your question isn’t here, let’s look at it together in a demo call.
Yes. All working data is scoped to the municipality (tenant), and plan data is further bound to the plan cycle. Separation is enforced by backend authorization together with PostgreSQL row-level security.
Users do not enter results. Calculations run deterministically on the server with versioned methods and factors; a locked result is never edited in place but superseded by a new version.
No. Without a verified official API contract, the platform produces a MyCovenant package ready for manual upload.
Besides e-mail and password, a second factor is mandatory for every user; the workspace cannot be reached until it is enrolled.
No. The platform does not invent evidence, factors, regulations or calculation results; every decision is made by an authorised user through the approval chain.
Yes. The interface is in Turkish and English, and report narrative fields are kept separately in both languages.
Contact
Let’s talk about your SECAP preparation and priorities; setup, users and module scope are configured to your needs.