Connect review modules into one governed evidence workflow
This guide explains how a Workflow project connects search, screening, PDF management, extraction, risk-of-bias assessment, abbreviation review, writing, outputs, activity history, and Living SLR updates.
What Workflow does
Workflow projects connect multiple SYMPRO AI modules around one review. Instead of managing search, screening, files, extraction, assessment, and writing as isolated projects, the workflow keeps the major stages associated with one master project and makes downstream handoffs more visible.
The workflow is a coordination layer. It does not remove researcher review. Each module still has its own setup, review gates, outputs, and responsibilities, but the master project helps teams understand what is ready, what is blocked, and what data can move forward.
| What you configure | What Workflow connects | What you review |
|---|---|---|
| Project details, deadline, and selected stages | Master project overview, activity, module tabs, PDF Manager, and output files | Stage readiness, required actions, and workflow history |
| Search records or imported studies | AccuSearch and AccuScreener source sets | Synced studies, manually added studies, duplicates, decisions, and conflicts |
| Included full-text studies and PDFs | PDF Manager, AccuSynthesis, ROB, AQUA, and AccuScripter | PDF readiness, extraction status, downstream eligibility, and generated outputs |
The complete Workflow path
A workflow can include different combinations of stages, but the same principle applies: upstream evidence and decisions should be reviewed before downstream modules rely on them.
- 1
Create the master project
Enter the workflow title, description, deadline, and basic review context.
- 2
Select connected stages
Choose the modules that belong in the same review, such as AccuSearch, AccuScreener, AccuSynthesis, AccuScripter, ROB, or AQUA.
- 3
Prepare the study source set
Use AccuSearch to develop and retrieve literature records, or add studies directly in AccuScreener.
- 4
Screen and confirm eligibility
Complete first-pass and full-text review so downstream work uses researcher-confirmed studies.
- 5
Manage full-text PDFs
Use Workflow PDF Manager to attach, upload, replace, retry, and check files before downstream processing.
- 6
Run downstream modules
Use eligible PDFs for data extraction, risk-of-bias assessment, abbreviation review, and report writing.
- 7
Review outputs and updates
Use activity, output files, and Living SLR paths to inspect history, downloads, and documented updates.
Choose the stages that belong in the same review
Workflow setup starts with the master project details and stage selection. The selected stages define which module tabs appear in the project and which handoffs the team can manage from the overview.
| Setup item | Purpose | User responsibility |
|---|---|---|
| Project details | Identify the review, deadline, and team context. | Use a title and description that make the workflow recognizable later. |
| Stage selection | Decide which modules appear in the workflow project. | Select stages that will actually share evidence or outputs. |
| Overview actions | Start or revisit stages from one project view. | Check status messages before moving forward. |
| Optional stages | Add tasks such as ROB or AQUA when they belong to the review. | Do not enable optional stages only because they exist. |
Understand what each module contributes
Workflow can connect the core systematic-review modules and supporting file workflows. AccuScope remains separate from this connected Workflow guide unless the product later adds it to master projects.
Know what moves forward between stages
The workflow is only useful when users understand what passes from one stage to the next. Search records, screening decisions, full-text eligibility, PDFs, extracted content, assessments, and writing outputs have different meanings and should not be treated as interchangeable.
| From | To | What moves forward | Review gate |
|---|---|---|---|
| AccuSearch | AccuScreener | Reviewed article records and search-derived source sets. | Search strategy and article details should be checked before sync. |
| AccuScreener | PDF Manager | Studies that reach full-text review and need document handling. | Eligibility decisions, duplicate handling, and study identity should be clear. |
| PDF Manager | AccuSynthesis | Eligible full-text documents for structured extraction. | PDFs should be matched, readable, and ready for extraction. |
| PDF Manager | ROB | Study files that need risk-of-bias assessment. | Study design and selected ROB type/scale remain researcher responsibilities. |
| PDF Manager | AQUA | Documents where abbreviation extraction supports review or writing. | Text, table, and figure abbreviation results should be checked separately. |
| PDF Manager | AccuScripter | Selected full-text studies and extracted text for report development. | Only eligible, intended files should enter writing. |
| Workflow stages | Output Files | Generated exports, reports, packages, and downloadable artifacts. | Outputs should be reviewed before external use. |
Move from search records to review decisions
When AccuSearch is part of the workflow, reviewed article records can be synced into AccuScreener. This helps avoid recreating the source set manually after the literature search is prepared.
AccuScreener can also be used without AccuSearch. In that path, users add studies directly through the screening project and then continue through duplicate review, first-pass screening, full-text review, and downstream PDF preparation.
Wait for the right gate before using downstream outputs
Later stages can be started only when the required upstream context is available. If earlier evidence, decisions, files, or protocol details change, downstream outputs may need review or regeneration.
| Dependency | Why it matters | Before continuing |
|---|---|---|
| Search changes | New or edited searches can change the article source set. | Retrieve fresh records and resync screening if needed. |
| Screening decisions | Downstream modules should not use uncertain eligibility. | Resolve relevant decisions and conflicts before using full-text evidence. |
| Full-text PDF readiness | Extraction, ROB, AQUA, and writing depend on usable documents. | Attach, extract, retry, replace, or exclude files intentionally. |
| Protocol or criteria changes | Module outputs can become stale when project context changes. | Review affected stages and regenerate outputs when needed. |
| Living SLR updates | Updated evidence should not overwrite the baseline without review. | Compare update outputs and confirm changed evidence before relying on Version 2. |
Use Workflow PDF Manager as the central full-text source
Workflow PDF Manager gives the project a shared place to manage full-text files. Users can attach, upload, replace, retry, and review PDFs before downstream modules consume them.
Use eligible PDFs differently in each module
The same full-text evidence set can support multiple downstream tasks, but each module has a different purpose and review responsibility.
| Module | Uses workflow evidence for | User review |
|---|---|---|
| AccuSynthesis | Template-driven extraction from included papers and supplements. | Check template structure, dimensions, values, missing data, and exports. |
| ROB | Risk-of-bias type recommendations and assessment processing. | Confirm user ROB type and scale before processing. |
| AQUA | Abbreviation extraction from selected documents. | Confirm definitions in text, tables, figures, and relevant candidates. |
| AccuScripter | Report structure, evidence tables, narrative writing, revisions, and versions. | Verify source selection, structure, tables, citations, and final interpretation. |
Use Living SLR when the review needs documented updates
Living SLR connects update work back to the existing workflow. The goal is to make changed searches, new screening decisions, updated PDFs, and report-version changes visible instead of mixing them into the original project state without review.
- 1
Refresh the evidence source
Update the search or import new records that belong to the continuing review.
- 2
Synchronize changed studies
Move additions or changes into screening without treating them as final decisions.
- 3
Screen new evidence
Apply the existing review process to new or changed records.
- 4
Prepare update PDFs
Attach and extract full texts for newly eligible studies.
- 5
Update writing outputs
Use the selected new evidence to create and review the documented report update.
Use history and output files to understand the project state
Workflow projects include activity and file areas because users need to understand what happened, which stages produced outputs, and which downloads support review or handoff.
| Area | Contains | Use it when |
|---|---|---|
| Overview | Stage status, start actions, progress signals, and current blockers. | You need to decide which stage to work on next. |
| Activity | Workflow history, user actions, retries, and stage events. | You need provenance, troubleshooting context, or audit review. |
| PDF Manager | Full-text files, matching, extraction states, replacement, and retry actions. | Downstream modules need reliable PDF inputs. |
| Output Files | Generated files and downloadable artifacts from workflow stages. | You need to inspect or share exports outside the app. |
Run the workflow as a governed review process
| Do | Avoid |
|---|---|
| check_circleChoose workflow stages based on the real review plan. | cancelEnable stages that will not share evidence or outputs. |
| check_circleReview AccuSearch results before syncing to AccuScreener. | cancelTreat synced records as already screened. |
| check_circleResolve duplicate, screening, and full-text decisions before downstream use. | cancelSend uncertain studies into extraction or writing. |
| check_circleUse PDF Manager as the source of truth for workflow full texts. | cancelUpload different file sets separately in every downstream module without checking consistency. |
| check_circleRerun or review downstream stages after upstream evidence changes. | cancelUse old extraction, assessment, or writing outputs after changing studies or PDFs. |
| check_circleUse activity and output files when reviewing project history. | cancelRely only on the current screen after a long workflow. |
Final checklist
- doneThe workflow project title, description, and deadline are clear.
- doneSelected stages match the intended review plan.
- doneAccuSearch records have been reviewed and synced if AccuSearch is used.
- doneStudies added directly in AccuScreener have required metadata.
- doneDuplicates, first-pass decisions, full-text decisions, and conflicts have been reviewed.
- doneEligible full-text PDFs are attached, readable, and extracted or intentionally excluded.
- doneAccuSynthesis, ROB, AQUA, and AccuScripter use the intended evidence set.
- doneGenerated outputs have been reviewed before export or handoff.
- doneLiving SLR updates are compared and checked before relying on updated reports.
Open the module guide for detailed tool instructions
Use this Workflow guide to understand the connected project. Use the module guides when you need detailed instructions for a specific tool, review gate, export, or retry path.