Worker Registrations (Sitemetric) - This page explains - how registrations create temporary profiles, - how badges and access behave - how Data Support I deduplicates workers into a single unified profile. - Use Troubleshooting for quick issue handling paths.

Overview

This page documents how worker registrations are handled in the Sitemetric platform.

Key Concepts

Quick mental model - *Registrations* are submissions. - *Profiles* are the worker records you ultimately want to be unique. - Every registration creates a temporary profile immediately, even if one already exists for that worker. Matching it to the correct existing worker is a manual step handled by Data Support I — the system doesn't do this automatically.

Worker Registrations vs. Worker Profiles

• Worker registrations and worker profiles are separate entities
• A worker registration will create a profile but will eventually be combined with one profile
• A worker can have multiple registrations tied to one profile
• The Sitemetric worker database is meant to have one unique record per worker, no matter how many sites a worker registers at

Worker Company Behavior (by site access)

• A worker's *company* is assigned per site access — even on a unified profile, a worker can have different companies per project
• Exception: on a Campus / parent-child hierarchy, a company change on one site propagates across the campus family tree

---

Registration States

Pending

• Awaiting review by Data Support I.
• Pending does not mean no access — registrations create temporary profiles and can temporarily assign badges, so the worker can often access the site while still pending.

Flagged

• Held for additional review, most commonly a Customer Approval step (customer wants to approve registrations themselves).
• Once the customer unflags it, it moves into Pending for internal deduplication/approval.

Approved

• Data Support I has completed deduplication/merge and finalized the record.
• Once approved, the registration is locked and cannot be altered.

---

Badge Logic

Registration Bot Behavior:

• Automatically crops a headshot from the registration
• Assigns a badge if it is not already assigned
• Will NOT unassign a badge from an existing user to give it to a new registration

The rule that drives everything below: an unused badge gets instant access; an already-assigned badge is delayed until the records are merged.

• New registration submitted — System Response: Creates temporary profile immediately; Result: Worker can proceed without delay during review
• Unused badge assigned — System Response: Registration bot assigns badge and grants access; Result: Badge works almost instantly
• Already-assigned badge submitted — System Response: Registration created but badge not assigned; Result: Requires Workforce Admin to merge with existing profile
• Multiple registrations for same worker — System Response: Each creates a temporary profile; Result: Data Support I merges into one unique record

---

Deduplication & Approval Process

It's Data Support I's job to make sure every worker ends up with one profile that has all their site access and all their badges. The process:

1. Review new registrations in queue
2. Search for existing profiles matching the worker (by name, badge, phone, etc.)
3. Merge registrations with existing profiles when matches are found
4. Consolidate all site access to the single unique worker record
5. Ensure all badges are properly assigned to the unified profile
6. Approve and finalize the worker record

---

Troubleshooting

Common Issues

Worker has multiple profiles in the system

• Expected behavior during the registration process — Data Support I will merge these during approval.

Duplicate profiles remain after Data Support I approval

• Can happen when dedup is difficult due to conflicting companies or conflicting worker data.

Worker with assigned badge not receiving access at new site

• Expected: badge is already assigned to their existing profile.
• Resolution: Data Support I must merge the new site access with the original profile.

Badge not working immediately after registration

• Check if the badge was already assigned to another profile — if so, dedup is required before access is granted.

Resolution Steps (Data Support I)

1. Identify if the badge is unused or already assigned
2. Search for existing worker profiles in the database
3. Merge the new registration with the existing profile
4. Verify all site access and badge assignments are consolidated
5. Confirm worker has access at all registered sites

Note: Make sure the worker's badge is assigned to the correct (unified) profile and is not still attached to a temporary/duplicate record.

Resolution Steps (Operations / anyone outside Data Support I)

1. Gather examples of the affected worker(s):
   • Worker name
   • Phone number and/or email (if available)
   • Badge number (if relevant)
   • Site(s) / project(s) where the issue is occurring
   • What you expected to happen vs. what is happening
2. Describe the issue type (screenshots help):
   • Duplicate profiles still present after approval
   • Access not granted because a badge is already assigned
   • Badge appears unassigned, assigned to the wrong worker, or not working at the gate
   • Conflicting worker data across registrations (name, phone, DOB, etc.)
   • Conflicting company assignments across sites
3. Create a ticket to Data Support I (Data Entry) and include all details above.
4. Hold any time-sensitive onsite actions until Data Support confirms the unified profile, site access, and badge assignment are correct.