Filter and Sort the Jobs List

Filters help you turn a busy day into a focused working list. Use them to find unassigned, pending, completed, or specialized jobs without changing the jobs themselves.

What you will accomplish

By the end of this guide, you will be able to complete a filtered Jobs view from the correct CleanOver screen, understand the important checks before saving, and verify that the result is visible to the people who use it next.

Before you begin

• Set the correct date first.
• Know whether you need a unit group, status, job type, staff member, team, or assignment state.
• Sign in to the Admin workspace and confirm you are in the correct business context.
• Use real operational dates and the property’s local timezone when the workflow includes time.

Step 1: Open Jobs and choose the date

Select Today or use the date controls. The date range is always applied before the filters in the side panel.

Expected result: The header shows the intended day or range.

Step 2: Open Filters

Select Filter at the top of the Jobs page. The panel groups options such as Unit Groups, Job Status, Jobs, Staff, Teams, Assigned Status, bedrooms, and bathrooms.

Expected result: The Filters panel is open.

Step 3: Limit by property

Expand Unit Groups and select the building, region, or unit you need. Use the search field when the list is long.

Expected result: Only relevant properties remain in the job list.

Step 4: Choose a job status

Select Pending for work still to do, In Progress for active jobs, Completed for finished work, or Cancelled for audit and troubleshooting.

Expected result: The list reflects the intended lifecycle state.

Step 5: Choose job types

Expand Jobs and select Clean, Audit, Maintenance, or a specific subtype such as Regular or Deep.

Expected result: Unrelated job types are removed.

Step 6: Filter by responsibility

Use Staff, Teams, or Assigned Status to find one worker’s route or all unassigned work.

Expected result: The list answers the assignment question you started with.

Step 7: Close the panel and sort

Close Filters and use Sort By to order the remaining cards in the most useful sequence, such as team or unit.

Expected result: The visible cards are both filtered and ordered.

Step 8: Clear filters when finished

Return to Filters and select Clear All before starting a different operational check.

Expected result: Old filters do not hide jobs in the next workflow.

How to confirm the workflow is complete

• Refresh the destination list or calendar and confirm the saved record appears only once.
• Check the unit, date, status, owner or assignee, and any linked record before leaving the page.
• Open the next downstream view mentioned in the guide and confirm it shows the same information.
• Record an internal note when the action corrects historical data or changes another person’s responsibility.

Common issues and what to do

The expected record is missing

Clear old filters, check the date and business context, then search by the most specific identifier available. If the data comes from a connected provider, check connection and mapping status before recreating it manually.

A button is disabled

Look for a required field, incomplete checklist item, missing permission, locked lifecycle status, or unresolved linked task. Complete the highlighted requirement instead of trying to bypass it.

The page shows different information after refresh

Another user or integration may have updated the record. Compare timestamps and the source system, then apply the correction in the system that owns the data.

You are unsure whether to continue

Stop before cancelling, overwriting, revoking, or issuing a financial document. Ask the workflow owner to confirm the intended outcome and add that decision to the internal record.

Best practices

• Use clear names that make sense to a new team member without extra context.
• Prefer the smallest safe scope for bulk actions, filters, permissions, and date ranges.
• Keep guest-facing communication separate from internal diagnostic notes.
• Verify a high-risk change in a second view before considering it finished.
• Update the source configuration when the same correction is needed repeatedly.