Set the page job
Approve the cluster role, audience, query job, entity focus, result set baseline, and useful difference.
Agency briefing system
Build agency content briefs that survive every handoff.
MIRENA turns the page decision into one shared operating brief for the strategist, writer, editor, and client. The framework stays consistent across accounts while entity, intent, proof, structure, and internal route decisions remain specific to each asset.
Four handoff rolesSix brief layersSeven workflow stagesOne approval state
Page jobOne role and one completion eventThe brief controls scope before writing
Semantic centerEntities and attributesKeywords inform discovery rather than page meaning
Useful differenceBaseline plus missing valueThe result set is studied, not copied
Internal routeHub, siblings, authority, next stepLinks are planned before the draft
Agency delivery system
The brief must survive four handoffs without losing the page decision.
MIRENA keeps strategy, production, review, and client explanation in one controlled record.
Receive a usable plan
See section purpose, entity priority, answer formats, proof needs, examples, links, and boundaries.
Review against decisions
Check intent, coverage, support, format, internal routes, claims, and unresolved source needs.
See the rationale
Understand why the asset exists, what it adds, how it fits the site, and what approval is still required.
Agency brief packet
Every client brief needs the same control layers, but not the same generic content.
Page ownershipTarget URL, page role, cluster home, parent, siblings, and overlap decision.
Entity and intentPrimary entity, support entities, attributes, dominant intent, reader job, and page model.
Baseline and gainRequired result set consensus, repeated angles, missing value, first hand input, proof, and examples.
Section operating planOpening answer, H2 sequence, section jobs, required formats, source notes, and review owners.
Internal routesHub link, sibling links, authority support, next step destination, anchor logic, and exclusions.
Approval stateClient approvals, protected claims, outstanding evidence, owner, blocker, and ready for drafting decision.
Seven stage workflow
Standardize the sequence, not the answer.
Confirm the cluster role
Start with the approved map row, parent hub, sibling assets, and page ownership decision.
Lock the page job
Choose one dominant purpose and one completion event before the outline begins.
Define entities and intent
Name the primary entity, supporting entities, attributes, query job, and page model.
Review the result set
Record the required baseline, repeated coverage, missing value, and proof needed.
Plan the sections
Give every section a job, entity focus, answer form, source need, and review note.
Plan internal routes
Name the hub, siblings, authority pages, next step, anchor guidance, and exclusions.
Audit the draft
Use the approved brief as the standard for writer, editor, client, and final QA.
Scale without drift
Reuse the control system while keeping every asset specific.
- Brief fields and approval states
- Source context and claim controls
- Entity, intent, format, and link checks
- Writer and editor handoff rules
- Draft QA and final review sequence
- Page role and target query
- Primary entity and attributes
- Result set baseline and missing value
- Required proof and examples
- Internal routes and client approvals
Questions
Agency content briefing questions.
What makes an agency brief different?
An agency brief must work as a strategy record, writer handoff, editor standard, and client explanation across different accounts and specialists.
How detailed should an agency brief be?
It should be detailed enough that a writer can draft without inventing strategy and an editor can review against explicit decisions.
Should client approval happen before drafting?
The page job, scope, required claims, protected topics, and major proof needs should be approved before production begins.
Should internal links be included?
Yes. The brief should name the hub, relevant siblings, authority support, next step destination, anchor guidance, and links to avoid.
Can MIRENA replace agency writers?
MIRENA can prepare briefs, audits, drafts, and repair plans. Human review, client knowledge, proof, editorial judgment, and approval remain necessary.
How does an agency scale the method?
Reuse the brief framework, approval states, QA rules, and handoff fields. Keep entity, intent, proof, structure, and link decisions specific to each asset.
Next route
Give the agency one brief that controls strategy, production, review, and client approval.
Start with the cluster decision and source context. MIRENA returns an entity led, intent led, format ready, link ready brief and the next production route.
Founder access is €20 per 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.