The submission goes to the regulator with your name on it. It has to hold.
Quality-of-service returns, spectrum compliance, coverage obligations — the operator's periodic submission to the Communications Authority, ICASA, or the NCC is an account the regulator relies on. When a single figure in it cannot be traced to source, the problem is no longer that report. It is the regulator's confidence in everything you file.
Regulatory reporting is dense, recurring, and consequential. An operator files quality-of-service data, coverage and rollout performance against licence obligations, spectrum usage, and interconnection metrics, on schedules set by the regulator. ICASA's call termination regulations require the major operators to publish reference interconnection offers and report against them; the Communications Authority of Kenya and Nigeria's NCC run their own quality-of-service regimes. These are not internal management reports. They are the basis on which a regulator decides whether an operator is meeting the terms of its licence.
The figures are assembled from across the estate — the OSS for network performance, the BSS for customer and billing data, the mediation layer for traffic — and that is where the exposure lives. A quality-of-service number in a submission has travelled through several systems and several stages of processing before it reaches the return. When the regulator queries it months later, the operator has to be able to walk it back to source. If it cannot, the figure is not just wrong; it is unaccountable, and an unaccountable figure casts doubt on the rest of the filing.
The pressure to automate this is intense and rational. Assembling regulatory returns by hand is slow and error-prone, and the volume only grows as regulators ask for more granular data more often. The instinct is to let a system pull the numbers and draft the narrative. The hazard is specific to this context: a regulatory submission is closer to a sworn statement than to a marketing report, and a figure that a model produced but that nobody can substantiate is a serious matter if it later proves wrong. Automation that cannot show its sourcing transfers risk to the signature at the bottom of the return.
There is a second-order risk that operators learn the hard way. A regulator that catches one unsubstantiated figure does not treat it as an isolated error; it revises its confidence in the operator's reporting generally, and that colours every subsequent interaction — licence renewals, spectrum allocations, enforcement decisions. The cost of a single indefensible number is rarely contained to the number itself. The asset an operator is protecting in its reporting is, ultimately, the regulator's trust.
The reporting workflow that survives, then, is not the fastest one. It is the one where every figure in the return is traceable to its source, the narrative is grounded in those figures, and the system declines to state a metric it cannot evidence — leaving a gap to be filled by a human who knows the answer rather than a number that merely looks complete.
The cadence of reporting makes the discipline harder to sustain than a one-off filing would be. Returns recur monthly and quarterly, assembled under deadline by teams that rotate, and the institutional memory of how a particular figure was derived erodes between cycles. A process that depends on the person who built last quarter's return remembering their own working is one that will eventually produce a number nobody can substantiate. The audit trail under each submission is not bureaucratic overhead; it is the only thing that lets the operator answer a query about a return filed months earlier by someone who has since moved on.
Spectrum reporting is the sharpest version of the problem, because the asset is scarce and the obligations are concrete. A spectrum licence carries coverage and rollout commitments, and the operator reports performance against them; as regulators liberalise bands such as E-band for high-capacity microwave backhaul, the obligations attached to new allocations grow alongside them. A coverage figure that overstates rollout, or a spectrum-usage return that cannot be substantiated, is not a soft compliance matter — it bears on the operator's claim to a national resource, and on whether it keeps or loses that allocation at renewal. The figure and the asset are the same conversation.
A regulator that catches one indefensible figure does not revise the figure. It revises its confidence in everything you file.
Where each sits.
Akki governs the source systems that feed the return — the OSS, BSS, and mediation layers — and preserves the lineage of each figure as it moves from raw data to reported metric. When the regulator queries a number, the walk-back to source is a query, not a forensic exercise. The operator can show how the figure was derived, not merely that it was reported.
This is the workflow Solva is built to govern. It drafts the submission with every figure traceable to its source, structures the supporting narrative through its five stages, and refuses to state a metric it cannot evidence. Where a number cannot be substantiated from the underlying systems, Solva surfaces the gap rather than filling it — which is precisely the behaviour that protects the signature on the return. The refusal is not a limitation; it is the control.
Where a return requires subscriber-level data — and some quality-of-service and complaints reporting brushes against it — SyniSense keeps identifiable detail inside the perimeter, reporting the aggregate the regulator needs without exposing the individuals behind it. In purely network-metric reporting its role is light; in subscriber-touching returns it keeps the filing compliant with the data-protection regime that sits alongside the telecoms one.
For the regulatory affairs function, the return is defensible by construction. Every figure carries its lineage, so a query from the regulator is answered by showing the derivation rather than launching an internal investigation to reconstruct it. The person who signs the submission is signing something they can stand behind.
For the operator's standing with the regulator, the reporting becomes an asset rather than a recurring risk. Consistent, traceable, substantiated returns build the confidence that smooths every other interaction — and that confidence, once earned, is worth more than any single favourable number.
For the teams that own the source data, the discipline runs upstream. Because the submission refuses to state what it cannot evidence, the gaps become visible early, in the data, rather than late, in a regulator's query. The reporting process surfaces the operator's own data-quality problems before the regulator does.
For the board, the reporting risk that sits quietly on most operators' registers — the indefensible figure waiting to be queried — is materially reduced. A reporting process that declines to assert what it cannot prove is the governance the audit committee has been asking the function to demonstrate.
For spectrum and licensing specifically, the operator protects its hold on the resource. A reporting record that traces to source is the operator's defence when a coverage or rollout obligation is questioned at renewal or in an enforcement review — the moment when an indefensible historical figure becomes most expensive, because the asset itself is on the table.