> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/creation-and-submission-date-are-different-for-forms.md).

# Creation and submission date are different for forms

Task form creation date precedes submission; check-in form creation date follows submission due to platform database processing logic

## Question

When we download a forms report from the Submitted Form tab, we notice that for some forms, the submission date and creation date do not match. In fact, there are several instances where the creation date is later than the submission date.

We would expect the creation date to always be earlier than the submission date, so this behavior is unexpected. Why does it happen?

![](https://296077121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5dyjvbUVXEbs60EnxnDz%2Fuploads%2Fgit-blob-ead410d285d578b1f65e5c53e98755d43383e142%2FUnknown%20image?alt=media)

## Answer

This is how the platform logic works for check-in and task forms:

* When a task is created with an assigned form, the platform immediately generates a form for that task. Since the task will require completion at some point, the system prepares a file with an empty form in the database right away - we know the form is needed before it is submitted.
* For check-ins, however, the platform doesn't know in advance that a form should be created. The form is only added to the database after submission, which is why the creation date for check-in forms appears after they're submitted.


---

# 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://navixy.com/docs/qna/using-navixy/creation-and-submission-date-are-different-for-forms.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.