Depending on the program, an automated milestone can include points, a physical or curated award, non-monetary recognition, or a combination of configured elements.

Points may allow employees to choose from a marketplace or a program-specific catalog. A separate catalog or award network can restrict certain milestone points to approved reward categories, such as physical goods, company merchandise, charitable donations, or another defined set of options.

The permitted reward formats, catalog restrictions, fulfillment method, and tax or payroll treatment vary by program and location. Organizations should validate those details before publishing a specific award promise.

Organizations can generally customize the recognition message and related employee experience for an automated milestone. This may include the sender, wording, branding, point value, visibility, notification, catalog, and whether colleagues or managers can contribute messages or memories.

For service anniversaries and other meaningful events, organizations may also choose to surface upcoming milestones, invite comments or photos, or share the recognition in an employee feed where supported.

Automation does not require every event to use the same generic message. Organizations should validate which experience elements can be customized for each program, population, and channel.

Organizations can configure the milestone schedule and decide which events receive a monetary award, non-monetary recognition, a message, a memory-book experience, or another outcome.

For example, an organization may recognize every service anniversary with a message but reserve points or a larger reward for specific years. It may also configure different rules for birthdays, onboarding stages, locations, employee groups, or other populations.

The available schedule, eligibility settings, award types, and population rules depend on the enabled program and configuration.

Awardco uses approved employee and organizational data to identify when a configured event is approaching or has occurred. Depending on the integration, that data may come from an HRIS, file feed, API, or another supported source.

For service anniversaries, the relevant employee start or hire date is commonly used to determine the milestone. Other events may use information such as birth date, onboarding date, employment status, location, department, or other configured fields.

The accuracy and timing of an automated award depend on the source data, field mapping, update cadence, employee identity matching, and configured rules. Organizations should define which system is authoritative for each trigger field.

Depending on the enabled programs, organizations may be able to automate:

• Service anniversaries and years-of-service awardsBirthdaysNew-hire onboarding stagesRetirement or other life-event recognitionsConfigured holidays, campaigns, or recurring employee events

Organizations can choose to automate one program or combine milestone automation with peer recognition, manager recognition, wellness, safety, incentive, or other programs. Not every event is available as a standard automated program, so custom use cases should be validated during implementation.