What you can hire me to deliver
- An employee journey and onboarding content plan.
- Policy-based scripts with named approval owners.
- Tool demonstrations, process guides and onboarding checklists.
- A publishing and update register tied to approved policy versions.
Make the employee journey the starting point
Employees rarely experience HR as a collection of policies. They need to join the company, request leave, update information, understand expectations or ask for help. A useful HR content plan follows those moments and identifies the information required at each stage. It also makes clear when a person should contact HR instead of relying on a recorded explanation.
I can help map the journey from an accepted offer through the first working period and later employment changes. The content brief separates shared company information from role-specific instructions. That keeps a new employee from receiving the entire handbook as an undifferentiated video series.
Have a specific workflow or content brief in mind? Send the audience, the task and your current material. I can help define the next useful scope.
Discuss human resourcesConnect instructions to the systems employees use
A video showing a request form is only useful if the employee can reach the form and has permission to submit it. I review the surrounding workflow: where the link lives, which account is required, what information is needed and how the employee knows the request has been received. Supporting screenshots should use demonstration data and avoid exposing real personnel information.
For recurring processes, a short written guide often complements the demonstration. Employees can scan the prerequisites and next step without replaying an entire video. The content should also explain who handles a failed submission or a case the form does not cover.
Separate acknowledgment from understanding
An employee can acknowledge a policy without remembering how to apply it. A scenario can check whether someone knows where to report an issue or which process applies to a common request. The assessment should be proportionate to the subject and approved by HR; sensitive employee matters should not become public examples or casual quiz material.
Reporting can distinguish assignment, completion, acknowledgment and any learning check. Access to those records should match your organization’s responsibilities and retention choices. I can help clarify the technical workflow while your HR and privacy owners decide what should be collected.
Illustrative first-week onboarding package
A practical first project could cover account setup, essential company information and the first manager check-in. The package might include an orientation video, a checklist of required actions, demonstrations of the main employee tools and a clear contact map. Role-specific training remains a separate path so the employee can see which tasks are expected now and which follow later.
Before rollout, test the package with someone unfamiliar with the process. Watch for missing access, unexplained abbreviations and links that assume an employee already knows where to look. Those observations are more useful than approving the material solely because the slides look consistent.
How delivery and scope are agreed
Start with a representative task and the people who can approve it. We agree the audience, source material, formats, review responsibilities and acceptance check before expanding production. A focused pilot makes it possible to evaluate both the content and the workflow required to use it.
Brief and source review
Confirm the task, available inputs and responsible reviewers. Separate decisions that need your approval from implementation work I can own.
One complete example
Produce a reviewable script, asset or workflow prototype. Test the important assumptions before repeating the approach across a library.
Review and pilot
Check accuracy with the source owner and usability with representative people. Record the agreed revisions and unresolved limits.
Publish and maintain
Deliver the agreed formats, editable sources and ownership notes. Define the publishing destination and the changes that trigger a review.
What shapes the quote
The quote depends on the condition of the source material, subject complexity, number of assets and languages, production method, integrations and review rounds. Specialist filming, language partners, platform licenses and external assets are itemized when needed. A target date and the review schedule are agreed after those dependencies are understood.
Implementation experience behind the service
My EverestX project work covers talent onboarding, client requirements, hiring requests, account transitions and lifecycle notifications. That experience is relevant to the handoffs between people and systems in an onboarding or learning process. That provides useful context for designing the content alongside its operational handoffs.
Explore EverestX onboarding workflows experience →Questions before we start
Can you rewrite our employee policies?
I can help make approved material clearer and turn it into training assets. Changes to policy meaning, employment terms or legal interpretation need approval from your responsible HR or legal owner.
Can the content include confidential employee examples?
We should use fictional or appropriately anonymized examples and demonstration accounts. The project brief identifies what information can be used and which reviewers must approve it before publication.
Bring me the task you need to explain.
Share the employee journey you want to improve, the approved source policy, the employee locations or arrangements in scope and the tools involved. Do not send employee records in the initial message.
Send your project brief on WhatsApp