When a Spain coordinator becomes a CTIS submitter
By Regulated Workforce Operations Editorial Desk · Publication editorial team
Updated
Do not grant Submitter permission under the old administrative-role approval. Keep the existing authorised submitter responsible while the sponsor reviews the additional activity, competence, access and employment scope. Submission can be allocated to a suitable person; it is not automatically forbidden to someone employed through another organisation. What fails is the assumption that the old record already covers it.
Fictional change CH-02 starts from the fully evidenced administrative counterfactual: the employment, trial-allocation/representation, privacy/access, provider and terms gates for unchanged duties D01–D08 have all closed. The coordinator has been preparing approved bundles under role ES-SSU-01. Those accepted records do not cover the new D09 submission duty. A manager asks them to submit the next application “because the usual submitter is on leave”. The new task has not started and no new permission has been granted. The baseline specification explicitly excludes submission.
CTIS distinguishes Preparer and Submitter permissions. A preparer can work on drafts within the assigned role; submission permissions add consequential actions. Match the current role matrix and trial scope to the requested action rather than selecting a broad administrator role for convenience.
Sources: CTIS Sponsor Handbook — section 1.7 role permissions · CTIS and Regulation 536/2014 information — CTIS introduction and transition. Checked 17 November 2026.
| Step | Completed decision in CH-02 | Evidence needed to move on |
|---|---|---|
| 1 · Freeze only the added duty | Coordinator continues approved document chasing and tracker work. Existing authorised submitter covers submission; no credential sharing. | Manager acknowledges the boundary; coverage owner accepts the task. |
| 2 · Define the change | Add D09: submit an approved application for a named trial. Specify whether preparation, submission, withdrawal or updates are actually needed. | New duty/access version; exact CTIS role and trial scope. |
| 3 · Allocate and qualify | Sponsor regulatory owner reviews the activity and responsible person. Trial agreements are reviewed where transferred scope changes. | Documented allocation, appropriate training/competence and review/oversight route. |
| 4 · Recheck employment and data | People sends the changed duty to the employer; privacy and system owners review additional access and data flows. | Written employer scope response and any terms change; approved permission design. |
| 5 · Activate with evidence | No activation yet in the worked case. The system owner grants only approved permissions after preceding gates close. | Role-grant record; permission test; effective date; acknowledgement by worker and approver. |
| 6 · Verify use | Review the first submission against the approved bundle and audit trail; retain who approved and who submitted. | Submission receipt and discrepancy resolution. A receipt is not regulatory authorisation of the trial. |
Two changes that need different answers
More administrative volume: ten sites become twelve, with unchanged duties and permissions. Review capacity, coverage and hours with the employer; this does not by itself make the coordinator a clinical decision-maker. Preserve the same authority boundary and document any material workload or employment change.
New clinical judgment or participant access: the manager asks the coordinator to decide whether a person meets eligibility criteria or answer a consent question. That is outside this support specification. The responsible clinical/investigator and sponsor owners must define the task, qualifications and allocation; privacy reviews any participant data; employment scope is reassessed. Refer the immediate question through the trial’s authorised pathway. Do not let a procurement delay become an unattended safety query.
If the added activity already happened
Stop the unapproved activity and secure the relevant records without deleting the audit trail. Notify the sponsor’s responsible regulatory, quality, safety or privacy owner according to the event. That owner assesses consequences and any applicable reporting duty; this article does not impose a generic reporting deadline on every error. Restore coverage through an authorised person. The employer separately assesses employment implications. Close the incident only against actual corrective-action and access evidence.
The counterfactual result
The explorer’s fully evidenced fictional administrative case can proceed within its eight duties. Add D09 and it returns hold added duty; reassess scope, even if the supplier name stays the same. Add D10 and it routes to specialist clinical/privacy review. Mark the employment arrangement unsuitable and it returns do not appoint on this route. These changes show why a role-wide “approved” tick is insufficient.
Use the scenario explorer to reproduce those outputs, then take the result back to the approval record. The source-linked controls underpinning this branch are in the duty evidence map.