Programme and business cards
Give every card a clear role in the relationship.
Business, loyalty and membership cards create different interactions. Start with the person, programme and information before choosing surface or finish.
Purpose before options
The card should support the programme people actually use.
A business card communicates identity once; a loyalty or membership card may be recognised, presented or checked many times.
Define the programme, visible information and changing records before finalising artwork or identifiers.
- Business
- Loyalty
- Membership
- Numbering
- Personalisation
Plan the card
Connect the card design to the programme
Every identifier or changing field needs a clear source and approval responsibility.
- 01Card role
- Business contact, loyalty recognition, membership or another defined use
- 02Static artwork
- Brand and information common to every card
- 03Variable fields
- Names, member details, dates or other changing records
- 04Identifiers
- Numbers or codes and the system responsible for them
- 05Programme workflow
- Issue, replacement and user interaction requirements
- 06Approval
- Who checks artwork and final records before production
Build the brief
Describe the programme and data flow
The team can help identify surface and personalisation questions once the user journey and record ownership are understood.
Include in the brief
- Card purpose and audience
- Quantity and versions
- Static and variable fields
- Record source
- Code or numbering responsibility
- Artwork status
- Delivery location and date
Card quote
Ready to discuss business, loyalty and membership cards?
Include the intended use, quantity, artwork status, delivery location and the decisions above. The team will confirm what is practical for business, loyalty and membership cards.