Specimen sheet
Paper anatomy
Technical papers look different from one field to the next, but they share a skeleton. Below is a mock paper, invented for practice, laid out like the real thing. Open any part to read its field note: what it is for, what to look for, what should make you pause, and how long it deserves.
The study below does not exist. Its numbers, if any, are illustrative, and its references describe what a citation does rather than pointing at real work.
The annotated mock paper
Left: the mock paper. Right: the margin note for each part. Use the button on each note to open the full field note.
Mock preprint · invented for practice
Fair Queues for Shared Trailheads: A Proposal and a Mock Evaluation
- What it is
- The paper’s smallest summary. Good titles name the subject and often the move: a proposal, a comparison, a measurement, a survey.
- Look for
- The verbs and qualifiers. “A Proposal and a Mock Evaluation” tells you the evidence is modest. Titles that say “Towards” or “A Note on” promise less than titles that say “Solving”.
- Red flags
- A title that claims more than the abstract delivers. Mark the gap and check it at the end.
- Time
- A glance. Then ask what you expect to find.
- What it is
- The names of the authors and the organisations they work for or study at, sometimes with a note about who funded the work.
- Look for
- Whether the authors work in the area they are writing about, whether they belong to a group that builds or sells the thing being evaluated, and any funding or competing-interest statement.
- Red flags
- An evaluation written by the people who built the system is not worthless, but it is not independent either. Read the results with that in mind. A missing affiliation is a question, not an accusation.
- Time
- Under a minute.
Abstract
Popular trailheads often have a single sign-in sheet and no agreed order of departure. We propose a lightweight turn-taking scheme, the Lantern Rule, in which each group takes a numbered lantern on arrival and sets out in lantern order. In an illustrative simulation, the Lantern Rule shortened the longest waits compared with informal first-glance-first-served ordering, while the typical wait stayed similar. We argue that the scheme is simple enough to adopt without new infrastructure. Limitations include the simulated arrival pattern and the assumption that groups comply.
- What it is
- A short summary written by the authors: the problem, what they did, what they found, and why it matters. Most readers decide here whether to continue.
- Look for
- Underline the claim sentence and the evidence sentence. In the mock abstract, the claim is that the rule “shortened the longest waits”, and the evidence is “an illustrative simulation”. Notice how much smaller the second is than the first.
- Red flags
- Findings with no mention of method, verbs like “proves” with nothing behind them, and abstracts that bury the limitation in the last clause.
- Time
- Two minutes. Reread it after you finish the paper; it will say something different the second time.
Keywords: trailheads; queueing; fairness; lightweight protocols
- What it is
- A short list of terms the authors want to be found by. Not every venue prints them.
- Look for
- Terms you do not know yet. Each one is a doorway into the literature and a candidate for your glossary.
- Red flags
- Hardly any. If the keywords describe a different field than the title, the paper may be borrowing methods from somewhere else, which is worth knowing.
- Time
- Ten seconds, and a note of anything unfamiliar.
1 Introduction
Anyone who has arrived at a busy trailhead knows the quiet negotiation over who goes first. Most places rely on habit, and habit favours the confident. This paper asks whether a rule simple enough to explain in a sentence could make the order fairer.
We make three contributions. First, we define the Lantern Rule. Second, we compare it with two common practices in a small simulation. Third, we discuss when the rule is likely to break down.
- What it is
- The authors’ case for why the work matters, what is missing from existing work, and what they will contribute. It often ends with a list of contributions and a roadmap.
- Look for
- The contributions list. It is the paper’s own checklist: after reading, ask whether each item was delivered. Here, the third is “discuss”, which is a softer promise than the first two.
- Red flags
- A problem described so broadly that any result would seem to solve it, and a gap that is simply the authors’ own preference.
- Time
- Read it fully, at normal speed. Introductions are written to be read.
3 Method
The Lantern Rule. A lantern is a numbered token. On arrival, each group takes the next lantern. Groups depart in lantern order, and a group without a lantern waits until all numbered lanterns have been used.
- Arrive and take the next lantern.
- Wait for your number to be called.
- Depart; return the lantern.
Simulation. We generated arrivals from a simple random process at a single trailhead and compared three rules: first-glance-first-served, a paper sign-in sheet, and the Lantern Rule. We assume that every group follows the rule it is given.
- What it is
- The recipe: definitions, procedure, data sources, and the setup of any experiment or model.
- Look for
- Definitions to copy into your glossary, and every sentence that begins “we assume”. In the mock method, compliance is assumed outright. Ask whether you could repeat the work from this description alone.
- Red flags
- Vague setup (“a simple random process” with no detail), choices made without reasons, and comparison rules that are weaker than what people really use.
- Time
- Slow down. This is the load-bearing part. Skim it first, then read it properly on your second pass.
4 Results
Figure 1 shows the relative length of the longest waits under each rule. Table 1 summarises the comparison in words.
| Rule | Typical wait | Longest waits |
|---|---|---|
| First-glance-first-served | Baseline | Longest |
| Sign-in sheet | Similar | Medium |
| Lantern Rule | Similar | Shortest |
- What it is
- The findings, reported as text, figures and tables. Captions should let each figure stand on its own.
- Look for
- What is on each axis, what is being compared with what, and whether the text describes the picture accurately. Here, the figure shows a ranking but no scale, so you cannot tell whether the difference is large or trivial.
- Red flags
- Missing units or scales, no sign of how much the results vary from run to run, a baseline nobody would really choose, and prose that says more than the figure does.
- Time
- Look at figures early, then come back for the prose after the introduction. Give the key figure real time.
5 Discussion
These results show that the Lantern Rule is fairer than existing practice and should be adopted at trailheads. The rule is cheap, easy to explain, and does not depend on any one person’s patience.
- What it is
- Interpretation: how the findings answer the original question, what they imply, and how they connect to earlier work.
- Look for
- The jump from results to recommendation. In the mock paper, a simulation of waiting times becomes a claim about fairness and a call to adopt the rule. Each of those is a step the evidence has not taken.
- Red flags
- Stronger verbs than the results section used, new claims that were never tested, and recommendations that follow from the authors’ values rather than from the data.
- Time
- Read carefully, side by side with the results. Interpretation is where papers drift.
6 Limitations
Our arrivals are simulated, not observed, and bursts of arrivals may behave differently. We did not test what happens when groups ignore the rule, or when groups differ greatly in size.
- What it is
- The authors’ own list of what the study cannot support. In many papers it is short, and it is among the most useful pages.
- Look for
- Compare it with the discussion. The mock limitations say compliance was untested, yet the discussion recommends adoption. When the limitations undercut the conclusion, trust the limitations.
- Red flags
- No limitations section at all, or limitations that are trivial while the real weaknesses go unmentioned.
- Time
- Read it early if you can. It tells you how far to trust everything else.
7 Conclusion
We proposed the Lantern Rule and compared it with two common practices in a simulated setting. Within the limits above, it shortened the longest waits without lengthening the typical one. Future work should observe real arrivals and test what happens when groups do not comply.
- What it is
- A restatement of what was done and found, and what remains open.
- Look for
- The hedges: “within the limits above”, “in a simulated setting”. Compare the conclusion with the abstract and the title. The distance between them is how much the framing grew.
- Red flags
- New claims that appear for the first time here, and a conclusion that sounds more confident than the results did.
- Time
- Read it right after the abstract. It is the second-best summary the paper has.
References
- [1] A foundational text on waiting lines, cited for basic definitions.
- [2] A discussion of fairness in ordering, cited for the idea of first-come order.
- [3] A descriptive study of informal turn-taking, cited for background only.
- What it is
- The list of work the authors drew on. Each entry should be traceable. The mock list describes what each citation is doing rather than pointing at real work.
- Look for
- Which citations carry claims and which are courtesy nods. Follow the one or two that support the central claim. Also note what is absent: a rival approach nobody cites is a signal.
- Red flags
- Central claims supported only by the authors’ own earlier work, entries you cannot find, and a list that is mostly very old or very new.
- Time
- Ten minutes at most on a first read. It becomes your reading list for later.
Appendix A · Simulation details
Parameters, random-number settings and extra tables for repeating the simulation are listed here, so that the main text can stay short.
- What it is
- Material that supports the paper but would clutter it: proofs, extra tables, detailed settings, survey questions.
- Look for
- Whatever lets you check the result for yourself. If the main text says “a simple random process”, the appendix should say which one. If it does not, you have found a gap.
- Red flags
- Important results that appear only here, and details promised in the text that are missing.
- Time
- Skip until you need it. Go straight there when a claim seems too convenient.
Using the specimen
Why this order, and when to break it
The suggested order puts the cheapest, most informative parts first. The title, byline and abstract cost a couple of minutes and tell you whether the paper is for you. The conclusion and the figures cost a few more and tell you what was found. Only then does it make sense to spend attention on the introduction, the method and the discussion, which is where the argument is actually made.
Real papers vary. Some fields put the method last, some fold related work into the introduction, and many technical reports have no abstract at all and open with an executive summary instead. White papers in particular may blur the line between explanation and advocacy, so read the part that says what the authors want you to do with extra suspicion. Use the skeleton as a checklist rather than a rule: ask of every document “where is the claim, where is the evidence, and where do the authors admit what they cannot show?”
When you have walked the mock paper, take the same routine to something you have to read. The reading lab lets you mark the parts as you go, and the 30 questions give you something to ask of each one.