Turn a monitored item into a useful post idea
A high relevance score is a reason to inspect an item. It is not a reason to repeat its claims or publish a response automatically.
In Monitoring, read the source snippet and Judge’s reasoning together. Then decide whether the item gives your audience something worth understanding, checking or doing.
Read the decision before acting on it
Monitoring uses three labels:
- Seeded → draft means the item has been selected for drafting. If a pending draft is available, Review the draft → takes you to Approvals.
- Logged to backlog means the item has been retained as an idea. It is not a published post or a promise of an immediate draft.
- Ignored means it has not been selected as relevant.
If a seeded item shows a draft status instead of a review link, read that status before assuming the draft is waiting for approval.
The snippet is only an excerpt. Find and read the original source before relying on it. Check who published it, when it was published, and whether the source supports the claim you want to discuss. A strong opinion, a prediction and a confirmed product change require different wording.
Decide what you can add
An item is worth developing when you can explain why it matters to your reader and contribute something beyond a shorter version of the source.
For an illustrative example, imagine an independent repair business sees a manufacturer's notice about a discontinued component. A useful response might explain which customers should check a part number and where to find it. A weak response would announce a sweeping shortage that the notice never described.
Before drafting, make a short working note:
Source: the manufacturer's dated notice. Reader: owners checking whether their device is affected. Useful addition: where to find the part number. Boundary: do not imply all models are affected or promise replacement stock we have not confirmed.
This is an invented example, not a monitored result from Solocial. The structure separates the source's claim from your own explanation. If you cannot identify a useful addition, leaving the item alone is a reasonable decision.
Correct a relevance decision without confusing it with post review
For an item that does not fit, choose Not relevant, actually. For an ignored item you believe matters, choose This WAS relevant.
The first action changes the relevance decision to ignored. The second changes it to logged and adds it to the idea backlog. It does not immediately create or approve a post.
These controls give feedback on the monitoring decision. They are not publishing controls. If an item has already produced a draft, inspect that draft separately in Approvals; do not assume marking its source irrelevant rejects the draft or cancels a post already in progress.
If a pending draft is available, use Review the draft →. Check that it preserves the source's scope, identifies uncertainty, and does not present someone else's experience as yours. Then follow the approval-queue review steps.
Improve the inputs when the feed is unhelpful
Use manage watchlist to open Connections. The watchlist lets you choose supported sources, a category and Add to watchlist. Available source choices include LinkedIn, X, Blog / RSS and YouTube. The category choices include Competitor, Industry news and Inspiration.
Pick a source because it regularly contains something you need to know, not just because it is popular. Watching a competitor does not mean their posts should become your posts.
In the watchlist, check Active, Last post seen and any source-status explanation. A paused or unavailable source is different from a quiet source. Switch off a source you no longer need, or use Remove. Monitoring allowances depend on your plan.
When Monitoring shows Nothing judged yet, check that you have active supported sources and look for any source error in Connections. Allow for the next check; monitoring is not an instant search across every social network.