Working with Projects

Projects are where the work happens in Stackr. Each Project acts as a board for organizing tasks, tracking progress, and keeping your team aligned on a specific goal — whether that's a one-time rollout or a recurring operational cycle. Instead of scattering updates across email and spreadsheets, a Project gives you one place to see status, ownership, and deadlines at a glance.

Setting up and running a Project

1. Create a new Project — Click New Project from your workspace dashboard and give it a clear name (e.g., "Laptop Refresh — Q3").
2. Choose a template or start blank — Pick a starter template if one fits your workflow, or build your board from scratch with custom columns (like To Do, In Progress, Blocked, Done).
3. Add tasks — Create cards for each task, assign an owner, and set a due date.
4. Organize with columns or stages — Group tasks by status, location, or phase depending on how you want to track progress.
5. Invite collaborators — Add teammates to the Project so they can update their own tasks and see the full picture.
6. Track progress — Move cards across the board as work advances, and use filters to check what's overdue or assigned to a specific person.
7. Close out or repeat — Archive the Project when it's complete, or duplicate it as a template for the next cycle.

In practice

Maria, an IT manager at a mid-size company, uses a Project board to run her quarterly laptop refresh and onboarding/offboarding rollout. She sets up columns for "Devices Ordered," "Configured," "Shipped," and "Delivered," assigns each device to a technician, and tracks due dates against employee start dates. When leadership asks for a status update, she just opens the board instead of chasing down emails.

Tom, a Facilities manager at a K-12 school district, duplicates a "Building Maintenance" Project every month across all five school locations. Each Project tracks HVAC checks, lighting repairs, and safety inspections by building, so he can see at a glance which sites are on schedule and which need follow-up before the next walkthrough.

Tips

• Use consistent naming conventions across Projects so recurring work is easy to find and compare over time.
• Duplicate a finished Project as a template if you run the same workflow regularly — it saves setup time and keeps structure consistent.
• Set due dates on every task, even rough ones — it makes filtering for overdue work far more useful.