Define the technology service and customer promise
Describe the software, platform, data, implementation, support, or consulting service provided. Identify customers, revenue by service, contracts, acceptance procedures, and any service-level commitments.
Show dependencies and failure controls
Explain third-party software and infrastructure, change management, quality assurance, backups, access controls, customer data, incident response, and prior service problems. Note where contracts limit or expand responsibility.
Technology questions to resolve before submission
- What service or deliverable does each customer contract promise?
- Which vendor, platform, data, or infrastructure dependencies could interrupt that promise?
- How are changes, errors, security incidents, and customer complaints identified and corrected?
What CARMA wants the submission to explain
These details help the team understand the account and identify the next useful question. They do not establish eligibility or available terms.
- Describe the software, platforms, integrations, data, implementation, support, and service commitments provided.
- Explain customer contracts, acceptance, change control, security responsibilities, backups, and incident response.
- Identify outages, errors, allegations, dependency failures, and technology services used by regulated businesses.
Records for a technology E&O review
- Service descriptions, customer types, revenue breakdown, and sample contracts
- Software and vendor dependencies, quality controls, security practices, and incident procedures
- Prior errors, customer disputes, cyber events, and current E&O or cyber coverage
Can CARMA consider this account?
CARMA confirms program fit, licensing, state availability, coverage options, and market interest for each account. This guide does not promise eligibility, terms, pricing, or placement.