Published November 19, 2026.
A new hire opens the onboarding portal with a mix of curiosity and nerves. A broken link at that moment teaches them that the workplace is disorganized. The page may have worked when it was published and failed after a system change. A short link check before the start date prevents that first impression.
List the routes a new hire actually uses
Start with the links in the welcome message rather than the full site map. The welcome message is the first path most new hires follow. Add the links in the first-day checklist and the benefits enrollment page. These are the routes where a failure is most visible.
Ask a recent hire which links they used in their first week. Their answer often includes a page that the onboarding team forgot. A recent hire also remembers which link confused them. Use their list to correct the official one.
Keep the list short and name each route by the task it supports. "Direct deposit setup" is clearer than a raw URL. A task name also helps a reviewer know what a working page should contain. Store the list beside the portal administration notes.
Test with an account that looks like a new hire
Use a test account with the same permissions as a new hire. An administrator account can open pages that a new hire cannot, which hides permission errors. A test account also shows the wording a new person actually sees. Ask the system owner to create or refresh the account before the check.
Test the full path rather than checking links in isolation. A page can load and still fail when a form is submitted. Follow each route to the point where the new hire completes the task. Stop before submitting real data and use test values where the system allows.
Repeat the test on a phone as well as a computer if new hires use both. A page that works on a desktop may collapse on a small screen. The first week often includes staff who rely on a phone. A quick mobile check catches the most common layout failures.
Decide what counts as broken
Agree on a definition before the check begins. A page that returns an error, a form that will not submit, and a login loop all count as broken. A page with outdated instructions counts as broken for this purpose even if it loads. The definition keeps the review from turning into a debate.
Separate a broken link from a missing document. A missing document may be a content problem rather than a technical one. Record the category so the right person can fix it. A technical fix and a content fix often follow different routes.
Set a severity level for each finding. A broken benefits enrollment page is more urgent than a broken optional resource page. Severity helps the team fix the most important route first. It also gives a manager a way to decide whether to delay a start date.
Record the check with a date and an owner
Write the date, the reviewer, and the environment used for the test. A record without an environment is hard to reproduce. Note whether the test used a desktop, a phone, or both. This detail explains why a later user might see something different.
For each broken route, name the owner and the expected fix date. An owner is a person rather than a team. The fix date should be before the next scheduled start. A finding without an owner tends to sit until someone complains.
Keep the record in the same place as the onboarding checklist. A separate audit file is easy to forget. One location also helps a new onboarding coordinator find the history. Attach a screenshot only when it clarifies the failure.
Fix the common failures first
Broken links often cluster around a few causes such as a changed domain or an expired form. Fix the shared cause rather than each link one by one. A domain change can break ten pages at once. Repairing the cause saves time and prevents a repeat.
Update the welcome message when a link changes. A fixed portal page is not useful if the message still points to the old address. Ask the person who sends the welcome message to confirm the new link. A short confirmation closes the loop.
Tell the support desk about any route that will be fixed after a new hire starts. The desk can help the new person if the page is still broken. A prepared support desk turns a failure into a quick recovery. Silence turns it into a complaint.
Check again before each start date
Run the check on a schedule tied to hiring rather than to a calendar quarter. A start date is the moment when a broken link matters most. A weekly check during a busy hiring period is reasonable. A monthly check may be enough during a quiet period.
Use the same route list and the same test account each time. A consistent method makes the results comparable. It also makes the check faster as the reviewer learns the path. Save the list with the portal notes so a new reviewer can repeat it.
Add a final check on the business day before the start. Systems change quickly and a link that worked last week may fail today. A short confirmation of the critical routes is enough. The final check is the last line of defense before the new hire logs in.
Review the process after a failed start
When a new hire reports a broken link, treat it as a process signal rather than a one-off. Ask how the failure escaped the pre-start check. The answer may reveal a route that was missing from the list. Update the list before the next start.
Look at whether the failure caused the new hire to wait or to ask for help. A quick recovery is less damaging than a long delay. Record the recovery time so the team can see the impact. A short delay is a warning, while a long one needs a fix.
Share the lesson with the people who maintain the portal. A fix that stays with one coordinator will be lost when that person moves. A short note in the onboarding guide keeps the knowledge. Over time, the portal becomes more reliable with each start.
