Keep the trail of a campaign job
Three months after a campaign ships, someone asks why the landing page says what it says. If the brief, the drafts and the approvals are scattered, nobody can answer.
· Work · 3 min read
A campaign job leaves a lot behind it. There is a brief, a few rounds of drafts, comments from three people, and a final approval. While the job is live, everyone remembers where those things are. A few months later, nobody does.
Why the trail matters
- When a result is good, you want to repeat what you did. When it is bad, you want to see what changed.
- When a claim is questioned, you want to show who approved it and what the evidence was.
- When a new person joins, they can learn from real work instead of from guesses.
- When you repeat a job, you start from the last brief and not from a blank page.
Where trails go missing
The brief lives in a document. The drafts are in a shared folder with names like "final v3 really final". The comments are in chat. The approval is a thumbs-up on a message. Every piece exists, but they are not connected to each other, and none of them says which job they belonged to.
A simple rule
Keep everything about a job on the job. The brief, each draft, the comments and the approvals should all be reachable from one place, with the job as the anchor. If you can open the job and read the story from top to bottom, you have a trail.
How Levric does it
In Levric, each job on the Work board keeps its own brief, its drafts, its comments and its approvals. Open the job and everything about it is there. Nothing has to be gathered later, because it was never kept anywhere else.
Approvals are part of that record. A job moves forward when a person says yes, and that yes stays with the job.
See it in the app: the Work tour