Pending work moves
Only pending assignments in explicitly selected targets are eligible to change.
The page is taking longer to load.
Change Team lets an administrator move pending FPS, FTR, and reviewer work without rewriting completed decisions. This guide explains the safeguards, arm rules, eligibility pools, distribution strategies, preview checks, and the correct lock–apply–unlock procedure.
Change Team is a controlled reassignment workspace for active screening projects. It separates FPS and FTR, separates Arm A and Arm B in double review projects, and treats reviewer work as an independent target. Every operation is previewed before it can be applied.
Only pending assignments in explicitly selected targets are eligible to change.
Completed analyst and reviewer decisions are preserved by the reassignment planner.
Preview, revision validation, an atomic update, and an audit receipt protect the operation.
| Work or project state | What Change Team does |
|---|---|
| Pending work in a selected target | May be assigned to another eligible owner according to the selected strategy. |
| Pending work in a preserved arm or phase | Remains with its current owner and its saved pool is not changed by that operation. |
| Completed analyst decision | Remains attached to the analyst who completed it and is not reset to pending. |
| Completed reviewer decision | Remains completed and is not redistributed. |
| Definitive agreement | Becomes final with no reviewer assignment and is counted as no adjudication required. |
| Review required but unassigned | Remains visible as an administrator exception and can receive an independent reviewer through Change Team. |
| Duplicate secondary study | Duplicate handling and restoration snapshots are preserved and reported separately in Preview. |
| Study with an arm anomaly | Is preserved/skipped or requires acknowledgement and repair; the system never guesses the arm. |
Do not treat reassignment as an ordinary team edit. It changes study-level ownership and therefore uses a controlled sequence.
The available cards and locked controls depend on the project’s screening configuration.
| Project configuration | Arm A | Arm B | Important rule |
|---|---|---|---|
| Single review | One human analyst assignment target | Not used | Each study has one analyst screening assignment. |
| Human double review | Human analyst | Different human analyst | Each study is screened independently twice. |
| AI Assistant double review | Human analyst with optional assistance | Different human analyst with optional assistance | AI assistance does not replace either human owner. |
| Double Review (AI+Humans) | AI Screener, locked | Human analyst | Administrators can change the human Arm B pool and assignments, not AI Arm A. |
| AI Screener single screener | AI Screener, locked | Not used | AI ownership is fixed; reviewer controls remain separate where configured. |
A double review study cannot assign the same human analyst to both Arm A and Arm B.
An analyst may be eligible for both pools, provided study-level assignments remain independent.
In double review AI Screener mode, AI owns Arm A and the human reassignment controls apply to Arm B.
AI Assistant supports human screening; both double review arms remain human assignments.
An eligibility pool defines who may receive pending work for one phase and arm. FPS Arm A, FPS Arm B, FTR Arm A, and FTR Arm B are separate pools. The people available during FTR may differ from those who performed FPS. FPS Unsure and decision conflicts wait for reviewer resolution before ordinary FTR processing. If both FPS arms agree on Include but their criteria differ, the study may enter FTR while its FPS criteria review remains pending. An administrator can also explicitly approve an eligibility override.
| Control or count | Meaning |
|---|---|
| Assigned | Total saved assignments shown for that phase and arm. |
| Pending | Assignments that may be redistributed when this target is selected. |
| Completed | Assignments retained as historical screening decisions; these are not reassigned. |
| Current owner table | Workload grouped by the person currently stored on each study. |
| Eligible analysts | The project-level pool allowed to own pending assignments for that specific phase and arm. |
The Phase selector controls whether the operation can affect FPS, FTR, or both. Each visible arm then has its own target switch.
| Strategy | Use it when | How ownership is chosen | Main check |
|---|---|---|---|
| Equal distribution | Share pending analyst work in automatically sized contiguous study-ID blocks. | Chooses a preferred owner for each selected arm per block; reviewer work remains conflict-aware. | Inspect the block table and actual changed counts in Preview. |
| Weighted distribution | Give some owners a larger or smaller planned share. | Uses positive numeric weights within each selected target. | Every selected owner weight must be greater than zero. |
| Selected studies | Move named studies to a specific analyst or reviewer. | One explicit study/phase/target rule at a time. | The owner must be eligible and independent for that study. |
| Study ID ranges | Move an inclusive block of numeric study IDs to one owner. | Applies the checked range rule only to pending eligible work. | Check range counts, overlaps, and opposite-arm ownership first. |
For analyst arms, equal distribution automatically calculates near-equal contiguous blocks of pending studies in study-ID order; there is no block-size input. For example, 300 studies with three analysts in each arm form three 100-study blocks, while two Arm A analysts and three Arm B analysts can share 240 studies in six 40-study blocks. Each block has one preferred analyst per selected arm, and the two people on a double review study must differ. Arm A stays fixed to AI Screener in AI+Humans projects. Completed decisions and unselected arms remain with their existing owners, so the preview may show exceptions to a block's preferred owner. Reviewer work still follows the independent, conflict-aware assignment rules when it becomes required.
Selected Studies and Study ID Ranges change only the studies named by their rules. They do not redistribute every pending study in the arm.
The project reviewer list is an eligibility pool, not an assignment to every study. AccuScreener waits for the required FPS or FTR screening decisions, then assigns one active independent reviewer only when the outcome is Unsure or conflicted. In sole AI Screener projects, definitive AI decisions remain final but are also available to selected reviewers as optional quality-assurance samples.
| Rule | Required behavior |
|---|---|
| Independence | The reviewer for a study cannot also be one of that study’s human analysts. |
| Definitive agreement | Accepted Include/Exclude agreement is completed automatically, marked as no adjudication required, and is not distributed to a reviewer. |
| Review-triggering outcome | Unsure, a decision conflict, or a criteria conflict creates required reviewer work. A definitive sole-AI result is optional QA work. |
| Automatic assignment | The active independent reviewer with the lowest unresolved workload is selected, with deterministic rotation for ties. |
| No independent reviewer | The screening decision is saved and the study is marked Review required, unassigned; completed analyst work is not rejected. |
| Equal or weighted mode | Turning Reviewer Assignment on targets only unresolved review-required work in the selected phase scope. |
| Selected studies or ranges | Reviewer rules apply only to studies that genuinely require review. Awaiting-screening and no-adjudication studies are preserved. |
| Completed reviewer decision | The completed review is preserved and is not reset to pending. |
| Reviewer removal | All remaining pending reviewer assignments must still have a valid planned owner. |
| Analyst change overlaps a preserved reviewer | Preview blocks the operation. Turn Reviewer Assignments on and provide an active independent replacement pool, or choose a different analyst. |
Preview does not write to the database. It calculates the proposed result against the current project revision.
FPS and FTR update counts show how many study records the operation will modify.
Confirms which phase, arm, and reviewer targets can change and which remain untouched.
Shows pending before, pending changing, pending preserved, and completed preserved.
Shows how pending and total workload moves between named owners.
Explains pool removals and pending work that would become invalid or orphaned.
Reports preserved duplicate studies and historical arm-integrity problems.
Explains work omitted because it was completed, duplicated, outside scope, ineligible, or not selected.
Connects Preview to the exact source state and later audit receipt.
Blocking errors appear in the preview panel and, when phase/arm information is available, on the relevant assignment card.
| Message or condition | Why it is blocked | How to resolve it |
|---|---|---|
| Screening is not frozen | Analysts or reviewers could submit decisions while ownership is changing. | Lock Screening and regenerate Preview. |
| Pending assignment would be orphaned | A removed pool member still owns pending work that the selected rules do not move. | Keep that person in the pool or move all of their remaining pending work. |
| Analyst already assigned to the other arm | The rule would give both double review arms of one study to the same person. | Choose another eligible analyst or adjust the studies/range. |
| No independent reviewer | Every proposed reviewer conflicts with one of the study’s human analysts. | Add an eligible reviewer who is not assigned to either arm. |
| Arm assignment anomaly | Historical decisions do not resolve cleanly to one Arm A and one Arm B assignment. | Preserve/acknowledge skipped records or repair the affected project data before reassignment. |
| Overlapping rules | Two targeted rules attempt to assign the same phase, role, and arm for a study. | Remove or split the overlapping selected-study/range rule. |
| No pending work | The selected target contains nothing eligible to redistribute. | Preserve the target or select another phase/arm with pending work. |
| Stale preview | The project revision, assignments, or request changed after Preview. | Refresh workload, review the latest state, and generate Preview again. |
| Invalid pool or weight | A selected target has no eligible owner or contains a non-positive weight. | Add an eligible person and use weights greater than zero. |
Apply rechecks the preview hash and project revision. Study assignments, selected project pools, assignment revision, FTR statistics where applicable, and the reassignment receipt are committed in one transaction.
If assignments or team selections changed after Preview, generate a new preview.
The assignment, pool, revision, statistics, and receipt writes commit together or roll back together.
The result records operation ID, revisions, time, selected targets, and changed counts.
Review refreshed workloads first; active sessions must close before Finish and Unlock is enabled.