Save a run preset you can repeat — reduce “did I do the same steps?” uncertainty with reproducible settings and manifests.
What this tool is for
Create reusable “recipes” for ReportMedic tools and apply them consistently across multiple file drops.
Storage:Local (browser)
This page does not run background cron jobs on GitHub Pages. Instead, it gives you a clean way to:
save presets, apply them to batches, and produce manifest + audit files for repeatable work.
Presets: 0Runs saved: 0Last save: —
Safety: your file is read locally in your browser. Use Masker if you need to share samples.
Quick start
3 steps
1) Create a preset
Choose a tool + options, then save it with a name.
2) Drop files
Upload one or many files. A manifest can store file hashes for traceability.
3) Generate run package
Download a “Run Manifest” JSON + “Audit Report” to document exactly what was done.
Optional: you can include the manifest in tickets/emails to prove settings used (especially for compliance or QA).
A) Build a preset
Tool + settings (saved locally)
Version 1
Settings (JSON)
Keep it short: only what matters.
Best practice: name presets like Tool • Purpose • Grain (example: “Outliers • Store weekly spikes”).
B) Preset library
Search, load, duplicate, delete
Selected: none
All presets are stored in your browser’s local storage. Export them if you want a backup.
C) Batch run package
Drop files + generate manifest + audit
Files
Drop here or use the file picker
Hash:SHA-256
Queued: 0Hashed: 0Duplicates: 0
The manifest can be used as a repeatable “run recipe” across machines. If you export presets too,
you can fully reproduce your setup later.
Run history
Saved run manifests you generated earlier
When
Preset
Tool
Files
Hashed
Notes
Actions
History is local. Use “Download run manifest” to store a copy outside the browser.