Two Lists, Two Decisions: The System That Stops Prospects From Automatically Becoming Approvals
Learn how to separate research findings from opportunities ready for approval or outreach. An operational method with fields, statuses, owners, and handoff rules.
Why a list of findings is not the same as an execution plan
In link building, discovering a publication or domain does not mean it should be added to a campaign. It is a finding: a possibility that needs context, validation, and a decision. When the same spreadsheet, board, or database mixes findings with approved opportunities, predictable problems arise: an option is treated as approved even though nobody has validated it, budget is requested without a defined purpose, or a prospect that was already rejected gets researched again. The solution is not to add more columns to a single list, but to separate two different decisions. The first is research-oriented: “Is this finding worth keeping for analysis?” The second is operational: “Does it fit this project, and is it ready for review, approval, or outreach?” These questions require different information, different owners, and different timelines. This separation is especially useful for agencies and teams working across several campaigns. The same outlet may seem relevant to different projects, but that does not mean it should have the same priority, proposed content, or approval. The opportunity is not just the publisher: it is the publisher in relation to an objective, topic, destination page, and conditions that need to be reviewed at that point in time. In addition, availability, rates, editorial requirements, and metrics from external tools may change. They should be recorded with a source and date checked, but not treated as permanent attributes or as a promise of results.
- A finding answers a research hypothesis; a validated opportunity supports a specific action.
- Not every publication relevant to a topic is suitable for every project.
- An approval should be explicit, traceable, and tied to a defined use.
- Variable data needs a verification date and should not be carried over without review.
The two layers of the system: a research inventory and a validated opportunity inventory
The system relies on two related but independent inventories. They can live in two tables within the same tool, two separate views in a database, or two sheets with shared identifiers. What matters is that one is not confused with the other. The research inventory collects domains, publications, sections, or contacts found through topic-based searches, search-result analysis, recommendations, competitor review, or exploration of industry sources. Its purpose is to retain signals and prevent the same work from being done twice. This is where immature alternatives, incomplete references, and opportunities that do not yet belong to any campaign can sit. The validated opportunity inventory contains only units that are ready for a business or execution decision. Each record should state what is to be achieved, for which project, with which destination page, through which format, and who needs to make the next decision. It is not a general catalogue: it is a prioritized queue of contextualized proposals. Assigning a stable identifier to each research finding is helpful. When a validated opportunity is created, it retains a reference to that identifier. This preserves the history without duplicating knowledge or turning a possible collaboration into an automatic approval.
- Research inventory: a record of discovery and initial assessment.
- Validated opportunity inventory: proposals tied to a campaign and a next action.
- Source identifier: the link between both layers that maintains traceability.
- One source can generate several validated opportunities when projects or purposes differ.
What to record when you discover a prospect, and what not to assume yet
The research record should be lightweight. Its purpose is to let someone else understand why the finding was saved and resume the work without repeating everything. If a full audit is required before a record can be added, the team will end up using personal notes or parallel lists. At a minimum, record the identifier, domain or publication, the specific URL that prompted the finding when available, the observed topic or section, the source of discovery, the date, the owner, and a short note on the fit hypothesis. If a public contact route or collaboration page has already been found, note it as a reference without turning it into a confirmed condition. It can also be useful to retain initial review signals, such as apparent language, country or market, content type, evidence of recent editorial content, or potential topic restrictions. These are observations, not verdicts. Do not assume that a publication accepts collaborations, that a rate seen in the past is still current, that a link will have a particular attribute, that the destination URL can be chosen, or that one metric reflects the opportunity’s overall quality. If you record changing information, include the date, source, and confidence level. This makes it possible to distinguish confirmed information from information that still needs verification.
- Minimum fields: ID, outlet, reference URL, topic, source, date, owner, and fit note.
- Recommended fields: observed market or language, content type, and identified restrictions.
- Variable data: record the source, date checked, and verification status.
- Do not turn an observation, historical rate, or isolated metric into implicit approval.
Handoff criteria: when an opportunity deserves editorial, commercial, and strategic review
Moving an item to the validated opportunity inventory should not depend on a vague intuition or on the finding having an eye-catching number. It should happen when the initial research provides enough evidence to formulate a concrete proposal and when there is a reason to dedicate review time or budget. A practical rule is to require four conditions. First, reasoned topical and editorial relevance: the publication, its section, or its apparent audience relates to the proposed content. Second, strategic fit: there is a project, purpose, and destination page that could benefit from a contextual, coherent mention. Third, operational feasibility: there is a realistic way to ask about terms or start a conversation. Fourth, traceability: the sources of the data and the outstanding unknowns are documented. From there, review can be divided into three lenses. The editorial lens assesses quality, the suitability of the approach, consistency with the publication’s editorial direction, and transparency. The commercial lens checks terms, the scope of the arrangement, indicative budget where appropriate, and approval owners. The strategic lens reviews priority, suitability for the destination page, plan diversity, and concentration risks. Not everything needs to be finalized before an opportunity is handed off. However, what needs to be validated and why should be sufficiently defined. If there is only a domain with no usage hypothesis, it remains in research.
- Editorial relevance: a reasoned relationship between the outlet, topic, and possible content.
- Strategic fit: identified project, objective, and destination.
- Operational feasibility: a realistic next action exists to obtain or confirm terms.
- Traceability: sources, dates, questions, and owner are documented.
- Validation opens a review; it is not the same as commissioning work or guaranteeing publication.
Recommended statuses to avoid confusing pending, rejected, approved, and reusable
Statuses should describe an operational situation, not a feeling. A short system works better than one full of nuances that are impossible to maintain. Each status should also have a definition, an owner, and a clear next action. For research, use statuses such as: New, for records without an initial review; Under review, for findings someone is validating; Awaiting information, when an essential detail is missing; Ready to propose, when the handoff criteria are met; On hold, when it may be revisited later; and Rejected, when a reason for not proceeding has been documented. For validated opportunities, a useful sequence is: Pending internal review; Pending client or owner approval; Approved for outreach or negotiation; In contact or negotiation; Confirmed for execution; Published or completed; Not approved; and Reusable for future review. “Reusable” does not mean available or approved for every case: it indicates that the learning may provide a starting point if it is verified again for another project or period. Avoid the generic status “approved” if it does not specify what has been approved. You may approve researching an option, making contact, allocating budget, negotiating terms, proposing content, or carrying out a collaboration. The status name should reflect the scope of the decision.
- Keep distinct statuses for research and execution.
- Set a mandatory next action for every active status.
- Record a structured reason for rejections and non-approvals.
- Replace “approved” with statuses that specify the scope: approved for outreach, negotiation, or execution.
- Review on-hold and reusable opportunities before using them again.
How to link each validated opportunity to an objective, topic, destination page, format, and project
A validated opportunity should be understandable without opening ten conversations or asking the person who created it. To achieve that, turn each record into a contextualized work proposal. The outlet is only one part of the record. Include the project or client, the action objective, the proposed topic or editorial angle, the destination page, the intended format, and the priority. The objective may, for example, be to support the visibility of a useful resource, reinforce the topical coverage of a campaign, or obtain a contextual mention within a relevant piece. It should not be reduced to a single metric or used to promise specific SEO effects. Also add the fit rationale: why that publication and format are appropriate for that destination. This note requires semantic and editorial coherence to be reviewed before the proposal is sent for approval. If the destination is too commercial for the available angle, or if the planned content does not provide value to the outlet’s audience, it is better to reframe the opportunity or return it to research. The format field should be descriptive, not presumptive: proposed editorial content, an update, a contextual mention, or another approach that can genuinely be suggested and must be confirmed with the publication. Paid collaborations should be transparent. Depending on the case, attributes such as rel="sponsored" or rel="nofollow" may be appropriate; the decision should respect applicable policies and the publisher’s terms. Google explains the use of these attributes in its documentation on qualifying outbound links: https://developers.google.com/search/docs/crawling-indexing/qualify-outbound-links
- Project: who would use the opportunity and in which campaign.
- Objective: the specific purpose of the action.
- Topic and angle: what content may be useful and editorially coherent.
- Destination page: exact URL, purpose, and contextual suitability.
- Format: a proposal subject to confirmation, not an assumed condition.
- Rationale: documented reason for the fit between outlet, content, and destination.
What to do with prospects that are not approved: archive, reasoned rejection, or future review
A non-approval is not necessarily a research mistake. It may result from a limited budget, a shift in priorities, an incompatible approach, a topic that is already covered, or an editorial decision by the other party. If the record is simply deleted, the team loses knowledge and repeats work in the future. Distinguish between three destinations. The archive keeps historical opportunities that are not active but whose information may be useful as background. Reasoned rejection is used when there is a consistent reason not to consider the prospect again under similar conditions: lack of topical fit, practices incompatible with the project criteria, insufficient information after a proportionate review, or structural duplication. Future review is reserved for options that could fit another campaign, another approach, or a new check. Record a standardized reason and a free-form note. The standardized reason makes trend filtering possible; the note preserves nuance. For example, “not approved due to current priority” is not the same as “rejected due to lack of editorial fit.” This distinction prevents a temporary no from becoming a permanent prohibition. Set a review date only for records that genuinely have a reason to be revisited. Without a trigger, the On hold status can become a limbo that hides pending work.
- Archive: preserve background without keeping it in the active queue.
- Reasoned rejection: use it when there is a stable, documented reason.
- Future review: requires a reason and a review date or trigger.
- Separate “not approved now” from “not suitable in general.”
- Use standardized reasons to analyze patterns and free-form notes to preserve context.
Frequently asked questions
Why do I need two lists to organize link building prospects?+
Because they address different decisions. The research list retains findings and hypotheses; the validated opportunity list brings together proposals linked to a project, an objective, and a next action. Separating them prevents discovering a publication from being interpreted as approving it.
What must a prospect have to move to the validated opportunity list?+
It should have a basic rationale for editorial relevance, an identified project and purpose, a realistic way to confirm terms, and a record of sources, dates, and outstanding unknowns. It does not need to have every condition finalized.
Can an approved opportunity be reused for another campaign?+
It can be reused as a research reference, but it should be evaluated again in the context of the new project. The topic, destination, format, terms, and availability may not be the same.
Which statuses are essential in this system?+
In research: New, Under review, Awaiting information, Ready to propose, On hold, and Rejected. In validated opportunities: Pending review, Pending approval, Approved for outreach, In negotiation, Confirmed for execution, Completed, Not approved, and Reusable for future review.
How should links be handled in paid collaborations?+
Paid collaborations should be communicated transparently and handled according to applicable policies. Depending on the agreement and circumstances, rel="sponsored" or rel="nofollow" attributes may be appropriate. The attribute should not be assumed before editorial terms are confirmed.
Sources and references
- Google Search Essentials — Google Search Central
- Spam policies for Google web search — Google Search Central
- Qualify outbound links — Google Search Central