One fictional client, Harborline Projects, taken through a week of social work: the weekly brief, an approval, a revision, a permission date, the client report, a results import, the Prompt studio and the playbook. Every screen below is the real app, not a mockup.
1 minute 56 seconds · silent · 3.4 MB, nothing loads until you press play
Harborline’s weekly brief opens on the decision due now: a reader question whose reply is overdue. Overdue replies come before release work, so Postward puts it first. Below it sit the posts waiting on someone, a post on permission hold and a source whose permission ends soon.
The brief also checks the hours. Two hours of planned work against the eight this client pays for, so you know before Monday whether the week fits.

Scroll the frame · weekly brief
The post “Who owns the next decision?” is approved by Jo, the account’s designated approver, against check code 1JTDUJC. Then one line changes. The new version gets a new code and goes straight back to Draft.
Nothing is overwritten. Release history keeps version 1 with its approval and marks every changed word in version 2, so nobody has to argue about what the client signed off.

Scroll the frame · post and release history
The carousel “Show the handoff in three frames” relies on a source the client cleared until 10 November. The publisher records a native schedule for 13 November. Postward keeps the confirmation as evidence, but puts the post on permission hold and names both dates.
The hold travels. It goes to the top of the weekly brief and the post is left out of the approved copy pack until the permission is renewed or the schedule moves inside the window.

Scroll the frame · post on permission hold
Harborline measures qualified walkthrough enquiries. Postward compares the latest week with the week before only because both windows are the same length and do not overlap. Otherwise the change would read Unknown.
The release record is the part clients remember. It shows how reliably the work went out: new posts live on or before the planned date, approvals at the first version and the median wait for approval.

Scroll the frame · decision report
Below the campaign measure, every published post carries its own results: impressions, reach, reactions, comments, shares, saves, clicks and views, each reading dated. Type them in, or import the CSV the platform exports. Postward matches rows to posts by live address, flags any row it cannot place with certainty and shows a preview before anything is saved.
The ranking answers the client’s favourite question. The Instagram carousel, read three days after publishing, reached 6% engagement. The LinkedIn post, read after seven days, reached 4.6% with 47 clicks. Postward shows the age of each reading so nobody compares a two day post with a two week one.
The post results box is at the foot of the decision report above
The Prompt studio holds twelve jobs, from an evidence extractor and a strategy brief to a campaign builder, channel drafts, a design brief, a first pass against the 26 editorial checks, comment triage, a monthly diagnostic, an experiment plan and an executive summary. Choose one and Postward assembles the prompt from the campaign, sources, posts and results it already holds.
Client material stays under control. Only excerpts with separate AI permission go in, never their location. Campaign details enter only when you choose a campaign, and the prompts that need one ask you to choose. You copy the text into the tool your client allows. Postward sends nothing.

Scroll the frame · a prepared Campaign builder prompt
Twenty two chapters cover roles and decision rights, ten stages and the gate that closes each one, the first 30 days, the operating rhythm, a metrics dictionary, crisis and privacy rules, capacity planning and a definition of done. Each stage ends with a note naming the screen and the prompt that support it.
It is the method you can explain to a client. Download a copy to print or share with your team.

Scroll the frame · the playbook