A recent customer-success hire shows how missing instructions can leave a new team member unsure of what to do. After that real example, this onboarding plan uses an illustrative administration assistant joining an operations team. It combines role context, guided practice, and review across five days. The agenda is illustrative, not a fixed Covela onboarding programme or a promise of independent work by Friday. Use the offshore onboarding checklist to prepare before the start date, then use this article to organise the first week of learning and work.
Early Check-Ins Exposed Missing Onboarding Instructions
An urgent hire can fill a vacancy before the business has prepared the instructions the person needs. In a recent customer-success hire described by Covela founder Lambros Photios, a customer moved quickly to backfill a role. The customer had been experiencing turnover in that role roughly every six months. During onboarding, we found that the new team member felt lost because the documentation and onboarding process did not explain what to do.
Our early HR check-ins brought the gap to our attention while we could help the customer address it. We interview team members at day one, week one, and month one. In this case, we raised the issue with the customer, worked through the onboarding needs in virtual calls, and used those discussions to help the customer produce documentation for the role.
The customer now has reusable documentation within its onboarding process and is better prepared for the next hire. That is the outcome Lambros reported; we do not yet have evidence that the changes reduced turnover. The previous six-month pattern also does not establish why earlier team members left.
The practical lesson is to ask the new team member whether they know what to do, then address the specific instructions they are missing. In this case, Covela helped the customer improve its onboarding documentation. The customer retained responsibility for role training and daily direction. The administration example below shows one way a manager could put clear instructions and supported practice into a first-week plan; it is separate from this customer experience.
Connect Role Training to a Complete First Task
Role training needs to explain why the work matters before asking the person to complete it. Introduce the colleagues who use the output, show where the task sits in the wider process, and explain which decisions the person can make. A first task then needs enough information for the person to attempt it and enough clarity for a manager to review it. Choose a small piece of real work with a known source, a defined output, and limited consequences if it needs correction. Keep sensitive or irreversible actions behind the relevant approval.
For the administration example, the first assignment is preparing a meeting pack from approved material. The manager supplies the current template, the source documents, and an example of a pack that has already been reviewed. The assistant prepares a draft; the manager approves it before distribution.
The task brief should record:
- The purpose of the meeting and who will use the pack.
- The source documents and which version is current.
- The expected file format and where to save the draft.
- The deadline, including its time zone.
- The checks the assistant should complete before submitting it.
- The reviewer and the questions that need escalation.
A login alone does not establish that the task is ready. Before assigning it, confirm that the person can open the required material, use the template, and save the output in the right place. If access is incomplete, record the blocker and its owner, then assign an appropriate task that can proceed.
One Manager Should Resolve Conflicting Instructions
A new team member needs to know whose decision takes priority when several people request work. Name the manager who owns the initial workload and a backup who can answer questions when that manager is unavailable. Other colleagues can contribute context, but changes to priorities should go through the agreed decision-maker.
For an offshore role, write down the working hours and the shared time available for questions. Set review meetings inside that overlap and identify the channel for urgent issues. If the team member is waiting on a decision, they should be able to state what is blocked, who can resolve it, and which deadline is affected.
Your business remains responsible for role onboarding, process documentation, system access, and training. We provide onboarding facilities through our platform and our required security policies, alongside HR and performance support. As the customer-success example shows, that support can include helping a customer address an onboarding gap. Agree the support needed for your role; your manager still directs the daily work and reviews its quality.
A First-Week Onboarding Agenda Should Combine Learning and Practice
The sequence below moves from a demonstration to a repeat task with less guidance. It keeps review time visible in the manager’s schedule, rather than treating questions and corrections as interruptions. Adjust the pace to the role, the person’s experience, and the evidence from completed work.
| Day | Team Member’s Work | Manager’s Contribution | Record to Keep |
|---|---|---|---|
| Monday | Meet the team, confirm access, learn the role’s purpose, and walk through an approved meeting pack | Introduce key colleagues, explain the workflow, demonstrate the process, and identify approval limits | Access gaps, questions, and the agreed task instructions |
| Tuesday | Prepare the first pack and flag missing or conflicting information | Review the draft against the criteria and explain corrections | Draft version, feedback, and unresolved questions |
| Wednesday | Revise the pack and repeat the relevant checks | Confirm whether the corrections meet the criteria; update unclear instructions | Accepted version or specific changes still required |
| Thursday | Prepare a second, comparable pack with less step-by-step guidance | Remain available for exceptions and review the result | Differences between the two tasks and how they were handled |
| Friday | Summarise completed work, open items, and support needed | Agree next week’s scope and review frequency | Accepted work, open actions, owners, and next review dates |
A fixed calendar should not force a task to progress before its inputs are ready. If Tuesday’s draft exposes an unclear instruction, resolve that instruction before judging the person’s ability to follow it. If the instructions were clear and an error remains, identify the missed check and review a corrected example.
The second task should be similar enough to show whether feedback was applied. Adding unrelated responsibilities immediately can make it harder to distinguish a training gap from unfamiliar work. Expand the scope when the person has shown how they handle the current task and its exceptions.
Agree What “Complete” Means Before Reviewing the Output
Feedback during onboarding is easier to apply when the acceptance criteria are visible in the original brief. For the meeting-pack example, the manager might require the correct meeting date, approved agenda wording, all listed attachments, and a draft saved in the agreed folder. These are suggested criteria for this example, not a universal standard for administration work.
| Check | Example of Acceptable Evidence | Approval Boundary |
|---|---|---|
| Meeting details | Date, time, time zone, and attendees match the confirmed invitation | Conflicting details go back to the manager |
| Agenda | Items match the approved agenda source | The assistant does not invent or reprioritise agenda items |
| Attachments | Each required document is present and matches the supplied version | Missing or uncertain versions are flagged |
| Output location | The draft is saved with the agreed name in the review folder | External distribution waits for approval |
| Open questions | Unresolved items identify the decision needed and its owner | The manager resolves decisions outside the assistant’s authority |
In a hypothetical Tuesday review, the pack contains the correct agenda but omits one attachment because the source file was unavailable. The assistant has recorded the missing file and asked the manager to confirm its location. The pack remains awaiting input; the manager supplies the file before asking for a final version.
If the attachment was available and the assistant overlooked it, the feedback should identify the omission and the check to repeat. For example: “Add the approved budget attachment, then compare the pack against the attachment list before resubmitting.” The reviewer can then assess the correction against the same criteria.
“Looks good” gives a weaker review record than a specific acceptance decision. A useful note would say: “Version 2 accepted for this meeting. Required documents checked. Manager approved distribution.” Acceptance applies to that output; it does not automatically grant authority to distribute future packs without review.
Keep Blocked Work Separate From Work Needing Correction
Blocked work needs an input or decision; work needing correction needs a change to the output. Recording those states separately helps the manager direct the next action. A shared queue can use straightforward labels such as ready to start, in progress, awaiting input, ready for review, and accepted.
Each open item should identify the next action and its owner. “Waiting” is incomplete. “Waiting for the manager to confirm the final agenda before Tuesday’s meeting” tells the team what must happen next. Add a due time when it matters to the task.
Corrections should also improve the instructions when they reveal a recurring ambiguity. Save the approved example and update the relevant step, so the next task begins with the clarified process. Keep a named owner for those documents to avoid several conflicting versions becoming routine.
End the Week With a Decision About the Next Workload
The first-week review should determine what the person can repeat, what still needs support, and which responsibilities should remain with the manager. Review actual outputs and open questions rather than relying only on how busy the week felt.
For the administration example, the manager might approve another week of meeting-pack preparation while retaining final distribution approval. CRM updates could remain outside the workload until their source records and review rules are ready. This is an illustrative scope decision, not a required progression for every assistant.
Record the next week’s tasks, who reviews them, and when feedback will be available. Keep unresolved access issues and training needs on the same action list. A review can be constructive even when the decision is to continue practising the original task.
Covela checks in with team members after one day, one week, and one month, then quarterly, with a more substantial review at each annual anniversary. Those check-ins support the working relationship; your manager continues to supervise and review daily work. Our performance-management guidance explains how those responsibilities fit together.
Adapt Onboarding to the Role You Have Hired
The onboarding sequence can stay consistent while the training and work examples change. An administration role may begin with a meeting pack; a bookkeeper may begin with a defined set of records and a finance reviewer. The source material, approval boundaries, and evidence of completion need to reflect that role.
Use the bookkeeper handover guide for finance-specific preparation, or the virtual assistant hiring guide if you are still defining an administration role. Keep the main onboarding checklist as the place to confirm access, responsibilities, and readiness across roles.
If you are planning a new offshore role, start a brief with the recurring work, required hours, and manager who will direct it. Those details help us discuss the staffing arrangement while your business prepares role training and the first week’s work.