Journal data editor ready
Increasingly, journals require a data editor sign-off before publication. Our packages pass these checks on first submission.
Service · 06 of 07
Code audit, replication package, README, and data documentation. The standard journals with open-data policies now require — and that referees increasingly check.
What's included
The engagement
Day 0
We discuss your research question, data, and timeline. You'll know by the end of the call whether this service fits — if it doesn't, we'll say so and suggest what does.
Day 1–2
A detailed scope with total cost, timeline, and deliverables. No surprises, no scope creep — you approve before any work begins.
Agreed timeline
Annotated code, documented decisions, and a report structured so that you understand every choice. Two rounds of revisions included as standard.
The case for reproducibility
Increasingly, journals require a data editor sign-off before publication. Our packages pass these checks on first submission.
Packaged to the standards of open-data repositories. DOI-citable on day of publication.
renv (R) or requirements.txt / conda (Python) to freeze the computational environment at the time of analysis.
We catch errors in the audit — including cases where the reported number doesn't match the script output. These are fixed, not smoothed over.
Pricing
Every engagement starts with a free 20-minute call. We scope it together, then quote a fixed price before you commit.
Consult
Typically includes