HR administrators at construction companies keep a lot of employee context outside the core profile: notes on conversations and follow-ups, signed documents, emergency contacts for the crew, company-issued equipment, and OSHA injury and illness records. Today, even after moving to the unified employee profile in Hub, admins still have to jump back into legacy Core HR to view or update these records. Each link on the Core HR tab opens a separate legacy page in a new browser tab, with a different look, different navigation, and a context switch every time.

That back and forth slows down routine work and makes the unified experience feel unfinished. For OSHA records in particular, admins need confidence that the data they enter is complete and accurate, because it feeds the annual OSHA 300 and 300A reports.

This release moves the Notes, Documents, Emergency Contacts, Assets, and OSHA Injuries and Illnesses pages into Hub, so admins can manage an employee's full Core HR record from one place without leaving the unified platform.

This release allows you to:

• Save time: Open and update employee notes, documents, emergency contacts, assets, and OSHA incidents directly from the employee's Core HR tab, with no new browser tabs or trips back to legacy pages.
• Reduce compliance risk: OSHA incident entry keeps every legacy rule, including unique case numbers, required OSHA Locations, and classification fields that become required when days away or restricted hours are entered, so records stay accurate for 300 and 300A reporting.
• Keep access exactly as it is: Existing Core HR page permissions carry over automatically. Admins see and edit in Hub exactly what they can see and edit in Core HR today, and nothing more.
• No data to move: Hub reads and writes the same Core HR records, so changes made in either place show up in both, and the Activity Log keeps recording changes the same way.
• A consistent experience: Every page follows the unified platform design, with the same layout, dialogs, and navigation admins already use for the rest of the employee profile.

Enhancements

The five Core HR employee record pages now open as Hub pages from the links on an employee's Core HR tab.

User Experience / How to Access

1. Open an employee's profile in Hub and select the Core HR tab.
2. Select Notes, Documents, Emergency Contacts, Assets, or OSHA Injuries and Illnesses.
3. The page opens in the same browser tab, inside Hub, for that employee. Each page includes a way back to the Core HR tab.

Links only appear for pages the admin has permission to view. Cost Centers continues to work exactly as it does today.

Notes

1. View an employee's notes newest first, with search. Columns show Date, Type, Category, Note, a Follow-up badge, and a paper clip when a note has an attachment.
2. Add, edit, and delete notes, including note text (up to 5,000 characters), note type (General or Performance Log), category, and requires follow-up.
3. Hide from employee is available on Performance Log notes, matching Core HR. Changing a note to General clears it.
4. Category is optional. If the company has no note categories set up, the Category column and field are hidden.
5. Attach a supporting file to a note, download it from the list, and replace or remove it. Allowed file types and sizes match Core HR and the Documents upload. Deleting a note also removes its attachment.

Documents

1. Browse an employee's documents with file name, category, tags, status (including Legal Hold), note, visible to employee, and uploaded date. Filter by category and tag, and search by file name.
2. Download any document.
3. Upload a document with a category, one or more tags, a note, and a visible to employee setting. Uploaded documents appear in Core HR and are available to Core HR workflows.
4. Delete documents one at a time or in bulk. Documents on legal hold can never be deleted.
5. Place or remove a legal hold (requires the matching legal hold permission).
6. Reassign the category or add and remove tags on several documents at once.

Emergency Contacts

1. View an employee's emergency contacts with first name, last name, relationship, home phone, and secondary phone.
2. Add, edit, and remove contacts inline, then save all changes at once, just like Core HR.
3. Removing someone as an emergency contact does not remove them as a dependent or beneficiary.
4. Company emergency contact settings from Core HR still apply: a required secondary phone, and the Notify if arrested designee rule (exactly one designee company-wide) when legal events contact is turned on.

Assets

1. View the company-issued assets assigned to an employee: description, tag, value, date issued, and notes.
2. Add, edit, and delete assets. Date issued is required; description is optional (up to 250 characters), matching Core HR.

OSHA Injuries and Illnesses

1. View an employee's incidents with case number, date, location, and recordable status.
2. Record, edit, and delete OSHA Form 301 incident reports, including reporter information, a company-unique log case number, OSHA Location, recordable status, and incident detail.
3. Record Post Injury Information (admins only), including medical and treatment detail, days away and restricted hours, case classification, and workers' comp claim detail. It saves together with the incident.
4. Case classification and injury or illness type become required when days away or restricted hours are entered, matching Core HR.

Interactions with Other Features

1. OSHA Locations: An incident cannot be saved until the company has at least one OSHA Location. OSHA Locations are still set up in Core HR.
2. OSHA 300 and 300A reports: Incidents entered in Hub appear in the existing Core HR OSHA 300 and 300A reports with no change to how those reports are run.
3. Activity Log: Changes to assets, OSHA incidents, documents, and legal holds are recorded in the Activity Log the same way they are in Core HR today.
4. Legacy Core HR: Hub and Core HR share the same records. A change made in either place shows in the other.

Not Included in This Release

• Acknowledging notes, the Requires acknowledgement option, and sending a note as email. These are tied to Core HR performance notes, which are not supported in the unified platform. Existing acknowledgement data on notes is kept when a note is edited.
• Bulk delete of notes.
• Print Asset List and the OSHA Form 301 print (PDF and Excel). Both remain available in Core HR.
• OSHA Locations setup and the OSHA 300 and 300A reports, which stay in Core HR.
• Manager, employee, and enroller views of these records, and Dependents, Beneficiaries, and Pets pages.

FAQs

Do admins need new permissions to use these pages?

No. Existing Core HR page permissions carry over automatically. Full Access becomes view and edit, Read Only becomes view only, and No Access hides the page.

Will records entered in Hub show up in Core HR, and the other way around?

Yes. Hub and Core HR use the same records, so changes made in either place show in both.

Will OSHA incidents entered in Hub appear on the OSHA 300 and 300A reports?

Yes. Incidents entered in Hub, including case classification and injury or illness type from Post Injury Information, feed the existing Core HR 300 and 300A reports. Reports are still run from Core HR.

Why can't I save an OSHA incident?

The company needs at least one OSHA Location set up in Core HR before incidents can be saved. Also check that the case number is unique and that classification fields are filled in when days away or restricted hours are entered.

Where did Acknowledge and send as email go on Notes?

These options are tied to Core HR performance notes, which are not supported in the unified platform, so they are not included. Existing acknowledgement data is preserved.

How does I get these pages?

An Arcoro admin turns on the Core HR Employee Tab Pages setting for the user in People. Until then, the Core HR tab links keep opening the legacy pages.