All resources

When the draft you asked a colleague for stalls: building a collaboration workflow for your recruiting blog

Build a workflow that keeps moving with your colleagues, from the first request through draft, review and publication. Includes a request message and a role-by-role workflow template.

Colleagues discussing work while looking at a screen together

It's been a week since you asked for the draft. Following up feels like nagging, but waiting brings the publish date closer. When this happens, don't chase more often. Start by finding out where your colleague got stuck.

Turn “Could you write a post?” into a small request

For someone with a day job, writing is new work squeezed in between everything else. If they don't know what to write or how much, it's hard even to block out time to start. Narrow down the reader, the question and the deliverable first.

For example, instead of “Could you introduce our team culture?” try “To help candidates understand how we collaborate, could you tell us about one recent time you solved a problem with another role?” When the scope of the experience is smaller, it's easier to find material and to remember what happened.

  • Reader: Note which role's candidates will read it and how much they know about the company.
  • Key question: Choose one question the reader should have an answer to after reading.
  • Deliverable: Agree on whether it's a finished draft, notes for each question or a short interview.
  • Schedule: Break out the interview, draft, fact-check and publish dates, and suggest how much time each should take.

Taking part doesn't have to mean writing the post yourself

The person with the richest experience isn't always the person who writes well. For a colleague who finds writing daunting, ask for notes on three questions or a short conversation. The blog manager can then shape that material while the colleague checks the facts and wording.

Before the conversation, agree on the purpose of publishing and on whether you'll record, and send the questions ahead. Asking for a scene, as in “Where did you get stuck, and what did you change, with whom?”, works better than “Tell us about your achievements.” After the interview, ask for any extra photos or figures in a single, organized request.

Have the person confirm any sentence you've edited. Polishing for readability is different from turning something they never said into a quote. For busy colleagues, point to the specific paragraphs and questions to check so the review is lighter.

For every post, decide who takes the next action

“In review” alone doesn't tell anyone who needs to do what. Write down the owner together with what “done” means, as in “Maya confirms the two quotes by Wednesday.” Even when one person holds several roles, responsibility for each step should be clear.

In Teamblog, you can invite colleagues as team members and give each a role with the right permissions. One way to split it: colleagues who help with drafts are contributors, and the person who shapes and publishes the content is an editor. Contributors can write and edit drafts, but they can't publish or edit posts that are already published. Owners and admins manage team members and roles.

An example of team permissions in which a contributor writes drafts and an editor handles publishing.

The people, content and figures shown are fictional examples.

You need both permission settings and review agreements. Assigning a role doesn't mean fact-checking or sign-off happens automatically. Record whose confirmation is needed, and whether it's done, in the workflow template below or in the document your team uses. Team collaboration is available on paid plans.

  • Source: Shares the real example and the material that can be made public.
  • Writer: Produces the draft and incorporates feedback.
  • Fact-checker: Confirms quotes, figures and how much customer and project information can be made public.
  • Publisher: Checks the final draft and links, then publishes.

Keep drafts in one place and agree on the order of edits

When chat attachments, personal documents and copied drafts are all floating around, the first job is working out which version is current. In your workflow document, settle on a single link to the working draft, and make edit requests against that link.

Teamblog drafts save automatically as you write. When someone with publishing permission picks up a colleague's draft and continues from there, you skip the step of moving the final text somewhere else. Rather than having several people edit the same post at once, set a rule for handing it on in order: “Writing done → Review → Incorporate changes.”

An example of finding a draft in the drafts list and continuing to write it. The saved status does not mean the draft has been reviewed.

The people, content and figures shown are fictional examples.

When a deadline slips, find out what's blocking it instead of asking “When will it be ready?” Make the next action small: narrow the question if material is thin, switch to an interview if there's no time to write, and point to the exact sentences to confirm if review is what's left.

Don't rewrite recurring information every time

The company introduction, role-specific hiring information and the apply button repeat across many posts. If you copy them from an old post each time, closed postings and outdated descriptions can slip in. For frequently used copy, set an owner and a last-verified date.

If you save hiring information and buttons in Reusable blocks, a paid Teamblog feature, you can pick a block in the editor and insert it into your draft. It helps you never miss recurring information and always start from the same baseline.

An example of choosing hiring information from Reusable blocks and inserting it into a draft. Inserted content is managed separately from the source block.

The people, content and figures shown are fictional examples.

Editing a block doesn't automatically change content you've already inserted into posts. When a job posting closes, check the saved block and the links in existing published posts separately. Treat reuse and post-publication checks as one package.

Finish one post, then adjust how you work

You don't need an elaborate process from the first post. Go through it once, from interview to publication, then write down where you waited the longest. For the next post, change only the request at that step.

Send your colleague the published link and tell them which parts of their input helped the piece. When people can see how their contribution was used, the next request makes more sense. Rather than just increasing the number of posts, focus first on building a flow your team can repeat.

Take this with you the next time you ask for a draft

Copy the request message together with per-post fields for owners, review and publishing checks. Replace the text in square brackets to fit your team.

No login needed. Use it right away.

Show the workflow template text