> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/data-capture/events/creating-an-event.md).
# Creating an Event
To create an event, go to **Events** in the top navigation and click **New event**. Unless you copy an existing event, your new event will be created with default settings and no fields on the registration form. You will need to select an Event date, and a date that registrations close on.
The New event button showing in the Events module.
If you want to base your new event on an existing one, use the **Duplicate** option from the event list. Click the three-dot menu next to the event you want to copy and select **Duplicate**. You can then edit the duplicated event as needed.
The event list showing the three-dot menu with the Duplicate option for copying an existing event.
Each event has a unique URL that is used for registration. You can find this on the Event Dashboard at any time.
The event date and close registrations date can be updated at any time from the **Edit Details and Settings** option.
---
# 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.ubiquity.co.nz/documentation/data-capture/events/creating-an-event.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.