Methodological compliance

For academic-style nonfiction. Checks whether you've covered the standard methodology beats most journal reviewers expect.

methodological-compliance report card

What it measures

For manuscripts flagged as academic (research paper, thesis, literature review, evidence-based nonfiction), the analyzer looks for the presence and adequate development of five expected structural beats that most peer-reviewed venues expect to see. These aren't arbitrary preferences — they're what the standard IMRAD (Introduction, Methods, Results, and Discussion) template and its variants have codified over decades of scientific and academic publishing.

The five checks are: a hypothesis or research question (explicit framing of what the piece is arguing or investigating); a methods section (how the evidence was gathered — data collection, source selection, analytic approach); a data or evidence description (what the evidence actually consisted of — sample sizes, corpus scope, source qualities); a limitations section (an honest accounting of what the methods can't establish or what constraints affected the results); and a conclusion tied back to the hypothesis (the closing that explicitly returns to the opening question and states what the evidence does or doesn't support).

Each beat resolves to one of three states: found (green checkmark — the analyzer identified a clearly present section covering that beat), missing (red cross — no such section was detected), or thin (amber — a section was found but is unusually short or superficial relative to the size of the manuscript). The output surface is a checklist rather than a score — this is a pass/fail checklist because journal reviewers treat these beats that way.

The report doesn't judge the quality of what's in each section — it doesn't tell you whether your methods are good, whether your data is sufficient, or whether your limitations are honest. It tells you whether the section exists in a form a reviewer can find. Depth of methodological rigor is the province of your discipline's peer review; presence of the structural beats is what this report catches.

Why it's useful

Journal reviewers reject papers for missing standard sections more often than for weak arguments. It's a common frustration: you spent three months on the argument and got a desk-reject because you didn't have a formally-labeled Limitations section, or because your Methods was buried inside the Introduction rather than standing on its own. This report gives you the reviewer's structural checklist before you submit — the same pass they'll do in the first two minutes of reading, done for you in advance.

The typical scenario: you're finalizing a thesis chapter or a submission draft. Run Methodological compliance. Four of the five beats come back green; Limitations comes back red. You know exactly what to write: a Limitations section. The report has saved you the desk-reject cycle by naming the structural gap before the reviewer does.

For thesis writers this report also functions as a rubric. Most graduate programs have formal expectations for chapter structure that mirror the same five beats — a chapter that skips Methods or handwaves at Limitations tends to come back from committee with revision demands. Running this report chapter by chapter as you draft catches the same gaps early.

Read this alongside Argument flow (which checks the internal shape of your arguments paragraph by paragraph rather than the outer structural beats) and Literature synthesis (which checks whether your citation density is adequate for the weight of your claims). The three together give you the "structure, argument, evidence" triad of academic-writing checks.

How to read it

The card renders as an animated checklist — one row per expected beat, in order (Hypothesis / research question, Methods section, Data description, Limitations section, Conclusion tied to hypothesis). Each row has a leading icon in a colored circle — a green ✓ if the beat is present and identifiable, a red ✗ if the analyzer couldn't find it — and the name of the beat as the row label. Rows fade in one at a time with a small staggered animation on first render, so the checklist feels like it's being ticked off rather than dumped all at once.

The collapsed card summary in the reports rail shows a one-word status ("ok" if everything's found, "missing" if any beat is red), so you can see the state of the compliance check at a glance from the panel without expanding. When the status is "missing" the card is worth opening immediately — a single missing beat is much more actionable than a single soft-flag on one of the more descriptive reports.

Read the checklist top to bottom. Missing beats need writing: the fix is almost always literally adding a section labeled with the beat's name and covering the expected content. If the analyzer flagged Limitations as missing, add a section titled "Limitations" (or the discipline-standard equivalent) and cover what constraints affected your methods, what the evidence can and can't establish, and what future work would address. Re-run the report and the row should flip to green.

Thin flags (where the analyzer found a section but it's underdeveloped) don't have their own tier in the current UI — they render the same as missing. If the row is red but you're sure the section exists, expand the section in your manuscript to make the beat more obvious; usually a clearer heading and one more paragraph of explicit content is enough for the analyzer to catch it.

When to ignore it

For fiction, poetry, essays, memoirs, narrative nonfiction, and anything else that isn't structured as an argument-and-evidence academic piece, this report is trivially "missing everything" — the five expected beats don't apply and shouldn't be expected to. Turn it off in the panel toggles (in the Reports accordion on the left sidebar) so it doesn't clutter your reports rail with permanent red crosses.

Even within academic writing, some legitimate structures deviate from IMRAD by convention. Philosophy papers often don't have a Methods section in the empirical sense — the method is argumentation itself. Long-form review articles frequently fold Data description into the body rather than putting it in a dedicated section. Historical or interpretive humanities work rarely has a formal Limitations section labeled as such — the limitations tend to be woven into the discussion. In all these cases the report will flag genuine gaps as if they were errors; use judgment.

Grant proposals, book chapters, conference abstracts, and other academic-adjacent formats have their own structural conventions that don't map cleanly to the five beats. If you're writing to a specific journal's or grant program's template, follow that template rather than this report — the compliance the report is checking is generic-academic, not venue-specific.

And any manuscript that's clearly a fiction draft mistakenly analyzed as academic (this happens occasionally when a fiction manuscript uses formal-register vocabulary throughout) will produce meaningless output; the fix is to turn the report off rather than trying to satisfy checks that aren't relevant.

How to run it

  1. Click Write in the left sidebar and open the document you want to analyze.
  2. Open the right-side rail: click the Reports button in the editor's top toolbar (the bar-chart icon).
  3. In the rail header, click the Reports tab.
  4. Scroll to the Methodological compliance card under the Academic heading.
  5. Click the card to expand it. First-time runs take 5–20 seconds; a spinner in the header shows while the LLM streams. Cached results render instantly. Use re-run after adding or removing a methods section.
  6. The card renders a checklist: each expected beat (Hypothesis, Methods section, Data description, Limitations section, Conclusion tied to hypothesis) gets a green ✓ if found or a red ✗ if missing. The collapsed summary shows a one-word status ("ok" / "missing").