If your team's project board has a column called “waiting on quotes,” or a card labeled “DO NOT ARCHIVE — has contact info,” you already know the problem. You didn't build that workaround because you like building workarounds. You built it because the tool doesn't know what a source is, what a campaign is, or what happens to a story after it gets a quote.
Most teams manage their work with generic project tools — Trello, Asana, monday.com. In these tools, a unit of work is usually called a “card” or a “task”: a single box that holds a title, an assignee, and a due date. That's the entire vocabulary. It's built to work equally well for a construction project, a software sprint, or a marketing campaign, which is exactly why it doesn't fit any one of them particularly well.
A university communications team isn't managing generic tasks.
A single story might touch a faculty source, a photo shoot, a social cutdown, a newsletter placement, and a campaign tied to an enrollment push — and every one of those pieces needs to stay connected to the others, this year and three years from now when someone asks “when did we last cover this program?” Generic tools have no concept of a “source” as its own thing. They don't know the difference between a news story and a podcast episode. Every one of those distinctions gets bolted on with labels, custom fields, and knowledge that only lives in one person's head.
What the mismatch actually costs:
- Source relationships live in someone's inbox, not in the system. When a staffer who's covered the nursing program for six years leaves, their contacts leave with them.
- Campaign history is a folder, not a workflow. Reconstructing “what did we publish for last year's giving day” means digging through a shared drive, not pulling up a record.
- Nothing talks to anything else. The content calendar, the contact list, and the campaign tracker are three different tools that agree with each other only as long as someone remembers to update all three.
What to look for instead.
The fix isn't more tooling — it's tooling that already understands the shape of this work. In Contoro, a story isn't a task that happens to have a due date. It's connected, natively, to the campaign it belongs to, the source it came from, and the person working on it — because those relationships are what the tool is built around, not what you have to invent yourself.
If you're evaluating what to replace the patchwork with, ask: does the tool have an opinion about what a source is? Does it know the difference between a news story and a podcast episode without you inventing that distinction yourself? If the answer is no, you're not buying a system — you're buying a blank canvas and volunteering to build the system on your own time, again.