Skip to content
U4SUniversity4Students
Menu

Guide · International students

Reading the unwritten rules of a new academic system

Every academic system runs on expectations it rarely states out loud. Asking about them directly is quicker than deducing them from a set of surprising marks.

Last reviewed · 12 min read · How we review

The syllabus is the easy part. It is written down, it is handed to you, and it says what the module covers. What is not written down is how anyone is supposed to behave around it: whether you are meant to argue with the reading or reconstruct it faithfully, whether a question in a lecture counts as engagement or interruption, how much of the work is expected to happen in a room with a teacher in it. Students arriving from a different system often notice the gap only when a mark comes back with a comment they did not anticipate.

Nothing here ranks one arrangement above another. Systems differ because they were built by different institutions for different purposes, and each one rewards a particular set of habits. What follows describes the dimensions along which they tend to vary, so you can work out where your own habits sit and then check rather than guess. Anyone still preparing for a move might read it alongside the guide to preparing to study abroad.

What counts as an argument here

The first thing to establish is what a piece of student work is supposed to do. In some settings the expected move is to reconstruct an established position accurately and completely, demonstrating command of the material. In others the expected move is to take a position and defend it against the obvious objections, and a faultless summary with no stance of its own reads as unfinished. Plenty of programmes want both at different points, and they rarely announce which is wanted when.

The same variation applies to disagreement. Where argument is expected, saying nothing in a seminar can read as not having engaged. Where synthesis is expected, a confident claim without the groundwork can read as under-read. Neither reading is a judgement on you personally, and neither convention is more rigorous than the other. They are different tests, and it is entirely possible to fail one by performing well at the other.

Assessment briefs carry the answer more often than students expect, and the verbs do most of the work: outline, summarise, discuss, evaluate, argue, critique. Where the wording is ambiguous, the marking criteria attached to the module usually resolve it. Where those are vague as well, one question in a seminar or an office hour settles the matter quickly, and asking it makes you look prepared rather than lost.

How formal things are with teaching staff

Forms of address vary widely and matter more than they look as though they should. In some places students use first names with lecturers from the outset. In others, titles are used consistently and dropping one reads as careless. Email register varies alongside it: an opening that is warm and brief in one setting looks abrupt in another, and an elaborate formal greeting looks odd where the norm is plain. Mirroring is the reliable method. Notice how staff sign their own messages, and how students who have been there longer address them.

Access conventions differ too. Office hours may be a standing invitation that goes largely unused, or a scarce resource that fills as soon as it opens. Some staff expect questions by email and treat a knock at the door as an interruption; others much prefer the opposite. Many programmes route pastoral and administrative questions through a named tutor or an office rather than through teaching staff, so going to the wrong door slows an answer down rather than causing offence.

Questions during class are their own convention. In some rooms, interrupting a lecture to ask something is normal and taken as a sign of interest. In others, the lecture is a delivery and questions belong to the seminar or the end of the session. Watch what happens the first time another student asks something, and note whether anyone asks at all. Where the culture stays unclear, asking a lecturer how they prefer to take questions is itself a reasonable question.

What independent study is assumed to mean

Contact hours are the visible part of a workload and rarely the largest part of it. How much unsupervised work is assumed varies enormously between systems and between subjects, and it is often stated only in a document nobody points you towards. The gap opens quietly. A timetable that looks light is sometimes a timetable that expects a great deal of reading between sessions, and the first evidence of the mismatch tends to arrive with the first assessment.

Note-taking habits usually need adjusting alongside this, because notes designed for a system where the lecture contained everything do not serve a system where the lecture is an entry point. The guide to reading and taking notes covers the mechanics of that. The point worth carrying here is that the right method depends entirely on what the sessions in front of you are for.

  • The reading list. Establish whether it is a menu, a core set or a contract. Lists that look identical on the page can carry entirely different obligations, and the difference is seldom visible in the document itself.
  • Before or after. Some systems expect the reading to be done before the session so that the session can build on it. Others treat the session as the introduction and the reading as consolidation. Arriving with the wrong assumption makes seminars uncomfortable.
  • What counts as done. Read closely, skimmed for the argument, or read only the parts bearing on your own question. Expectations differ by subject as much as by system, and asking a tutor what depth they have in mind is a normal request.
  • Where the teaching happens. In some programmes the lecture carries the content and the seminar tests it. In others the lecture is orientation, and the work that counts happens in labs, studios, reading groups or your own notes.

Group work and what a group is supposed to produce

Group assessment carries assumptions that are almost never spelled out. Whether the mark is shared or individual changes behaviour completely. So does whether a group is expected to divide the work into parts and assemble them, or to produce something collectively that nobody could point to a section of. Some settings expect a nominated leader and a visible structure; others treat any attempt to lead as presumptuous. All of it is learned somewhere, and none of it is announced.

Mixed groups are where these assumptions collide. Somebody trained to deliver their section on time and stay out of everyone else's can look disengaged to somebody trained to review the whole thing together. Somebody who edits a teammate's paragraph looks either helpful or intrusive depending on where they learned to work. Naming the working method at the start, before anyone has invested effort, prevents most of the friction, and there is more on that in the guide to working in a student group project.

Communication norms vary alongside the rest: who contacts staff on behalf of a group, whether disagreements get raised in the room or afterwards, how directly criticism is phrased. Assume difference before assuming indifference. A surprising amount of what looks like a personality problem in a mixed group turns out to be two reasonable conventions running at the same time.

What academic honesty conventions assume

Every system has rules about attribution, collaboration and reuse, and they are not identical. What counts as common knowledge and therefore needs no citation differs. Whether lecture material must be cited differs. Whether a passage from your own earlier work can be reused differs, as does how much collaboration on an assessed task is permitted before it stops being permitted. None of that makes one convention more serious than another. It makes them different, and the one that applies to you is the one written down in your own programme's regulations.

Tools and materials fall under the same principle. Whatever is permitted for drafting, checking, translating or generating text is defined by your institution and often by the individual assessment, and permission in one module does not carry over to another. Where the documentation is silent, the person setting the work can tell you, and asking creates no suspicion. Uncertainty is a reason to ask early, since the same question raised after submission becomes a different conversation.

  1. Read the actual regulations. Not a summary, not a friend's account, and not the version from a system you studied in before. Programme handbooks and assessment regulations are the documents that get applied if a question ever arises.
  2. Ask before, not after. Questions about what is permitted are ordinary and are treated as ordinary by the people who set the work. The same question asked once the work is submitted sits in a completely different category.
  3. Check the collaboration line. Work out where discussion ends and shared production begins for each specific assessment, because the answer often differs between a problem set, an essay and a project on the same programme.
  4. Record where things came from. Keeping a note of sources while you work, rather than reconstructing them afterwards, prevents most accidental problems and takes less effort overall than the reconstruction would.

Assessment, and what it quietly rewards

Some systems concentrate almost everything into a final assessment. Others spread it across the term through coursework, presentations and marked participation. Some use oral examinations, where thinking aloud under questioning is the thing being tested. Each arrangement rewards a different working pattern. A student who paces work towards one heavy assessment at the end can be caught out by continuous marking, and a student used to steady coursework can badly underestimate what a single terminal assessment asks for.

Marks themselves do not translate. Grading conventions differ in what a typical result looks like and in how much of the range gets used, so a mark that seems alarming against the scale you grew up with may be entirely ordinary where you are now. Rather than converting it, ask what the distribution normally looks like on that module and what the comments are pointing at. The comments almost always carry more information than the number does.

Feedback culture varies as well. Written feedback may be detailed or minimal, and some of the most useful commentary is given verbally, only to the students who come and ask for it. Where feedback looks thin, it is worth asking what would have moved the work up, phrased as a question about the next piece rather than a challenge to this one. That framing tends to get a fuller answer.

How to find out instead of guessing

Most of the difficulty described here dissolves under one habit: asking narrow questions early, of the person who can actually answer them. Vague questions attract vague reassurance. Asking whether the reading is expected before the seminar produces something usable, while asking how to do well produces encouragement and little else. The other half of the habit is knowing which questions belong to a lecturer, which to a personal tutor, and which to an administrative office.

None of this is remedial. Everyone in the room is working from assumptions absorbed somewhere else, and the students who look effortless usually absorbed the local set at school. Asking is read as diligence far more often than as ignorance. If the wider transition into university life is what unsettles you rather than the academic conventions specifically, the first-year survival guide covers more of that ground. The broader sense of everything being slightly out of register has its own territory in the guide to culture shock.

  • Start with the handbook. Programme handbooks, module descriptors and assessment regulations state more than students expect. Read the assessment sections before the first deadline rather than after the first mark.
  • Ask a narrow question. Whether an essay wants a defended position or a survey, whether the reading is needed before the seminar, what depth counts as having read something. Narrow questions get precise answers.
  • Look at examples. Where past work or exemplar answers are available, they show the expected shape faster than any description of it can. It is worth asking whether any exist and where they are kept.
  • Use an office hour early. A first visit is easier when nothing is wrong, and it makes the second visit, if something does go wrong later, considerably less daunting than a cold approach would be.
  • Cross-check student advice. Other students are a good source of orientation and an unreliable source of regulation. Take the tip, then confirm anything consequential against the written version before you rely on it.

Common questions

How do I find out what my new university actually expects?
Start with the documents that get applied if anything is ever queried: the programme handbook, the module descriptor and the assessment regulations. Then ask narrow questions of the person setting the work, because narrow questions get precise answers and broad ones get encouragement. Whether an essay wants a defended position or a survey of the field, whether reading is expected before a seminar, what depth counts as having read something: each of those can be settled in a sentence. Other students are useful for orientation and worth cross-checking on anything consequential.
Is it rude to disagree with a lecturer?
That depends entirely on the setting, which is why it is worth establishing rather than assuming. In some rooms, well-supported disagreement is the point of the session and silence reads as disengagement. In others, challenge belongs to the seminar and the lecture is a delivery. Observation followed by a direct question is the reliable method: watch what happens when another student pushes back, notice whether anyone does, and ask a lecturer how they prefer to take questions. Framing a disagreement around the evidence rather than the person travels well in most settings.
Why did my mark come back lower than I expected?
Before concluding that the work was weak, check whether it answered the local question. A thorough summary can score modestly where a defended argument was wanted, and a bold claim can score modestly where the task was to demonstrate command of the literature. Grading conventions also differ in how much of the range gets used, so converting a mark into the scale you grew up with can mislead badly. Ask what the distribution usually looks like on that module, and what specifically would have moved this piece up.
Does struggling with academic culture mean my subject knowledge is weak?
Not usually. Conventions about argument, independence, group work and attribution are learned locally, often at school, and they are close to invisible to the people who absorbed them. A student can know the material thoroughly and still misjudge what a task is asking for, which is a different problem with a different remedy. Where a second language is genuinely part of the load, that difficulty is covered separately in the guide to handling language barriers. Separating the two makes both easier to work on.