United Kingdom
IndependentUnbiasedInformative
Study Guides

How to Read a University Assignment Brief Before You Start Writing

Illustrated assignment sheet with highlighted passages and separate task, scope and deadline symbols

Before researching a university assignment, turn the brief into a clear account of what you must produce, what question you must answer and how the work will be assessed. Separate confirmed requirements from your assumptions, then ask about anything that could change your approach. This first check can prevent you from writing a thoughtful answer to a different task.

The method below is a practical planning aid. Your module's current brief, marking criteria and regulations take precedence over general advice. The worked example is fictional and does not represent the rules of any university.

Collect the complete instructions

Start with the assignment brief, any associated marking criteria and the relevant module guidance. Check whether the tutor has issued a clarification or revised document. A screenshot of the question may omit submission details or instructions located on another page.

Record the document title and the date you checked it. Keep a link to the authoritative version rather than maintaining several unnamed copies. If two documents disagree, identify the exact conflict and ask which instruction applies. Do not resolve a consequential difference by following the version that seems easier.

Look for linked materials such as a case study, dataset, source pack or presentation specification. They may define the task as much as the title does. Confirm that you can access them before scheduling the main research or drafting work.

State the deliverable in plain language

Write a sentence describing what the marker expects to receive. Is it an essay, report, portfolio, annotated bibliography, presentation or another format? Is the submission individual or collaborative? Are there several components that must be submitted separately?

Then note the audience and purpose where these are specified. A report addressed to a fictional organisation may require a different presentation from a theoretical essay, even when both concern the same topic. Do not assume that headings, recommendations or a particular structure are compulsory unless the brief or disciplinary guidance supports that interpretation.

Identify any supplied template. If it is mandatory, plan within it. If it is an example, ask whether alternatives are acceptable when that matters. A familiar format from a previous module should not silently replace the requirements of the current assignment.

Separate the action from the subject

Find the words describing what you must do with the topic. A task might ask you to compare explanations, evaluate an approach, analyse evidence or reflect on an experience. Knowing the subject alone does not establish the kind of answer required.

Leeds Beckett University's guidance on understanding assignment questions recommends examining learning outcomes and instruction words, and seeking clarification from the lecturer when needed. Use those principles to create your own working interpretation rather than treating a dictionary definition of a verb as the whole marking scheme.

Write the interpretation as a question you can test. For example, “Which approach works better under the conditions specified, and what evidence supports that judgement?” provides more direction than “Write about the approaches”. If the task contains several actions, account for each rather than answering only the first.

Draw a boundary around the answer

Identify the population, period, location, case or theoretical perspective specified in the brief. Also identify what is excluded. These boundaries determine which evidence is relevant and how far your conclusion can reasonably extend.

Suppose a question concerns one organisation during a named period. A broad account of an entire industry may provide background, but it will not automatically answer the case question. Your plan needs to show how the evidence relates to that organisation and period.

Where the brief permits you to choose a case, make the choice explicit and check whether approval is required. Avoid choosing a case because it has abundant search results before checking whether it allows you to perform the requested analysis. Availability of material and suitability for the task are separate tests.

Translate criteria into checks on your work

Read the marking criteria alongside the question. For each relevant criterion, describe what the marker could actually see in your submission. For example, evidence of comparison might be a paragraph that applies the same criteria to both approaches, rather than two unrelated descriptions.

Do not turn broad criteria into invented numerical rules. A requirement for critical analysis does not automatically mean a fixed number of quotations, references or counterarguments. The depth and appropriateness of the work matter, and subject expectations differ.

Use the criteria to test your outline. If a major requirement has no place in the plan, address that gap before writing several pages. If you cannot understand a criterion, ask for clarification using a concrete example of what you think it means.

Make a separate submission checklist

Record the deadline, submission location, accepted file format and any naming instructions. Check how the institution defines the word count, including treatment of tables, captions, quotations, references and appendices. Do not import another module's rule without verification.

Check instructions concerning collaboration, permitted tools and acknowledgement of assistance. Where generative AI is mentioned, follow the current assessment-specific rules and clarify uncertainty before using it. A general statement that a tool is available does not establish permission for every use in assessed work.

Also identify the formal route for technical problems or circumstances affecting completion. This guide cannot tell you whether an extension or alternative submission will be accepted. Locate your institution's current process rather than relying on another student's account of a previous assessment.

A fictional example: from broad topic to workable plan

Imagine a brief asking you to compare two approaches to reducing waste in a fictional campus café and recommend one, using a supplied dataset. The deliverable is a report. The task contains comparison and recommendation; the café and dataset establish important boundaries.

A weak plan might describe waste generally, explain each approach and end with a personal preference. A stronger working plan would identify comparison criteria, examine what the supplied data can show, consider relevant limitations and connect the recommendation to that analysis.

You might discover that the dataset records quantities but says nothing about implementation costs. Record that limitation and ask whether additional research is expected. Do not invent missing costs or quietly claim that the data proves affordability. The uncertainty should shape the work rather than disappear from it.

Ask questions that can be answered

Instead of asking “Is my plan right?”, identify the interpretation needing confirmation. You could ask whether the recommendation should address only the supplied case or whether external cases are also required. Include the relevant wording and explain how you currently understand it.

Keep the reply with your assignment materials. If clarification is given verbally and affects a major decision, ask where it is recorded for the module. Avoid sharing another student's private feedback as if it were an official instruction for everyone.

Once the requirements are clear enough, begin. Repeatedly checking a brief without making a plan can become a delay in itself. Keep unresolved points visible while progressing with work that does not depend on their answer.

Recheck the brief during revision

Before submission, compare the actual draft with the task sentence, scope boundaries and criteria you recorded. Look for sections that are interesting but do not contribute to the answer. Check that conclusions follow from the evidence presented and that all required components are present.

Then complete the technical checklist using the final file. The aim is a submission that answers the assigned question and meets the confirmed requirements, with fewer decisions resting on guesses made at the start.

Featured image: AI-generated editorial illustration.

Related reading: Building an Academic Argument: From Evidence to Answer; How to Check Citations and a Reference List Before Submission.