This scorecard is part of the guide to permission-aware agents and the second approver, which traces one account change minute by minute. That guide explains the concept. This page turns it into a scoring exercise for a call with an IT director, head of security or controller, using answers only, never files.
Three gates before any scoring
A gate is pass or fail. If one fails, stop: the approval records may be excellent, but the company cannot be introduced yet.
| Gate | Passes when | Question that settles it |
|---|---|---|
| Size | 50 or more full-time employees at peak, contractors excluded | "What was your full-time headcount at its highest?" |
| Authority | The CEO is named and could authorize a discussion about licensing IT and approval records | "Who would sign off on anything involving your identity or ticketing data?" |
| Location and English share | The company is in a covered country; outside the U.S., Canada and the EU, at least 70% of tickets, justifications and notes are in English | "Where is the company based, and are request reasons and ticket notes written in English?" |
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. The company also needs documented operating history and rights to license, which criteria 3 and 6 test in more detail.
Six criteria, each scored 0, 1 or 2
Ask in this order. Criteria 1 and 2 establish that permission-gated work happens and is enforced; 3 and 4 establish that its trail survives and connects; 5 and 6 establish that it can be judged and licensed.
| Criterion | 2 points: strong | 1 point: borderline | 0 points: weak |
|---|---|---|---|
| 1. Volume of gated changes | Admin role use, payment releases, credit limit or price overrides need a second approver hundreds of times a year | Dozens a year, or only in one department | Rare, or approvals happen verbally |
| 2. Enforced separation | The system blocks self-approval and records blocked attempts | Separation is policy only, checked in audits | Requester and approver are often the same person |
| 3. Retention beyond default | Approval and audit records archived outside the tool for several years | Archived for a year or two, or only some systems | Only what the tool keeps by default |
| 4. Request-to-action linkage | A ticket or change ID ties request, approval and action, and is validated | The ID is typed by hand and mostly right | Nothing connects the approval to the ticket or action |
| 5. Recorded outcome | Ticket closure, user confirmation or reversal is logged against the change | Closure is logged without the result | The change is made and nothing records whether it worked |
| 6. Rights clarity | The company owns its IT and approval records; no known provider term limits use | An MSP or outsourcer's contract has not been checked | A parent company, client or outsourcer controls the records |
Two sources explain why criteria 2 to 4 carry weight. Microsoft's documentation for Entra Privileged Identity Management says approvers can't approve their own activation requests, which is what system-enforced separation looks like. The same documentation says ticket information entered at activation is informational and not checked against any ticketing system, so linkage often depends on someone typing the right number. And Entra keeps audit logs seven days on the Free tier and 30 days on P1 and P2 unless they are routed to longer-term storage; expired data that was not archived cannot be recovered. A company scoring 0 on criterion 3 may hold years of tickets but almost no approvals.
Strong, borderline and weak fits
Add the six scores. The bands are a guide to the next action, not a verdict.
| Total | Band | What it usually looks like | Next action |
|---|---|---|---|
| 10 to 12 | Strong | Enforced approvals, archived logs, ticket links and outcomes across several years | Introduce the CIO, COO or CEO |
| 6 to 9 | Borderline | Approvals exist, but retention is short or linkage is manual | Ask whether audit logs were ever exported or archived, then decide |
| 0 to 5 | Weak | Approvals are informal, unlinked or gone | Note the company for later; do not introduce yet |
A borderline score often turns on one fact the IT director can find in a day, such as the date audit-log archiving began. That is worth asking for before the introduction, not after.
A worked score (Illustrative)
Illustrative and fictional. A 380-person civil engineering firm in Canada gives these answers on a discovery call with its IT director:
| Criterion | Answer given | Score |
|---|---|---|
| 1. Volume | About 90 admin role activations and 40 payment releases need a second approver each month | 2 |
| 2. Separation | Identity tool blocks self-approval; payment release is enforced in the ERP | 2 |
| 3. Retention | Audit logs streamed to an archive since 2021 | 2 |
| 4. Linkage | Change number required on activation, but typed by hand and not validated | 1 |
| 5. Outcome | Ticket closure notes record the result; reversals are linked | 2 |
| 6. Rights | Records are the firm's own; the managed service provider contract has not been reviewed | 1 |
| Total | 10 of 12, strong |
The two single points are honest borderline answers, not disqualifiers. Hand-typed change numbers mean some approvals will not link to their ticket. The MSP contract may or may not limit use; SourceX's rights review, not the introducer, settles it. The firm is worth introducing, with both points noted.
Questions that move a borderline score
Five follow-ups, asked in plain language, settle most borderline answers. None needs the phrase "permission-aware agents".
- "Which changes need a second person to approve, and roughly how many a month?" (criterion 1)
- "Can someone approve their own request, or does the system stop it?" (criterion 2)
- "How far back can you see who approved an admin change, and is that kept outside the tool?" (criterion 3)
- "When someone approves access, how do you tie it to the ticket and to what was actually changed?" (criterion 4)
- "Who owns these records, and is any of it held by an outside provider?" (criterion 6)
Keep the call at metadata level: which systems, how many changes, how many years, who owns them. Partners never ask for logs, screenshots or tickets. If you need a warm route to the IT director, the guide to introducing two people on LinkedIn covers it. The company qualification checklist and the introducer guide to operational data licensing cover the wider basics. Authority inside a task is not the same as the company's right to license; that distinction is in de-identification versus permission to license.
After a strong or borderline score, the evidence gaps analysis shows what is likely to be missing, and the review packet contents list shows what the company would assemble later. Other record families are in data types.
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 a client clears all three gates and scores 10 or more, or a borderline score you can explain, register as a partner, confirm the details on who qualifies, and read the program terms before you introduce the decision-maker.