PlatformSocial

Keep the approved campaign connected to every post.

A campaign can be approved once and still have a different result on every channel. The publishing design follows the content revision, account and outcome separately.

Social publishing is planned. No production network connections are offered in this build; supported networks, media types and account actions still need confirmation.

One campaign. A clear result for every destination.

Northwind’s launch update is being prepared for several accounts. Follow the campaign plan, review package and mixed publication results to see why each destination needs its own outcome.

Illustrative workflow. A campaign can be partly published; each account keeps its own result.

Social & CampaignsDesign example · fictional data

Northwind campaign

Client: Northwind Traders · Brand: Northwind

Draft

Example recordCustomer story

LinkedIn

NW

In review

Example recordQ3 launch update

LinkedIn + X

NW

Scheduled

Example recordProduct briefing

YouTube

NW

Fictional provider destinations, not confirmed network support. Publishing actions still require implementation and verification.

Explore the proposed workflow; no live actions are performed

Move deliberately from brief to published content.

The proposed sequence, from the starting event to the confirmed result.

Select a stage to inspect the handoverProposed workflow · illustrative responsibilities
01
Inside this handover

Choose client and accounts

Establish the brand, campaign and destination accounts before preparing the publication.

Responsible role / sourceCampaign owner
Social & Campaigns

Explore the capability.

ORQESTRA Social is a planned capability for teams managing content across clients and brands. It centres on knowing what was approved, where it should publish and which destinations still need attention.

1 / 4 · Capability in focus

Choose the client, brand and account

Keep the commissioning client separate from the brand and publishing account. Review the intended destinations before content enters the publishing process.

What this means in practice

An agency’s client record and the brand’s publishing account answer different questions: who commissioned the work and where it will appear.

Connected information.
Clear responsibility.

The target design links information across these systems. Each retains responsibility for its own transactions or content.

Business informationResponsible systemWhat stays connected
Client and campaign identityORQESTRAThe business relationship, campaign brief and linked work.
Brand accountsSocial engineProvider connection and account ownership.
Content and publicationSocial engine + FlowApproved version, schedule and per-target execution result.
Engagement informationConnected providerProvider-supplied metrics with period and observation time.

Define the first
working scope.

Scope one process before committing to a rollout. Agree these requirements and verify the workflow with the people who will use it.

Our implementation approach
  • Map clients, brands and social accounts.
  • Agree the content review and approval process.
  • Validate the required network actions and previews.
  • Define handling for reconnects and partial publication.

Before you connect the work.

Can the workflow separate clients and brands?

The planned model keeps clients, brands and publishing accounts distinct and linked. Account permissions and review must be validated before a team uses it for client work.

What if only one channel publishes successfully?

The design records an outcome for each destination. Recovery should address failed or uncertain targets without repeating a confirmed post; live publishing and recovery remain to be implemented.

Which social networks are supported?

No production network support is confirmed by this site. Bring the accounts, media formats and publishing actions you need to the scoping discussion.

What needs to be approved before your next campaign publishes?

Describe the process, systems and decision-makers involved. Use the enquiry to identify scope, dependencies and what must be demonstrated before use.

Discuss your requirements