> For the complete documentation index, see [llms.txt](https://report.pytogo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://report.pytogo.org/pycon-togo-2025-post-conference-report/event-logistics-and-operations.md).
# Event Logistics and Operations
PyCon Togo 2025 was carefully organized to ensure smooth logistics and operations for both in-person and online participants.
#### **Media Team and Recordings**
The conference was **recorded and livestreamed on YouTube**, allowing virtual participants to join from around the world. All recordings, including the livestream, were uploaded to the Python Togo YouTube channel. High-quality photographs of the event were also taken and uploaded to **Google Drive**, which was made publicly accessible to the community.
#### **Registration, Check-in, and Swag Distribution**
The check-in process was efficiently managed using a **dedicated check-in application**. All attendees were verified with their tickets, and participants who had not registered prior to the event were able to **register on-site** without any issues. Additionally, the **distribution and sale of event t-shirts and swag** were smoothly executed by the organizing team, ensuring all participants received their items seamlessly.
#### **Accommodation and Local Transportation**
International speakers and media team members were **provided accommodation for a minimum of two nights**, with some staying for three nights. Accommodations were arranged as follows:
* **Nigeria:** 2 speakers + 1 volunteer
* **Côte d’Ivoire:** 1 speaker (3 nights)
* **Ghana:** 3 media team members
The organizers also arranged **local transportation** for all speakers and media team members. This included travel **between the event venue (UniPod, University of Lomé) and their accommodations**, ensuring a smooth commute during the conference, from the point of arrival in Togo to their accommodation and for departures.
#### **Food, Beverages, and Sponsors**
All participants, including speakers, volunteers, media team members, and **local sponsors**, were provided with **meals and beverages** throughout the event. The catering team carefully managed **dietary restrictions**, ensuring that everyone could eat safely. Participants had a **choice of three meal options and multiple beverage options**, including water and juice, for each meal. Meals were served for **breakfast, lunch, and other breaks**, allowing attendees to select what best suited their needs.
#### **Program Execution**
The conference program was **followed closely**, with only a few speakers unable to present due to unforeseen circumstances. Workshops, panels, and standard talks were executed smoothly according to the schedule.
#### **Connectivity and Technical Setup**
The internet connection was **stable and sufficient for livestreaming**, providing a smooth experience for online attendees. Minor electricity interruptions occurred, but power was restored quickly, causing minimal disruption. Overall, technical operations ran efficiently, ensuring a seamless experience for both in-person and online participants.
---
# 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://report.pytogo.org/pycon-togo-2025-post-conference-report/event-logistics-and-operations.md?ask=&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.
