The tack room
Three planning tools and a shelf of short guides. All tools run in your browser; nothing is sent to us.
Readiness
Use this before a first conversation to see how much material already exists. Partial records are normal and still useful.
How ready are your yard records?
Tick what exists today, however untidy. The score only describes how much raw material there is to build from.
Volume
Session records add up quickly. This planner shows the scale of a season so you can judge whether a spreadsheet will hold up.
Season record planner
How many session records will a season produce? Useful for deciding between a spreadsheet and a proper app.
0 session records, about 0 individual values.
Scope
See how each must-have feature weighs on a first release. Removing one heavy item is often the fastest way to launch sooner.
First-release sizer
Choose what a first version must do. We show a broad range for discovery, design and build, so you can see which choices carry weight.
Real timescales depend on discovery. This is a conversation starter, not an estimate we would hold you to.
If you accept optional storage in the cookie choice, these tools remember your last inputs on this device. If you reject it, nothing is kept.
Short reading for long winter evenings
Naming things before building things
Agree one name per horse, per surface and per session type, and write them down. Software built on a shared vocabulary can compare a season with the last; software built on free text cannot. Start a single list today and stick it in the tack room.
What to ask of a device export
Before buying into any tracker, ask: can I export my own data as a file, what columns does it contain, and does the timestamp include the time zone? Those three answers decide whether the data can ever leave the vendor's app.
Owner updates people read
A good weekly update has three parts: what was done, anything notable written by a professional, and what is planned. Charts help only if they come with a sentence explaining them.
Choosing between app and website
If the people using it are staff entering records, think app. If they are the public looking for information, think website. If both, keep them as separate products sharing one design language.
Keeping a spreadsheet healthy
One header row, one record per row, no merged cells, dates in a single format, and a column for who entered it. A spreadsheet kept this way imports cleanly into almost anything.
Before you call any developer
Write down one routine that wastes time, who does it, and what happens to the information afterwards. That paragraph is worth more than a long feature list.