
- systematic review workspace
- 6 min read
- By George Burchell
- View publications on PubMed
- ORCID
Saving your SRT work: browser drafts, exports, and backups
To save your systematic review work in SRT, stay signed in until the tool shows the draft saved to your account, then export the file into your review folder. A browser draft is not a backup. Signed-in work lives in this browser, scoped to your account, and on the account when workspace sync is on, which it is unless turned off for the site. The tools are Search Builder, Research Gap Finder, the manuscript outline, the PRISMA checklist, and the PRISMA flowchart. If site data is cleared, or you open a new machine, recover from the account draft on Saved work or from the exported file. The browser copy does not travel.
Where a draft lives
The local copy is browser storage for this signed-in account, on this browser, at this site address. A draft on the live site is not the draft on a preview deployment or on localhost. The tool reads and writes that local copy while you are signed in.
The account holds one current draft per tool. Saved work lists it, plus up to five previous downloads. A previous download is kept when an export succeeds. A sixth, different export drops the oldest of those five. Download on Saved work rebuilds that file. It does not load the snapshot back in as the current draft, and it does not keep the Word, PDF, or image bytes themselves. Leave the tool only after it shows the draft saved to the account. "Saving…" is not that. "Saved locally only" means the account does not have this copy.
The tool does not merge two copies. A newer account draft replaces this browser. A newer browser draft is saved to the account when sync is working. If sync is unavailable, the tool says the draft is saved on this browser only. If the draft is too large for the account, it says a copy remains in this browser.
Clearing a tool removes the current draft. Previous downloads already on Saved work stay.
What crosses devices, and what does not
When sync has saved, a new browser on the same site can open the current draft after you sign in to the same account. Another person’s account cannot see it. This is not a shared team workspace, and it is not a history of every edit.
| Tool | Kept in the current draft | Export as well |
|---|---|---|
| Search Builder | Question, aspects, blocks, the one selected database, filters, and selected aspects. With no question and no blocks, nothing is saved to the account. | Word, text, CSV, or JSON. Write the search date in your log. The draft does not store it. |
| Research Gap Finder | Scope, citations, classifications, map settings, and gap decisions. Imported citations can include titles and abstracts. | Markdown or Word, plus the original citation files. |
| Manuscript outline | Section answers, including the title page and the introduction. | Word, text, or PDF, for the sections you select. |
| PRISMA Checklist | The main checklist and the abstract checklist. | PDF or Word. |
| PRISMA Flowchart | Settings and the identification, screening, and inclusion counts. | PNG or SVG, or a PDF from the print dialog. Keep the count log. |
Deduplication does not save the upload or the archive. Download the RIS and audit reports, and keep the original database exports. Search Translator does not keep a draft. Copy the translation into the search log with the source query and the target database. The Search Block Library is a shared catalog. Browsing it does not save your review. A block is yours once it is in a Search Builder draft or in a file you downloaded.
Signing out does not clear the local draft. Clearing site data does. Closing a private-browsing window drops that session’s local copy. A file in the review folder is not a one-click import back into the tool.
A cleared browser, or a new machine
You have been building a search on a shared computer. You close the tab. Someone clears the browser’s site data. Or you open a laptop that has never held the draft. If the only copy was in that browser, it is gone.
- Before you stop, download Word, text, CSV, or JSON into the review folder. Name the version, and write the database and the search date in the log.
- Stay signed in until the draft has saved to the account. Saved work should show the current Search Builder draft. If the tool says the draft is on this browser only, or too large for the account, the file from step 1 is the copy that survives.
- On the new machine, use the same site address and the same account. Open Search Builder, or open the current draft from Saved work. If the account copy is newer, the tool loads it.
- Saved work can rebuild up to five earlier downloads. That is the export again, not the live draft. If you never exported and sync never saved, there is nothing to rebuild.
The checklist, the flowchart, the outline, and Research Gap Finder use the same path. Deduplication and Search Translator do not.
At a stopping point, export, record the date and version, and put the file next to the inputs. The Quick Start Guide is the wider sequence. The handoff that depends on a download you must keep is deduplication counts into a PRISMA flowchart. The browser draft is convenient on this machine. The account draft and the exported file are what you still have after the browser is wiped.
What the review folder should hold at the end
The exports map onto the reporting checklist. PRISMA reporting guidelines explained lists which file fills which item. A practical minimum:
- One search strategy download per database, with the search date, for PRISMA 2020 item 7.
- The original database exports, the deduplicated RIS, and the deduplication audit, for the identification counts.
- The grey literature search log for the "other methods" column; grey literature searching shows the columns.
- The flowchart file and the count log behind it.
- The checklist export with the page or section for each item.
SRT does not store your screening decisions. On a team, the screening queue is a shared file or screening tool held by one coordinator, as in managing large-scale reviews. Keep a dated copy of it in the same folder.

About the Author
Connect on LinkedInGeorge Burchell
George Burchell is a specialist in systematic literature reviews and scientific evidence synthesis with significant expertise in integrating advanced AI technologies and automation tools into the research process. With over four years of consulting and practical experience, he has developed and led multiple projects focused on accelerating and refining the workflow for systematic reviews within medical and scientific research.