Report an error

What to report

• A number, date, fee or threshold that is wrong or out of date.
• A rule that has changed since the "Last checked" date on the page.
• A translation that says something different from the English page.
• A broken link, a source that no longer opens, or a tool that gives a wrong result.
• A fact about a developer or a project that you can show is wrong.

Send the report

The form opens WhatsApp with your report ready to send. Nothing is stored on this website. You can also email info@avi.ge.

Your name

Email or WhatsApp number (for our reply)

Page address

What is wrong, and what should it say?

Source that shows the correct information (link, optional)

Send the report on WhatsApp

By sending, you agree to our privacy policy.

What we do with it

1. Check

   We open the page and the source it cites, and the source you sent if there is one.

2. Correct

   If the page is wrong, we fix it in every language and update the "Last checked" date.

3. Log

   The page's change log gets a dated line that records what changed. If you agree, it names you.

4. Reply

   You hear from us either way, including when we think the page was right and why.

What this page is not for

Questions about your own purchase or residence permit belong on the contact page. Developers who want to comment on a profile or a review can use this form or email us; the independence statement explains how comments are published. The editorial policy describes the full corrections process.

What makes a report easy to act on

The fastest reports to resolve have three things: the page address, the exact sentence or figure that is wrong, and where the correct information can be found. The page address matters because many pages discuss the same subject in five languages, and "the residency page" could be any of ten. The exact sentence matters because we check the claim, not the topic; "the threshold is wrong" sends us to re-read a whole page, while "the page says the threshold applies from 1 January 2026 and the official text says 1 March 2026" sends us to one line. The source matters most of all: a link to the law on the Legislative Herald, to the Public Service Hall's page or to the research report lets us verify the correction in minutes, and it is what the correction will cite. A report without a source is still welcome and still checked; it simply takes longer, because we have to find the source ourselves.

Examples of reports we act on

• A changed rule. "The page still says $100,000; the threshold has been $150,000 since 1 March 2026." We check the official text, update the figure in all five languages, re-run the residency checker, and date the change.
• A translation mismatch. "The Hebrew page says the permit is for two years; the English says one." We compare the two against the source, correct the one that is wrong, and check the other three languages for the same slip.
• A dead source. "The link to the Colliers report returns an error." We find the report's new address or a reporting outlet that carries it, replace the link, and note the replacement in the sources list.
• A tool result. "The yield calculator ignores the management fee when it is set to zero." We reproduce the result, fix the calculation, and record the fix on the tool's page.
• A developer fact. "The profile says the project was delivered in spring; here is the commissioning record showing autumn." We verify the document, correct the delivery table with the new source, and tell the developer.
• An outdated practice note. "The registry no longer requires this document; here is the current list." We confirm with the authority's page or the partner lawyer, update the guide, and add the date.

What a report does not change

Some things are not errors, and the reply says so with the reason. A figure that is correct for its date and source is not changed because a different source gives a different figure; instead, if the second source is reliable, both are recorded and the page explains the difference. A statement of general law is not changed because an official applied it differently in one case, although the page may add a note that practice varies. An opinion or an interpretation that a reader disagrees with is not an error; the reader's view may be published as a comment if it is substantiated, and a developer's response to a profile or review is published next to it under the rules on the independence page. A request to remove a sourced negative fact about a developer or a project is refused unless the source is shown to be wrong. And a report that is really a question about the reader's own purchase is answered as a question, through the contact page, rather than as a correction.

How long it takes

Every report gets a reply, and the reply tells you what will happen. A straightforward factual error with a source is usually corrected within a few working days in all five languages, and the reply arrives when the correction is live. A report that needs the partner lawyer or the accountant, because it concerns a legal or tax page, is answered once they have confirmed, and the page carries a review notice in the meantime if the point is material. A report about a developer or a project is checked against the documents and the developer is given the chance to respond before a change is published, which takes longer. If a report turns out to be wrong, you still hear from us, with the source we checked against, because an explanation of why a page is right is as useful as a correction.

Credit, anonymity and thanks

When a correction is made, a dated line goes into the page's change log saying what changed and why. If you agree, the line names you, by the name you give us, or describes you as a reader; if you prefer, it says nothing about who reported it. We do not publish your contact details in any case. Readers who report errors are doing the site's quality work for free, and the least we owe them is a reply, a credit if they want one, and a site that is a little more right than it was. The people who report most are often the ones with the most knowledge: lawyers, accountants, developers' staff and owners who have been through the process, and a report from any of them is read with that in mind.

What we learn from reports

Reports are logged with the page, the type of error and the source, and the log is read once a quarter by the analyst and the lead adviser. The point is not to count them but to find patterns: a subject where the same error appears on several pages, a source that has become unreliable, a translation into one language that slips more often than the others, a tool whose defaults confuse people. Where a pattern appears, the fix is to the process, not only to the page: a term is added to the terminology list, a source is replaced across the site, a tool's default is relabelled. The editorial policy is updated when a pattern changes how we work, and that change is dated in its log like any other.

A worked example, from report to change log

A reader writes: "On the Invest & money page the link to the Galt & Taggart article on Batumi returns an error; the article now lives at a different address." The analyst opens the page, confirms the link fails, finds the article at its new address on the same outlet, and checks that the figures quoted on our page still match the article as republished. The link is replaced in all five language versions of the page and in the sources list of any other page that cites it. The last-checked date on each affected page is updated, and a line is added to each change log: the date, "source link updated", and, because the reader agreed, "reported by a reader". The reader receives a reply with the list of pages changed. Total elapsed time, in a case like this, is usually a day. A report that changes a fact rather than a link goes through the same steps with one more: the new fact is entered in the facts register with its source before any page is edited, so that the correction is made once and inherited everywhere the fact appears.

Reporting different kinds of problem

A fact or figure	Give the page, the sentence and the source for the correct version. Checked against the facts register and the source; corrected in all languages.
A translation	Give both the page in the language you read and, if you can, the English line it differs from. Checked against the source, not only against the English, because the English can be the one that is wrong.
A tool	Give the inputs you used and the result you got. We reproduce it before changing anything; a tool is corrected and re-dated like a page.
Structured data or the machine summary	If a search engine or an assistant shows something about a page that the page does not say, tell us what you saw and where. The markup is checked against the page and corrected.
A page past its next-check date	If a page's last-checked date looks old for a subject that moves, say so even without a specific error. It is re-checked and re-dated, and if nothing changed the change log says that too.
Something about you	If a page mentions you, your company or your project and you believe it is wrong, write with the evidence; you receive the right of reply described on the independence page, and the text changes if the evidence shows it should.

Reporting in your language

Reports can be sent in Georgian, English, Russian, Hebrew or Arabic and are read by a person who reads that language; the reply comes in the same language. Because every page exists in five versions, a correction found through one language is checked in all five, and a translation error in one version is a signal to re-read the other three. If you are reading the site in a language that is not your first and are not sure whether a difference is an error or a difference of expression, send it anyway; deciding that is our job, and the reply will say which it was.

Reporting a security or privacy problem

This site is plain pages without accounts, payments or stored data, but if you find something that could expose a reader's information, such as a form behaving unexpectedly or a link that leads somewhere it should not, please report it by email rather than through the public form, with "Security" in the subject line, and do not post the details publicly until we have replied. Such reports are read first and answered the same working day where possible. How the site handles the little data it touches is set out in the privacy policy and the cookie policy.

Frequently asked questions

What happens after I send a report?

We open the page and the cited source, check the claim, and reply to you. If the page is wrong, we correct it and add a dated line to its change log.

Will you credit me?

If you want, yes: the change log can name you. If you prefer to stay anonymous, say so.

Do you change opinions as well as facts?

Facts are corrected against sources. Opinions, for example which district suits whom, are ours; we add your view to the page if it adds something readers need.

I disagree with a developer profile. What can I do?

Send the source that supports your point. Developers and readers have the same right of reply, and comments are published next to the text they refer to.

Change log

• 11 October 2026 - Published.