Status. Proposed design only. Nothing in this vault is GGA client approval. The GGA client documents are supplied drafts: see GGA-Source-Digest. No application, service or test has been executed; every scenario is Not executed. Delivery fees and dates are open.

Q14 · consent and contacts

Field	Value
Status	Pending GGA decision (recorded in 1.3 as “Pending DG decision”)
1.3 to GGA disposition	Reframed
Responsible role to confirm (recommendation)	GGA service/privacy owner
Needed before	Before outreach; DG03/04/07–11/21
Named owner	[ ]
Due date	[ ]
GGA approver / decision date / chosen rule	[ ]

What the GGA documents say

Consent is bound to introduction, recipient, fields and files, purpose, version and expiry; changing the package invalidates it; operations cannot consent for a participant; personal contacts stay restricted (pp. 6, 17).

Source class: client-supplied design proposal or proposed default unless stated; GGA acceptance is not recorded. See GGA-Requirement-Register.

Rule or question as proposed in 1.3 (kept as history)

Authorised delegate/verification route, exact release/recipient/purpose/period, final check, affected-case hold/resume authority and review window to limit abuse, stop-contact and departure handover. A protective hold is not a company instruction.

Still open

Delegate and verification route for acting for a company, hold and resume authority, stop-contact and departure handover (carried, Proposed).

Scenarios that depend on this decision (1.3 IDs, unchanged)

DG03, DG04, DG07, DG08, DG09, DG10, DG11, DG13, DG21, DG24, DG27, DG34, DG35, DG38, DG39, DG42. Their dispositions are set in work package R4.

Related

GL04-staged. Index: Decision-Index.

A suggested default is a recommendation, not an approval. Record any actual decision with: ID · chosen rule · amendment to architecture and acceptance · GGA approver · decision date · affected test IDs · implementation owner.