Skip to main content

Configuring Organization Settings & Performance Thresholds

Learn how to customize your organization's details and set the global performance thresholds that power Mero's analytics and alerts.

Updated over 10 months ago

The Organization settings page allows administrators to apply universal rules that define what the Mero platform considers a "complete" or "on-time" action. These settings are critical for ensuring that analytics and alerts are aligned with your operational standards.

How to Access Organization Settings

  1. Navigate to Settings in the bottom-left menu.

  2. Select the Organization tab.

Customizing Your Organization Profile

At the top of the page, you can customize your organization's profile by:

  • Changing or deleting your organization's photo/logo.

  • Editing the organization's name.

Setting Performance Thresholds

These three settings are the core of Mero's performance logic.

1. Task Completion Time Buffer

This is a percentage-based grace period for completing a task. It allows for minor deviations from the Scope of Work without marking a task as incomplete.

  • How it works: Mero compares the time a cleaner actually spent in an area to the required duration in the Scope of Work, plus the buffer.

  • Example:

    • A task requires 10 minutes in a location.

    • The Task Completion Time Buffer is set to 20% (which is 2 minutes).

    • If a cleaner works for 9 minutes, the task is considered Complete because 9 minutes is within the 2-minute buffer of the 10-minute requirement.

2. Scope of Work (SoW) Completion Metric

This is the percentage of total tasks in a shift that must be completed for the entire shift to be considered "complete."

  • How it works: It's the benchmark for a successful shift.

  • Example:

    • If the SoW Completion Metric is set to 80%, a cleaner must complete at least 80% of their assigned tasks for their shift to be marked as having a complete Scope of Work in the Shift View report.

3. Schedule Compliance Buffer

This is a grace period, in minutes, for a cleaner's shift start time. It prevents late-start alerts for minor delays.

  • How it works: It creates a window around the expected start time.

  • Example:

    • A cleaner's shift is scheduled to start at 8:00 AM.

    • The Schedule Compliance Buffer is set to 45 minutes.

    • If the cleaner starts their shift anytime before 8:45 AM, they are considered on time, and no alert will be triggered. If they start after 8:45 AM, a "Missed Shift" alert may be generated.

Did this answer your question?