Batch scheduling 30 days of LinkedIn content in 2 hours

Batch scheduling 30 days of LinkedIn content in 2 hours is a writing session with a fixed clock, not a button that invents a month of posts. You spend the two hours turning notes you already have into drafts you have read, then you place those drafts on the next open slots. The calendar after that is the queue. You do not reopen it every morning to pick a time.

On boykli.com, Queue Schedule stores the weekdays, one Time of Day, and one timezone. Each Add to Queue takes the next open slot. Drag changes which draft gets which date. The queue publishes to the personal profile you connected with LinkedIn OAuth. It does not post to a company Page, and it does not store a different clock on each row. The sheet that predicts those dates is the LinkedIn content calendar. The filing cabinet for drafts you have not queued yet is the LinkedIn post draft manager.

Logged-in visitors can browse Radar and Algorithm with no plan. Writing, carousels, images, Voice Agent, Post to LinkedIn, and Add to Queue need a paid seat. BYOK is $29 a month: your OpenRouter key for chat and images, and a Google AI Studio key if you use Voice Agent. Boykli does not add a monthly generation cap on that seat. Managed is $88 a month and includes the platform models inside caps: 210 posts, 150 carousels, 150 images, 25 Voice Agent sessions, and 130 post refinements. A month of personal posts sits inside the 210-post cap. Both seats use the same queue. Prices are the public list on boykli.com as of 26 October 2026.

What "30 days" is, once the queue has one clock

Thirty days is the window. It is not automatically thirty posts. The number of slots is the weekdays you save, counted forward from the next open one.

A new queue starts on Monday, Wednesday, and Friday at 10:00, in the timezone of the device, until you click Save. If you want a US operator audience and you are sitting in another zone, save America/New_York or America/Chicago before you add anything. The slot stays in that zone when you open the app later from somewhere else.

Boykli holds the row and publishes when that slot's time has arrived. It does not hand the date to LinkedIn's composer. People currently describe the personal composer as about 10 minutes to 3 months, and company Pages as a different window. Recheck the clock and LinkedIn Help. A six-month list of unfinished ideas is a sheet. It is not a queue.

Where the two hours go, compared with the other ways to batch

A general scheduler is the better tool when the copy is already finished, each post needs its own minute, or the same calendar has to cover other networks and a company Page. The product description of this queue, without the two-hour session, is the LinkedIn scheduling tool. The free composer versus the paid seat is in Schedule LinkedIn posts.

The two-hour session

Use a weekday afternoon when LinkedIn is already connected and the seat can generate. If Schedule shows Reconnect LinkedIn, fix that before you write. A batch that cannot send is a folder of drafts.

Assume you sit down on Sunday 25 October 2026, nothing is queued, and you save Monday through Friday at 09:15 in America/Chicago. The next open slot is Monday 26 October at 09:15. From that Monday through Tuesday 24 November is 30 days and 22 weekday slots. You will fill 16 of them. Six stay empty on purpose.

Minutes 0–10: lock the clock

1. Open Schedule. Under Queue Schedule, toggle Monday through Friday. Clear Saturday and Sunday unless you truly have weekend notes.
2. Set Time of Day to 09:15. One clock. If a launch post must leave at 16:00 on a Thursday, that post uses LinkedIn's composer. Do not pretend the queue can represent it. A reading of public timing datasets, and why one midweek slot is enough to test, is in Best time to post on LinkedIn.
3. Set the timezone and click Save. Zero selected days leaves the queue inactive. If items are already queued, Schedule asks you to confirm, because turning off every day pauses auto-publish. A missing timezone blocks new items until you save one.

Write the clock once above your sheet: Mon–Fri, 09:15, America/Chicago. You will not type a date into Boykli. Order assigns the date.

Minutes 10–30: sixteen source notes, no topics

Open a note with sixteen numbered lines. Each line is a fact you can stand behind: a number you changed, a sentence a customer used, a decision you cut, a URL you read, a file you can show. "Thought leadership on pricing" is not a line. A line is: "Free tier moved from 1,000 calls a day across 4 workspaces to 250 per workspace, decided Friday, because one workspace was burning the pool."

Stop at the count you can actually fill. Sixteen notes in twenty minutes is one note every seventy-five seconds. If you are still inventing themes at minute 25, you do not have a month of content. You have a wish. Queue fewer posts.

Sort the lines in the order a stranger should meet them. The first note is the one that stands alone. A result note that needs next week's numbers goes to the bottom, or off the list, until the numbers exist. A series is several lines, not one. Four parts occupy four weekday slots. Count them before you promise a collaborator that "the carousel is Wednesday."

Shapes, decided now so you do not re-decide inside the model:

• Twelve medium or short text posts. Short is labeled 45–400 characters. Medium is 400–1,400. Long is 1,400–3,000. Use long only when the note is already a paragraph, not when you hope the model will find a point.
• Three carousels, 2 to 8 slides, square 1080×1080 or portrait 1080×1350. Same note as a text post only when the document adds a swipe a caption cannot. The document title is required.
• One series, only if the notes are sequential. Add Series to Queue places 2 to 10 parts on successive slots.

Voice Agent is a source machine for three of those lines, not for the whole month. One live interview transcribes both sides and drafts three posts from that transcript. On Managed, the saved interview counts as one of 25 Voice Agent sessions. The three drafts do not also decrement the 210-post allowance. On BYOK, the live session uses your Google AI Studio key and the drafts use OpenRouter. How that session works is in LinkedIn voice agent. Three drafts from a twenty-minute conversation still need the same read as a typed note.

Minutes 30–100: write, then read, one row at a time

Seventy minutes for sixteen drafts is about four minutes each. That budget holds only because the note already contains the fact. The pass is an edit, not a discovery.

For each text row:

1. Create posts. Pick the length you marked. Paste the note, including the numbers and the date of the decision. Turn on a hook only when you want alternate first lines drawn from that note.
2. Read the hook, the body, and the close against the note. Delete any number the note did not contain. If the draft argues a side you did not take, fix the sentence or discard the draft. Do not queue it "for later."
3. Leave it in Library until you have read it. Add to Queue waits until the draft has an id. A cover image on the draft is sent with the post when one exists. On Managed, that image draws from the 150-image allowance.

For each carousel: pick the design (Neo-Brutalist is the default). Build from the same note. Set the document title. Write the caption as the commentary, not as a paste of every slide. On Managed, the generation counts toward the 150-carousel cap. Scheduling a file that already exists does not call the model again.

Do not open a second draft while the first is unread. Batching fails when sixteen tabs are "almost done" and minute 100 arrives with nothing you would sign.

Minutes 100–120: queue in sheet order, then check the header

Add row 1 first. It takes Monday 26 October at 09:15. Add row 2. It takes Tuesday 27 October. Continue in order. Sixteen consecutive weekday slots, with no weekend days saved, land the last item on Monday 16 November at 09:15. Count that on the sheet. The product will not type those dates into your note.

If the same post is already queued, the app asks before it adds another copy. Confirming adds a second slot. It does not edit the first row in place.

Then read Schedule:

• Posts ahead should equal the number you added. Sixteen, in this example. A series of four counts as four.
• Scheduled through should be the last slot in the saved timezone.
• Drag only when the sheet should change. If you move the first carousel above the Monday text, the carousel takes Monday and every later row shifts one slot. Rewrite the Slot column. The old dates are now fiction.
• Open a preview of the first three text posts and the first carousel the way they will sit in the feed. The mobile and desktop check is in LinkedIn post preview. A line that breaks badly is still cheap to fix while the item is queued. The publisher reads the Library row for a normal text post when the slot fires, so an edit in Library is the edit that sends.

Post to LinkedIn is for "now." It does not consume the next calendar slot. If you also leave that draft queued, you will publish it twice. Remove the queued copy.

The six weekday slots you did not fill stay empty. The queue does not invent posts to keep a streak. When a real note appears next week, Add to Queue places it on the next open slot after the sixteen, not on a date you left blank in the middle. Blank days in the past are gone. To insert into a gap you must drag, or you must remove later rows and add again in the new order.

What the publisher does after you close the laptop

When a slot's time arrives, the publisher sends the earliest due item through the LinkedIn connection you approved. It skips the user when the token is unusable, when no weekday is selected, when the timezone was never saved, or when the account no longer has a generatable plan. A cancellation that still has current_period_end in the future still has access. on_hold and an expired cancel do not. Due posts wait until a plan exists again.

On Monday, open Schedule before 09:15. If the header is Reconnect LinkedIn, fix the token. If a row failed, send it back to queued so the next pass retries that slot. Do not write a replacement in the same ten minutes unless the failed post should not go out.

How that authorized send differs from a browser tool that posts for you is in Automated LinkedIn posting. The queue will not move your clock because a post got impressions. You change Time of Day yourself, and every unsent row moves with it.

Habits that blow the two hours

Generating from a pillar name. The model is instructed to use what you provide. A row with no fact produces a post you should not ship, and fixing it costs the four minutes you did not budget.

Filling all thirty days because the keyword said 30. Daily posting with thin notes trains people to skip the name. Thirteen strong posts on Monday, Wednesday, and Friday beat thirty reminders that you are still posting.

A different time on every row. The queue ignores that column. Collapse to one time, or put the odd rows on LinkedIn's clock and keep Boykli for the repeating slot.

Treating a series as one calendar cell. Four parts consume four weekdays. The post you thought was "next Monday" lands the week after.

Queueing the hold. A result post that needs next Friday's numbers stays off the queue. Write it after the week closes. It takes the next open slot from the moment you add it.

Marking the sheet "scheduled" inside another app. Status is queued when the item is on Schedule and Scheduled through moved. Another tab does not call LinkedIn.

Loading carousels without a document title. The add will not be a complete document post. Set the title in the same sitting. Slide size and the safe zone are in LinkedIn carousel dimensions. Scheduling the PDF itself, including what the document upload accepts, is in How to schedule a PDF on LinkedIn.

FAQ

Is there a button that writes all 30 days at once?

No. There is no month generator, no pillar picker, and no Kanban of ideas. You create each post or carousel, or one series of 2 to 10 parts, and you add each item to the queue. Library stores what you made. Schedule stores what you explicitly added. Radar can suggest what is being discussed. It does not file a month of drafts for you.

Can I batch-schedule to a company Page in the same two hours?

No. The queue publishes the personal profile from LinkedIn OAuth. Page posts stay on your sheet as a reminder. Publish those from LinkedIn as the Page, or from a tool built for Pages. The difference in author, admin role, and native clocks is in LinkedIn personal profile scheduler.

Will 22 posts blow the Managed cap?

No. Managed includes 210 posts, 150 carousels, 150 images, 25 Voice Agent sessions, and 130 post refinements in the period. Sixteen text posts, three carousels, and one short series are a normal month, not an edge. BYOK has no Boykli generation cap. You pay the provider. Scheduling a draft that already exists does not spend another post.

What do I need open before the timer starts?

A paid seat that can still generate, LinkedIn connected on the personal profile, at least one weekday selected, a timezone saved, and a list of source notes. Add to Queue also needs a saved draft id. A carousel needs a saved file and a document title. An AppSumo lifetime code redeemed at /redeem is a BYOK seat, one code for one account. An existing paid seat blocks redeem. It is not a free scheduler.

What if I only finish eight drafts when the two hours end?

Queue the eight you read. Posts ahead should say 8. Leave the rest as notes. A half queue of real posts is the session working. A full queue of unread drafts is the session failing in a way the calendar will not show until the posts are already live.

Can I reorder after the batch without rewriting everything?

Yes. Drag updates which draft occupies which slot. The date is "nth open weekday," not a stamp glued to the draft. After a drag, fix the Slot column on the sheet so a collaborator is not expecting Monday's post on Wednesday. Removing an item does not renumber a spreadsheet you forgot to open.

What if I cancel halfway through the month?

Access continues until current_period_end if that date is still ahead. After that, and while a payment is on_hold, the publisher skips due posts. The rows are not a promise that LinkedIn will receive them without a generatable plan. Move anything that must leave onto LinkedIn's clock before the period ends.