Evaluate · Line by line

Forty requirements, six vendors, one afternoon

You have a tender with forty numbered requirements and six vendor brochures to read before you can score any of them. This tool does the first pass for you: paste the requirement lines, and each one comes back matched against what is actually compiled into SkyRoster today, with the specific rule, module or regulatory element that substantiates it.

What this is, and what it is not

This is a keyword match, computed in your browser, against an index built from the compiled rule catalogue, the platform modules and the ATS.OR.320 elements. It is not a lawyer's reading of your tender and it is not a formal response we would sign. Wording that does not overlap with our index comes back as no match, even where the underlying capability exists under different words, and wording that does overlap can still be coincidental. Treat every result as a starting point for a conversation, not the conversation itself.

Standard SaaS includes a 99.5% uptime SLA, daily backups and automatic updates on Microsoft Azure in the EU. The tool still sends service-level requirements for direct review: a keyword cannot determine whether a tender's full conditions match that commitment. Security certification, recovery objectives, support response times and accessibility evidence also need a specific answer. Pricing lines point to the published rate card and commercial conditions.

Requirements matcher

verified

Paste your requirement lines. See exactly where each one lands.

Paste your requirement lines below, one per line, numbered or not

Nothing you type here is sent anywhere. Matching runs in your browser only. Your lines stay in this browser's storage so you can come back to them, and you can clear them at any time.

Turn on JavaScript to match your own lines. The table below already shows a worked example, fully matched.

Covered
3
Partially covered
1
No match found
1
Requires direct confirmation
1

6 lines checked: 3 covered, 1 partially covered, 1 no match found, 1 requiring direct confirmation.

Each pasted requirement line against SkyRoster's compiled rules, platform modules and regulatory elements
#	Requirement line	Result	Why this matched	Evidence
1	1. The system shall enforce a minimum rest period of at least 12 hours between the end of one duty and the start of the next.	Covered	Shares specific wording with ATS.OR.320 "ATS.OR.320 element 2: Maximum hours per duty period": "hours", "duty", "period".	ATS.OR.320 element 2: Maximum hours per duty period There is a minimum rest gap between two duties ATS.OR.320 element 5: Minimum rest periods ATS.OR.320 element 7: Minimum rest period after a duty period encroaching the night time A long run of hours earns its rest afterwards
2	2. The solution shall automatically prevent assignment of a controller to a position requiring a rating or licence that has expired.	Covered	Shares specific wording with the compiled rule "Only staff rated for the position are allocated to it": "employee", "position", "qualification".	Only staff rated for the position are allocated to it An expired rating cannot cover a shift A suspended rating cannot be used on position Time on each position meets the currency minimum Staff still in a support period do not cover alone
3	3. The system shall allow controllers to request a shift swap electronically, with automatic checking of eligibility rules before the swap is approved.	Covered	Shares specific wording with the platform module "Shift swaps": "swap", "eligibility", "request", "shift".	Shift swaps A shift can only be in one pending swap at a time Staff should not be assigned to shifts that are not required A swap cannot collide with approved leave or duty
4	4. The mobile application shall allow controllers to view their roster and submit leave requests, and shall continue to operate fully offline without a network connection.	Partially covered	The mobile app has no offline mode. Every screen needs a live connection to the tenant backend, documented on the platform limits page. It also overlaps with the platform module "Mobile app" on "mobile", "app".	Mobile app has no offline mode Mobile app
5	5. The vendor shall provide evidence of an independent penetration test and guarantee a minimum of 99.5% platform uptime.	Requires direct confirmation	This line asks about a security certification. That is not published on this site as a checkable claim. It is answered directly, in writing, in an evaluation call.	Ask us directly
6	6. The system shall provide integrated air traffic flow management slot allocation directly linked to network manager systems.	No match found	No rule, platform module or regulatory element in this index shares enough of this line's wording. That does not prove the capability is missing, only that keyword matching did not find it.	None

Read the result the way it is meant to be read

No match is not a rejection

It means this index did not find enough shared wording, nothing more. A requirement phrased in language our rule names, modules and regulatory elements do not use will land here even when the capability exists. Bring it to a working session rather than scoring it as absent.

Partial means read the reason

A partial match usually means the topic is right but the detail is not a full match, or that a documented limit sits inside the line, such as the mobile app's lack of an offline mode. The reason column says which, every time.

Covered still needs the link opened

A covered line names the actual rule, module or regulatory element behind it. Open the link and check it against your own wording before you write it into a scoring sheet, the same way you would check any other vendor's claim.

Bring the lines it could not place.

A working session is 45 minutes with your actual requirement list on screen. We will go through every line this tool marked partial or no match and tell you, specifically, what is true.

Book a working session Send a question instead