Guides · 2026-11-21 · 861 words
Building a competitor log your team will actually keep
How to design a simple competitor log for an Australian small team — short fields, a shared home, and a monthly read — so the notes survive past the first week.
Most competitor files die of kindness. Someone creates a beautiful template with twenty columns, a colour key, and a request that every staff member add screenshots after every phone call. For a week it feels organised. Then the file is out of date, people are embarrassed to open it, and the business is back to rumours in a group chat.
A log that survives is almost plain. It is short enough to complete at the end of a 45-minute weekly review, shared enough that more than one person can find the last note, and modest enough that a month of empty "no change" rows is considered a success, not a failure of the system.
One page per rival, not one row per rumour
Give each active rival a single place: a sheet tab, a document heading, or a record in the watchlist tool on this site. At the top, keep the stable facts: the business name they trade under, the main website, the suburbs or customer type they appear to serve, and the date you added them. Under that, add dated entries. Do not start a new file every time something happens. The history is the point.
Three rivals is enough for most small teams. If a fourth name keeps coming up in customer conversations, add it only when you are prepared to drop one that no longer matters. A log with twelve forgotten names is a graveyard, not a watching system.
Use a handful of fields and refuse to add more
These fields cover almost every useful note:
- date of the observation
- URL or location (a page, a shopfront, a public ad library entry)
- what you saw, in one or two sentences
- what was recorded last time, if it changed
- so-what: ignore, watch, or act
- owner: who will do the action, if there is one
That is all. A "priority score", a "threat rating out of ten", or a free-text essay box will slow people down and invite argument about the rating instead of about the fact. If someone wants to attach a screenshot for internal use, they can, but the written sentence still has to stand on its own. In six months nobody will want to open a folder of unlabelled images.
Put the log where work already happens
The log has to live in a place the team already opens. For some businesses that is a shared spreadsheet. For others it is the same document they use for a Monday meeting. Browser tools on this site can hold a personal or exported copy, which is useful for an owner-operator, but a team still needs a shared home so the notes are not trapped on one phone.
Set a simple permission rule: anyone who talks to customers can read the log; a smaller number of people can add the weekly entries; prices on your own site still change only through whatever approval process you already use. A watching file should not become a back-door price board.
Train the tone as well as the template
Write in facts. "Their free-shipping threshold dropped from $150 to $99 on the delivery page" is professional. "They're coming for us" is not, and it spreads anxiety through a team that then repeats it to customers. If you need a judgement, keep it in the so-what column and make it operational: "Brief Saturday staff that customers may ask about a $99 freight deal; we are not matching this week."
New staff should be shown one good entry and one poor entry. The poor entry is usually a rumour, a screenshot with no date, or a copy-paste of a rival's marketing paragraph. The good entry is dull and dated. Dull is a feature.
Close the loop every month
A log that is only written and never read is a diary, not a tool. Once a month, spend a short meeting — even fifteen minutes — reading the last four weeks for each rival. Ask two questions: did we say we would act, and did we? And has a slow pattern appeared that no single week revealed?
This is also the time to archive a rival who has left your market, and to celebrate "no visible change" if that is the truth. Teams stop filling in logs that seem to demand a drama every Friday.
What not to store
Do not store other people's personal information, private messages, login details, or material you would be uncomfortable producing if a dispute started. Do not paste a rival's product photography into a file you later share outside the business. A competitor log is your note of public facts, not a scrapbook of their assets.
If the log ever starts to include legal accusations, stop and get advice. The file should help you serve your customers with clearer information. It should not become a brief against another business.
Build the smallest log that will still be complete in three months. Short fields, a shared home, a weekly author, a monthly read, and a tone that would look reasonable if a customer sat in the room. That is a log a team will actually keep.