How to Organize a Moot Court Authorities Bundle

A controlled bundle keeps every active authority numbered, verified, and ready for retrieval.

A moot team can find excellent authorities and still waste preparation time if nobody can locate the exact case, provision, or paragraph when the argument needs it. An authorities bundle solves that operational problem. It gives the team one controlled set of the sources actually being used, with a master index that shows what each authority supports and where the relevant passage can be found.

The competition rules must decide what may be submitted, carried, cited, highlighted, tabbed, or provided to judges. Some competitions may not use a formal authorities bundle at all, or may define it differently. This article therefore focuses on a private team organization system that can be adapted to the current rules; it does not claim a universal submission format.

Separate the working library from the authorities bundle

Your research folder may contain dozens of judgments, articles, statutory versions, screenshots, notes, and rejected sources. The bundle should be smaller. Include the primary and other permitted authorities that the team is genuinely relying on or needs as serious backup. A crowded bundle makes retrieval slower and can hide which sources actually carry the argument.

Keep rejected or background sources in the research archive, not mixed with the controlled bundle. If a source returns to active use, move it into the bundle through the same indexing process as every other authority.

Start with one master index

Create a table with these fields: Bundle number; Full authority name/citation; Source type; Proposition supported; Pinpoint; Moot issue; Side using it; File name; Verification status; Notes on distinction or limitation. If the competition requires a different list of authorities for submission, create that separately from this private working index.

Stable bundle numbers and a verified master index reduce retrieval friction during preparation.

The proposition column is the most important. "Jurisdiction" is too broad. Write what the authority actually supports, such as "consent must be established by the stated instrument" or "the exception is interpreted narrowly where condition X is absent." The wording should remain faithful to the source.

Give every authority a stable bundle number

Use a simple identifier such as A01, A02, A03 for active authorities. The number should not communicate legal weight unless your team has deliberately designed a system that everyone understands. Its main purpose is retrieval: the memorial note, oral outline, and index can all point to A07 without relying on a long file name.

Do not renumber the entire bundle every time one case is removed. Gaps are less dangerous than changing every reference after the team has rehearsed. If A06 is dropped, mark it inactive in the working index and leave the remaining numbers stable unless the final competition submission requires a consecutive sequence.

Use file names that can be read under pressure

A useful file name might combine the bundle number, short authority name, year, and source type: A07_ShortName_2024_Judgment.pdf. Avoid files called finalcase.pdf, case2-new.pdf, or screenshot(14).pdf. The naming rule should work across laptops and shared folders without depending on one person's memory.

If you save legislation, include enough information to distinguish versions. Record the date on which the text was checked and preserve the official source details in the index. Do not silently replace an old file with a newer text while leaving the team unsure which version was used in the memorial.

Keep one clean source and one annotated working copy

Where the competition and copyright/access conditions permit local working copies, keep the clean source separate from the team's annotated copy. The clean copy preserves what the authority actually says. The working copy can contain highlights, margin notes, argument tags, and cross-references for internal preparation.

Use labels such as RULE, LIMIT, FACT ANALOGY, CONTRARY, and QUOTE to make the annotation purpose clear. Do not highlight half the judgment. A highlight should answer a retrieval question: which exact passage do we need and why?

Attach pinpoints to propositions, not only to files

A case can be fifty pages long while the useful proposition sits in one paragraph. The master index should record the pinpoint beside the proposition. If the source has numbered paragraphs, use them where appropriate. If it uses pages, record the relevant page. If the competition's citation style requires a specific locator, follow that style.

PLC's guide to citing Pakistani cases and statutes can help students keep source identity and pinpoint information usable. The bundle adds an internal retrieval layer: which authority, which proposition, which exact passage, and which argument section needs it.

Organize by argument without duplicating source files

A single authority may support more than one issue. Avoid saving three copies of the same judgment in three folders. Keep one controlled file and let the master index contain multiple proposition rows or issue tags. Your oral outline can point to the same bundle number from different arguments.

This reduces version drift. If the team later discovers a better scan, a corrected citation, or an official copy, there is one source file to replace and one verification status to update.

Create an oral-argument retrieval view

The full index is useful for research, but oral preparation may need a shorter view. For each issue, list the three to six authorities most likely to be used, the proposition, the pinpoint, and one line on the likely opposing use. Keep the bundle number beside each entry. This creates a quick map without changing the master index.

Do not predict every judicial question. The view should cover the authorities that structure your submission and the obvious contrary sources. If the bench takes the argument somewhere unexpected, the full bundle and index remain available subject to the competition rules.

Use a verification status that can be audited

Give each source one of four statuses: Found, Read, Verified, or Final. Found means the source was located. Read means the relevant portion was actually reviewed. Verified means the proposition, source identity, pinpoint, and status have been checked. Final means the authority is approved for the controlled bundle and any required file-quality check is complete.

Do not let a search-result snippet jump directly to Final. A team member should open the source and confirm the passage. If the legal status or currency of the authority matters, include that check in the verification note.

Record contrary treatment in the same bundle

A bundle is not only a folder for favorable authorities. Include serious adverse or limiting authorities the team expects to address. Mark them clearly so nobody mistakes their role. The index can say "contrary on element 2; distinguish on facts X and Y" without rewriting the source into something favorable.

Keeping adverse sources visible improves rehearsal. It also prevents the team from being surprised by an authority that was found during research but left in someone's personal folder.

Freeze the bundle before the final rehearsal

Choose a point when the working bundle becomes controlled. After that, additions or replacements should be deliberate and recorded. A late authority can improve the argument, but it can also break citations, oral notes, numbering, or compliance if it is added casually.

For each late change, ask: What proposition does this improve? Has the memorial or oral outline been updated? Is the source verified? Does the current competition rule permit its use? Has the index changed? Does another authority now become redundant?

Run a bundle integrity check

Before the final rehearsal, take the memorial and oral outline and verify every authority reference against the bundle. Then reverse the process: scan the Final authorities in the bundle and ask where each is used. Remove dead items or clearly label them as backup. Check that file names open correctly, scans are readable, pages are complete, and the index pinpoints still match.

If the team is using printed material, check that physical tabs or numbering correspond to the same bundle numbers. If the team is using digital files, test the folder on the device that will actually be used, within the competition's rules. Organization that works only on the researcher's laptop is not team organization.

Assign one bundle custodian

Give one team member responsibility for the controlled index and final bundle structure. This does not mean that person owns the research or decides which arguments the team uses. It means changes enter the controlled set through one visible process. A researcher can propose a new authority, correction, or replacement; the custodian checks that the file name, bundle number, proposition, pinpoint, verification status, and affected argument references are updated together.

Keep a short change log for late revisions: date, bundle number, change made, reason, and person who verified it. The log can be only a few lines, but it helps the team distinguish a deliberate update from an accidental overwrite. Once the competition deadline approaches, that trace becomes more valuable than another folder called "latest."

Protect the source of truth

Store the controlled bundle in one agreed location with access appropriate to the team. Do not allow ten near-identical copies to circulate under names such as Final, Final2, FinalLatest, and FinalLatestCorrected. Use a simple version label or date and identify who is responsible for approving a change.

PLC's Mooting Club page provides the broader advocacy context, but the exact handling of authorities in any competition must follow that competition's current rules. The private team system should make compliance easier, not replace those rules.

A useful bundle answers four questions immediately

For every authority, the team should be able to answer: What is it? What proposition does it support or challenge? Where is the exact passage? Where is the file? If those answers are visible in the master index, the bundle is doing its job.

The point is not to build an impressive archive. It is to reduce retrieval friction while preserving source accuracy. Keep the active set controlled, number it consistently, separate clean and annotated copies, verify pinpoints and status, retain serious contrary authorities, and freeze changes before the final rehearsal. Then the team's research remains usable when the memorial, oral outline, and questions from the bench all need the same sources quickly.