How should a lean team evaluate an outsourced enablement coordinator's work sample?
A work-sample rubric for outsourced enablement coordination that scores evidence handling, structure, and review readiness.

Purpose of the work sample
A work sample helps a lean team judge whether an outsourced enablement coordinator can do the actual work, not just describe it. The sample should test the tasks the role will own in the first month: organizing assets, checking claims, preparing a review packet, and recording the handoff. It should not test a generic writing skill or a software feature the coordinator will never use. Choose one task the role will repeat weekly rather than a one-off writing prompt.
Use the sample to compare candidates on the same task with the same instructions and the same review rubric. A consistent sample reduces the influence of a polished interview and gives the team evidence it can discuss. It also gives the candidate a realistic view of the work. A sample that is too abstract will attract the wrong person and frustrate the right one.
Design a realistic task
Choose a task that can be completed in about ninety minutes with materials the team can share safely. A good example is taking five enablement assets, grouping them by buyer question, and drafting a short recommendation for which one should be canonical. Another is preparing a launch handoff checklist from a provided asset list. Both tasks require judgment, not just formatting.
Use fictional or approved sample data. Do not ask a candidate to work with real customer information, live rate cards, or confidential launch plans. The task should include one ambiguity, such as two assets that appear to answer the same question differently. The candidate's handling of that ambiguity is more informative than a clean, easy task. State the time limit and whether the candidate may use public sources.
Write clear instructions
Give the candidate the goal, the audience, the materials, the time limit, and the deliverable format. Explain what the team will evaluate: accuracy, evidence handling, structure, and clarity of the recommendation. Do not hide the rubric, because the goal is to see how the candidate works against a real standard. A candidate who understands the standard is more likely to produce a useful sample.
Include a question the candidate can ask if something is unclear. Note whether the candidate asked it and how they proceeded. A coordinator who flags a missing source or an ambiguous instruction is showing a useful habit. A coordinator who invents an answer to fill the gap is showing a risk. Record both the question and the handling in the evaluation.
Build a scoring rubric
Score the sample on four dimensions: evidence handling, structure, accuracy, and review readiness. Evidence handling means every claim has a source and the candidate separates fact from inference. Structure means the deliverable follows the requested format and is easy to scan. Accuracy means the claims match the provided materials. Review readiness means a manager could approve or reject the work without reconstructing the candidate's reasoning.
Use a simple scale, such as one to four, with a written description of each level. A four is not perfect prose; it is work a reviewer could use with a small correction. A two is work that needs a new evidence pass. The descriptions should be specific enough that two reviewers score similarly. Avoid a single overall score, because it hides which dimension needs coaching.
Calibrate the reviewers
Have two reviewers score the same sample before the team reviews candidates. Compare their scores and discuss the differences. If one reviewer gives a four for structure while the other gives a two, the rubric needs a clearer example. Calibration takes less time than debating candidate quality without a shared standard. Record the scores before the discussion so the calibration is not anchored by the louder reviewer.
Record the calibration result and any rubric change. If the reviewers cannot agree on a sample after a short discussion, the task or the rubric is ambiguous. Fix it before judging the next candidate. A rubric that only works for the person who wrote it will not help a lean team make a consistent hiring decision.
Review the evidence trail
Ask the candidate to include a short note on where each fact came from and what they could not verify. The note does not need to be a full source log, but it should show the candidate's evidence habit. A candidate who lists a source for every claim and flags a gap is easier to trust with real work than one who presents a polished summary with no trail. If the note is vague, ask the candidate what they would check next.
Check whether the candidate's citations actually support the claims. A link that opens to a different topic is worse than a missing link because it looks reliable. If the task uses internal sample documents, check that the candidate quoted the right section. Evidence handling is the dimension most likely to predict whether the coordinator can work without constant supervision.
Test the handoff, not just the artifact
Ask the candidate to write a short handoff note as part of the sample. The note should explain what they did, what remains open, and what the reviewer should check. This tests whether the coordinator can prepare work for another person, which is central to the role. A strong artifact with a weak handoff still creates review work for the manager.
Review the handoff note with the same rubric. Look for a clear next action, a named owner, and a limit the reviewer should know. A candidate who writes a handoff that a stranger could follow is demonstrating a skill the team will use every week. A candidate who assumes the reviewer has the same context is not ready for a distributed team.
Make the decision rule explicit
Decide before the sample how the scores will be used. A common rule is that no dimension may fall below two and the average must reach three. Set the rule in advance so a strong interview does not override a weak sample. The rule should reflect the work the role will own, not an idealized standard that no busy coordinator could meet.
Keep the scores and the reviewer notes for each candidate in one place. Compare candidates on the same dimensions and discuss the evidence, not the impression. If the team cannot fill the role at the required level, consider changing the task scope or the support model rather than lowering the rubric without a plan. Write the rule down before the next candidate so the decision does not drift.
Limits of a work sample
A short sample cannot show how a coordinator handles a real deadline, a difficult stakeholder, or a week with three competing priorities. It also favors candidates who are comfortable with the provided tools. State these limits and use the sample as one input among several. A structured reference check and a paid trial task can cover what the sample cannot.
The cited public sources describe employment, privacy, and security practice. They do not validate this rubric or predict performance. Use the sample to compare candidates against the team's own standard and to decide what support the new coordinator will need. Do not treat a high score as a guarantee. The rubric is a local hiring tool, not a validated test.
Follow up after hiring
After the first month, compare the new coordinator's actual work with the sample scores. Did the candidate who handled evidence well continue to do so under deadline pressure? Did a strong structure score translate into a usable library? Record the comparison and adjust the rubric for the next hire. Note which dimension predicted the actual result and which did not.
Share the result with the coordinator as coaching input, not as a verdict. The sample is a starting signal, and the real work is the better measure. Keep the rubric and the sample task in the team's hiring record so the next evaluation starts from evidence rather than a blank page. A short follow-up review is more useful than a score kept without context.