Quality checks in Cosmos — also known as Service Basics — are a way to document whether essential services were delivered as agreed. These checks help both airlines and service providers ensure reliable, day-to-day operational quality.
When Are Quality Checks Used?
Quality checks are typically created when:
A service is missing or incomplete (e.g. unmanned check-in counters)
A provider does not meet a basic operational expectation (e.g. lost & found not staffed)
An airline wants to document a service breakdown without logging a delay
They can be used proactively or in response to an observed issue.
How Do They Work?
On the Quality Check page, airline users can click + New Check in the top-right corner and select:
Service partner
Airline
Service Basic (e.g. counter staffing, baggage delivery)
The result is marked as either:
Check Passed
Check Not Passed
Optional: Add a comment or upload supporting documentation
By default, every new check starts as a draft.
While in draft, the check can be edited at any time. Once published, it becomes SLA-relevant, triggers a provider notification — and can no longer be changed.
Best Practice: Review all fields carefully before publishing. Published Quality Checks are final, part of the SLA process, and cannot be edited.
What Happens Next?
Both sides can comment directly in the Activity Feed. Learn more about the Activity Feed here.
Issues can be clarified, discussed, or resolved in real time.
All checks are stored and tracked for reporting and SLA evaluation.
Why It Matters
Quality checks help turn small issues into structured feedback — without delay codes or formal penalties. Over time, they support a culture of transparency, responsiveness, and continuous improvement.