> For the complete documentation index, see [llms.txt](https://help.getswimtech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getswimtech.com/documentation/working-smarter-with-swimtech/the-power-of-a-consistent-ui-experience.md).
# The Power of a Consistent UI Experience
Learn the consistent and intuitive screen patterns SwimTech uses throughout the application so that once you know how to find, read, and edit information in one area, you already know how to work in m
**SwimTech was intentionally designed to be consistent and intuitive.**
In most areas of SwimTech, users interact with information using the same familiar pattern: **LIST → READ → EDIT → Save**. Once you learn how to find, review, and edit information in one area of SwimTech, you already understand much of how to work in other areas.
This consistency is deliberate. Business applications can become difficult to learn when Contacts behave one way, Work Orders another way, and Products or Services use completely different navigation and editing patterns. Users are then forced to learn each part of the application separately.
**SwimTech takes a different approach.** Wherever practical, the same controls, screen organization, menus, Search, Filter/Sort, READ mode, EDIT mode, and Save behavior are used throughout the application. This helps reduce confusion and makes the application easier to learn and use as users move from one functional area to another.
A user who learns how to manage a **Contact** will recognize the same basic interaction pattern when working with **Quotes, Work Orders, Services, Products, Checklists, Activity Reports, Fleet records**, and many other areas of SwimTech.
> **Learn the pattern once. Use it throughout SwimTech.**
The basic workflow is:
**Home → LIST → READ → EDIT → Save**
> **Exceptions:** Map, Route, and Settings do not follow this Entity LIST → READ → EDIT pattern in the same way.
## 1. LIST — Find and Select an Entity
Selecting a functional area from the **Home UI** generally opens that functional area's **LIST UI**.
The LIST displays the Entity records available in that area. Because LIST screens follow a common pattern, the controls you learn in one area will usually be familiar when you open another.
Depending on the functional area, the LIST may provide controls for:
* **Search** — Find records using text entered in the Search field.
* **Filter/Sort** — Change the order of the LIST and narrow the records displayed.
* **Refresh** — Refresh the records displayed in the LIST.
* **Add (+)** — Add a new Entity record.
* **Three-dot menu** — Open the Menu Actions available from that LIST.
* **Select an Entity** — Open an existing record in READ mode.
### LIST Menu Actions
Select the **three-dot menu** in the upper-right corner of a LIST to display the Menu Actions available for that functional area.
The actions vary by functional area. For example, the Contacts LIST can provide actions such as exporting the LIST to Excel, importing a device contact, printing the LIST, adding a User, accessing the AI Assistant, messaging, and opening instructional videos.
> Menu Actions are context-sensitive. The options displayed depend on the functional area and the functionality available to the user.
### Filter and Sort
Select **Filter/Sort** to control how records appear in the LIST.
The Filter/Sort screen can provide:
* **Sort** options, such as alphabetical order, most recent, or oldest.
* **Category** filters.
* **Type** filters, when applicable.
* **Status** filters, when applicable.
The filters available depend on the Entity being viewed.
Select **Apply filters** to update the LIST. Select **Clear all** to remove the selected filters.
## 2. READ — Review an Entity
From a LIST, select an Entity record to open it in **READ mode**.
READ mode allows you to review the Entity and its related information without changing the record. This same approach is used across most SwimTech Entities, so users know where to go when they simply want to review information.
Depending on the Entity, the READ UI can include:
* The Entity's primary information.
* Related information organized into sections.
* Expandable or collapsible sections.
* **+** controls for adding related information where available.
* An **Edit** button.
* A **three-dot menu** containing actions for the selected Entity.
* Prominent Entity-specific actions.
For example, a Contact can provide actions such as **Add Quote**, **Add Work Order**, and **Message**.
### READ Menu Actions
The three-dot menu in READ mode displays actions related to the Entity currently being viewed. These actions can be different from the Menu Actions available on the LIST UI.
## 3. EDIT — Change or Add Information
Select **Edit** from the READ UI to place the selected Entity into **EDIT mode**.
In EDIT mode, editable fields become available so you can change existing information or add new information to the Entity. The consistent transition from READ to EDIT helps users immediately understand when they are reviewing information and when they are changing it.
Depending on the Entity, you may be able to:
* Change existing field values.
* Select values from lists.
* Add additional related records using **+** controls.
* Delete information where the Delete action is available.
* Use Entity-specific actions associated with individual sections.
For example, when editing a Contact, you can maintain information such as phone numbers, email addresses, addresses, Water Bodies, Products, Services, websites, and other related information.
### Save Your Changes
When you have finished editing, select **Save** at the top of the screen.
SwimTech saves the changes to the Entity record. You can then continue reviewing the Entity or return to the LIST.
## Remember the Pattern
For most SwimTech functional areas, remember this simple workflow:
**LIST** — Find the record.\
**READ** — Review the record.\
**EDIT** — Change or add information.\
**SAVE** — Store your changes.
The real advantage of this pattern is that users do not have to relearn the application every time they move to another functional area. Once the pattern becomes familiar, users can concentrate on the customer and the work being performed instead of trying to remember how each screen operates.
> **Consistency reduces the learning curve, reduces confusion, and helps users work more confidently throughout SwimTech.**
Once you understand this pattern, the individual functional-area instructions can focus on the information and actions that are unique to that area rather than repeating the same navigation steps.
## What's Next?
Continue to **Initial Company Setup** if you are setting up SwimTech for the first time.
When you are ready to begin entering business information, continue to **Contacts** to build your business directory and add your first customer.
---
# 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://help.getswimtech.com/documentation/working-smarter-with-swimtech/the-power-of-a-consistent-ui-experience.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.
