A corporate gifting program is mature when decisions are repeatable, evidence-backed, and owned across policy, recipient data, finance, choice, fulfillment, and measurement. The 100-point scorecard below turns that idea into a practical assessment: score only what you can prove, expose the largest gaps, and convert them into a dated improvement roadmap.
How to use the scorecard
Start with a cross-functional review involving the program owner, finance, procurement, privacy, tax or payroll, and operations. Score each criterion from 0 to 4: 0 means no reliable evidence; 1 means an initial practice; 2 means a documented process; 3 means the process is measured; and 4 means it is routinely improved. Every nonzero score needs a note, link, sample, or dated decision. Download the English maturity scorecard In v1.1, each pillar has one bundled assessment criterion. Use the lowest evidence-supported score among its listed controls. Supported points require an evidence note or link, an owner, and a date; a high score without those fields earns no supported points. Initial scores are zero and do not represent an assessment of any company.
A high score without evidence is not maturity. A lower score with named owners and a funded roadmap is a more useful starting point.
- Choose one program boundary, such as employee recognition, customer gifting, or events.
- Gather policy, approval, supplier, delivery, finance, privacy, and measurement evidence.
- Score independently, then resolve material differences in a review meeting.
- Assign an owner and due date to every priority-one gap.
- Reassess quarterly and preserve the version used for decisions.
The 100-point operating model
The model has six pillars. Governance and fulfillment receive 20 points each because weak ownership or unreliable delivery can undermine the entire program. Recipient and data, funding and finance, catalog and personalization, and measurement and improvement receive 15 points each.
| Pillar | Weight | Decision question | Decision-ready evidence |
| Governance | 20 | Who owns the program and exceptions? | Policy, accountable owner, approval rules, review minutes |
| Recipient and data | 15 | Is data collected and retained deliberately? | Data map, notice, access roles, retention rule |
| Funding and finance | 15 | Can spend and obligations be reconciled? | Budget, tax handoff, ledger mapping, exception log |
| Catalog and personalization | 15 | Does choice remain inclusive and controlled? | Approved catalog, accessibility checks, substitution rules |
| Fulfillment and service | 20 | Can the team deliver and recover globally? | Routing rules, lifecycle states, service owners, fallback supply |
| Measurement and improvement | 15 | Does evidence change later decisions? | Outcome definitions, attribution method, review actions |
The score bands are planning shorthand: 0–39 ad hoc, 40–59 managed, 60–79 scaled, and 80–100 optimized. They are not certifications. The model is inspired by evidence, governance, and improvement principles found in the NIST Cybersecurity Framework 2.0 and ISO 31000:2018, but it does not claim equivalence or certification.
What counts as evidence
Evidence should show that a control operates, not merely that someone intends to use it. A policy without dated approvals is weak evidence. A dashboard without definitions or an owner is weak evidence. A supplier claim without a contract, test, or sample is weak evidence. Stronger evidence connects a decision, owner, transaction, and review date.
How should reviewers handle incomplete evidence?
Record the current score, state the missing proof, and assign an evidence owner. Do not award points because a tool might support a feature. For tax-sensitive employee rewards in the United States, use the current IRS Publication 15-B (2026) as one official starting point, then obtain jurisdiction-specific advice. The scorecard is not legal or tax advice.
Sample-based testing is useful. Select several campaigns across recipient types and countries. Trace the approval, data collection, funding, fulfillment, failed-delivery handling, and reconciliation. If the documented process and the sample disagree, score the operating reality and log the difference.
Turn gaps into an improvement roadmap
Do not begin with the lowest-scoring item automatically. Prioritize the gaps that combine material risk, frequent volume, recipient harm, financial leakage, and feasible remediation. A missing owner for customs exceptions may matter more than a sophisticated attribution model; an unresolved payroll handoff may matter more than expanding the catalog.
| Priority | Typical condition | Expected action | Completion evidence |
| 1 | Legal, tax, privacy, safety, or delivery-stop risk | Name an owner, contain the exposure, and set a near-term decision | Approved decision and tested control |
| 2 | Repeated cost, support, or inclusion weakness | Redesign the process and measure a pilot | Pilot results and updated procedure |
| 3 | Optimization opportunity with controlled downside | Test against a defined baseline | Measured result and keep/change decision |
A useful roadmap is short enough to fund. Limit the first cycle to three to five priority gaps. Define the before state, target state, owner, due date, required evidence, and the business decision that will change when the work is complete.
Govern the model and its limitations
The model baseline is September 6, 2026; the current workbook is v1.1, rebuilt September 7, 2026. The weights are deliberately transparent so teams can debate them. If a regulated program changes a weight, record the rationale and keep the original result for comparison. Never edit a prior assessment silently. This self-assessment can overstate maturity. Use sample testing, cross-functional review, and external advice where appropriate. It does not replace an audit, certification, privacy assessment, tax position, employment decision, or legal opinion. Do not compare two business units unless they use the same boundary, evidence standard, date, and weights. The public workbook contains eight worksheets: Start Here, Assessment, Evidence Log, Gap Heatmap, Priority Roadmap, Methodology, Sources, and Checks. Formula checks confirm that weights total 100, scores remain within range, and nonzero scores have evidence. The workbook contains no macros, external workbook links, customer data, or hidden tracking.
Conclude with a controlled next cycle
The score is useful only if it changes a decision. Preserve the completed workbook and checksum, approve a small roadmap, and schedule the next evidence review. Mature programs do not eliminate exceptions; they make exception ownership, recipient impact, and follow-up visible. Giftpack can serve as the execution layer for recipient choice, controlled delivery states, localized fulfillment, and program evidence. It does not replace the employer’s tax, legal, payroll, privacy, procurement, or policy decisions; it helps teams carry approved decisions into repeatable operations.