The evidence record should be purpose-level, not page-level. A single product feature may need different bases for account creation, billing, support, security logging, analytics, marketing, and research.
For consent, evidence must show more than a current configuration setting. EDPB guidance says the controller should be able to show how consent was obtained, when it was obtained, what information was provided at the time, and that the workflow met the criteria for valid consent.
Can a GDPR team choose consent first and switch to legitimate interests later?
No. EDPB consent guidance says the controller must decide the lawful basis in advance and cannot retrospectively rely on legitimate interests when consent is invalid or withdrawn.
Does special category data only need explicit consent?
No. Special category processing needs an Article 9 condition, and explicit consent is only one Article 9(2) condition. The record should still identify the Article 6 basis for the processing purpose.
What should a GDPR consent record prove?
It should prove who consented, when and how consent was given, the purpose and information shown at the time, the affirmative action used, the consent workflow version, and the withdrawal method.