Chapter 8: Collecting, Protecting, and Approving Supporting Evidence
A credible digital transformation achievement depends on reliable evidence. Organizations may remember that an initiative improved performance, reduced costs, strengthened security, or increased customer satisfaction, but memories and general statements are rarely sufficient. Supporting evidence shows what conditions existed before the transformation, what actions were taken, what changed, and how the results were verified.
Evidence should be collected while implementation is taking place. Reconstructing an achievement months later—shortly before a leadership review, case study, annual report, or award nomination—can lead to missing records, inconsistent calculations, and uncertain attribution. A secure digital transformation evidence repository creates a reliable record while protecting information that should not be disclosed.
Collect Evidence From Approved Sources
Useful evidence can come from many parts of an organization. Examples include approved performance dashboards, project reports, financial analyses, implementation plans, audit findings, risk assessments, policies, survey results, training records, and operational reports.
Publicly available materials can also provide support. These may include organizational announcements, authorized case studies, published customer stories, government reports, media coverage, research findings, public presentations, and official website pages. Save the relevant link, publication date, title, and source because webpages may later be updated or removed.
Not every available document should be preserved or shared. Select materials that support the principal digital transformation achievement. Ten strong documents closely connected to the challenge, actions, and results are more useful than hundreds of unrelated files.
Preserve Baseline and Final Performance Data
Before-and-after comparisons require consistent records. Organizations should preserve the baseline data used to describe the original condition and the final data used to demonstrate improvement.
Record the measurement period, affected population, system or process involved, data owner, and method used. If processing time declined from ten days to four, preserve the reports supporting both figures and document whether the measure represents an average, median, or another calculation.
The same discipline applies to cost savings, adoption, customer satisfaction, system availability, error rates, employee productivity, revenue growth, security improvements, and public-service outcomes. Evidence becomes much stronger when another authorized person can understand how a result was calculated.
Record Decisions, Actions, and Contributors
Metrics show what changed, but implementation records help explain how the change occurred. Maintain a timeline of significant decisions, actions, milestones, setbacks, adjustments, and results.
The record might identify when the strategy was approved, when a pilot began, when systems were migrated, when employees were trained, and when performance targets were reached. It should also identify the leaders, departments, teams, professionals, technology providers, and consultants that contributed.
Accurate attribution is especially important when recognizing a leader, department, team, or professional. The evidence should support statements about who initiated, designed, managed, implemented, improved, or contributed to the achievement. Seniority or visibility should not replace documented contribution.
Preserve Authorized Feedback and Recognition
Customer, employee, patient, student, resident, or stakeholder feedback can demonstrate how people experienced the transformation. Useful evidence may include approved survey results, testimonials, interview summaries, service reviews, or authorized quotations.
Confirm who provided the feedback, when it was collected, whether it is representative, and whether permission exists to use it. Personal information and confidential comments should not be shared without authorization.
Internal recognition, leadership acknowledgments, independent assessments, certifications, published reports, and previous awards may provide additional context. However, recognition from another source does not independently prove the underlying achievement. It should complement—not replace—evidence of actions and measurable results.
Verify Sources and Calculations
Every important claim should have an identifiable source. Assign an owner to validate each metric and confirm the data source, definitions, assumptions, time period, and calculation method.
Financial figures should specify whether they represent realized savings, estimated savings, cost avoidance, revenue, or projected value. Percentages should include the starting and ending values whenever appropriate. Security and risk measures should be reviewed by qualified personnel to ensure they are accurate and safe to disclose.
If the organization cannot verify a figure, it should qualify or remove the claim rather than present uncertain information as fact.
Protect Sensitive Information
An evidence repository should not become a collection of uncontrolled confidential data. Organizations must protect personal information, customer records, employee data, trade secrets, privileged communications, financial details, proprietary methods, and information restricted by contract or regulation.
Cybersecurity evidence requires particular care. Do not disclose system credentials, network architecture, uncorrected vulnerabilities, detailed incident information, security configurations, access methods, or other material that could increase risk. A transformation can often be explained through aggregated or redacted results without revealing sensitive operational details.
Establish Approval and Governance Practices
Assign ownership of the evidence repository and establish access controls based on organizational roles. Define who may add, review, approve, edit, share, archive, or delete materials. Retention practices should follow applicable laws, contracts, policies, and recordkeeping requirements.
Before evidence is used externally, obtain appropriate privacy, cybersecurity, legal, leadership, customer, and communications approvals. Keep a record of what was approved, by whom, for which purpose, and for how long. Approval for an internal report does not necessarily authorize public disclosure or submission to an external evaluator.
Prepare a separate evidence package containing only materials approved for external use. Redact unnecessary information, verify links, label confidential items appropriately, and confirm current submission requirements.
The Globee Awards recognize specific, demonstrable achievements—not job titles, responsibilities, or unsupported claims. Secure, verified, and authorized evidence helps external evaluators understand what was accomplished. Current programs, categories, eligibility requirements, achievement periods, nomination rules, supporting-material requirements, and deadlines can be reviewed at GlobeeAwards.com.