> For the complete documentation index, see [llms.txt](https://guide.wiseapp.co.kr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.wiseapp.co.kr/wiseapp/data-methodology/data-correction-timing.md).

# 데이터 보정 시기

#### 비정기적인 데이터 보정

* 스마트폰 사용인구 변화로 모집단이 변경될 때
* 통계 알고리즘 개선으로 데이터가 변경될 때

{% hint style="info" %}
통계 데이터는 발행된 이후에는 가급적 변경되지 않습니다만, 좋은 품질의 통계를 위해 별도의 고지없이 보정될 수 있습니다.

모집단 변경 등과 같은 전체 통계 기준이 변경되는 경우 반드시 별도 고지를 합니다.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guide.wiseapp.co.kr/wiseapp/data-methodology/data-correction-timing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.