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-EVIDENCE

Sources, Integrations, and Evidence Foundation

Meeting — Files & Versions

Packages2 min readDownload Markdown ↓
On this page

Navigation: Home → Meetings → select a meeting → Files & Versions
Primary audience: meeting users who can access referenced media, documents, and source versions

Purpose

Files & Versions identifies the files used, mentioned, created, or changed in relation to the meeting. It prevents decisions from relying on obsolete document versions and shows which clauses or file changes materially affected the meeting outcome.

Summary indicators

The screen shows total files, current verified versions, material version conflicts, a highlighted missing current version, and clauses or references that changed the outcome. Counts span the authorized source systems shown in the current meeting context.

File register

Each row shows file name, version, source system, version state, number of meeting references, classification, owner where available, and last modified time. Typical states are Canonical, Draft, Newer available, Conflicting, Missing, Superseded, or Unverified.

Selecting a file opens the permitted preview and a reference list showing where it was used in the conversation or related findings.

Version comparison

The comparison panel identifies the meeting-cited version and current repository version, then lists added, changed, or removed clauses. Each difference includes its business effect, such as schedule, acceptance, scope, security, or price. A newer version is not automatically authoritative if it was not effective at the meeting time.

Supporting panels

Version health summarizes conflict and currency states. Material clause references links the exact meeting timestamp to a clause. Required file actions lists comparison, attachment, canonical-version, and opportunity-linking work.

Actions

  • Link file associates an authorized file with the meeting and records the reason.
  • Export manifest creates a list of file identities, versions, sources, checksums, and references.
  • Compare selected opens a version diff.
  • Mark a version as canonical when authorized.
  • Request, attach, or verify a missing current version.
  • Open a clause or meeting timestamp.

Resolve material conflicts before formalizing a decision, acceptance, or scope change. Confirm effective date and authority, not only the highest version number. Preserve the version cited during the meeting and link the newer source separately.

Context, Audio & Transcript, Acceptances, and Scope Changes.