| Incident intake, routing and escalation | Documented by vendor | The incident product documents customizable intake, severity or impact-based workflow, notifications, escalation and response playbooks. Buyers must configure fields, thresholds, ownership and response rules for their own governance model. Enterprise incident workflows |
|---|
| Root-cause and corrective-action tracking | Documented by vendor | Onspring documents root-cause analysis, resolution steps, closure verification and incident trend reporting. This is a configurable enterprise incident workflow, not proof of a prebuilt regulatory safety-investigation method. Enterprise incident workflows |
|---|
| Risk register and mitigation management | Documented by vendor | The risk product documents centralized and hierarchical registers, assessments, causes and interdependencies, mitigation measures, controls, barriers, acceptance, KRIs and overdue-action notifications. Scoring and approvals must be configured to the buyer's method. Risk assessment and register |
|---|
| Internal-audit planning and workpapers | Documented by vendor | The audit product documents audit-universe planning, resource and budget tracking, workpapers, multi-level sign-off, findings and report issuance. Validate methodology, templates and retained change history with a sample audit. Internal audit workflow |
|---|
| Audit evidence and external collaboration | Depends on scope | Onspring documents surveys, evidence requests and secure external-auditor portal access. Confirm Portal/product entitlement, external-user licensing, upload controls and record-level permissions. Internal audit workflowPortal and external collaboration |
|---|
| No-code data model and task automation | Documented by vendor | The platform documents data references, formulas, tasks, shared lists and multi-record creation. No-code reduces coding dependency but still requires design ownership, change control, testing and administrator capacity. No-code platform feature overview |
|---|
| Rules-based workflows and approvals | Documented by vendor | Visual workflows can route internal or external assessments, tasks, notifications and approvals using conditions. Public versus private visibility and email, SMS or Slack actions must be tested against least-privilege requirements. Rules-based dynamic workflows |
|---|
| Surveys and attestations | Documented by vendor | The platform overview documents scheduled or ad hoc assessments, attestations and compliance questionnaires. Confirm participant licensing, authentication, reminders, evidence requirements and reopening rules. No-code platform feature overview |
|---|
| Dashboards, reports and document exports | Documented by vendor | Onspring documents role-oriented dashboards, live drill-down reports and Word or PDF output. 'Real-time' depends on the configured data inputs and does not establish safety-critical monitoring or an immutable regulatory report. No-code platform feature overviewReal-time reporting and exports |
|---|
| Automated messages, alerts and scheduled reports | Depends on scope | Business rules can trigger notifications and scheduled reports; the workflow and overview pages name email, SMS and Slack channels. SMS allowances vary by platform level and channel delivery, escalation and failure handling require validation. Automated messages, alerts and reportsCommercial licensing and platform tiersRules-based dynamic workflowsNo-code platform feature overview |
|---|
| Integrations and API | Depends on scope | Onspring lists native integrations and provides API-planning material. Some data connectors require third-party subscriptions; confirm API allowance, authentication, supported direction, error handling and maintenance for each interface. Integrations and API planningCommercial licensing and platform tiers |
|---|
| Data consolidation and relationships | Documented by vendor | The platform documents importing data, relating records to workflows, reports or people, and aggregating them into dashboards. Source ownership, matching, refresh, duplicate and reconciliation controls remain implementation responsibilities. Data import, relationships and consolidation |
|---|