> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/badge-printing/custom-badge/submitting-your-badge-design.md).

# Submitting Your Badge Design

Once your badge design is complete and all required files are ready, you can submit everything to our team by emailing [**support@letsgetdigital.com**](mailto:support@letsgetdigital.com). You can use the email template below to make sure your submission includes everything we need. Simply copy, fill in the details, add all attachments (fonts and badge designs) and send

{% hint style="info" icon="envelope" %}
**Subject:** Custom Badge Submission - {Fill event name}

\
Dear support,

Please find attached our custom badge submission for the following event: {**Fill event name**} which starts on {Fill start date of event}.

**Badge type:** \[e.g. T180 / T180S / 260T / 260TS / Sticker 102×51 / Sticker 76×51]

**Variable elements on badge:** \[e.g; First name, Last name, Company name, Company role,  QR code]

**Tag-based background logic:** (remove this section if not applicable)

* \[Background file name] → Tag: \[Tag name]
* \[Background file name] → Tag: \[Tag name]

**Attached files:** I confirm that i've included in the attachments the following files:

* A version of the badge background(s) without variables
* A version of the badge background(s) with variables
* The relevant TTF (Font files) for the badge

**Additional comments to Let's Get Digital:**\
\
Many thanks in advance. 
{% endhint %}

{% hint style="warning" %}
**Important to check**

* Save your design in **PNG** format.
* Use the **RGB colour space** to ensure accurate colour replication when printing.
* Do not include crop marks, trim lines, or any other layout markings in final submited design.
  {% 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://knowledge-base.letsgetdigital.com/badge-printing/custom-badge/submitting-your-badge-design.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.