Choose a service and prepare the details

Gather the location, observed issue, desired outcome, and relevant timing before using your organization's published request channel.

The categories below are employee-facing service examples. They help you describe a need; they do not submit a request or establish a service promise. Use the request route your organization publishes for the relevant service.

Worked example: “Cedar meeting room, second floor: the display shows ‘no signal’ when connected to the room laptop. The room is booked at 10 a.m. tomorrow; the display is available for a check after 3 p.m. today.” This gives the service owner a location, an observable issue, and useful timing without guessing at a cause.

Workplace service categories

Use the closest match to describe your need; these summaries are not separate request links.

Workplace support

  • Name the building, floor, or area.
  • Describe the condition you observed and when it began.
  • Include relevant access or scheduling constraints.

Meeting spaces

  • Give the room name and intended setup.
  • Describe the equipment or room issue you observed.
  • State when the room is next needed.

Office access

  • Name the location and type of access question.
  • Describe the issue without sharing credentials or sensitive information.
  • Use the organization's published route for follow-up.

Moves or changes

  • Identify the affected area or workgroup.
  • Describe the requested change and desired timing.
  • Note dependencies such as equipment or room availability.

Prepare a useful request

Use this sequence before handing the request to the published service channel.

  1. 1

    Choose the closest category

    Select the category that best fits the workplace need. If the cause is unclear, describe what you observed instead of guessing.

  2. 2

    Identify the place

    Include the building, floor, room, or area so the receiving service role can locate the request.

  3. 3

    Describe the outcome and timing

    State what is happening and what would help. Include relevant schedule, access, or availability constraints.

  4. 4

    Use the published request route

    Send the details through the organization's approved channel for that service. Keep follow-up in the same channel when possible so the context remains together.

Make the request easy to route

A specific location, observable issue, and timing help the first service owner assess the next handoff.

Needs more detail

“The meeting room equipment is broken. Please fix it soon.”

  • No room or building is identified.
  • The observed issue is unclear.
  • There is no timing context.

Ready to route

“Cedar meeting room, second floor: the display shows ‘no signal’ with the room laptop. The room is booked at 10 a.m. tomorrow; it is available for a check after 3 p.m. today.”

  • Names the location and observed behavior.
  • Includes the next known use and a workable time window.
  • Leaves diagnosis to the service owner.