How do you show us whether service is meeting expectations over time?

Slate gives authorized client contacts time-bounded service metrics with property and area filters, visit drilldowns, satisfaction, issues, and configured SLA views.
How do you show us whether service is meeting expectations over time?
Slate’s client Metrics page turns cleaning records into a time-bounded review of visits, satisfaction, issues, overnight work, and SLA results. You choose a date range and can narrow the view by property or area. The result is not a single unexplained score: it combines totals and trends with visit, rating, issue, and resolution details so your team can ask what changed and where follow-up is needed.
Start with the question, then choose the measure
On /metrics, select the period you want to review and apply the property or area filter. The Visits view helps establish the service volume and shows completion and on-time calculations, including visits with issues. The Satisfaction view brings together ratings, rating tags, and weekly trends. Issues groups issue types and shows resolution information. Other tabs cover overnight work and SLA-oriented reporting where those records and configurations apply.
This lets a facilities leader use the same workflow at different levels. Review all authorized properties for a monthly account meeting, filter to one area when a regional manager sees a pattern, or select one property before discussing a specific service concern. Use trends to spot a change over time, then move to the underlying visits or issues rather than relying on an average alone.
Drill into the record behind the number
Metrics are most useful when a number leads to an action. From a visit or issue drilldown, review the records included in the selected period and filter state. Visit details can help distinguish completed work, timing, and visits associated with issues. Issue details can show the issue type, status, and resolution path. That context supports a fair conversation with Slate: “This area had more access issues after the schedule changed” is more actionable than “the score went down.”
Satisfaction reporting provides ratings, tags, and weekly trend information when clients have submitted that feedback. Issue reporting can include resolution hours and comparison with the configured SLA. Use the date range and property filters consistently from one review to the next so a month-over-month comparison does not quietly change scope. Save the questions your team asks—completion, punctuality, quality signals, recurring issue types, and response time—and use the corresponding tab or drilldown for each.

Make the report useful without overstating it
The portal limits metrics to the client tenant and the contact’s allowed properties. A regional or local contact therefore sees metrics for their authorized scope, while a client-wide contact can review the broader portfolio. This protects location information and explains why two contacts may see different totals.
Metrics describe recorded activity; they do not independently prove that every cleaning met a contract’s full definition of quality. Completion and on-time calculations use Slate’s visit and schedule data. Satisfaction depends on submitted ratings and tags, so a lack of feedback is not the same as a perfect result. SLA comparisons use the configured target and issue timestamps; they are not a universal service-level definition unless the account has been configured that way. Overnight reporting and quality signals likewise depend on the applicable records and settings.
Use the report as a review and improvement tool: identify a pattern, open the underlying visits or issues, agree on the next action, and revisit the same filtered period later. It gives your team evidence to discuss with the service operator without pretending that a dashboard replaces site knowledge or a human quality review.
Review service with evidence
Ask Slate to demonstrate a metrics review using your preferred date range, property hierarchy, quality measures, and issue follow-up questions.
Proudly supporting

.avif)





.avif)





.avif)





.avif)






.avif)



.avif)
.avif)
.avif)

.avif)
.avif)