University, Curriculum and Futures

Faculty Atlas

Explaining faculties through their programmes and shared academic resources rather than a name list

Sources checked: 27 July 2026Matched Turkish–English release
01

The question this page actually answers

Explaining faculties through their programmes and shared academic resources rather than a name list

One number, slogan or previous-year example is insufficient for Faculty Atlas. The four lenses below collect different kinds of evidence; source, date and the learner’s own experience are recorded for each.

02

Four topic lenses

1

Shared infrastructure

A faculty can shape access to laboratories, studios, research and academic governance.

For Shared infrastructure, seek dated documentation or an observable outcome rather than hearsay. Reopen this card and update the decision log when the evidence becomes outdated.

2

Misleading labels

The same faculty label can contain different departments and curricula across universities.

For Misleading labels, seek dated documentation or an observable outcome rather than hearsay. Reopen this card and update the decision log when the evidence becomes outdated.

3

Programme level

Candidates choose a programme code; the faculty is the broader academic context.

For Programme level, seek dated documentation or an observable outcome rather than hearsay. Reopen this card and update the decision log when the evidence becomes outdated.

4

Comparison

Review the faculty at programme, staff, infrastructure and support levels.

For Comparison, seek dated documentation or an observable outcome rather than hearsay. Reopen this card and update the decision log when the evidence becomes outdated.

03

Evidence desk: what to inspect

Evidence desk: what to inspect table
LensStrong evidenceRed flagRecord to produce
Shared infrastructureOfficial source + current condition for shared infrastructure + real exampleOnly promotional language or an undated screenshot about Shared infrastructureShared infrastructure: verified / to check / unsuitable
Misleading labelsOfficial source + current condition for misleading labels + real exampleOnly promotional language or an undated screenshot about Misleading labelsMisleading labels: verified / to check / unsuitable
Programme levelOfficial source + current condition for programme level + real exampleOnly promotional language or an undated screenshot about Programme levelProgramme level: verified / to check / unsuitable
ComparisonOfficial source + current condition for comparison + real exampleOnly promotional language or an undated screenshot about ComparisonComparison: verified / to check / unsuitable
04

Real-life scenario

Imagine a learner has an initial choice about faculty atlas. The first review makes shared infrastructure look strong, but current evidence for misleading labels 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 Faculty Atlas page should be checked again.

05

Twenty-minute workshop

  1. Write “What do I currently know about Faculty Atlas?” and make a three-sentence first hypothesis.
  2. Find one piece of evidence for each of the four lenses; add its date and the question it answers.
  3. Select one unsupported claim and specify the person, document or mini trial needed to verify it.
  4. Divide the decision into “now”, “next” and “if conditions change”.
  5. Set a return date; update not only the outcome but also the evidence that changed.
06

Topic-specific micro quiz

1. Why can Shared infrastructure not be evaluated through one slogan or number?

A faculty can shape access to laboratories, studios, research and academic governance.

2. Why can Misleading labels not be evaluated through one slogan or number?

The same faculty label can contain different departments and curricula across universities.

3. Why can Programme level not be evaluated through one slogan or number?

Candidates choose a programme code; the faculty is the broader academic context.

4. What should happen when evidence cannot be verified?

Record it as “unknown—to be verified”; do not treat it as zero or a definite negative.

5. Why should this page be revisited?

Dates, fees, quotas, programmes, personal priorities or evidence can change, so the decision log must be updated with dates.

09

Deepening: turn the decision into an evidence file

Open a research file for Faculty Atlas 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 Shared infrastructure, Misleading labels, Programme level and Comparison. Each box contains source link, source date, a short finding and how that finding changes the decision.

The second layer is comparison. Shared infrastructure may look strong while Misleading labels 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 Faculty Atlas, 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 Faculty Atlas 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.

Deepening: turn the decision into an evidence file table
RecordNowUpdate trigger
KnownDated evidence with a sourceNew guide or programme version
UnknownPerson/document/mini trial to useAnswer or new observation
Non-negotiableCondition the learner can sustainOption removed if condition fails
ReturnScheduled review dateBefore preference, term or application
07

Official sources and currency

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.