Last Look

How Last Look works

Scheduling posts in advance is how good social media gets done, and it is also how a post that was right on Monday goes out wrong on Thursday. Last Look is the pre-flight check: one look at everything queued, with the problems pulled to the top.

1. Connect

You sign in with Buffer (OAuth with PKCE). Last Look gets a token that lasts about an hour. It can read your queue, and it can change a post only when you press a fix and confirm it.

2. Scan

Last Look reads every scheduled post, post awaiting approval and draft across your channels in one to three requests, and your browser runs the checks in plain code. There is no AI model involved: every flag comes from a rule you can read below, so the same post always gets the same answer.

3. The checks

4. Fix

Each flag offers the fixes that make sense for it: edit the text (with a suggested version where one can be made, a live character count and a word-by-word view of the change), move the post to drafts, or move a queue post to the top or bottom of its queue. Nothing is saved until you confirm. Before saving, Last Look reads the post again and stops if it changed in Buffer since your scan, or if it goes out in the next three minutes. Threads are left to Buffer’s editor so every part stays in step. After a fix, that one post is updated on the page from Buffer’s answer and checked again; nothing else is re-read. After an edit, Undo stays available for two minutes: it reads the post again and puts the previous text back only if the post still holds exactly what Last Look wrote. Last Look never deletes a post.

Reorders move more than one post

Moving a post in its queue changes when it goes out. Moved to the end, it takes the last slot, often days later; moved to the front, Buffer sets it to share next, with no time until it goes out. After every move, Last Look reads that channel’s queue again and re-checks the day words of every post whose time changed: a “tomorrow” that meant Friday at the old slot but now means Saturday is flagged, with a one-click word that keeps Friday (“today”, a weekday, or a date). If that day has already passed at the new time, it offers the front of the queue or drafts instead. A post set to share next has no time to judge, so its day words are flagged for you to check.

5. Look back

After you connect, the Look back tab reads your most recent sent posts (up to 90, one request per organization) and runs the text checks on them, each judged at the moment it actually went out in its channel’s time zone: formatting that showed as raw text, posts longer than the network allows, leftover placeholders, the same post sent twice, day and time words that were wrong when it went out, and images sent without alt text. The result reads “Last Look would have caught N issues in your last M sent posts”, grouped by check, each linking to the post. It only reads: sent posts cannot be changed, and their links are not opened.

6. Daily digest (opt-in)

A pre-flight check only helps if someone opens it. Turn on the daily digest and, every day at the hour you pick, Last Look reads the posts going out before the end of the next day and lists what it would fix, on a private page and an Atom feed: follow it in Slack (/feed subscribe), any feed reader or an RSS-to-email service. It uses its own read-only Buffer connection, keeps the last 7 digests, and one click turns it off and deletes everything.

Limits

Connect BufferTry it on your own postSample queue