Key takeaways
- Score a small set of measurable vendor behaviors and keep definitions stable.
- Judge delivery evidence from your own team, not account-management polish.
- Check access accuracy and replacement handling every quarter.
- Require a current roster and a tested coverage path.
- Close with one improvement and one renewal condition, each with an owner.
Choose a small set of vendor measures
A vendor scorecard works when it measures the few things that affect delivery and can be checked. Start with fill time, replacement time, access accuracy, invoice accuracy, and the quality of the candidates presented. Add a delivery measure only if the provider shares responsibility for it. Too many measures turn the review into a data collection exercise.
Define each measure in one sentence and keep the definition stable across quarters. Record the source of the data so a later reviewer can repeat the number. Use raw counts beside any percentage when the sample is small. A scorecard that changes its rules cannot show a trend.
Score delivery evidence, not account management
A friendly account manager is not evidence that the developer is delivering. Score the candidate quality, the first-month ramp, the review record, and the handoff notes the developer produces. Ask for examples rather than impressions. The account relationship matters, but it should not hide a weak delivery pattern.
Compare the provider's claims with what your own team observed. If the provider reports fast fill times but the first two candidates could not start, the measure is incomplete. Record the gap and ask how the process will change. A scorecard is useful when it produces a question the provider must answer.
Review access and replacement handling
Access handling is a strong signal of operational discipline. Check whether accounts are named, approved, reviewed, and removed on schedule. A provider that treats access as an administrative afterthought will create risk when a developer leaves. Score the accuracy of the access record, not the speed of granting everything.
Replacement handling matters as much as initial placement. Ask how quickly a replacement is proposed, what handoff is included, and who owns the transition. Review one real replacement if one occurred during the quarter. A provider that plans for turnover is easier to trust with a critical seat.
Ask for the roster and coverage record
Request a current roster with roles, start dates, and named contacts, and compare it with your own records. Confirm the coverage plan for holidays, leave, and escalations. Check that the provider's contact list is current and that the escalation path has been tested. These documents are simple to produce when the operation is well run.
Keep the roster and coverage record with the contract so the next reviewer can see what changed. Note any unexplained gap between the provider's list and the people who actually worked. A roster is not a surveillance tool, but it should be accurate enough to support billing and access review. That comparison is the fastest way to find a billing error or an unapproved substitution.
Run the review with the same questions each quarter
Use a fixed agenda so each quarter is comparable. Review the measures, the delivery evidence, the access record, and one improvement from the previous review. Ask the provider to bring evidence rather than a presentation. Keep the meeting short and write the decisions down.
Invite the buyer owner, the delivery lead, and the provider contact, and keep the group small. If a measure failed, ask for the cause and the corrective action with a date. Do not let a good relationship smooth over an unresolved failure. The record should show what was accepted and what was not.
Use the review to improve the next quarter
Turn the scorecard into a short list of changes for the next quarter rather than a grade for the past one. If fill time was slow, ask which part of the process caused the delay and who owns the fix. If access records were inaccurate, agree on the source of truth and the review date. A measure that does not change a process is only a scoreboard.
Share the summary with the provider and the internal budget owner so expectations match. Keep the language factual and tie each point to evidence. Avoid comparing providers on a single number without the definitions behind it. The review should make the next placement or renewal decision easier to defend.
Keep the scorecard evidence in one place
Store the quarterly evidence pack, the scorecard, and the commitments in one folder that the contract owner can reach. Link each score to the source record rather than copying a number without context. A new reviewer should be able to reconstruct the quarter from the folder. That test shows whether the evidence is real or only a summary.
Keep the pack for the life of the engagement and for the period your records policy requires. Remove personal data that is not needed for the review. If the provider disputes a point, add its response rather than deleting the original. A durable record makes the next review faster and the renewal decision easier to explain.
Write one improvement and one renewal condition
End each review with one improvement the provider will make and one condition the buyer needs before renewal. The improvement should be specific and checkable, such as a corrected access record or a shorter replacement handoff. The renewal condition should protect the next quarter, such as a named backup or a completed security review. Two commitments are easier to track than ten.
Record the owner and the due date for each commitment and review them at the start of the next meeting. If the same commitment is carried twice, treat it as a performance issue rather than a scheduling problem. Share the summary with the people who approve the contract. A scorecard earns its place when it changes what happens next.
Questions about assessing Philippine developers
How many measures should a vendor scorecard have?
Five or six that the buyer can verify from its own records. More measures add work without improving the decision, and unstable definitions make quarter-to-quarter comparison meaningless.
Should the scorecard include developer performance?
Only with a clear evidence standard and the buyer's own review record. The vendor review should focus on the provider's sourcing, access, replacement, and billing behavior.
What if the provider disputes a score?
Ask for the underlying evidence and record the disagreement. A measure that cannot be reproduced from shared records is a weak measure and should be replaced.
