Complete Time Accounting gives you a full, gap-free view of cleaners’ on-site time. Instead of only logging long, scheduled cleaning tasks, Mero now captures all meaningful presence: quick checks, movement between rooms, breaks, and even cases where a beacon was left behind.
This is done through a set of visit types that each describe what that time represents for your operation.
1. Standard Cleaning Visits (Scheduled & Unscheduled)
These are your “normal” cleaning visits and the backbone of your reporting.
Scheduled Visit
A visit that matches the expected schedule or Scope of Work (SoW).
What it does for the business
Drives SoW completion and core performance metrics
Proves that contracted work was done at the right times and places
Unscheduled Visit
A valid cleaning visit that wasn’t originally on the schedule (e.g., spill response, touch-up, ad-hoc task).
What it does for the business
Shows extra value beyond the formal SoW
Helps you quantify “nice to have” service and reactive work for clients
Counts toward SoW?
Scheduled: ✅
Unscheduled: ✅ (config/SoW rules may apply)
2. Transient Visits (Ultra-Short Stops)
Definition:
A very short stop (under 1 minute) at a location — a quick check, pop-in, or brief pause while moving through an area.
Typical examples:
A cleaner steps into a washroom for 20–30 seconds to inspect
A quick glance into a room while walking a route
What it does for the business
Fills what used to look like “missing time” between tasks
Shows that areas were actually touched or inspected, even briefly
When aligned with the SoW, these count as visits toward task completion
Counts toward SoW?
✅ Yes, when the transient visit hits a space that’s part of the Scope of Work.
(This is why SoW % typically increases and stabilizes once this feature is on.)
3. Persistent Visits (Short Travel / Prep Windows)
Definition:
A short continuous presence between two visits, where the cleaner is still active on-site but not in a major cleaning task.
Under the hood, Mero creates persistent visits when:
There’s a gap greater than 0 minutes between two valid (non-abandoned) visits
That gap is less than or equal to a configured threshold (a “few to several” minutes – typically up to around a quarter hour)
Typical examples:
Walking 5–10 minutes from one area to another
Prepping supplies in a nearby space before entering the next task
Wrapping up in one zone and staging materials for the next
What it does for the business
Makes travel and prep time visible and measurable, not “lost”
Helps explain why cleaners appear in certain areas without a major task logged
Lets you optimize routes and staffing, seeing how much time is walking vs cleaning
Counts toward SoW?
❌ No. It’s work time, but not a cleaning task completion.
It’s there for time accounting and efficiency analysis, not SoW %.
4. Break Room Visits
Definition:
Time when a cleaner’s beacon is detected at a location marked as a break room or rest area.
Typical examples:
Lunch or coffee break
Short rest between heavy cleaning blocks
What it does for the business
Clearly separates work time vs. break time
Explains longer gaps in cleaning activity without suggesting lost productivity
Helps confirm that break policies are being followed (not over- or under-utilized)
Counts toward SoW?
❌ No. Logged for transparency, not as cleaning work.
5. Abandoned Beacon
Definition:
Time where the system detects that a beacon has effectively been left behind, not worn by a moving cleaner.
From the CleanerVisitAbandonedService, a window is marked abandoned when:
The beacon pings from only 1 base station for at least 6 hours, or
The beacon pings from no more than 2 base stations for at least 8 hours
…and very short “noisy” visits (≤ 1 minute) are ignored so they don’t break that window.
So practically:
How long does it take to be marked as abandoned?
6+ hours stuck on a single base station, or
8+ hours bouncing only between 1–2 base stations
⇒ That time range is flagged as an Abandoned Beacon window and those visits are markedis_abandoned = true.
What it does for the business
Prevents obviously wrong data (e.g., a beacon “working” in a closet all day) from being interpreted as real activity
Helps you find and recover forgotten devices
Keeps reports honest by separating device issues from cleaner behavior
Counts toward SoW?
❌ No. Abandoned time is explicitly excluded as real work.
How It All Comes Together in Reports
In activity views and exports, you’ll see a Type column with one of:
Scheduled Visit
Unscheduled Visit
Transient Visit
Persistent Visit
Break Room
Abandoned Beacon
Durations are shown in human-friendly form:
Transient:
Visited for <1 minute(or<1 minute (x times)for multiple quick hits)Others:
Visited for ~N minutes(rounded whole minutes)
Default filters (simple view)
By default, you’ll usually see:
✅ Scheduled Visit
✅ Unscheduled Visit
⭕ Transient Visit (off by default)
⭕ Persistent Visit
⭕ Break Room
⭕ Abandoned Beacon
This keeps everyday reports focused on core cleaning tasks.
When to turn on the extra types
Investigate gaps / complaints
Turn on Transient + Persistent + Break Room + Abandoned
Reconstruct what really happened minute-by-minute
Optimize operations
Look at Persistent to see travel / prep overhead
Check Break Room patterns against shift design
Client or executive deep-dives
Add Transient to show all touch-points and quick checks
Use Abandoned Beacon in internal investigations, not client decks
Quick Mental Model
Scheduled / Unscheduled → The work you planned and performed
Transient → Tiny, task-related touchpoints that now count
Persistent → Movement and prep that explain where time goes
Break Room → Legitimate pauses, clearly labeled
Abandoned Beacon → Device left behind; don’t confuse with work