Home / Blog / YeS-TR Amendment of 28 October: How Should Project Files Be Version-Controlled?
Yörünge Kurumsal Blog
YeS-TR Amendment of 28 October: How Should Project Files Be Version-Controlled?
Three annexes to Türkiye’s Green Certificate Regulation for Buildings and Settlements changed on 28 October 2026. Project teams should compare the sources and assessment documents in their files with the current texts.
What change has been confirmed?
The amendment published in Official Gazette No. 33414 on 28 October 2026 replaced Annexes 1, 2 and 3 of the Green Certificate Regulation for Buildings and Settlements and took effect on publication. This provides a reason to check document versions in YeS-TR projects. The amendment alone does not establish how a particular project’s score, certificate status or assessment changes; the current annexes and project conditions must be reviewed together.
List the sources used in the project
Assessment sheets, checklists and presentations may have been prepared at different times. Record each official source, guide and internal template with its name, date, version and file location. Flag documents of unknown origin or version. A shared source register reduces the risk of treating an old file as current.
Review changes document by document
Compare the updated official annexes with the project’s documents. A comparison table can show the old source, current source, affected file, required action, reviewer and review date. Do not mark unreviewed items as complete. Changing a document title does not show that its content has been checked against the new source.
Assess whether existing evidence remains usable
Earlier measurements, calculations and technical reports should not automatically be discarded. Check what each item supports, its scope, date and building area. If a report’s design version is unclear, clarify that link before ordering the work again. Record any needed explanation or new study as a separate task.
Assign owners and decision points
Design, operations, purchasing and project management teams may hold different information. Give each review topic an owner and expected output. Record the document examined and decision reached, rather than only “checked”. Escalate needs for new measurements, expert assessment or implementation changes with their reasons.
Keep source versions visible in digital tools
A completion percentage alone does not identify the criteria and source version behind an assessment. Link the source version, evidence file, review status and change history. Put records needing reassessment in a work list. Any predicted rating or certificate should state its sources and must not be presented as an official decision or guarantee.
How can completion be checked?
The team should know where current sources are kept, which documents have been reviewed and which tasks remain open. Trace a few sample records from source through assessment to evidence, then assign owners and dates to gaps. Yörünge Kurumsal can support source review, document organisation and digital progress tracking; official assessment and certification decisions remain with authorised bodies.
Resmî Gazete · The workflow is an editorial recommendation, not a claim about specific changes to criteria or scores. Photo: Adam Binder / Pexels; the pictured building is not identified as YeS-TR certified or a Yörünge project.