Asset register · Policy schedule · Reconciliation
Everything you own. Everything you’ve declared.The difference is uninsured.
AssetCoverIntel holds both sides of the record and reconciles them — asset by asset, valuation by valuation — so the gap between your portfolio and your policy is a number you manage, not one you discover at claim time.
Every finding traces to one of these
Four deterministic rules, not model outputs.
Every finding names the rule that raised it, the records it compared and the method version in force at the time. Run it twice against the same data and you get the same answer.
POL-001
Potentially uninsured asset
An asset sits in the register with a declared value, and no matching item exists on the policy schedule for the period covering it.
Raises · Critical · Blocks renewal sign-off
VAL-002
Declared value shortfall
The declared value is compared against the last valuation indexed forward to today, not the raw valuation. Stale valuations surface as shortfall, which is what they are.
Raises · Critical above 10% · Method v2.2
BI-001
Indemnity period below recovery estimate
The indemnity period on the policy is tested against the longest reinstatement path through the site’s dependency chain, including single-supplier plant.
Raises · Critical · Evidence: dependency graph
VAL-004
Stale formal valuation
The last formal valuation for an asset is older than the policy allows, so the declared value rests on indexation alone rather than on anyone having looked at it.
Raises · High · Evidence: valuation record
Declared value against indexed valuation
The gap opens quietly, and closes only at renewal.
Declared values step. They move on the day you declare them and not before. Indexed valuations rise continuously, every day, whether anyone is looking or not. Between the two surfaces an uninsured band opens across the whole portfolio and collapses only when you declare again — 56 sites, four renewal cycles, one sawtooth.
Declared value steps at each renewal while indexed valuation rises continuously; the band between them is uninsured exposure, widest immediately before renewal.
- Declared value · steps at renewal
- Indexed valuation · continuous
- Uninsured band · widest before renewal
Twelve surfaces over one spine
One record, read three ways.
Position is what you hold today. Assurance is whether the record can be trusted. Events are what changes it. Every screen reads the same reconciled spine.
Position
What you hold, and what you’ve told the insurer you hold- Command CentreCoverage, exceptions and value at risk across the portfolio
- Portfolio MapGeographic exposure, concentration and hazard overlays
- Asset RegisterEvery insured asset with its valuation and declaration history
- Policy Digital TwinThe schedule as structured data: limits, sub-limits, deductibles
Assurance
Whether the record holds up under examination- ReconciliationRegister against schedule, line by line, with a decision on each break
- Valuation AssuranceValuation age, method and indexation confidence by site
- Business InterruptionDependency chains tested against declared indemnity periods
- Risk EngineeringRecommendation register through its eight-stage closure lifecycle
Events
What changes the record, and what the record has to prove- Material ChangesDetection through to insurer notification, with the clock visible
- Renewal ReadinessDeclaration completeness and attestation status ahead of submission
- Claims ReadinessEvidence completeness per site before an incident, not after
- ExceptionsEvery open finding, its owner, its age and its next action
Control posture
Built to be audited, not just used.
This record carries declared values, valuations and claims evidence. It is designed so that an internal auditor, a broker or an insurer can trace any number back to its source.
- AccessRow-level security on every schema. Organisation context is derived from the signed-in session, never from a request parameter.
- IdentityEmail and password with mandatory TOTP for every account. No self-serve signup — access is granted, not requested.
- HistorySelective bitemporality across valuations, declarations and findings. You can reconstruct what was known and declared on any past date.
- AuditAppend-only log of every state transition, with the actor, the role that permitted it and the prior value retained.
- Write pathsFindings move state through hardened database functions with role and terminal-state guards. The application cannot write around them.
- ResidencyPostgres in ap-southeast-2, Sydney. Scheduling is external; every rule evaluation runs inside the application boundary.
The gap is already there. The only question is whether you can see it.
Access is provisioned per organisation. Sign in to open your Command Centre.