Approval flow and export
What Growth and Managed include for drafted content, the approval rule that governs publishing, and what exists today versus what is still to ship.
Updated
EchoPilot's positioning is that it audits, explains and drafts, and that nothing reaches a channel without a person approving it. This article describes what the Growth and Managed plans include for drafted content, how approval is meant to work, and, plainly, which parts exist in the product today.
What the plans include
The plan matrix is one table that the pricing page, the billing page and the worker all read:
- Growth — 12 drafted posts a month across any 2 of Facebook, Instagram, LinkedIn, X and Google Business.
- Managed — 24 drafted posts a month across any 4 of those channels, plus Google Business posts and review reply drafts.
- Audit — no content drafting.
Features are tied to the release phase that ships them. Today the product is at phase 3 (audit, memo, billing). Content channels and drafted posts belong to phase 4; Google Business posts and review replies to phase 5. On /app/billing those features are listed with the chip "included when it ships": they are part of what you pay for and switch on the day they are released, with nothing billed separately. The terms §5.2 say the same.
The approval rule
Nothing is published to any channel on your behalf unless a person on your account has approved that specific item, and each approval is recorded (terms §7). In the data model, a post moves through the states draft, approved, scheduled, published or rejected, and a publishing action requires an approval row naming who approved it and when. There is no setting that turns approval off.
If you downgrade, queued drafts above the new plan's quota are marked "unavailable on tier" rather than published or deleted silently; published and rejected posts are never touched.
What exists today
- Memo actions owned by EchoPilot. When a 90-day memo assigns an action to EchoPilot (drafting posts, Business Profile posts, review replies, FAQ text or page copy), it is recorded as an automation request. The request is "pending" when your plan covers it and "unavailable on tier" when it does not; drafted posts and page copy need Growth, review replies and AI-visibility work need Managed. Execution of those requests arrives with the content engine.
- The claim guard. The guard that checks memos for promises of rankings, traffic or revenue is the same one that will apply to posts, briefs and rationales; flagged content is never emailed, published or shown.
- Tables for content. Content batches, posts, approvals, brand voice and channel recommendations exist in the database with no code writing to them yet.
What does not exist yet
- There is no queue of drafted posts to approve in the app, and no channel connection for Facebook, Instagram, LinkedIn, X or TikTok. /app/integrations says so.
- There is no export of drafted posts, because there are no drafted posts to export.
- Nothing is published anywhere, to any channel, by EchoPilot today.
What you can export today
- The memo as an A4 PDF, from /app/memos or the memo page.
- The memo email, sent to every member of the account when a memo is ready, containing the summary, actions, steps, quick wins and watchlist in plain text.
- The audit report on screen, with evidence per rule; and a scores-only public link, see Sharing a result.
Related
- Plans, pricing and the money-back guarantee for what each plan costs.
- What EchoPilot is for the positioning behind the approval rule.