The Spain coordinator duty-to-evidence map
By Regulated Workforce Operations Editorial Desk · Publication editorial team
Updated
Use this map to turn a job description into an employment specification and a trial-task allocation. It identifies the decision that a support worker must not acquire by accident, the operational owner and the evidence that would make the boundary reviewable. The rows below are the completed fictional specification for the Spain case, not assertions that a real sponsor has approved it.
Eight baseline duties are proposed. D09 and D10 are excluded additions used to test what happens when the role changes. “Required evidence” describes the record to obtain; it does not assert that it exists. Every row binds to the official source family that informs the interpretation. The precise permission design is our worked operating proposal.
| Duty | Permitted action and boundary | Operational owner | Data in the proposed design | Evidence and source binding |
|---|---|---|---|---|
| D01 · Request missing site CVs and GCP training evidence | Send the sponsor-approved request; record receipt only Boundary: No authority to decide investigator suitability | Sponsor clinical-operations lead owns acceptance; investigator/institution supplies its evidence | Named site staff and professional records in approved repository | Request-list version; qualification reviewer; role training record GCP-R3 · ES-TRIAL |
| D02 · Maintain the startup tracker | Enter received / missing / under review; never turn receipt into approval Boundary: A green tracker cell is not site authorisation | Sponsor clinical-operations lead owns status rules and readiness decision | Document identifiers, site contacts and dates | Tracker field rules; separate reviewed-by field; correction history GCP-R3 · EU-CTR |
| D03 · Prepare a document bundle | Assemble approved versions for a sponsor reviewer; no independent finalisation Boundary: No CTIS Submitter role in the baseline | Sponsor regulatory owner approves submission content and sequence | Approved study documents; no participant records in baseline | Document versions; reviewer acceptance; destination check GCP-R3 · CTIS · AEMPS |
| D04 · Arrange site calls and chase milestones | Schedule and escalate delays; no promise that recruitment may begin Boundary: Scheduling is not a decision to activate a site | Sponsor study lead decides sequencing with responsible site personnel | Site staff contacts and calendars | Escalation recipient and backup; meeting action record EU-CTR · GCP-R3 |
| D05 · Receive an unexpected consent or safety question | Route immediately through the approved trial escalation process; do not assess it Boundary: No clinical response, seriousness assessment or reporting decision | Investigator/medical/safety owners handle their respective duties; sponsor maintains its reporting process | Unexpected sensitive message: preserve in approved restricted channel | Named primary and backup; receipt acknowledgement; failed-delivery escalation EU-CTR · ES-TRIAL · GDPR |
| D06 · Use the controlled study repository | Access only assigned records; no bulk export or sharing to HR tickets Boundary: Employment support does not need trial documents by default | Sponsor records/system owner controls permissions; privacy owner approves processing design | Site professional records; no general participant-level access | Permission export; access test; retention instruction; access review date GCP-R3 · GDPR |
| D07 · Take leave or return to work | Inform employment contact and study manager through separate channels Boundary: Leave approval cannot appoint a trial delegate | Employer handles employment process; sponsor appoints qualified study cover | Employment record separated from study handover | Employer case ID; coverage owner; access and duty recheck on return ES-LABOUR · GCP-R3 |
| D08 · End assignment or leave employer | Hand over open tasks; lose work access at authorised cutoff Boundary: Deleting the account is not deleting the trial record | Sponsor system owner closes trial access; employer closes employment obligations | Study records remain with authorised custodian; employment documents use agreed channel | Revocation event and session check; record custody; employment confirmation GCP-R3 · GDPR |
| D09 · Proposed addition: submit CTIS application | Outside baseline; a named authorised submitter performs the task until reassessed Boundary: Technical permission alone is not sufficient task authorisation | Sponsor regulatory owner decides documented allocation and system role | CTIS application and associated documents | Change approval; competence evidence; CTIS role grant; employer scope response CTIS · GCP-R3 · EU-CTR |
| D10 · Proposed addition: decide eligibility or consent response | Outside baseline; refer to investigator/qualified clinical owner Boundary: Do not rename clinical judgment as administrative support | Investigator/clinical and sponsor owners define correct allocation for actual task | Participant-level information may be involved | Clinical scope and qualifications; privacy basis; trial allocation; employment route reassessment EU-CTR · ES-TRIAL · GDPR |
How to interpret the map without a provider recommendation
Read across a row, not down a list of certificates. In D01, a GCP training certificate is an input to a reviewer’s decision; possession of the certificate does not authorise the coordinator to make that decision. In D03, a correct document bundle is an output for review; the person with access to prepare it is not automatically allowed to submit it. In D07, the employer’s leave process needs a sponsor-side cover decision, but does not make it.
Our evidence rule has three states. Supported means an official rule or supplier statement supports the stated general proposition. Assumed means a detail is fixed for this fictional case. Unresolved means the real record or applicability finding has not been supplied. Never convert an assumed control into an observed approval.
The completed baseline result
D01–D08 can be sent as a bounded specification for assessment. The overall offer and access decision remains on hold: the proposed employer arrangement, trial allocation and representation, privacy/access design and provider acceptance are unresolved. Eight well-described duties are not eight approvals. This is a dependency model; there is no compliance score and no safe percentage.
The interactive scenario explorer runs the same rule on the baseline, a fully evidenced fictional counterfactual, a new CTIS Submitter duty, a participant/clinical expansion and a failed employment route. It does not store or certify approvals. Download the CSV map and the structured inputs for your own controlled procurement record.
What belongs in the real evidence file
Keep the role version; actual legal parties; service and employment terms; duty allocation; named reviewers and backups; training evidence; approved field list; permission test; and change process. References should identify the document version and date, not just say “Legal approved”. Keep personal or participant records out of the downloadable template. The provider generally needs the duty and access description, not the underlying trial data.
For personal data, the privacy owner determines purpose, lawful basis, relevant health-data conditions, parties’ actual roles and safeguards. An employee-data processing agreement should not be assumed to cover trial records. GDPR Articles 5, 6, 9, 28 and 32 provide the framework; the particular arrangement supplies the answer.
Sources: General Data Protection Regulation — Articles 5, 6, 9, 28, 32. Checked 17 November 2026.
Next: turn the map into a procurement decision or test the changed-duty branch.