To see the most recent followers free, you need a way to distinguish accounts already present from accounts newly observed. A top-of-list position is not enough unless the source explains its ordering. You can build a useful arrival report with authorized snapshots and ordinary spreadsheet tools, but the result should describe the observation window honestly. This guide focuses on identifying arrivals and deciding what, if anything, to do with them.
Define recent as a window, not a vague label
Choose the interval you care about: since yesterday's observation, since a workshop launch or since the previous weekly report. Record the earlier and later observation times with timezone. A report that simply says “recent” becomes difficult to interpret when someone opens it later. A dated interval stays meaningful and makes it possible to compare like periods.
Decide whether you need named arrivals or only a net audience change. Named arrivals require member-level evidence, while two totals can only establish a difference in counts. If your source supplies a limited preview, you may have useful examples but not a complete arrival list. Keep the scope small enough that the available evidence can answer the question you actually plan to report.
Keep the first snapshot as a baseline
Collect the incoming follower list through a source you are authorized to use, preserving its account, scope and available identifiers. Label the first successful record as a baseline. Every account in that list was present at that observation, but you may not know when each joined. Calling all of them new would inflate the first report and confuse later comparisons.
At the next observation, confirm the same direction and coverage before comparing. Record failed attempts rather than replacing them with empty lists. A missing observation creates a wider uncertainty interval; it does not create a period with zero followers. If you only have a current screen and no earlier record, establish today's baseline instead of pretending the missing history can be inferred from row order.
Find members present only in the later set
Clean the comparison keys consistently and remove exact duplicates in working copies. Then find identifiers in Later that are absent from Earlier. These are newly present in the observed set. Use stable identifiers where legitimately available; otherwise flag possible handle changes. Preserve the raw lists so you can investigate any suspiciously large set of additions without losing the original evidence.
Check several proposed arrivals manually against the earlier data. A truncated earlier export can make long-standing followers appear new. A cleaning mismatch, such as leaving an @ prefix on only one sheet, can do the same. For the underlying data checks, use the follower-list reading guide before assigning meaning to the comparison result.
Worked example: welcoming a workshop audience
Suppose a community workshop has a complete follower snapshot before registration opens and another two days later. Seven identifiers appear only in the later list, while three earlier identifiers are absent. The observed audience gained four members overall, but the arrival set contains seven names. A net increase of four should not be used as a list of four specific new people.
The organizer wants to welcome interested readers. Instead of sending unsolicited individual messages to every observed arrival, they publish a clear public introduction with workshop information and a voluntary contact route. The arrival report helped identify a useful communication moment, but it did not establish why each person followed or whether they wanted a direct sales message. The action stays proportionate to the evidence.
Be precise about timing
If an account was absent at 09:00 Monday and present at 09:00 Wednesday, the supported statement is that it was newly observed between those snapshots. Do not assign Wednesday morning as the exact follow time. A narrower interval requires another valid observation or a documented event-time source. More detailed-looking labels do not make the underlying data more precise.
An account can also follow and unfollow between snapshots without appearing in the endpoint difference. That possibility means a snapshot report is not a complete event stream. It can still answer the practical question of who is newly present now compared with the baseline. Describe that task clearly rather than promising to reveal every short-lived relationship that may have occurred in between.
Arrival-report questions
Is the first visible follower necessarily the newest?
No. You need a documented chronological order or comparable observations to support a recency claim. A position in an unexplained list should remain a display observation, not a timestamp.
Can I find recent arrivals with only two follower totals?
No. Totals can establish a net change, but they do not identify the members responsible. Use comparable member lists for names, or keep the report limited to aggregate growth.
What should I do if I missed an observation?
Keep the gap and compare the nearest valid snapshots if their coverage matches. Report the wider interval. Do not fabricate a midpoint list or assign precise event times to compensate for missing data.