Proving the Work Happened: An Evidence Pack for Managed LinkedIn Outreach
Managed LinkedIn outreach requires transparent proof that comments, connections, and messages actually happened. This evidence pack specification defines what to document, what to protect, and how often to deliver.
Research this article with AI
Follow Well Met on Google
A client paying for managed LinkedIn outreach needs one question answered before anything else: did the work actually happen? Without evidence, the relationship runs on trust alone. Trust erodes the moment a client spots a gap, a delay, or a metric that doesn't match their expectations.
The evidence pack solves this. It documents every comment posted, every connection sent, every message delivered. It does this without exposing the target's private information, without violating LinkedIn's terms, and without creating a compliance liability for either party.
This specification defines what belongs in a proof-of-work evidence pack, what must stay out, and how often to deliver it. The goal is transparency that builds confidence without creating risk.
What evidence actually proves comments and messages were sent?
Four artifact types provide verifiable proof of outreach activity:
Comment screenshots with post context. Capture the published comment, the timestamp, and enough of the original post to confirm it was a real LinkedIn post, not a staged image. Include the post URL in the filename or in a log entry that references the screenshot. This proves the comment exists and can be independently verified.
Connection request confirmation screens. After sending a connection request, LinkedIn displays a brief confirmation overlay. Screenshot this screen. It shows the target's name and profile headline, proving the request was sent. Do not capture the personalized message text unless the client explicitly requests it and the service agreement permits sharing that level of detail.
Conversation thread previews with redacted message bodies. When a connection accepts and the conversation begins, capture the thread list view showing the recipient's name, the date, and the fact that messages were exchanged. Redact all message content with a solid black rectangle or blur. This proves the conversation exists without exposing what was said. If the client needs to review message quality, provide a separate sample set with explicit written consent documented in the service agreement.
Activity logs in structured format. A spreadsheet or CSV file with columns for date, time, target profile URL, action type (comment, connection request, message sent, message received), and a unique screenshot reference ID. This log acts as the index. Every claim in the log should match a corresponding screenshot or platform export.
- Comment screenshot: visible published comment, post author name, post URL or enough content to locate it, timestamp, your profile name or logo visible in the comment author field
- Connection confirmation: target name, profile headline, confirmation message (e.g., 'Invitation sent'), timestamp
- Conversation preview: recipient name, date of last message, thread exists indicator, all message text redacted
- Activity log: date, time, target profile URL, action type, screenshot reference ID, optional status note (e.g., 'accepted', 'pending', 'replied')
What should never be screenshotted or shared with a client?
When in doubt, ask: does this screenshot expose information the target or another client did not consent to share? If yes, redact or omit it.
- Full LinkedIn profile pages (name and headline in context are acceptable; full profile export is not)
- Unredacted direct message conversation threads (prove existence, not content)
- Inbox views showing multiple conversations or other clients' activity
- Platform analytics screenshots that include aggregate data from other accounts or campaigns
- Any content that reveals the target's email address, phone number, or other contact details not already public on their profile
How often should the evidence pack be delivered?
If the client requests a different cadence, document it in the service agreement. The default should match the activity level. High activity earns weekly delivery. Low activity shifts to monthly.
| Campaign Phase | Activity Level | Delivery Frequency | Rationale |
|---|---|---|---|
| Launch (first 2 weeks) | 100+ comments/week, 100–200 connections/week | Daily | Tight feedback loop to confirm targeting and messaging work; catch problems early |
| Active optimization | 100+ comments/week, 100–200 connections/week | Weekly | Matches weekly reporting rhythm; enough data to spot trends without overwhelming client |
| Maintenance | <50 comments/week, <50 connections/week | Monthly | Reduces admin overhead; trust established, client needs periodic confirmation only |
| Crisis or audit | Any volume | Daily | High-stakes troubleshooting; demonstrates responsiveness and transparency under scrutiny |
How do you structure the evidence pack for easy review?
This structure makes it trivial for a client to spot-check. They open the summary, see the totals, then drill into the Comments folder to verify a handful of examples. If the filenames are clear and the log is complete, the entire review takes five minutes.
- Top-level folder: YYYY-MM-DD_to_YYYY-MM-DD_Evidence
- Subfolders: Comments, Connections, Messages
- Screenshot filenames: YYYY-MM-DD_TargetFirstLastInitial_ActionType_Context.png
- Activity log: Activity_Log_YYYY-MM-DD_to_YYYY-MM-DD.csv with columns for date, time, target profile URL, action type, screenshot reference, status
- Summary PDF: one page, key metrics, period covered, deliver date
What tools automate evidence collection without manual screenshots?
No tool perfectly automates every evidence type. Connection confirmations and conversation thread previews still require manual capture in most workflows. The goal is to reduce manual work from 100% of actions to 20% of actions, focusing human time on the interactions that matter most.
How do you handle evidence when a connection blocks or reports you?
If a target blocks the profile or reports it to LinkedIn, the evidence changes form. The conversation thread disappears from your inbox. The connection vanishes from your network. You can no longer screenshot proof that the interaction occurred.
Capture evidence immediately after every message sent or connection accepted. Do not wait until the end of the week to gather screenshots. By that time, a block or report may have erased the thread. If you log the action in real time and screenshot within the same session, you preserve proof even if the relationship ends badly.
When a block or report happens, document it in the activity log with a note: '2026-09-18: Target blocked profile; conversation thread no longer accessible; final screenshot captured 2026-09-17 before block.' This transparency shows the client that you are not hiding a negative outcome. It also protects you from accusations that you failed to perform the work. The evidence exists up to the point the target terminated the interaction.
What privacy and compliance risks does the evidence pack introduce?
The evidence pack sits at the intersection of proof and privacy. Three risks require active mitigation:
Exposure of LinkedIn member data without consent. LinkedIn's terms prohibit scraping, automated collection, and sharing of member data outside the platform without permission. Screenshots of comments and connection requests are generally acceptable because they document your own activity, not bulk collection of third-party data. Screenshots of full profiles, contact details, or private messages cross into riskier territory. Stick to the minimum necessary to prove the action happened.
Client misuse of collected evidence. If you deliver unredacted message threads or full profile screenshots, the client could use that information for purposes outside the original engagement (competitive intelligence, direct solicitation, contact list building). Your service agreement should prohibit this and require that evidence is used only for performance verification. Include a clause stating that the client will not extract, store, or repurpose LinkedIn member data from the evidence pack.
Data breach or unauthorized access. Evidence packs contain names, profile URLs, and interaction details. If stored insecurely (unencrypted cloud folder, email attachment without password protection), they become a liability. Use encrypted file transfer (password-protected ZIP, secure client portal, or a service like Dropbox with link expiration). Delete evidence from your systems after the client confirms receipt, or retain it in an encrypted archive with a documented retention policy (e.g., 90 days for active clients, 30 days after contract termination).
- Minimize data collected: prove the action, not the person's full profile or private details
- Prohibit client misuse in the service agreement: evidence for performance verification only, no extraction or repurposing
- Encrypt file transfers: password-protected archives, secure portals, link expiration
- Document retention policy: 90 days active, 30 days post-termination, then permanent deletion
LinkedIn's terms prohibit scraping and bulk collection of member data
LinkedIn Marketing Solutions (accessed), 2026-09-26Marketing agencies track activity evidence and client reporting metrics to demonstrate proof of work and maintain transparency
AgencyAnalytics (accessed), 2026-09-26Client reporting combines quantitative metrics with qualitative context to prove work was done and budget was used appropriately
Improvado (accessed), 2026-09-26LinkedIn analytics includes engagement metrics such as clicks, impressions, and professional demographic information at account, campaign, and creative levels
Sprout Social (accessed), 2026-09-26Frequently asked questions
Can I just send the client a spreadsheet of activity without screenshots?
A spreadsheet without screenshots is a claim, not proof. Clients pay for evidence that the work happened. Screenshots of published comments, connection confirmations, and conversation threads provide that evidence. The activity log is the index, not the proof itself.
What if the client asks for full message transcripts to review quality?
Full message transcripts expose private conversation content that the recipient did not consent to share. If the client needs quality review, provide a separate sample set (5 to 10 representative threads) with explicit written consent documented in the service agreement. Redact all other message bodies in the standard evidence pack.
How do I prove a connection request was sent if LinkedIn doesn't show a confirmation screen every time?
Log the action in the activity log with the target profile URL, date, and time. If no confirmation screen appears, note 'No confirmation screen; request visible in Sent Invitations tab' and screenshot the Sent Invitations list showing the pending request. This provides traceable proof even without a dedicated confirmation overlay.
Should I include screenshots of comments that got zero engagement?
Yes. The evidence pack proves the work happened, not that every action succeeded. A comment with zero likes still demonstrates that you posted it, engaged with the target's content, and followed the strategy. Omitting low-engagement comments creates a selection bias that undermines trust.
What happens to the evidence pack after the client contract ends?
Your retention policy should specify a deletion timeline (e.g., 30 days post-termination). After that period, permanently delete all evidence files from your systems. Retaining them indefinitely creates an unnecessary data liability and violates privacy best practices. Document the deletion in your contract closeout log.