Result
- Experimental unit
- Animal
- Animals
- 10 treated · 10 control
- Treatment − Control
- −2.08 g
- 95% CI
- −2.83 to −1.33 g
- Method
- Welch, two-sided
Compare text, tables and figures with their research evidence. See where numbers or wording drift, distinguish rule-based checks from AI assessments, and review corrections as a new document version.
Select a finding to trace the statement to its evidence and review the suggested correction.
Illustrative draft · synthetic study data · not a SciGround report
Day-14 body weight was compared between treated and control mice (n = 12 per group). Mean body weight was 2.08 g lower in the treated group (95% CI 1.33 to 2.83 g; Welch’s t-test), showing that the treatment causes weight loss.
Figure 1. Day-14 body weight by group. Bars show mean ± error.
Recorded as a declaration; the supplied files do not document it.
The draft says 12 per group; v3 has 10 animals per group, counted by animal.
Delete: n = 12 per group Insert: n = 10 animals per group
Rule-checked. A specified rule compared this item with its evidence.
Sample-size rule: a count in the text must equal the cited result’s n for the same experimental unit.
The rule compares this one count with the result; the rest of the study is checked by its own checks.
| The claim says | What the study shows |
|---|---|
| “2.08 g lower”vs Result · v3 | SupportedEstimate and 95% CI (1.33 to 2.83 g lower) agree. |
| “weight loss”vs Design · v3 | Not measuredOne weighing per animal on day 14; no baseline, so no change within animals. |
| “causes”vs Declarations · v3 | Declared onlyA causal reading rests on random assignment, which is declared but not documented. |
Mean body weight was 2.08 g lower in the treated group (95% CI 1.33 to 2.83 g; Welch’s t-test)Delete: , showing that the treatment causes weight loss.
With assignment records: “…, indicating that the treatment lowered day-14 body weight.”
AI-assessed. An AI assessment. Review its reasoning and suggestion; it can miss problems or raise false alarms.
AI assessment of the wording against the result, design and declarations.
“Weight loss” implies change within animals, but each animal was weighed once: the result is a day-14 difference between groups. “Causes” rests on random assignment, which is declared but not documented. A suggestion to review, not a proven correction.
The caption does not define the bars, and Figure 1 was supplied as an image only.
Then the caption is checked against the plotted values.
Not checkable. The supplied evidence does not allow this check yet.
The figure-definition check needs the plotted values or their source.
Nothing supplied says whether the bars show SD, SE or a confidence interval, and the definition is not inferred from the image. The gap stays in the report until the material is supplied.
Review corrections as a new document version, with the original preserved. Submit the revised draft to check it again.
Findings cover the text, tables and figures you submit, and each says how it was reached: rule-checked, AI-assessed or not checkable.
Text, tables, figures with source data, and the verified results.
Numbers, units, directions, and claims are matched to their sources.
Corrections come as a new version with reasons and a diff.
The corrected draft is checked again before it goes back to your document.
Generate a package with methods, results table, assumptions, limitations, checked scope, and the Record reference. Every number traces to its evidence, and display rounding never flips a decision.
Submit a methods or results section with its tables and figures. SciGround checks numbers and rounding, sample sizes and experimental units, group direction, units, methods, axis and error-bar definitions, and how strongly each claim is worded.
Rewritten and shortened text is checked again. Overstatement—non-significance as equivalence, association as causation, a limited result as a full guarantee—is flagged, and so is wording that weakens a sound result unnecessarily.
SciGround drafts corrections for numbers, wording, and figure notes, keeps the original, and checks the new version again with a clear diff and reasons.
Bring documents from GitHub, Word, or Google Docs with their versions. Corrections come back as a separate branch or pull request, a new document, or a diff—the original is never overwritten.
The package lists every result you planned in advance, significant or not, drawn from the study’s own Records. A reviewer can fetch them by study ID and compare them with the manuscript.