A Project Does Not Fit in a Spreadsheet: How to Hand Over Link Building Without Restarting Research
A practical method for handing over a link building project with verifiable context: goals, decisions, opportunities, commitments, owners, and open questions.
Why a Change of Owner Can Restart a Project Without Anyone Intending It
A link building project is not just a list of publications or potential URLs. It also contains reasoning: why a landing page was prioritized, which editorial approach was approved, which opportunities were ruled out, who authorized a condition, and which conversations remain open. When that context lives in messages, scattered tabs, emails, or one person’s memory, a change of owner can turn work already completed into research that must be repeated. The risk is not only lost time. It can also lead to resuming contact with people who asked not to receive further pitches, interpreting an estimate as a committed date, reopening a rejected opportunity without new information, or continuing a collaboration without validating its terms. A good handover does not try to present the history as a guarantee that the plan will work. Its purpose is to enable the incoming person to understand what is known, what was decided, what still needs to be checked, and what they can do next with sound judgment.
- Operational information must outlast the person who gathered it.
- Every opportunity needs context, not just a URL, a price, or a metric.
- Forecasts, initiated contacts, and stated terms do not equal confirmed outcomes.
- The goal of the handover is to reduce assumptions, not to speed up decisions without review.
Start With a Handover Package, Not an Export
To understand how to hand over a link building project, it helps to treat the delivery as an operational package. A spreadsheet can be part of it, but it should not be the only resource. The package brings together the summary needed for decisions, the inventory needed for execution, and the evidence or sources needed for review when necessary. The first page should make it possible to understand the project in a few minutes: current goal, scope, work period, involved landing pages, constraints, owners, and the next relevant decision. Then, the detail should be organized by workstream, such as prospecting, evaluation, outreach, negotiation, content, validation, and follow-up. This way, the person receiving the project can reconstruct its status without having to read every previous conversation.
- Goal: what is being supported and with what business or SEO priority.
- Scope: markets, languages, collaboration types, budget, or internal limits if they are defined.
- Landing pages: URL, search intent, core message, and editorial constraints.
- Status by workstream: complete, in progress, blocked, paused, or awaiting a decision.
- Owners: who executes, who approves, and who needs to be informed.
- Context sources: links to documents, threads, or evidence accessible to the team.
Use Four Certainty Labels So Information Is Not Confused With Decisions
The clarity of a handover depends less on accumulating fields than on distinguishing the nature of each piece of information. One useful approach is to label information across four levels. This separation prevents a comment from a counterpart from becoming, through inertia, an accepted condition; or an internal recommendation from appearing to be a verified fact. Verified facts are observations that can be checked against a source and a date. Stated conditions are details communicated by a third party that may still require formal confirmation. Approved decisions are internal agreements with an owner and date. Items pending confirmation are explicit questions that should not turn into implicit tasks or promises. In practice, every important record should include a certainty label, update date, source, and the person who logged the note. If information changes, retain the relevant change and its reason; there is no need to turn the project into an endless archive of every minor interaction.
- Verified: traceable evidence, verification date, and the exact scope of what was checked.
- Stated: a communicated condition, availability, or detail that is pending validation where applicable.
- Approved: an internal decision, approver, date, and the criterion supporting it.
- Pending confirmation: a specific question, the person or source that can resolve it, and a planned review date.
Create a Minimum Inventory That Reflects the Real Status of Opportunities
The inventory should not be an indiscriminate list of possibilities. Its purpose is to help decide what to keep, what to review, and what not to resume. To do this, classify each opportunity as active, rejected, paused, or pending review. Status describes the current situation; priority indicates relative importance. They are different fields, and both are needed. An active opportunity has an action underway and a clear owner. A rejected opportunity is no longer suitable for a documented reason. A paused opportunity could be valid, but a dependency or decision prevents progress. An opportunity pending review should not yet be contacted or approved because an important check is missing. This classification reduces the risk of reopening conversations without sound criteria or leaving critical tasks without an owner.
- Internal identifier or opportunity name.
- Status and priority, recorded separately.
- Landing page and proposed approach, where applicable.
- Last action, date, owner, and specific next step.
- Reason for rejection, pause, or pending review.
- Links to available evidence and relevant conversations.
- Expiry or review date when the context may become outdated.
Record Editorial Context and Landing Page Details
A proposed link cannot be evaluated in isolation. The handover should note which landing page was meant to be supported, why it fits the topic, which search intent it addresses, and what type of content or mention was considered reasonable. This is not about mechanically imposing anchor text or assuming that a metric summarizes an opportunity’s quality. It is about documenting the editorial and commercial criteria used to assess it. Constraints should also be clear: messages that should not be used, sensitive topics, legal or brand review requirements, languages, geography, exclusivity arrangements, and any condition that affects publication. Where paid collaborations are involved, the record should state that the commercial nature must be handled transparently. Depending on the case, links in a paid collaboration may require attributes such as sponsored or nofollow. Final implementation and disclosure should be reviewed according to the editorial agreement and applicable guidelines. Google explains the use of rel="sponsored" to identify links that are part of advertisements, sponsorships, or other compensation arrangements, and accepts rel="nofollow" as an alternative when sponsored is not possible. This reference helps document the criterion, but it does not replace review of the specific case.
- Destination URL, page objective, and priority.
- Proposed topic, audience, and editorial format.
- Rationale for fit and any known objections.
- Link text or suggested wording, if available, without treating it as an automatic requirement.
- Commercial transparency needs, link attribution, and editorial review.
- Brand, legal, territorial, or language restrictions.
Document Commitments, Dates, and Dependencies Without Turning Them Into Promises
In link building, approximate dates, changing availability, and terms subject to approval are common. For that reason, the handover should record the degree of commitment for each milestone. A date proposed by a third party is not the same as a date confirmed in writing, and neither guarantees that a publication will produce a specific SEO result. For every commitment, note what is expected, who expressed it, through which channel, what remains for it to take effect, and what happens if it is delayed. When several people are involved, identify dependencies: content approval, landing page validation, budget, brand materials, or a response from an external counterpart. This allows the incoming person to prioritize real blockers instead of chasing dates that were never confirmed.
- A specific milestone or condition, without ambiguous wording such as “closed” if steps remain.
- Confirmation level: estimated, stated, internally approved, or confirmed in writing.
- Date, time zone where relevant, and information source.
- Dependencies, the owner of each one, and follow-up date.
- Fallback plan or escalation criterion if the milestone is not met.
- An explicit note that publication timelines do not equal guaranteed SEO outcomes.
Hold a Handover Meeting Focused on Identifying Gaps
Documentation reduces context loss, but it does not eliminate assumptions. A short, prepared meeting helps verify that the project is understood in the same way on both sides of the transition. It is not a read-through of the inventory: it should focus on reversible and irreversible decisions, risks, differences in judgment, and actions that cannot wait. The outgoing person should explain where information is solid and where there is interpretation. The incoming person should raise questions from the current goal, rather than from a need to rebuild the entire history. If there is no clear answer, the outcome should not be an assumption: open a pending item with an owner and review date.
- What is the most urgent decision that cannot be made from the inventory alone?
- Which active opportunities could lose relevance if no action is taken this week?
- Which rejected opportunities should not be reopened unless new evidence appears?
- Which terms have been stated but are not yet confirmed?
- What criterion was used to prioritize landing pages and opportunities?
- Which approvals, materials, or external responses are blocking progress?
- Which counterparts require especially careful communication or a single point of contact?
Frequently asked questions
What should a link building project handover include?+
At a minimum, it should include the goal and scope, landing pages, the status of each workstream, an opportunity inventory, owners, next steps, approved decisions, pending conditions, and links to the sources that make the information verifiable.
How can you prevent the new owner from repeating the research?+
Record the reason behind every decision, not just the outcome. Include what was verified, what was stated by third parties, what was approved internally, and what remains unconfirmed. Rejected opportunities should include a reason and an explicit condition for reconsidering them.
Is handing over a spreadsheet enough?+
Not always. A spreadsheet can serve as the inventory, but the handover also needs an operational summary, a decision log, owners, and access to relevant evidence or conversations.
How should paid collaborations be documented?+
Record the commercial nature of the collaboration, the agreed or pending terms, the person responsible for validating them, and transparency requirements. Depending on the case, links may require sponsored or nofollow attributes. It is advisable to review implementation and disclosure with the publication and according to applicable guidelines.
What should the incoming person validate before resuming outreach?+
They should check the current goal, landing page, latest contact and its date, terms that remain unconfirmed, brand or legal restrictions, the owner of the next action, and whether new evidence changes the priority or previous rejection.
Sources and references
- Google Search Essentials — Google Search Central
- Spam policies for Google web search — Google Search Central
- Qualify outbound links — Google Search Central