Most teams lose a moot long before they stand up to speak. The damage is usually done in the first week, while reading the proposition, and it looks like nothing at the time.
The instinct is to read a proposition the way you read a case: front to back, following the story. That instinct is wrong. A proposition is not a story. It is a controlled set of facts, deliberately drafted so that a fixed number of arguments are available to each side. Your job is extraction, not comprehension.
Read it three times, for three different things
The first read is for the shape of the dispute. Who is against whom, before which forum, and what has already happened below. Do not stop to think about arguments. You are only building a mental map.
The second read is for hard particulars. Every date, every name, every figure, every statutory provision named. Write them out separately as you go. Dates in particular are almost never decorative. If a proposition tells you a notice was issued on one date and a petition filed on another, the gap between them is usually there for a reason: limitation, delay, laches, or the sequencing of a statutory requirement.
The third read is adversarial. Read only for facts that hurt you. Every proposition is drafted to be roughly balanced, which means the drafter has deliberately planted material against your side. If you cannot find it, you have not found it yet.
Separate the issues from the reliefs
Beginners collapse these two. They are different.
The reliefs are what the party is asking the forum to do. They are usually stated near the end and are easy to miss because they read like formalities. The issues are the legal questions that must be answered before the forum can grant those reliefs.
Work backwards. Take each relief and ask: what would a court need to be satisfied of before granting this? Those satisfactions are your issues. Done properly, this stops you arguing points that are interesting but that lead nowhere, which is the single most common failure in a first moot.
Treat the forum as a constraint
A proposition that places you before a constitutional court is asking a different question from one that places you before a tribunal or an appellate forum. The forum determines the standard of review, what can be reopened, and what must be accepted as settled below.
If the proposition says findings of fact were recorded below and not disturbed, then arguing the facts is usually wasted breath. Read the forum first, because it silently deletes entire categories of argument.
Build a dates table before you build arguments
Take a blank page and lay out every event in chronological order with its date, even events that seem trivial. Two things fall out of this almost every time.
- Sequencing problems the narrative reading concealed
- Gaps where the proposition is deliberately silent
That silence matters. Where a proposition does not tell you something, you generally cannot assume it. Clarifications exist for exactly this, and most competitions set a deadline for them. Reading closely early is what lets you use that window at all; teams who read late discover their questions after clarifications have closed.
Write the other side's argument first
Before drafting your own memorial, write a short, honest version of your opponent's best case. Not a strawman. Their best case.
This is uncomfortable, which is the point. It tells you where your case is genuinely weak, and weak points are where the bench will spend its time. A speaker who has already sat with the hardest question against them answers it calmly. A speaker meeting it for the first time in the round does not.
What good preparation looks like by week one
By the end of your first week you should have a dates table, a list of issues derived backwards from the reliefs, a page of facts that hurt you, and a list of clarifications worth seeking. You should not yet have a memorial, and you should not yet have authorities.
Research before extraction produces confident arguments about the wrong questions.