> For the complete documentation index, see [llms.txt](https://docs.quilter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quilter.ai/using-quilter/submit-your-layout-job.md).
# Submit your layout job
Once you've uploaded valid input files, set physics constraints, and specified design parameters, you're ready to name and submit your layout job.
Quilter will generate a default name for the layout job from your design files, but you can override it here if you prefer.
{% hint style="success" %}
**Renaming jobs**\
Don't worry – you can always rename your job later (see [Job Actions](/job-actions.md)).
{% endhint %}
Once you've submitted your job, you'll see a blank loading screen while Quilter explores the best layout options for your job.
Quilter's time to explore all layout candidates varies depending on the complexity of your job, ranging from 15 minutes to 24 hours. Typically, you'll get the first results back within an hour. Once returned, candidates are instantly available for review in the candidate sidebar.
You'll receive an email when Quilter finds the first successful candidate for your layout job, and another email when the job is finished, along with a summary of the results.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.quilter.ai/using-quilter/submit-your-layout-job.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.