CliniGA CRO

CliniGA CRO Blog

Connecting portal support tickets to submission decision evidence

Resolving a technical support request differs from assessing its effect on an application.

Representative research photograph: Connecting portal support tickets to submission decision evidence
Photo: U.S. Navy CLDJ by Petty Officer 2nd Class JEROME FJELD · License: Public domain · Cropped and resized.
Published
Updated

Resolving a technical support request differs from assessing its effect on an application. Important context can disappear if the response is not linked to the trial record explaining what the team did and why. Sponsors should not track support only as a count of closed tickets without examining their operational consequences.

Decision framework

Separate the request's technical scope from its possible trial impact. Distinguish support instructions from an authorised regulatory or project decision. Identify where relevant evidence belongs and who assesses the response. Include only information needed to resolve the problem rather than sharing confidential study content unnecessarily with the support channel.

Worked example

For example, support recommends uploading a file again. The project team assesses whether doing so affects the package version or transaction history. The action and outcome are recorded in the same linked trail. Ticket closure is not reported internally as completion of an authorised application assessment; the actual platform state is verified separately.

Implementation checks

  • Link the ticket identifier to the relevant technical event, package version and internal decision record needed to explain the response.
  • Record who assessed the advice and which action was actually performed rather than retaining the instruction alone.
  • After the problem is resolved, recheck application status and outstanding actions with the appropriate business owners.

Acceptance and boundaries

Accept the record when a new team member can distinguish technical guidance from the trial decision. This example gives support staff no regulatory approval authority. Resolve uncertainty about official interpretation or application status through appropriate authorised channels, using technical records to explain the basis of actions already taken.

Frequently asked questions

Does a closed ticket prove the application is complete?
No. Technical closure and official submission status are separate events.
Should support advice always be executed immediately?
Assess authority, consequences and applicable trial processes before determining an appropriate action.

Sources

  1. EMA — CTIS sponsor handbook and support
  2. EMA — ICH E6 good clinical practice