Reading SAY, EA, SÖZ and DİL scores as programme-access keys rather than subject labels
Reading SAY, EA, SÖZ and DİL scores as programme-access keys rather than subject labels
One number, slogan or previous-year example is insufficient for YKS Score Types. The four lenses below collect different kinds of evidence; source, date and the learner’s own experience are recorded for each.
Used for programmes associated with mathematics- and science-heavy field proficiency.
For SAY, seek dated documentation or an observable outcome rather than hearsay. Reopen this card and update the decision log when the evidence becomes outdated.
Used for programmes combining mathematics with Turkish literature and social sciences.
For EA, seek dated documentation or an observable outcome rather than hearsay. Reopen this card and update the decision log when the evidence becomes outdated.
Used for programmes where Turkish literature and social-sciences tests are decisive.
For SÖZ, seek dated documentation or an observable outcome rather than hearsay. Reopen this card and update the decision log when the evidence becomes outdated.
Used where YDT performance is decisive; the programme language and special conditions are also checked.
For DİL, seek dated documentation or an observable outcome rather than hearsay. Reopen this card and update the decision log when the evidence becomes outdated.
| Lens | Strong evidence | Red flag | Record to produce |
|---|---|---|---|
| SAY | Official source + current condition for say + real example | Only promotional language or an undated screenshot about SAY | SAY: verified / to check / unsuitable |
| EA | Official source + current condition for ea + real example | Only promotional language or an undated screenshot about EA | EA: verified / to check / unsuitable |
| SÖZ | Official source + current condition for söz + real example | Only promotional language or an undated screenshot about SÖZ | SÖZ: verified / to check / unsuitable |
| DİL | Official source + current condition for di̇l + real example | Only promotional language or an undated screenshot about DİL | DİL: verified / to check / unsuitable |
Imagine a learner has an initial choice about yks score types. The first review makes say look strong, but current evidence for ea is missing. Instead of assigning zero or ignoring the uncertainty, the learner marks it “to be verified”, opens the official source, compares the programme’s own information and completes a small trial. The result may support the first choice, change it or create a two-option plan. A sound decision is not one that protects the first guess; it updates its reasoning when new evidence arrives.
For this case, record the process as well as the outcome: which evidence changed the view, which question remains open, where the learner felt comfortable or strained, and when the YKS Score Types page should be checked again.
Used for programmes associated with mathematics- and science-heavy field proficiency.
Used for programmes combining mathematics with Turkish literature and social sciences.
Used for programmes where Turkish literature and social-sciences tests are decisive.
Record it as “unknown—to be verified”; do not treat it as zero or a definite negative.
Dates, fees, quotas, programmes, personal priorities or evidence can change, so the decision log must be updated with dates.
Open a research file for YKS Score Types and record the date, purpose and unknowns on the first page. “It looks good” or “my score is enough” is not a reasoned decision. Create separate evidence boxes for SAY, EA, SÖZ and DİL. Each box contains source link, source date, a short finding and how that finding changes the decision.
The second layer is comparison. SAY may look strong while EA is weak or unknown. Before creating any total score, define non-negotiables: safety, sustainable cost, ability to follow the language of instruction, real practice and learner willingness. A strong brand or historical rank cannot hide a failed non-negotiable condition.
The third layer is a small trial. Rather than only reading about YKS Score Types, attempt a short first-year task, sample assessment, campus journey, budget simulation, student conversation or programme-document review. Record duration, difficulty, whether curiosity continued and what support was required. One trial is not a final verdict, but it converts an abstract expectation into observable behaviour.
The fourth layer is a return calendar. Information in YKS Score Types can become outdated when quotas, fees, guides, regulations, curricula or personal priorities change. Reopen the file before preference or application; compare the new version instead of deleting the old evidence. This preserves not only the outcome but also why the decision changed.
| Record | Now | Update trigger |
|---|---|---|
| Known | Dated evidence with a source | New guide or programme version |
| Unknown | Person/document/mini trial to use | Answer or new observation |
| Non-negotiable | Condition the learner can sustain | Option removed if condition fails |
| Return | Scheduled review date | Before preference, term or application |
Do not act on changing dates, conditions, fees or quotas from this summary alone. Reopen the primary source for the relevant year before acting. Dated indicators such as YÖK Atlas are read as historical data for the YKS year shown.
Completing this page does not mean that every decision about yks score types is settled. To make the information usable, the learner should bring personal circumstances and current official evidence into one decision file. The plan below turns general guidance into observable evidence, uncertainty into a verification question and a first reading into a record that can be revisited.
Begin by examining “The question this page actually answers” beside “Four topic lenses”. For each heading, record one real situation, one unknown and one question to verify through a reliable source. Then test the suggestion under “Evidence desk: what to inspect” on a small scale. Do not record only success or failure; note time used, support needed, the error encountered and what would change in a second attempt.
The third layer is comparison. Evaluate the focus “Real-life scenario” against at least two alternatives using the same criteria. Criteria should not be the title, institution name or first impression alone; use everyday practice, accessibility, time and cost, safety, source freshness and the learner’s own view. Do not assign a guessed score to missing information. Mark it clearly as “to be verified” and name the responsible source.
For dates, conditions, fees, quotas, rules or application details that can change, do not rely only on the page’s review date. Open the primary official notice, record its date and scope, and preserve the earlier value in a version history when information changes. This makes it possible to see which decision relied on which evidence at a particular time.
The final step belongs to the learner. Answer: what did I understand, what remains doubtful, what support do I need and what is my next small action? Keep parent or teacher observations in a separate row rather than replacing the learner’s view. Reopen the same record after one week or one month and compare changed evidence with needs that remain.
| Focus | Evidence to produce | Closing question |
|---|---|---|
| The question this page actually answers | One real situation + one verification question | What changes in my own context? |
| Four topic lenses | Source, date and scope record | Is the source current and direct? |
| Evidence desk: what to inspect | Small trial + error log | What will change in version two? |
| Real-life scenario | Two-alternative comparison | Which difference genuinely affects the decision? |
Suggested return: a short check seven days after the first record; whenever an official change is published; and a full reread before an important decision.