Decisions, Commitments, Actions, and Follow-Up

Decisions, commitments, acceptances, actions, questions, follow-up, and approved synchronization drafts. This package has its own data model, workflows and interface contributions. Its documentation applies wherever the package is installed, not only to one industry solution.

Overview

Package: BND-WORK · Type: Business capability · Documentation: 1.0

Marketplace listing · Technical reference

A rollback of software does not undo an email or an external write. Such effects need explicit compensation or remediation.

User guide

1. Review extracted decisions, commitments, open questions and proposed actions against their source.
2. Resolve missing owners and dates; distinguish a proposal, acknowledgement and confirmed commitment.
3. Track completion evidence and approve any external-system draft before synchronization.

Screens owned by this package

• Meeting — Decisions & Actions — SCR-MTG-04.
• Actions — SCR-WRK-01.
• Decisions & Commitments — SCR-WRK-02.

Contributions to other screens

• My Development — Recommendations — owned by BND-DEVELOPMENT; this package contributes analysis or interface content.
• My Development — Today — owned by BND-DEVELOPMENT; this package contributes analysis or interface content.
• My Development — Progress — owned by BND-DEVELOPMENT; this package contributes analysis or interface content.
• Overview — owned by BND-OVERVIEW; this package contributes analysis or interface content.
• Meeting — Overview — owned by BND-MEETING; this package contributes analysis or interface content.
• Meeting — Activity — owned by BND-EVIDENCE; this package contributes analysis or interface content.
• Findings — Resolved — owned by BND-FINDINGS; this package contributes analysis or interface content.
• Commercial Intelligence — Overview — owned by BND-COMMERCIAL; this package contributes analysis or interface content.
• Commercial Intelligence — Opportunities — owned by BND-COMMERCIAL; this package contributes analysis or interface content.
• Commercial Intelligence — Objections — owned by BND-COMMERCIAL; this package contributes analysis or interface content.
• Commercial Intelligence — Forecast — owned by BND-COMMERCIAL; this package contributes analysis or interface content.
• Project Execution — Portfolio — owned by BND-PROJECT; this package contributes analysis or interface content.
• Project Execution — Risks & Issues — owned by BND-PROJECT; this package contributes analysis or interface content.
• Project Execution — Dependencies — owned by BND-PROJECT; this package contributes analysis or interface content.
• Project Execution — Scope Changes — owned by BND-SCOPE; this package contributes analysis or interface content.
• Project Execution — Acceptances — owned by BND-SCOPE; this package contributes analysis or interface content.
• Relationship & Trust — Overview — owned by BND-RELATIONSHIP; this package contributes analysis or interface content.
• Relationship & Trust — Corrective Actions — owned by BND-RELATIONSHIP; this package contributes analysis or interface content.

Configuration

Configuration changes are versioned overlays. Preview the changed permissions, schemas, workflow bindings and interface contributions in Development; qualify them in Testing and Staging before authorized Production promotion. A business administrator configures permitted solution settings; platform deployment authority is separate.

Technical reference

The implementation reference identifies DM-WORK, WFP-WORK-LIFECYCLE, 4 owned agents, interface contributions, policies and evaluation profiles. Shared platform services execute these definitions; they do not hard-code this package's business meaning.

Compatibility and dependencies

• Meeting and Conversation Intelligence — BND-MEETING.
• Finding Lifecycle, Evidence Assurance, and Review — BND-FINDINGS.

Direct consumers: Commercial Intelligence, Project and Portfolio Execution, Scope, Contract, SOW, and Acceptance Alignment, Relationship and Trust Intelligence, Internal Team Intelligence and Personal Development, Engineering, Architecture, and Cross-Object Impact, Role-Aware and Executive Overview.

Dependencies declare compatible ranges; the installation resolver records exact signed versions and digests in the environment lock. This documentation's version is not an installed-package version. Before updating or removing the package, inspect dependent workflows, records, interface slots and retained artifacts. Never delete referenced evidence or silently remove a required capability.

Extensions and enrichment

Add workflow steps, task-system adapters and external draft types. Idempotency, approval and compensation remain mandatory for external effects.

Extensions declare their own package identity, dependencies, provided capabilities and evaluation evidence. They preserve the publisher's original package and are qualified with the complete resolved composition. See the developer extension guide.

Versions and upgrades

The documentation describes the current 1.x solution composition and the package's declared capabilities. The exact installed package, model, prompt and schema versions are shown in the environment lock and run provenance; no historical release sequence is implied.

1. Compare release manifests, permission changes and migrations against the current lock.
2. Test package behavior and affected dependent workflows with representative, authorized evidence.
3. Promote the signed release after approval and record the resulting lock.
4. Roll back only when schema/data compatibility and retained artifacts permit it. Irreversible migrations require a tested recovery or forward-fix plan; completed external actions require compensation, not a software rollback.

Used in solutions

Technology Consulting & Delivery includes this package as mandatory. That activation rule belongs to this solution; it does not make every business capability mandatory for every Telynt deployment.