What the 90-day memo contains
The memo's summary, up to eight actions, quick wins and watchlist; how it is generated, guarded, reviewed, emailed and downloaded as PDF.
Updated
The 90-day memo turns an audit's findings into a short plan, one memo per run. Scheduled audits generate theirs automatically; for a manual run, press "Generate memo" on the dashboard at /app. Every paid plan includes memos; a public example is at /sample/memo.
What goes in
The memo is built only from the run's results. Its input is:
- every failed and partial rule, ordered gating failures first, then critical, high, medium and low severity, grouped by category with the heaviest category first;
- compact evidence for each finding, and the one-line fix from the rule set;
- your business type and typical ticket band;
- the overall score, its uncapped value, and the change since the previous run;
- the previous memo's actions and whether you marked each open, done or dismissed;
- whether Google Business Profile is connected.
The writing instructions forbid inventing facts, numbers or competitors and promising outcomes (rankings, traffic, leads, customers, sales, revenue), and require every action to cite its rule ids.
What comes out
The memo is a fixed structure, validated before it is stored:
- Summary — three to five sentences on where the business stands, what changed since the last run, and what the next 90 days focus on.
- Top actions — at most eight. Each has the rule ids behind it, a short imperative title, one to three sentences on why it matters grounded in the evidence, two to five concrete steps, an effort (S under an hour, M a few hours, L a project), an owner, and a due week from 1 to 13.
- Quick wins — one-line fixes under an hour that are not already in the actions.
- Watchlist — partial results, not-assessable checks worth unlocking, and things to re-check next run.
An action's owner is "you" when it needs your own account, vendor, developer or decision. It is "EchoPilot drafts, you approve" only when the step is content EchoPilot can prepare: posts, Business Profile posts, review replies, FAQ text, page copy. Those actions are recorded as automation requests, marked pending when your plan covers them and "unavailable on tier" otherwise; see Approval flow and export.
Actions you can tick off
On /app/memos and the memo's own page, each action can be set to open, done or dismissed. The next memo receives those statuses: a done action does not reappear unless the finding is still failing, a dismissed one may only return with a different approach, and an open one may be carried over with a note saying so.
Generation and the claim guard
A language model writes the memo from the input above. A reply that does not match the structure is retried once with the validation error attached; if it still fails, or no model is available, a deterministic fallback plan is built from the top findings and their fixes and the memo is marked for review.
Every sentence then passes a claim guard. A phrase that reads like a promise of rankings, traffic or revenue is rewritten once; if it still trips the guard, the memo is marked for review. An advisory second pass by the model checks the whole text the same way.
In review
A memo marked "in review" is never emailed and never shown on your account; the list at /app/memos shows the status and the page says it is being checked before release. EchoPilot resolves it by hand; you receive it when it is ready.
Email and PDF
When a memo is ready, every member of the account receives a plain-text email with the subject "EchoPilot:
The PDF is an A4 document generated on the server, available from the memo page and the memo list. Only ready memos are downloadable. The memo's Markdown body is also stored as a portable copy.
Timing
The pages say generation takes about a minute; a memo in review takes as long as its review.