One of the most frustrating ways to start an Epic assignment is to arrive ready to work and discover you cannot get into the systems you need.
In my experience, provisioning is often the biggest onboarding problem. Sometimes Epic access is missing. Sometimes it is ServiceNow. Other times, email or Teams has not been set up either.
On assignments where this has been a problem, I have seen access take anywhere from one to four weeks to resolve, depending on how responsive IT is and how closely the manager follows up. That is my experience, not an industry-wide benchmark. But it is enough to make access one of the first things I would check before someone starts.
A start date does not necessarily mean a consultant is ready to do the assigned work. Neither does confirmation that an access request has been submitted.
Start with the work, then check the access
An onboarding checklist should connect each system to what the consultant is expected to do. If they are supposed to work tickets, can they access the ticketing system? If they need to join project discussions, can they use email and Teams? If they are assigned Epic work, have the appropriate permissions and required prerequisites been completed?
The emphasis is on appropriate access. A useful onboarding process gets someone the permissions their assignment requires, through the organization's approved process. It does not mean giving every consultant every permission just to avoid a delay.
It also helps to distinguish between an account being created and that account actually working for the assigned task. Those are different checkpoints.
The checklist I would use before day one
For an Epic consultant, these are the core items I would want the hiring manager and onboarding team to review:
- Epic: Confirm the required environment and role-appropriate access for the assignment. Identify any training or approval steps that must happen first, and who owns each outstanding item.
- ServiceNow or the organization's ticketing system: Confirm the consultant can access the work they are expected to support. Establish how they should report an access problem if they cannot enter the ticketing system itself.
- Email: Confirm the account is usable and the consultant has the information needed to connect with the project team.
- Microsoft Office: Confirm the tools needed for the assignment are available, rather than assuming that email access covers everything.
- Teams: Confirm the consultant can participate in the relevant meetings and team discussions.
- An onboarding contact: Name someone who can coordinate unresolved issues. The consultant should not have to guess which department owns each missing piece.
- A first-day check: Verify access through approved sign-in and task checks. Record what still needs attention, who is handling it, and what work can proceed in the meantime.
This is a starting point, not a substitute for the hospital's own security, training, and onboarding requirements. Each organization will have additional steps.
Waiting for access does not have to mean waiting to contribute
When I have been blocked from systems, I have used the time to help colleagues think through their tickets at a strategic level. I have also met people on my team, other teams, and the clinical decision-makers involved in the work.
That time can reveal things you would not learn from reading a ticket. Why is the hospital's workflow set up this way? What decisions led to the current process? Who understands the practical impact of a proposed change?
Those conversations give me context for the work I will eventually do in the system. They can also make it easier to find the right person when a question crosses team boundaries.
None of that requires borrowing somebody else's credentials or working around an access restriction. It requires choosing useful work that fits the access and authorization you actually have.
The manager still needs to close the gap
There is a difference between making productive use of a delay and treating the delay as acceptable. A consultant can learn the organization while the manager continues following up on provisioning. Both should happen.
Before your next consultant starts, walk through the tools they will need and test your assumptions. The simplest question is often the most useful: what would stop this person from doing the work we hired them to do?
If you are bringing in Epic consulting support, BridgeLine Health can discuss the assignment and the experience it calls for. Include your onboarding requirements in that conversation so the role and the path to getting started are clear from the outset.