Build a First-30-Days Scorecard for a Philippines Offshore Hire

# Build a first-30-days scorecard for a Philippines offshore hire

A new offshore hire can look busy for a month without becoming ready to own useful work. Meetings are attended, documents are read, and managers answer questions, yet nobody has defined what the person should be able to do by day 10, 20, or 30. A first-month scorecard fixes that ambiguity. It turns onboarding into a sequence of observable results while preserving room for coaching and genuine learning.

The scorecard is not a probation verdict compressed into a spreadsheet. It is a shared operating agreement for the employee, the Philippines-based team lead, and the onshore process owner. It should reveal missing access, unclear instructions, weak examples, and unavailable reviewers as readily as it reveals a skill gap.

Start with the role's first useful outcome

Choose one recurring output that represents the role without exposing the business to its highest-risk decision. For an accounts payable coordinator, that might be a complete invoice discrepancy package rather than payment approval. For customer support, it might be an accurate drafted response for review rather than an unsupervised account change. For an executive assistant, it could be a conflict-checked calendar proposal rather than authority to accept commitments.

Describe the outcome in concrete terms: the input, permitted action, required evidence, reviewer, and acceptance condition. “Understand the process” cannot be scored consistently. “Prepare three cases from approved sources, flag every exception, and achieve reviewer acceptance without a missing field” can. Keep judgment and approval with the named owner until a separate authority decision is made.

Score conditions as well as performance

Create two sides of the record. The employee side covers demonstrated behavior: finding the authoritative source, following the sequence, documenting evidence, recognizing an exception, communicating status, and correcting returned work. The enablement side covers what the company supplied: active accounts, least-privilege permissions, current instructions, worked examples, practice cases, reviewer availability, and feedback within the promised time.

This distinction prevents a common error. If the employee could not complete a task because an account was never provisioned, the scorecard should show an access failure, not a performance failure. If a reviewer waits four days to return a first attempt, the delayed learning cycle belongs in the management record. Good onboarding makes both parties' obligations visible.

Use a small rating vocabulary tied to evidence. “Not yet attempted,” “completed with step-by-step guidance,” “completed with a prompt,” and “completed independently within current authority” are more useful than a subjective one-to-five score. Add an evidence link and reviewer note. A rating without an example invites inconsistent interpretation.

Days 1–5: prove safe access and orientation

The first checkpoint should confirm identity, equipment, secure sign-in, required policies, system access, and the location of current procedures. Test permissions rather than relying on a provisioning ticket marked complete. Ask the employee to perform one permitted action and confirm that a restricted action remains unavailable. Record any temporary workaround and its removal owner.

Then use a guided case to trace the work from request to closure. The employee should identify the source of truth, the output, the reviewer, the escalation path, and the data that must stay in an approved system. The goal is not speed. It is a correct mental map of the process and its boundaries.

For a Philippines-based employee working with an overseas manager, also test practical communication conditions. Confirm working-hour overlap in the relevant time zones, backup channels, expected acknowledgement times, and what counts as urgent. Do not infer availability from a calendar invite alone. Write the agreement in local times for both parties and specify how daylight-saving changes will be handled where applicable.

Days 6–10: observe practice work

Give the employee a small set of representative, non-sensitive or properly controlled cases. Include a normal item, an incomplete request, and a genuine exception. The employee should demonstrate that they can stop when evidence is missing instead of forcing every item through the happy path.

Review the work against a checklist that matches the actual output. Capture the first-pass result, reasons for return, questions asked, and correction. Avoid silently repairing the work before showing it to the employee. A correction that disappears into the reviewer's hands cannot improve the next attempt.

At the day-10 conversation, ask what remains unclear and compare that answer with the returned-work record. If several people misunderstand the same step, repair the instructions or example. If one person repeatedly skips a clearly taught control, plan focused coaching and a new demonstration.

Days 11–20: move into bounded live work

Introduce a limited live queue with a named reviewer and a safe volume cap. Define which items the employee may complete, which require pre-action review, and which must be escalated immediately. The manager should be able to see work in progress without demanding a private status report for every case.

Measure quality with denominators. Record first-review acceptance as accepted items divided by reviewed items, not as a bare count. Track returned items by reason, time in employee control, time waiting for a reviewer, and exceptions identified before action. Speed matters only after the team agrees when the clock starts, pauses, and ends.

Suppose a coordinator processes 18 requests. Four arrive without required evidence, 14 are reviewable, and 12 of those pass on first review. The useful record is 12 of 14 accepted, four correctly held for missing evidence, and two returned for specified corrections. Calling the result “12 completed” hides both judgment and learning.

Days 21–30: test continuity and judgment

The last checkpoint should test more than repetition. Ask the employee to prioritize a mixed queue, explain one escalation, prepare a handoff another person can continue, and locate the current instruction without using a personal copy. Include a realistic interruption or reviewer absence so the team can see whether backup ownership works.

Review trends across the month. Is first-pass quality improving? Are the same error reasons recurring? Does work stall at the same approval point? Are questions becoming more specific? Look at a sample of actual records rather than relying on a manager's general impression.

The day-30 decision may be to continue the lane, extend supervised practice, narrow scope, repair enablement, or begin a separate discussion about broader authority. It should not automatically grant access or approval rights. Competent preparation and authorized decision-making are different controls.

Keep the conversation fair and specific

Share the scorecard at the start, not on day 30. Hold short checkpoint conversations and let the employee add context or point to evidence. Separate a correctable skill issue from a policy question, system outage, workload spike, or unavailable reviewer. Personnel decisions should follow the employer's applicable policies and qualified advice, not an improvised content checklist.

Store only information needed for the onboarding purpose, use approved access controls, and follow retention rules. The Philippine National Privacy Commission's Data Privacy Act materials provide a first-party starting point for privacy responsibilities; company counsel or a qualified privacy owner should interpret obligations for the specific employment and data context.

A compact scorecard layout

Use rows for the milestone, evidence expected, employee status, enablement status, reviewer, observed result, feedback date, next demonstration, and due date. Add a decision log for changes to scope or access. A single page can work if links point to the authoritative records.

End with five questions: Can the person produce the bounded output? Can they identify an exception? Can another teammate continue from their record? Did the company provide the promised conditions? What exact evidence supports the next decision? Those answers create a more useful first month than a vague declaration that onboarding is complete.

If you are defining the first month for a new role, explore Offshore Resourcing's onboarding coordination service or request a role plan. Bring the intended output, source systems, restricted decisions, reviewer capacity, working-hour needs, and two or three realistic examples.

Sources and further reading

• Philippine National Privacy Commission: Data Privacy Act resources
• NIST Cybersecurity Framework 2.0
• CISA: Secure Our World
• ISO: Quality management principles