BRIEF passes to FILES_V7 through a fragmented handoff marked COPIED.
- BRIEF to FILES_V7 (unresolved) — problem handoff: COPIED
Content Engine and Media Render Engine coordinate a recurring workflow from source material through editorial review, visual production, human approval, publishing and measurement.
The system automates repeatable coordination around the work. Editorial, visual and publishing decisions remain explicit human decisions.
A complete editorial carousel produced for FB DIGITAL MEDIA. Navigate to explore all eight slides.
A review asset requires explicit human approval before it becomes a production asset.
Drafting content, producing media, approving an asset or publishing a post are individually manageable tasks.
The complexity appears between them.
One source can produce several content candidates. Editorial review determines what moves forward. Different platforms may require different execution. Visual production introduces another review decision. Publishing needs the correct approved combination of content and media. And the system still needs to understand what happened if a step succeeds only partially.
Without a clear operating structure, automation can make a fragmented workflow move faster without making it safer.
BRIEF passes to FILES_V7 through a fragmented handoff marked COPIED.
EMAIL? passes to REVIEW through a fragmented handoff marked WHO?.
STATUS passes to OWNER through a fragmented handoff marked WAITING.
Create one controlled path from source material to measured publication.
The system was redesigned around a simple idea: the workflow should know what has happened, what is allowed to happen next and which decisions still belong to a person.
Work has an explicit state. Approvals are recorded as decisions rather than inferred from messages. Known work is not blindly repeated. Review and production remain separate environments. Failures can be identified and recovered. Publishing becomes part of the recorded workflow rather than a private checklist.
The result is not simply “more automation”. It is more control over how the work moves.
BRIEF passes to FILES_V7 through a fragmented handoff marked COPIED.
Source moves through editorial review to an approved state, then production.
Content Engine owns the content lifecycle: source records, candidate state, eligibility, review and publishing status.
Media Render Engine handles visual-production requests and returns the result to the requesting work.
Neither system is meant to make every judgement itself. The renderer does not decide whether a visual is good enough, and the publishing layer does not decide whether content deserves to be published.
That separation keeps responsibility clear.
Source material moves through candidate content, two explicit human reviews, publishing and measurement.
Editorial approval remains human. Visual approval remains human. Platform suitability, exceptional holds and releases, strategic choices and decisions about what should be automated next also remain human.
The system can prepare the work, move information, update state, create production requests and make the next action visible.
It does not need to replace the judgement that gives the work its value.
The objective is not to remove judgement from creative work. It is to remove unnecessary coordination around that judgement.


Passing a render check does not mean the creative is approved.
The Sandbox version is available for human inspection. A rejected asset returns for revision instead of silently continuing because the render succeeded.
Only explicit visual approval permits the clean Production render to move forward. The decision remains visible in the operating workflow.
How to fix a content approval workflow spread across email and chat
If the process is simply create → approve → schedule → publish, an existing content platform may already solve the problem very well.
This workflow had additional requirements: source harvesting, editorial decisions, bilingual content candidates, platform-specific execution, separate media production, visual approval, review-versus-production boundaries, recovery after uncertain execution, publishing state and later measurement.
The objective was not to rebuild software that already existed.
The missing piece was an operating layer connecting parts of the process that were not sensibly modelled together.
Use existing software where it works, connect or extend it where useful, and build only what the workflow genuinely requires.
The system became more useful after real operation exposed problems that were difficult to see in a clean prototype.
Duplicate execution showed that retrying a task is not always safe. External success combined with incomplete internal state showed that a system sometimes needs to reconcile what actually happened before acting again.
Review and production activity exposed the need for a stronger boundary between experimentation and live execution. Repeated status checking showed that some work was better triggered by events than by constant polling.
Those failures led directly to architectural changes.
A schedule repeatedly checks for work, whether or not a real event occurred.
Real events, deliberate schedules and operator actions trigger appropriate work.
Early versions of a workflow often rely on scheduled checks: “Is there anything to do yet?”
That can be useful initially, but it creates unnecessary activity when nothing has changed.
Where appropriate, the system now favours events, operator actions or defined production windows that indicate when real work exists.
The live Content Engine dashboard records candidate activity, editorial decisions and published output. These figures come from a captured dashboard view, not a projected saving or a claim of ROI.
Content Insights was captured on 10 October 2026. The settings and publishing queue screenshots document separate operating views; they are not presented as simultaneous measurements.



Content Engine and Media Render Engine are not client templates that FBDM Systems copies into another business.
The transferable value is the way the workflow was designed and improved: explicit state and ownership; clear human decision points; connected stages without losing responsibility; duplicate prevention; failure recovery; review-versus-production separation; auditability; and architecture changed by operating evidence.
Another team may use completely different tools, approvals, content types and integrations.
How should the work actually operate?
You need the right operating design for your own recurring work.
The Workflow Systems Blueprint looks at how the process works today, where coordination becomes difficult, which decisions should remain human, what existing tools can continue to do and whether anything should be connected, automated or built.