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.
Why quality checks matter
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.
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 quality checks work?
On the Quality Check page, airline users can click + New Check in the top-right corner and select:
Time of Check
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
Publish the quality check: Once finished you can publish the check by clicking on Create and confirming sending a notification to your service partner
Best Practice: Review all fields carefully before publishing. Edits are only possible within the current reporting period.
What happens after quality check publication?
The relevant service partner and other users with access to the station get a notification.
Both sides can comment directly in the Activity Feed.
Issues can be clarified, discussed, or resolved in real time.
All checks are stored and tracked for reporting and SLA evaluation.