Telynt by Effority
Telynt by Effority

Explore Telynt

Telynt / Documentation

Search documentation

Search platform contracts, developer guides, package manuals and the Technology Consulting & Delivery solution.

Browse documentation
Docs/Packages/BND-SCOPE

Scope, Contract, SOW, and Acceptance Alignment

Project Execution — Scope Changes

Packages2 min readDownload Markdown ↓
On this page

Navigation: Intelligence → Project Execution → Scope Changes
Primary audience: project managers, delivery leaders, commercial owners, contract owners, and customer sponsors with appropriate access

Purpose

Scope Changes manages requests, statements, and discoveries that may alter agreed deliverables, timing, cost, resources, responsibilities, or acceptance. It separates possible changes from formal change requests and shows commercial and delivery exposure while approval is incomplete.

Scope controls and indicators

Period filters detection or lifecycle date. Project narrows context. Approval State selects possible, formalizing, under review, approved, rejected, withdrawn, or implemented. Impact filters cost, schedule, resource, deliverable, contractual, or materiality bands.

Possible Changes need clarification. Under Review have an active approval route. Approved are formally authorized in the selected period. Uncontrolled Exposure estimates supported impact for changes being acted on without sufficient formalization.

Scope-change pipeline

The pipeline groups items from Detected through Formalizing, Approval, and Approved. Each card shows project, change statement, impact, value, schedule effect, evidence, owner, and current control gap.

Baseline versus requested

The comparison displays current baseline and requested state for deliverables, sources, features, quality, schedule, cost, and resources. Differences are linked to SOW clauses, proposal sections, project plan, meeting evidence, and other authoritative sources.

Approval route and supporting analysis

The approval route shows project, commercial, customer, legal, or other required authorities and their current decisions. Potential impact summarizes supported cost, schedule, resource, and deliverable effects. Source of change groups customer request, discovery, regulation, internal proposal, or other origins. Change controls identifies missing formalization, duplicate requests, and approvals due.

Actions

  • Create change request starts a governed draft from selected evidence.
  • Formalize a possible change.
  • Compare baseline and requested state.
  • Request approval or record a decision.
  • Reject, withdraw, merge, or identify a duplicate with rationale.
  • Link opportunity value, risks, actions, and acceptance conditions.

Validate the current baseline first. Quantify impact and record affected obligations before requesting approval. Do not treat a conversational request as approved scope. Ensure project and commercial records are updated only after the required authority has decided.

Acceptances, Meeting Files & Versions, Decisions & Commitments, and Commercial Opportunities.