Scratch-panel cards
Define what is concealed, who controls it and how it is used.
A scratch panel may hide a code or other variable detail, but the programme, record source, security expectation and redemption process sit outside the surface alone.
Concealed variable content
Treat the hidden record as controlled programme data.
The visible card, concealed field and wider issue or redemption process need a shared specification.
Confirm the actual panel construction, data responsibility and security suitability before treating the option as part of the job.
- Concealed field
- Records
- Panel
- Issue
- Approval
Plan the card
Coordinate the concealed field with the card and programme
Define the required security level, platform and programme behaviour so the panel and data responsibilities can be scoped together.
- 01Concealed content
- The field hidden beneath the panel and its purpose
- 02Record source
- Who creates, protects and approves the variable values
- 03Panel position
- A consistent zone with suitable artwork clearance
- 04Issue workflow
- How cards are distributed and linked to the programme
- 05Redemption or use
- The system or team responsible for recognising the hidden detail
- 06Approval
- Who validates artwork, records and representative samples
Build the brief
Bring the programme owner into the specification
The print team can assess the physical card only when the data and use responsibilities are clear.
Include in the brief
- Programme purpose
- Concealed field
- Record owner
- Panel position
- Quantity
- Artwork status
- Approval and testing owners
Connect the scratch panel to the security plan
Security, uniqueness, activation and redemption depend on the wider programme and the parties responsible for its data and controls.
Card quote
Ready to discuss scratch-panel cards?
Include the intended use, quantity, artwork status, delivery location and the decisions above. The team will confirm what is practical for scratch-panel cards.