Chapter 7: Collecting Evidence and Building an Achievement Repository
A strong SME achievement story depends on more than memory and promotional language. It requires credible evidence showing what happened, when it occurred, who contributed, and what results were achieved. Small and medium-sized businesses that collect this information throughout the year are better prepared for strategic reviews, customer case studies, employee recognition, annual reports, partnership discussions, media opportunities, and business award nominations.
An achievement repository is a secure, organized location where an SME preserves approved information about meaningful accomplishments. It may be created within a shared drive, document-management platform, project-management system, or another protected business application. The technology can be simple. Consistent documentation, responsible access, and accurate organization matter more than purchasing an elaborate system.
Decide What Evidence to Collect
Evidence should support the central claims of an achievement. If a company states that a new process shortened delivery times, the supporting material might include operational reports showing performance before and after implementation. If an employee initiative improved retention, relevant evidence may include workforce data, employee feedback, and program records.
Possible types of supporting evidence include:
- Financial and operational reports
- Sales and customer data
- Project plans and completion summaries
- Product testing or adoption information
- Customer feedback and authorized testimonials
- Employee engagement or training results
- Quality, safety, or compliance records
- Website analytics and campaign reports
- Photographs, videos, and presentation materials
- Public announcements and media coverage
- Certificates, approvals, or independent assessments
- Relevant website, news, press, or social media links
The objective is not to collect every available file. Preserve the strongest materials that establish the baseline, actions, results, and significance of the achievement.
Create a Standard Achievement Record
Each potential achievement should have a summary document or database entry. Using a consistent format makes records easier to review and compare.
The record should include:
- Working title of the achievement
- Business objective or problem addressed
- Baseline condition
- Actions taken
- Beginning and completion dates
- Employees, teams, and partners involved
- Measurable results
- Data sources and calculation methods
- Challenges or limitations
- Business, customer, workforce, or community significance
- Supporting evidence available
- Permissions and approvals required
- Person responsible for maintaining the record
The title can change later. The immediate priority is to preserve accurate facts before details are forgotten or become difficult to verify.
Organize the Repository Clearly
A practical folder structure could begin with the year, followed by the business function and achievement name. For example, an SME might organize material under Operations, Customer Service, Product Innovation, Workforce, Growth, Sustainability, and Community Impact.
Each achievement folder could contain the summary, approved data, supporting documents, visual materials, published links, and permission records. Consistent filenames should include a date and short description rather than unclear labels such as “final” or “newest version.”
A simple index or spreadsheet can help users search the repository. Useful fields might include achievement type, department, contributor, completion date, geographic reach, status, evidence strength, approval status, and possible communications or recognition use.
Preserve Baselines and Calculation Methods
Results become more credible when the SME can show how they were calculated. A percentage improvement should identify the original figure, final figure, comparison period, and data source.
For example, “customer response time improved by 40 percent” should be supported by records explaining what counted as a response, which periods were compared, and whether the calculation covered all inquiries or only a particular channel.
Definitions should remain consistent. If the company changes how it measures active customers, defects, employee turnover, or delivery performance, it should record that change. Otherwise, comparisons may appear stronger or weaker than the actual result.
Verify Information Before Using It
Someone familiar with the project should review the achievement for factual accuracy. Finance, human resources, operations, legal, privacy, or communications personnel may also need to verify claims relevant to their responsibilities.
Useful verification questions include:
- Do the records support the stated result?
- Are the comparison periods appropriate?
- Have any projections been presented as completed outcomes?
- Are all contributors credited accurately?
- Did outside factors materially influence the result?
- Can the supporting evidence be shared publicly?
- Are customer, employee, or partner permissions required?
Independent evidence can strengthen a claim, but it is not always necessary. Internal records may be sufficient when they are reliable, consistently collected, and appropriately approved.
Protect Confidential and Personal Information
An achievement repository may contain financial records, customer information, employee data, intellectual property, security details, and confidential contracts. Access should be limited according to business need.
SMEs should not upload sensitive material to a public platform merely to support a nomination or promotional claim. Confidential figures may sometimes be communicated through percentages, ranges, anonymized examples, or aggregated results. Personal information and photographs should be used only with appropriate consent and in accordance with applicable requirements.
Security measures may include access controls, multifactor authentication, backups, encryption, retention rules, and procedures for removing access when an employee leaves. Cybersecurity or incident-related achievements require particular care because supporting evidence could expose vulnerabilities.
Review and Maintain the Repository
Assigning responsibility is essential. A designated employee or small committee can request updates monthly and conduct quarterly achievement reviews. Department leaders should confirm that records remain accurate, permissions are current, and important evidence has not been lost.
The repository should distinguish between emerging, completed, verified, approved, and publicly available achievements. Not every promising initiative will become a completed accomplishment, but early documentation makes progress easier to monitor.
By maintaining an evidence-based achievement repository, an SME can respond more quickly when it needs a case study, proposal, employee profile, annual report, or award nomination. The business will already have its strongest facts, supporting materials, contributor information, and approvals in one organized location.
SMEs interested in external recognition can review current Globee Awards programs, categories, eligibility requirements, achievement periods, nomination rules, deadlines, and supporting-material requirements at GlobeeAwards.com.