This scorecard is part of the guide to partial-credit evaluation in an ordinary workflow, which scores one vendor onboarding that collected every document but never got the controller's approval. That guide shows the arithmetic. This page asks the earlier question: does a client's workflow archive hold enough step-level detail for anyone to do that arithmetic at all?
Why weight the criteria instead of counting them
Partial credit depends on seeing each step on its own. Some record properties matter far more than others for that: a workflow that records every approval separately but deletes abandoned requests can still be scored on finished cases, while one that keeps only a final status cannot be scored step by step at all. Equal weights would hide that difference, so the scorecard weights each criterion by how much partial scoring depends on it.
Research benchmarks show what the records must support. TheAgentCompany, a benchmark of workplace tasks, gives full marks only when every required stage passes, and otherwise blends the share of stages completed with a bonus reserved for finishing. A buyer applying a rule like that needs each stage visible, dated and attributable.
The partial-credit evaluation scorecard
Eligibility gates (all must pass before scoring)
| Gate | Pass | Fail |
|---|---|---|
| Headcount | 50+ full-time employees at peak, contractors excluded | Under 50, or mostly contractors |
| Operating history | Several years of workflow history in an ERP or workflow tool | A recent start or a rebuilt system |
| Rights | The company owns its workflow records; software terms allow use | A parent, outsourcer or vendor controls them |
| Authority | A named CEO can approve a licensing discussion | Nobody can say who decides |
Location is a fifth gate, and outside the U.S., Canada and the EU it includes English share. The rule in full: Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
Weighted record criteria (100 points)
| Criterion | Weight | Full points when | Half points when | Zero when |
|---|---|---|---|---|
| Named steps | 20 | A written procedure lists each step, such as tax form, insurance, bank details, approval | Steps are known but not written down | "It depends who handles it" |
| Step-level records | 25 | Each step has its own entry with date and approver in a workflow tool | Some steps recorded, others by email | Only a final status survives |
| Stalled attempts kept | 20 | Abandoned or rejected requests stay in the system with their status | Kept for a while, then purged | Deleted or never entered |
| Versioned procedure | 15 | Dated history of steps added or removed | Changes known informally | No idea when the steps changed |
| Final outcome linked | 10 | The process links to its real-world result, such as the first payment to a new vendor | Linkable by name and date only | No link |
| Retention span | 10 | Several years of workflow history with a known start date | One to two years | Months |
Reading the total. With every gate passed: 75 to 100 is strong, 50 to 74 is borderline (introduce with the low rows named), under 50 is weak for now. A zero on step-level records caps the result at borderline, however high the total, because nothing between zero and full completion can be scored without it.
Five questions that settle the weights
Ask the controller, procurement lead or COO. Each answers from memory; no screen needs to be shared.
| # | Question | Criterion it scores |
|---|---|---|
| 1 | Which multi-step processes have a written procedure with named steps? | Named steps |
| 2 | Is each step recorded separately, with a date and approver, in a workflow tool? | Step-level records |
| 3 | Do stalled or abandoned attempts stay in the system, or are they deleted? | Stalled attempts kept |
| 4 | Is the procedure versioned, with dates for added or removed steps? | Versioned procedure |
| 5 | Who owns the ERP and workflow history, and who can authorize a licensing discussion? | Rights and authority gates |
Follow question 2 with "and is the final result linked, for example the vendor's first payment?" and "how far back does the history go?" to score the last two rows.
Some tools make question 2 easy to answer. Microsoft's documentation for Dynamics 365 Finance says edits to approval-flagged vendor fields are held as proposed changes and written to the vendor record only after every approval step is complete, and vendor bank accounts have their own approval workflow in which approvers can reject, delegate or cancel. A controller running a setup like that can usually describe exactly which steps leave records. A controller whose onboarding runs through a shared inbox usually cannot.
Three fits, scored (Illustrative)
All three companies are fictional; the scores show the method, not a forecast.
Strong: a 280-person property management company. Vendor onboarding follows a written four-step procedure in an ERP workflow: tax form, insurance certificate, bank details through a separate approval, and controller sign-off. Each step has a date and approver. Rejected requests stay with their status for two years before archiving, the procedure was last changed on a known date, and first payments can be matched to an onboarding only by vendor name and date. Workflow history starts two years ago, after an ERP move. Scores: 20, 25, 10, 15, 5, 5 for 80.
Borderline: a 150-person regional construction firm. Subcontractor onboarding has named steps, but insurance and tax forms arrive by email and only the final vendor record sits in the ERP, so some steps are recorded and others are not. Stalled requests are deleted after 90 days, procedure changes are known only informally, payments carry the vendor ID from day one, and workflow history covers about two years. Scores: 20, 12.5, 0, 7.5, 10, 5 for 55. Worth introducing, with the email-only steps named.
Weak: a 65-person software consultancy. Vendors are set up by whoever needs one; there is no written procedure and nothing between "requested" and "active." Payments can be matched to vendors only by name and date, and accounting history goes back about two years. Scores: 0, 0, 0, 0, 5, 5 for 10. Not ready, however willing the founder.
Who owns the records, and what the score leaves open
Finance usually owns approval history, procurement owns the onboarding procedure, and IT runs the ERP or workflow tool. The CEO, or the owner in an owner-run firm, authorizes a licensing discussion. The company needs 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license, and an authorized contact.
The score cannot show how many cases a buyer could actually grade, how tax identifiers and bank details would be removed, whether software vendor terms limit use, or whether any buyer wants this task type. Some buyers want step-scored material only for testing models, never for training them, which is a different agreement; see evaluation-only data licenses. Discovery stays at metadata level: partners never ask for vendor files, screenshots or exports.
Check the basics with the company qualification checklist, and see how approvals are assessed more generally in procurement approvals and exception workflows and on procurement and vendor workflows. Low rows can be described using partial-credit evaluation evidence gaps; after an introduction the company prepares the partial-credit evaluation review packet. The introducer guide to operational data licensing covers the rest of the process.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If every gate passes and the records score 50 or more with step-level records above zero, register as a partner, confirm the basics on who qualifies, and read the terms before you introduce the CFO or COO.