Label foot pedal actions for a shared desk
Pedal Four places four foot controls under a desk, where their assignments are not always visible to the next person using the workstation. A shared setup needs a clear legend and a known starting profile. The person who configured the pedals may remember every action, but that memory should not be a prerequisite for sitting down at the desk.
What does each label need to explain?
Use the actual action name and destination, such as Next page in reader or Focus editor. Avoid broad labels like Go that conceal whether a press changes a view, starts a process or submits text. If a pedal's meaning depends on a particular application, include that condition.
Describe whether the action repeats while held or changes state until another press. A toggle and a momentary control can feel similar at first touch. Check the configured behaviour rather than inferring it from the label you intended to create.
Where should the legend be placed?
Keep a readable reference on the desk or in the workstation's normal setup notes, where someone can inspect it before using the pedals. A label only on the underside of the controller is not useful during work. Match the physical order of controls in the reference to the arrangement actually installed.
Use an editable master copy and add a revision date or profile name. Whenever an assignment changes, update both the configuration record and the visible legend. An old label can be more misleading than no label because it encourages confidence in an action that no longer exists.
How do you provide a neutral starting state?
Choose a simple navigation profile for shared use, or document how to leave the controls inactive when the workstation is handed over. Follow the device and remapper's supported controls for doing that. Do not assume unplugging one component disables every software rule associated with its input.
Remove private text macros and machine-specific commands from the shared profile. A colleague should not discover stored account details or trigger a personal workflow by experimenting with an unfamiliar pedal. Keep any specialised operational profile separate and clearly identified.
What should the handover test include?
Ask a user to follow the legend in a disposable document, then compare their expectation with the actual result. Check the wrong-application case and the behaviour after reconnecting. Record any required background utility and the way to restore ordinary input. The Pedal Four setup information is the hardware reference; the shared legend should explain the particular workstation configuration, including its limitations.