# Referral outstanding questions tracker | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-track-questions-waiting-on-the-company
Last updated: 2026-11-04

Track the question, never the answer. Each open item is one line: which permitted question was asked, who at the company can answer it, where the answer should travel, when it was asked, one reminder date and a drop date. When the answer comes, the line records that it came, by which route and on which day, and nothing it said. Questions SourceX raises in its review never appear on your board, and a decision, such as whether to apply, gets no reminder at all.

This page is for the operations lead at a consultancy, accounting firm, managed service provider, agency or fund who needs to know what the firm is still waiting to hear from referred companies, without the tracker turning into a file of what those companies hold.

## A question is not a step

A step is work someone owes; when nobody owns one, the fix is a named owner and a date, as the guide to [referrals with no named next-step owner](/guides/when-a-referral-has-no-named-next-step-owner) sets out. A question is different in two ways.

- **Its answer has content.** "Which entity holds the records?" can come back with a registry number, or with a paragraph about the company's systems. The second is not yours to keep.
- **Silence is a legitimate answer.** A company that does not reply has told you something. A question record needs a date on which the firm stops asking, not just a date by which someone should act.

So the board stores the existence of each question, its route and its dates, and treats silence after the drop date as a closed line. The Federal Trade Commission's guide to protecting personal information makes the same argument for any business record: if there is no legitimate need for sensitive information, do not collect it, keep what you need only as long as you need it, and give each employee access only to what their job requires, which the guide calls the "principle of least privilege" (our paraphrase apart from that phrase).

## Six questions a partner may leave open, and the ones it never asks

Before an introduction, a partner needs only a handful of facts from the company, and all of them come from the CEO or someone the CEO names.

| Code | Question | Who can answer | Where the answer goes |
|---|---|---|---|
| P1 | Does the CEO want a conversation about licensing company records? | The CEO | Your referral record, as a dated permission |
| P2 | Has anyone at the company dealt with SourceX before? | The CEO | Your referral record, before anything is submitted |
| P3 | Which entity holds the records, and who decides for it? | The CEO | Your referral record, then the introduction |
| P4 | Which facts may travel in the introduction? | The CEO | The introduction, and nowhere else |
| P5 | Who should SourceX's first message go to? | The CEO | The introduction |
| P6 | When, if at all, would the CEO like to hear from you again? | The CEO | The board's reminder date |

P2 matters because section 3 of the terms treats any earlier application, relationship, lead, account or email correspondence between SourceX and the company as a duplicate that is not credited to a later partner. The four fit facts (a full-time headcount that peaked at 50 or more, contractors excluded; years of records made in the company's own work; its right to license them; and a CEO keen to talk) are the CEO's to state in their own words; record them as pass, unknown or fail in the referral record, as in the [three-object referral CRM schema](/guides/the-referral-crm-should-track-companies-permissions-and-next-steps), not on the board.

Some questions never belong on a partner's board, whoever wants the answer:

- record counts, samples, exports or screenshots;
- logins or access to any system;
- what customer contracts say about reuse;
- what the records might be worth, or what a deal might pay;
- anything SourceX asks the company during its review.

Those answers travel from the company to SourceX through SourceX's own process, or to the company's counsel. SourceX's process page is explicit that a partner need not export, upload or describe confidential records, and the partner agreement gives a partner no authority to share them. When a company asks you something you cannot answer, such as whether data from one system is enough, point to SourceX's published answer on [whether one system's data can be enough](/questions/one-system-company-data-enough-for-licensing) rather than opening a line.

## The question owner and deadline board

One line per open question, and these columns only.

| Column | What goes in it | Rule |
|---|---|---|
| Ref | Referral code plus question code, such as R-047/P3 | Never the company's name |
| Answerer | A role at the company: the CEO, or a person the CEO named | Changed only when the CEO names someone |
| Asked by | The colleague who put the question | That colleague owns the line |
| Route | To your firm, in the introduction, or company to SourceX | Decides whether anything is recorded at all |
| Asked | Date | Set when the question goes out |
| Reminder | One date, or "none" for a decision or a company-set wait | Never two |
| Drop | Date the line closes if unanswered | Set when the line opens |
| State | Open, answered, dropped or withdrawn | Answered means the date and route, nothing more |

Five rules keep it small:

1. **A line holds a code, not a sentence the company wrote.** P3, not "which of our three subsidiaries owns the dispatch archive".
2. **Close on the route, never on the content.** "Answered day 6, to the firm, recorded in the referral record" is a complete close.
3. **One reminder, then wait.** When the drop date arrives, the line closes as dropped. A dropped line is a normal ending, not a failure.
4. **A decision is not a question.** Whether the company applies, licenses anything or carries on is its own call; SourceX's process page leaves the company in control of whether to proceed. The board may note the window's end for your own planning, with "none" in the reminder column, and that date never appears in a message to the company.
5. **SourceX's questions are not lines.** After an introduction, SourceX may communicate directly with the company, and the agreement says a partner need not join every call or email. If a CEO forwards you something SourceX asked, reply that it is for SourceX, keep nothing and open no line.

## Whose clock each date runs on

| Date | Whose clock | Can it move? |
|---|---|---|
| Reminder and drop dates | Your firm's | Yes, but only later, never earlier |
| "After our board meets" or a similar date | The company's | Only when the company moves it; use it as the reminder, as in [following up after a company asks for more time](/guides/a-referral-follow-up-after-a-company-has-asked-for-more-time) |
| Day 90 after the recorded introduction | The program's | No; the terms say the window does not extend |
| SourceX's review steps | SourceX's | Not shown to partners beyond generic stages on the dashboard |

The 90-day window is the one hard date, and it belongs to your planning, not to the company's agenda.

## Who moves a line, and when the operations lead steps in

- **The colleague who asked owns the line** until it closes. If that colleague changes role, the line moves with the referral.
- **A weekly sweep.** The operations lead closes every line past its drop date, checks that no line has two reminders and deletes any answer text that crept into a note.
- **A complaint ends the board for that company.** If a CEO says the questions feel like pressure, every open line for that company is withdrawn the same day, and the referral record gets a do-not-raise flag if the CEO asks for one.
- **A wrong-route answer.** When a company sends records instead of an answer, the line closes as answered by the wrong route, the material is deleted and the CEO is told. The [metadata-only referral queue](/guides/how-to-build-a-referral-queue-without-uploading-client-data) has a fuller routine for the day a file arrives.
- **Questions the founder asks you** run the other way and live elsewhere; a [backlog for founder questions](/guides/a-backlog-for-founder-questions-your-platform-team-cannot-answer) routes those to whoever can answer.

## One referral's board over six weeks (Illustrative)

Illustrative: a generic company, invented dates and no outcome implied beyond what is described.

The CEO of a 180-person regional engineering consultancy agreed on day 0 to hear about licensing. The relationship owner opened R-047.

| Line | Asked | Reminder | Drop | How it closed |
|---|---|---|---|---|
| R-047/P1 | Day 0 | Day 5 | Day 10 | Answered day 2, to the firm, recorded as a dated permission |
| R-047/P2 | Day 2 | Day 9 | Day 16 | Answered day 4, to the firm, recorded in the referral record before anything was submitted |
| R-047/P3 | Day 2 | Day 9, sent | Day 16 | Answered day 13, to the firm, after the one reminder |
| R-047/P4 | Day 13 | Day 18 | Day 25 | Answered day 15; the facts went into the introduction |
| Application | Day 15 | None: a decision | Window ends day 105 | The dashboard showed an application on day 38 |

On day 12, the snapshot in the graphic, two lines were answered and P3 was open with its reminder already spent. The introduction went in on day 15. The CEO then said she would decide after her board met in week 5, so the board carried no reminder at all for the application. On day 33 she forwarded a question SourceX had sent her about customer contracts; the relationship owner replied that it was one for SourceX and her counsel, kept no copy and opened no line. No record of the company's ever sat on the board.

## Closing lines, and what is left when the referral ends

When the referral closes, delete the board's lines for it. The agreement's return-or-delete clause already excepts records needed for reward accounting and dispute evidence, and those live in the referral record (the dated permission, the introduction reference, the dashboard labels), not on the board. A board that holds only codes and dates can go without loss.

## Where a question board goes wrong

- **It becomes a chase list.** A board that counts unanswered lines invites people to clear them by asking harder. Count dropped lines as normal endings, and report reminders sent, which should never exceed one per line.
- **Content creeps in.** A "notes" column is where answers end up. Do not create one.
- **It cannot see SourceX's side.** The dashboard shows generic stages, and partners never get access to applicant documents. A long silence after an application is not a question for the company.
- **No outcome data yet.** Whether boards like this shorten the time from a CEO's yes to an application is unmeasured; log ask and answer dates for two quarters to find out. No figures are published.

More playbooks for referral operations sit in the [guides library](/guides).

## 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.

Once your board holds codes and dates and nothing a company wrote, [register your firm as a partner](/register), keep [who qualifies](/who-qualifies) open when the CEO answers P1 to P3, and read the [program terms](/terms) for the one date your board cannot move.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/how-it-works
- https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business
