Foundation Color Match Consultation Record
Record the foundation swatches tested, undertone classification, and final shade selected so a customer can be re-matched on a future visit. Use it to keep consultations consistent and make repeat matching faster.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Beauty Retail · Cosmetics · Salon And Spa · Department Store
Overview
The Foundation Color Match Consultation Record is a workplace form for documenting how a customer was matched to a foundation shade. It captures the consultation date, store location, associate name, customer identifier, skin tone depth, undertone classification, undertone notes, lighting conditions, swatches tested, and the final brand, product line, shade name, and shade number selected.
Use this template when your team needs a repeatable way to record shade matching results for future visits, clienteling, or training review. It is especially helpful when customers test multiple swatches, compare several brands, or return later asking for the same match. The consent section helps you record permission to store and reuse the consultation details.
Do not use this form as a broad customer intake or profile. It is not meant to collect unrelated personal data, medical history, or full demographic details. If your process does not require record retention or follow-up matching, a simpler one-time note may be enough. Keep the form focused on the fields that directly support accurate rematching and a clear audit trail of what was tested and chosen.
What's inside this template
Consultation Details
This section anchors the record to a specific visit so the match can be found, reviewed, and reused later.
- Consultation Date
- Store or Counter Location
- Associate Name
-
Customer Identifier
Optional. Use a loyalty ID, client code, or other internal identifier instead of collecting unnecessary PII.
Skin Tone and Undertone
This section explains how the shade decision was made and gives the next associate the context needed to repeat it accurately.
- Skin Tone Depth
- Undertone Classification
-
Undertone Notes
Optional notes about visible cues, oxidation, or lighting conditions that affected the match.
- Lighting Conditions Used
Swatches Tested
This section preserves the comparison set so the final choice is traceable instead of relying on memory.
-
Swatches Tested
Add one row per swatch tested.
Final Match and Follow-Up
This section records the selected shade and any notes needed to support a future rematch or seasonal adjustment.
- Final Brand Selected
- Final Product Line
- Final Shade Name
- Final Shade Number
- Match Confidence
-
Future Re-Match Notes
Include any tips for future visits, such as seasonal changes, oxidation, or preferred application method.
Consent and Record Use
This section documents permission to store and reuse the consultation details, which matters whenever customer records are retained.
- Customer consent to save this shade match for future re-matching
-
Consent Notes
Optional notes about any customer preferences, limitations, or privacy requests.
How to use this template
- 1. Enter the consultation date, store location, associate name, and a minimal customer identifier so the record can be found later without collecting unnecessary PII.
- 2. Record the customer’s skin tone depth, undertone classification, undertone notes, and lighting conditions using the same terms your team uses during consultations.
- 3. List every swatch tested, including brand or shade references where relevant, so the comparison set is clear if the customer returns.
- 4. Capture the final brand, product line, shade name, shade number, and match confidence immediately after the selection is confirmed.
- 5. Add future rematch notes and consent details, then save the record where associates can access it during the next visit.
Best practices
- Use a date picker for the consultation date and structured fields for shade name and shade number so the record stays searchable.
- Keep the customer identifier minimal and avoid collecting extra PII unless it is needed to retrieve the consultation later.
- Document lighting conditions because natural light, store lighting, and camera flash can change how a match appears.
- Record swatches tested in the order they were applied so associates can understand the decision path, not just the final result.
- Use progressive disclosure for optional notes such as skin concerns, finish preference, or seasonal changes so the form stays fast to complete.
- Mark consent clearly and explain what happens after submission if the record will be stored, shared, or reused for future visits.
- Train associates to write specific undertone notes instead of vague language like "warm-ish" or "looks good".
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template captures the details of a foundation matching consultation, including skin tone depth, undertone classification, swatches tested, and the final shade chosen. It is designed so an associate can re-match the same customer later without starting from scratch. It also includes consent fields for storing and reusing the record. Use it as a repeatable consultation record, not as a general customer profile.
Who should fill out the record?
A beauty advisor, makeup artist, or store associate should complete it during or immediately after the consultation. The person doing the match should enter the swatches tested and the final shade while the details are still fresh. If a manager reviews consultations, they can use the record for quality checks or training. The customer should only complete consent-related fields if your process requires it.
How often should this be used?
Use it every time a foundation matching consultation is performed, especially when a customer wants a repeatable shade on future visits. It is also useful when a customer tests multiple brands or product lines in one session. If the customer’s skin tone changes seasonally or they switch formulas, a new record should be created or the existing one updated. That keeps the match history accurate and easy to search.
What information should be collected, and what should be left out?
Collect only the fields needed to reproduce the match: consultation date, location, undertone notes, swatches tested, final shade, and consent for record use. Avoid collecting unnecessary PII or sensitive details that do not help with future matching. If you use a customer identifier, keep it minimal and internally meaningful. This follows data minimization and reduces clutter in the record.
How does this template help with repeat visits?
The record gives associates a clear reference point for the customer’s previous match, including the exact shade name and number. Future visits can start from the last confirmed match instead of re-testing every option. The future rematch notes field can capture seasonal changes, formula preferences, or lighting issues that affected the original result. That makes the next consultation faster and more consistent.
Can this be customized for different brands or store workflows?
Yes. You can add brand-specific shade libraries, product line options, or store-specific notes fields if your assortment changes by location. Some teams also add conditional logic for coverage level, finish, or skin concerns when those details affect the match. Keep the form focused so associates are not forced through irrelevant fields. Progressive disclosure works well if you support many brands.
What are common mistakes when using this record?
A common mistake is writing vague shade notes like "medium" without the actual shade name and number. Another is skipping lighting conditions, which can make a match hard to reproduce later. Teams also sometimes mark every field required, which slows the consultation and creates poor data quality. The best records are short, specific, and completed at the point of service.
How can this connect to other systems or workflows?
This template can feed a CRM, clienteling tool, or appointment record so associates can find the match history before a visit. It can also be linked to inventory or product catalogs if your team wants to check whether the final shade is in stock. If you export records, keep the field names consistent so search and reporting stay reliable. That makes the consultation useful beyond a single appointment.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
Most enterprise integrations just add navigation, not unity. Learn why workforce integration fails and what a truly unified platform looks like for desk and...
-
Ask AI now routes multi-part questions to specialist agents simultaneously, returning one combined answer with a transparent agent trace — no app-switching...
-
A vendor-agnostic checklist covering architecture, frontline access, AI, compliance, and payroll to evaluate any scheduling platform.
-
MangoApps 2026 Winter Release adds native shift scheduling, structural AI for surveys and wikis, and a redesigned search—unifying frontline operations in one...
Ready to use this template?
Get started with MangoApps and use Foundation Color Match Consultation Record with your team — pricing built for small business.