Inspection scoring methodology: OrangeQC, CleanTelligent, and the APPA appearance standard

9 min read 2006 words Updated Jun 03, 2026 Reviewed by Opora Editorial Team

By the Opora Editorial Team

A facility manager sends an inspection report showing a 74% score for last quarter. The BSC's operations manager pulls the same data from their own system and shows a 91%. Both numbers are from the same building — but one platform weights missed trash pickups equally with a dirty sink, while the other weights restroom deficiencies three times higher than general-area deficiencies. Neither score is wrong. They measure different things. The dispute is about methodology, not performance.

Inspection scoring is the primary objective quality signal in a commercial cleaning contract. It is also one of the least standardized elements of the industry. APPA publishes a five-level custodial appearance standard widely used in higher education and K–12 facilities. OrangeQC and CleanTelligent are the two most widely deployed inspection platforms for independent BSCs. Each embeds different scoring logic, deficiency weighting, and reporting architecture. Understanding those differences is essential before you propose a quality measurement protocol in an RFP response or negotiate inspection terms in a contract.

The APPA 1–5 custodial appearance standard

APPA — the Association of Physical Plant Administrators, which serves facilities management professionals in educational institutions — developed the 1–5 Level Custodial Appearance Standard as a benchmarking tool for evaluating cleaning program outcomes in educational facilities. The standard describes five levels of appearance from Level 1 (orderly spotlessness) through Level 5 (unkempt neglect), per APPA's custodial staffing guidelines publication.

The APPA scale is an appearance outcome standard, not a task-completion standard. It evaluates what the space looks like, not whether a specific task was performed. Level 1 describes a space that is maintained in near-perfect condition with all surfaces clean, all fixtures operational, and no visible soil. Level 3 — the most common contractual target — describes a space that "shows evidence of soil, stain, or other blemishes but is still functional and not unacceptable to the majority of users." Level 5 describes conditions that "could lead to legal liability," including accumulated trash, broken fixtures, and hazardous conditions.

The practical value of the APPA standard in a contract context is that it gives the facility manager and the BSC a shared vocabulary for what the expected outcome is, independent of the task list that produces it. A contract that specifies "maintain the facility at APPA Level 3" is less ambiguous than one that specifies "clean restrooms nightly" with no quality benchmark. APPA also links the appearance levels to custodial staffing ratios — the guidance documents correlate each level with the hours-per-1,000-square-feet of cleanable space required to achieve it, giving BSCs a production-rate framework for their bids, per APPA's custodial staffing guidelines.

The limitation of the APPA standard as a day-to-day quality measurement tool is that it requires a trained inspector who can make consistent appearance-level judgments across different space types. Without calibrated inspectors, the same space can score Level 2 or Level 3 depending on who is doing the assessment and what they weight most heavily. This is where digital inspection platforms add value: they standardize the checklist, force the inspector to evaluate specific items, and record results with a timestamp and — in current platforms — photographic documentation.

The APPA 5-level custodial appearance standard deep dive covers how to structure APPA-referenced contract language and what the staffing ratios mean for a bid.

OrangeQC: weighted checklist scoring for BSCs

OrangeQC is a mobile-first inspection platform designed for building service contractors and facility management teams. Its scoring architecture centers on a weighted checklist model: the inspector evaluates discrete items, each item is assigned a point value or weight, and the inspection score is a weighted average of pass/fail results across those items.

The platform's key structural decisions are the ones operators must understand before deploying it in a client-facing context. Items in OrangeQC can be assigned different weights — a restroom deficiency can be configured to count more than a lobby deficiency, and safety-related findings can be flagged as critical items that require immediate remediation separate from the overall score. This flexibility is useful for operators who want their scoring to reflect priority-weighted quality standards. It is a negotiating point in client contracts: if the client expects restroom cleanliness to weigh five times the lobby score, configure that in the system before the first inspection, not after the first dispute.

OrangeQC generates inspection reports that can be shared directly with clients through a client portal, per OrangeQC's platform documentation. That transparency is a competitive differentiator when clients are comparing BSCs that self-report quality verbally versus BSCs that provide a timestamped inspection trail. It also changes the accountability dynamic: a client who sees inspection data weekly rather than quarterly is in a fundamentally different relationship with the BSC than one who gets a phone call when something goes wrong.

The operating risk with OrangeQC's flexibility is inconsistent configuration. A BSC that builds different checklists for different accounts — different weights, different items, different scoring scales — produces scores that are not comparable across the portfolio. For operations managers trying to identify systemic quality problems across 20 accounts, apples-to-oranges scoring is worse than no scoring at all. Standardize the core checklist structure across accounts, then use account-specific items as supplements rather than replacing the standard core.

CleanTelligent: client-facing transparency and QR verification

CleanTelligent operates on a similar checklist-inspection model but places greater emphasis on client-facing documentation and the integration of task verification with inspection scoring. The platform supports QR code-based task verification, where cleaning staff scan a QR code at each location to confirm task completion, creating a timestamped record of which areas were serviced and when, per CleanTelligent's platform documentation.

This task-verification layer addresses a specific account-management problem: the gap between what the cleaning crew says they completed and what the client believes was completed. A BSC that can show a client a timestamped log of every QR scan across every service area for the past 30 nights is in a different position when a complaint arises than one that relies on a written log or a supervisor's assertion.

The inspection module in CleanTelligent produces reports that the client accesses directly through a portal with configurable visibility settings — the BSC controls what the client sees. Inspection scores, work order responses, and service confirmations can all be shared in real time or with a reporting lag that the operator configures. This architecture is particularly effective for clients who manage multiple sites or who have facilities managers who expect data-driven oversight of their vendor relationships.

The distinction between OrangeQC and CleanTelligent is not one of better or worse — it is a design emphasis question. OrangeQC's strength is inspection weighting flexibility and internal quality-management depth. CleanTelligent's strength is client-facing transparency and the task-verification layer. A BSC primarily focused on internal operations management may weight the OrangeQC architecture more heavily; a BSC competing for accounts that specify proof-of-service documentation may find CleanTelligent's QR verification layer directly responsive to the RFP requirement.

The Swept, Janitorial Manager, and CleanTelligent feature matrix covers the broader software stack context, including how inspection platforms integrate with scheduling and payroll systems.

What the scoring methodology differences mean for contracts

The core problem that inspection scoring methodology creates in a BSC contract is divergent benchmarks. If the client uses APPA Level 3 as the contractual standard and the BSC uses OrangeQC with a default 80% threshold as the operational benchmark, there is no guaranteed alignment between the two. An 80% OrangeQC score on a default-weighted checklist might represent APPA Level 2 performance in a given facility, or it might represent APPA Level 4 — the relationship between a platform score and an appearance level depends on how the checklist is configured and what the inspector is trained to evaluate.

The resolution is explicit contract language, not just a platform choice. A well-constructed quality standard in a janitorial contract specifies:

The inspection method (APPA, platform-based, facility manager walkthrough)
The minimum acceptable score or level
The frequency of inspections
Who conducts them (client, BSC, third party, or joint)
The protocol when a score falls below the threshold (notification, remediation timeline, financial consequence)

Operators who are evaluating inspection platforms for a new account should present both the platform and the proposed scoring configuration during the sales or RFP process, not just reference the platform name. A client who agrees to "CleanTelligent scoring" without seeing the checklist and weighting is agreeing to something they have not evaluated.

The first-line supervisors who conduct inspections are a material cost in the inspection program. BLS puts the median hourly wage for first-line supervisors of housekeeping and janitorial workers at $23.89 as of May 2024, per BLS OEWS for SOC 37-1011. A supervisor spending two hours per week per account on digital inspections at that wage rate represents a real cost that either belongs in the bid or needs to be offset by the quality-management value the inspections generate through earlier deficiency detection, reduced complaint rates, and improved client retention.

Building a scoring baseline before the first inspection

The most common mistake operators make with inspection platforms is beginning inspections without a baseline. An account that has never been formally inspected will produce a first-inspection score that reflects the account's current state, not the BSC's performance since contract start. If the account was taken over in poor condition, the first score will be poor. If the first score is shared with the client without context, it reads as a failure.

Establish the baseline inspection within the first seven to ten days of service commencement, document it clearly as a pre-service or post-handoff baseline, and share it with the client. All subsequent scores are then measured against the baseline, not against an abstract standard. The improvement trajectory from a documented baseline is the quality story — it is more compelling than any single score in isolation.

The 30/60/90 day account onboarding playbook integrates baseline inspection into the onboarding sequence at day seven, precisely because establishing the baseline before the quality expectation is fully set protects both parties from score disputes in the first quarter.

What to verify yourself

The platform descriptions in this article reflect publicly documented features and general operator experience. Software features, pricing, and configurations change frequently.

Verify current feature sets and pricing directly with OrangeQC and CleanTelligent before committing to either platform. Contact information is available on each vendor's site.
Review the APPA custodial staffing guidelines directly at APPA's publications page to confirm current edition and level descriptions. The APPA standard is updated periodically.
Negotiate the inspection methodology explicitly in every contract before signing. Do not assume shared understanding of what a score means.
Calibrate your inspectors before deploying any scoring system. Interrater reliability — whether two inspectors produce the same score for the same space — is the operational validity test for any inspection program.
Confirm ISSA CIMS alignment if your BSC holds or is pursuing CIMS certification. ISSA's CIMS standard specifies documentation and quality-measurement requirements that your inspection program must satisfy.

Disclaimer — Software comparison content

Software features, pricing, integrations, and availability change frequently. Feature comparisons in this article reflect information gathered as of the research date shown and are provided as a factual reference matrix only — not as a product endorsement, recommendation, or ranking.

Before selecting software for your operation, verify current feature sets, pricing tiers, and contract terms directly with each vendor. Contact information and product documentation links are included where available. Opora Supply has no affiliate relationship with any software vendor unless separately disclosed, and vendor mentions do not constitute endorsements.

Opora Supply is not responsible for software performance, vendor service changes, pricing changes, or any business outcome resulting from a software decision informed by this content. If you spot an error in this article, contact us.

This article links up to its hub pillar, the Buying Smart hub.

Primary sources

Part of these field guides

Facility Playbooks

Related hubs

Tags: Buying smart, Product-guides, Tier-c

Previous article Next article