Who You Lose by Requiring It
The requirement filters applicants, and the filter works against the people a client most wants to hire.
A monitoring requirement does not reduce the number of applicants uniformly. It changes the composition, and the direction is consistent.
The issue in “Who You Lose by Requiring It” becomes easier to manage when the record and its limits are explicit. A team reviewing this workforce solution for fte meaning should choose only the necessary evidence, explain how it will be used and keep a human correction path open.
Who declines
Contractors with enough demand to choose their engagements.
For an independent reference relevant to “Who You Lose by Requiring It”, consult the European Data Protection Board guidelines; compare its principles with the proposed contract, collection, access model and real review process.
Specialists whose work is thinking rather than execution, for whom tracking penalises the thing they are paid for.
People with established direct clients, who do not need marketplace terms.
And anybody with professional obligations that make screen capture awkward, which the other-clients note covers.
Who accepts without negotiating
Contractors new to the market, building a record.
People in markets where every client requires it.
And those who have not calculated the overhead.
Not a judgement about their ability — several are excellent — but the selection is real and it is not in the direction a client would choose.
The specialist problem specifically
The more the work involves judgement, the worse tracking fits it and the more likely the specialist declines.
Which means the requirement is least acceptable to the people whose work is hardest to replace.
For routine execution the filter costs little; for analysis, design or architecture it costs a great deal.
What this looks like in practice
A shortlist that is cheaper and less experienced than the one you would have had.
Longer time to fill.
And a higher failure rate on the engagements you do make, because you selected on willingness to be monitored rather than on fit.
Testing it cheaply
Advertise the same role twice: once with the requirement, once offering fixed price with milestones.
Compare who applies.
Most clients who run this find the second list stronger, and it costs nothing to find out.
Where the filter does not matter
High-volume routine work with many available contractors.
Short engagements where fit matters less.
First engagements with somebody unknown, where it is a genuine bridge.
In those cases the cost is small and the arrangement is defensible.
The reasonable middle
Require it for the first engagement, then review.
Offer fixed price as an alternative at the point of hiring.
Both keep the protection for the case it was built for and remove the filter for everything after, which is the practical conclusion.
What to check
Who declined your last monitored engagement, and why?
Is the work execution or judgement?
Have you ever offered an alternative at the point of hiring?
And would your shortlist look different without the requirement?