Parties
Name the investigator, sponsor, institution, and any CROs with role definitions and contact information for accountability and routing.
A clear ICH GCP Statement documents compliance commitments, aligns investigators with regulatory expectations, and supports IRB and sponsor oversight. It reduces ambiguity about roles, improves audit readiness, and helps demonstrate adherence to data integrity and participant protection standards under ICH E6.
Typical users include principal investigators, study coordinators, sponsors, contract research organizations, and institutional review boards.
The statement creates a formal accountability record that multiple parties reference during enrollment, monitoring, and inspections.
Name the investigator, sponsor, institution, and any CROs with role definitions and contact information for accountability and routing.
Cite applicable guidance such as ICH E6(R2) and relevant FDA regulations to anchor expectations for conduct and documentation.
Describe the protocol or study identifiers, investigational product, and the specific activities the statement covers, such as recruitment or data handling.
List concrete commitments—consent processes, safety reporting timelines, monitoring frequency, and source data verification practices.
State when obligations begin and, if applicable, expiration or review date to manage version control and responsibility windows.
Include printed name, title, signature, and date for each authorized signer; note any witness or notary requirements if used.
| Field | Configuration |
|---|---|
| Signer Order | Set role-based order (PI → Site Admin → Sponsor) |
| Authentication | Require email plus SMS or organization SSO for higher assurance |
| Conditional Fields | Display witness or notary fields only when required |
| Retention Policy | Auto-archive signed copy to secure repository |
Choose a platform that supports secure authentication, audit trails, and required compliance frameworks for clinical records.
Ensure the chosen system provides tamper-evident storage, reproducible audit logs, and a HIPAA-capable BAA if protected health information is present.
Statement should be signed prior to enrolling the first subject
Include signed statement with IRB or rely on site assurance as instructed
Update statement when amendments change scope or responsibilities
Provide copy during initial monitoring visit
Make available for FDA or sponsor audits without delay
Finalize language and obtain institutional sign-off
Gather all required signatures and authentications
Share signed copies with sponsor, IRB, and site regulatory file
Store in controlled repository with audit trail
| Criteria | Electronic Signature | Digital Signature |
|---|---|---|
| Definition | any electronic mark | pki cryptographic signature |
| Authentication | email/sms or account | certificate authority based |
| Non-repudiation | audit trail evidence | strong cryptographic proof |
| Typical Use | routine approvals | high-assurance regulatory filings |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
A PI signs a site-level GCP statement before enrolling subjects
When a major amendment changes safety monitoring, the investigator signs an updated statement