Castle List

So You Want to Use Castle List

Castle List is a project management and task tracking platform. It's designed for small teams who want something simpler than Jira but more structured than a shared spreadsheet. I started using it about three years ago when my team was drowning in Trello boards that had gone stale and Asana configs nobody understood. The interface looks clean at first glance. That's mostly because there's not a ton of surface area to mess up. You have boards, lists within those boards, and cards that move between lists. It follows a Kanban-style workflow by default, though you can switch to list view or calendar view if that works better for whatever you're tracking.

Getting Started with Castle List

Sign up takes about two minutes. Email, password, team name — you're in. The biggest mistake people make early on is creating too many boards from the start. I learned this the hard way. I set up six different boards in my first week for different projects, and by week three I was jumping between them constantly without any visibility into overall workload. One board per team makes more sense. You can use labels or custom fields to segment work within that single board. Here's the practical part that the marketing pages won't tell you: the bulk editing features are basically nonexistent. If you need to change a due date for twelve cards, you do it one by one or you export, edit in a CSV, and re-import. That re-import step is where things get messy because the field mapping isn't always intuitive. I spent about forty-five minutes once trying to figure out why my dates were shifting by a day — turns out the timezone handling on import defaults to UTC unless you explicitly set it during the upload process. I just write everything in the local timezone upfront now and skip the import path entirely for date-heavy batches.

What Actually Works Well

The real-time collaboration is genuinely good. Multiple people can edit cards simultaneously without conflicts, which is something I took for granted until I switched away from it and back. The notification system is also properly configured by default — you get pinged when cards are assigned to you, not when every card on the board moves. That restraint matters. Too many tools blast you with notifications and then you disable them entirely. Custom fields are reasonably flexible. You can add text, numbers, dates, dropdowns, and checkboxes. The dropdowns are where you'll hit your first wall — they're board-level, not global. If you need the same dropdown values across multiple boards, you create them manually on each one. There's no master list import. I keep a notes file with my standard dropdown values and copy-paste them when setting up new boards. Saves me from having to rebuild them from scratch every time.

Where It Falls Apart

Reporting is thin. If you need Gantt charts, burndown reports, or any kind of timeline visualization, Castle List doesn't have it built in. There's a basic calendar view and you can sort by date, but that's it. For a team that does sprint planning or needs to show clients a roadmap, this is a dealbreaker. I ended up integrating with a separate tool for that — we use a simple spreadsheet for timeline tracking and link it in card descriptions. It's not elegant but it gets the job done without forcing the whole team to learn another platform. The mobile app is functional but slow. Loading a board with more than fifty cards will make it stutter. If your team does a lot of on-site work and needs to update tasks from a phone, you'll run into this. I recommend keeping your active board under fifty cards and archiving completed work regularly. That keeps performance acceptable. Another thing nobody mentions: the API rate limits are strict. If you're building any kind of automation around Castle List, you'll hit the limit fairly quickly. I tried automating card creation from a webhook and got rate-limited after about twenty requests per minute. The workaround is batching your API calls and adding a two-second delay between them. It's not ideal but it keeps things from breaking.

Who Should Actually Use This

Small teams — five to fifteen people — who are doing project work that doesn't require heavy reporting or compliance tracking. Marketing teams, product teams in early-stage companies, operations groups that need visibility without governance overhead. If you're in regulated software development or running construction projects with strict milestone requirements, look elsewhere. Castle List won't give you what you need. There's a free tier that supports up to five team members with unlimited boards and cards. The paid tiers unlock custom fields across all boards, advanced permissions, and priority support. The pricing is reasonable if you need those features, but I'd stick with the free tier as long as possible. You'll discover your actual needs faster that way instead of paying for things you don't end up using. I've been running Castle List as my primary tracking tool for about two years now across two different teams. It hasn't replaced everything — I still use a separate tool for code-level task tracking and a spreadsheet for budget work — but for day-to-day team coordination it does the job without getting in the way. That's usually the bar I hold these things to.