A community story for Facebook is nearly ready. The interview has been reviewed, but the opening date has changed and a contributor has supplied a replacement photograph. The producer needs to know which decisions still
A community story for Facebook is nearly ready. The interview has been reviewed, but the opening date has changed and a contributor has supplied a replacement photograph. The producer needs to know which decisions still apply before the post can move forward.
Xander can work alongside the Facebook team as a coworker in FridayHQ, using the Page's project knowledge to help make that assessment. The team can discuss the changes with Xander, assign the follow-up work, and have the content's tags and state updated to reflect the current package.
A useful workflow connects the creative with the facts, copy, and responsibilities around it.
Keep the Page's audience, editorial voice, recurring formats, and approved examples in its KnowledgeBase. For a local publication, that could mean writing for residents who need enough background to understand a story and accurate practical information to act on it.
Maintain a separate entry for the current assignment's confirmed facts: names, dates, location, links, and the basis for using contributed media. Record who confirms those details and who owns the final publishing decision.
Give Xander clear review responsibilities. For example, Xander may assess copy against the agreed voice and identify missing context, while a named editor confirms disputed facts and a responsible person confirms media permissions. Define how those decisions affect the tags and overall content state.
Keep original contribution in the review brief. Meta's Facebook originality guidance distinguishes original production and meaningful creative contributions from low-value reuse. Ask the team to explain what its reporting or creative work adds.
Suppose the story concerns a community garden's opening weekend. The source material includes a gardener's interview, location footage, and the organizer's practical details.
Xander, develop a Facebook version for our local audience. Suggest the opening and Page copy using the confirmed project facts. Explain what context a first-time viewer needs and flag missing information.
Choose the direction, then ask Xander to create the adaptation, copy, link-check, and media-review tasks using the agreed owners and deadlines. Xander can send the briefs to the relevant teammates.
Keep distinct deliverables separate where they need separate review. A portrait adaptation can have its own content state while remaining connected to the same assignment and confirmed facts.
These suggested tags make the underlying decisions explicit:
| Suggested tag | When Xander records it | What requires another check |
|---|---|---|
| Original Contribution Reviewed | The agreed editorial assessment of the current creative is complete. | Added third-party material or a substantially changed treatment. |
| Page Copy Approved | The current wording has passed the required review. | Revised copy or changed facts affecting it. |
| Links Checked | The assigned person confirms the destinations used in the post. | A replacement link or changed destination details. |
| Media Rights Confirmed | The responsible person records the basis for using the selected media. | Replacement media or a changed intended use. |
Connect the applicable tags and the current cut's review to your configured content states. Xander can maintain that state when you ask for a readiness check or report a decision. The tags should describe the actual package being considered for release.
These are internal production checkpoints. An originality review records your team's assessment; it does not establish a platform distribution outcome.
Bring the change to Xander with enough detail to identify the affected work:
The opening date changed in the confirmed brief, and we replaced the lead photograph. Reopen the copy and media-rights checks for the affected content, update its state, and create tasks for the editor and media owner. Notify them with the details.
Xander can update the relevant tags and state and coordinate those tasks. A completed review of an unchanged interview can remain recorded while the new copy and image receive attention.
For previous feedback, ask which content version the findings refer to. That keeps an older review from being mistaken for confirmation that a new caption or photograph has already been checked.
Before publication, ask Xander for the current package, missing checks, and next owners. Resolve the outstanding decisions and confirm the Page, final version, publishing owner, and release time. Contact FridayHQ support to discuss eligibility for limited partner direct-publishing access and the destinations your team needs.
Once the release is confirmed, ask Xander to update the production record. If a correction is required later, discuss it against the affected version, assign an owner, and have Xander update the corresponding checks and state.
Begin with one local story or adapted campaign. Give Xander the Page's decision rules, and let the team's conversation keep the creative, supporting information, and release status connected.
