Municipality or public body
Use the same evidence provenance and accountable decision record with proportionate stakeholder, transparency and assurance requirements.
Enterprise readiness
Enterprise-grade where it matters. Proportionate where it should be.
Technology decisions vary in scale. The standard of evidence should not.
1.Define
2.Evidence
3.Compare
4.Decide
5.Prove
PROVE TDI uses one evidence and accountability standard across organisations, while scaling controls, assurance and governance to the actual decision. Enterprise procurement can validate the exact environment and engagement without turning every smaller decision into an enterprise programme.
Requirements→Evidence→Compare→Approve→Outcome
One decision standard
Built to scale from local public-sector decisions to multinational programmes.
Organisation size does not determine decision quality or commercial treatment. PROVE TDI classifies the decision by complexity, evidence requirements, governance and cost of error, then applies proportionate assurance without changing the underlying provenance, contradiction and accountability model.
Mid-market organisation
Start with a bounded decision and scale assurance only where complexity, evidence gaps or cost of error justify it.
Multinational enterprise
Extend the same decision model across business units, countries, architecture dependencies, layered approvals and repeat decision programmes.
Readiness register
Current public position
This is a disclosure boundary, not a certification statement. Evidence supplied for an enterprise review should be checked for currency, environment and scope.
Available
Tenant-aware application controls
Organisation boundaries, scoped roles and controlled actions are part of the application design. Exact controls still require validation for the proposed customer scope.
Available
Evidence and decision auditability
Sources, gaps, confidence, approval state and decision history remain distinct in the governed workflow.
Scope-dependent
Data processing and retention
Data categories, controller and processor roles, subprocessors, transfers, retention and deletion must be agreed before customer data is accepted.
Scope-dependent
Identity and access integration
SSO, provisioning, enterprise identity requirements and privileged administration are evaluated against the requested deployment rather than implied by the public site.
Not claimed
ISO 27001 or SOC 2 certification
PROVE TDI does not currently publish a claim that either certification is held.
Contract-required
Production service commitments
Service levels, support, recovery objectives, liability, governing law and data residency require signed scope-specific terms.
Procurement questions
Resolve these before customer data enters the service.
- Which legal entity contracts and in which jurisdiction?
- Which data categories, regions and subprocessors are in scope?
- What identity, tenant and privileged-access controls are required?
- What retention, deletion and export obligations apply?
- What service, recovery and incident commitments are required?
- Which assurance evidence is current for the production environment?