How we update this guide: change log and revision policy

Why this matters

Travel content about Ukraine falls into four categories that age at different speeds:

1. Fast (weeks — months): NBU currency limits, combat zone lists (Cabinet of Ministers), martial-law rules.
2. Medium (months — half a year): customs allowances, dual-use permits, visa regime, border crossing points.
3. Slow (half a year — year): visa-free stay rules, other stable legislative norms.
4. Stable (years): historical context, geography, fundamental principles.

We cannot promise that every article has been verified today. But we can promise that the review process exists, works, and is transparent.

Review principles

1. Last-updated date is present on every article. This is the date of the last substantive editorial review (not the date of a cosmetic fix). If an article has not been changed for more than 60 days, that's a signal the content may need review. A visual «under review» indicator for such articles is planned for Phase 7 production launch.
2. Update triggers — four types:
   • Regulatory trigger: official publication of a new Cabinet resolution, NBU / SMS / SCS / Ministry of Reintegration order that changes facts in an article. Reviewed within 7 days of the act's effective date.
   • User trigger: your report to editor@ukraineborder.com about a factual error. Reviewed within 5 business days.
   • Internal fact-check: a regular review cycle for high-priority articles every 90 days (for the «fast» category), 180 days (for «medium»), 365 days (for «slow»).
   • Event trigger: a significant change in the situation (new sanctions, new border crossing point, change in the insurance product model) — an out-of-cycle review of all affected articles.
3. One trigger — full cycle. Changes are not «pushed silently». Each substantive edit: (a) is verified by an editor, (b) is logged in the change log with date, (c) updates the last-updated field.
4. We don't edit silently. If we rewrote a substantive paragraph (rules, figures, references) — it appears in the article's change log. If we fixed a typo or added an internal link — it's not logged (cosmetic).

Change categories (what we log)

We log only substantive changes. The log has three levels of significance:

• 🔴 Major — factual edit (numbers, dates, regulatory references, legal categories). Example: «Currency limit updated from UAH 10,000 to UAH 50,000 (NBU Resolution No. 60/2026, effective 01.05.2026)».
• 🟡 Minor — wording clarification, nuance addition, structural rearrangement without content change. Example: «Expanded section on the 50-km buffer in the policy's territorial coverage».
• 🟢 Editorial — stylistic edits that change tone without changing facts. Logged in aggregate once a month, not per individual edit.

Cosmetic fixes (typos, formatting, typography) are not logged.

Change log format

For substantive changes we log the date, significance level (🔴 Major / 🟡 Minor / 🟢 Editorial), and trigger (regulatory / user / internal fact-check / event). The target format is a Revision history table at the bottom of each article:

Rollout status: the public Revision history table is rolling out across the catalogue. By the Phase 7 production launch, every article will carry its full log on the page. Until the table appears on a specific article, request its change history via editor@ukraineborder.com with a link to the article; reply within 5 business days.

AI-assisted content creation and review

UkraineBorder.com uses AI (specifically Claude by Anthropic) for first drafts and translations. This is documented in accordance with the EU AI Regulation (EU AI Act, Article 50 — transparency requirement for general-purpose AI deployments).

How this affects the revision policy:

• Every AI draft passes through a human editorial gate. AI does not publish directly — a human editor verifies facts, regulatory references, tone, localisation nuances before publication.
• AI-assisted updates are logged with an «AI-assisted» tag in the trigger. This does not change the significance level (🔴/🟡), but transparently indicates that automation was involved.
• Translation workflow — AI generates a draft translation based on the approved UK source; a native-speaker editor verifies terminology accuracy (especially for legal/regulatory terms) before publication.
• Factual edits never use AI alone. If we update a regulatory reference — a human reads the original act and confirms.

What is not in the revision policy

Honestly:

• We don't monitor 24/7. Regulatory triggers fire upon publication in official sources, but a lag of up to 7 days is possible.
• We don't guarantee simultaneous updates across all 10 locales. The UK source is updated first; the 9 other locales follow within 2-5 days. If you are reading a localised version and the last-updated lags behind UK — UK is the source of truth.
• We don't edit archive entries. If an article had an erroneous statement in a previous edition, the change log shows when it was corrected — but the old version of the text is not publicly preserved (the git repository is internal).

How you can help

If you notice:

• an outdated regulation,
• an inaccurate figure,
• a wrong citation,
• a translation error,
• a regulatory change we missed,

— write to editor@ukraineborder.com with a link to the article and the specific issue. We review within 5 business days and respond to you personally with the verification result. If you are right — we change the content and add an entry to the log with the tag «User (editor@)».

Thank you for helping. It makes the content better for everyone.

Cross-references

• Editorial standards — how we fact-check before publication.
• Contact — channels for reporting needed changes.
• About UkraineBorder.com — operator, transparency, AI disclosure.
• Affiliate disclosure — how commercial ties do not influence editorial decisions.