# Boards: Projects and tasks in view > Project planning and tasks in one: projects with their own board, columns, weeks or sprints and goals with a date. Every task has a key like CIR-142, an owner, a due date and a priority. Whatever comes from outside lands in the board's inbox, and whatever is open sits on the owner's start page. - Page: https://www.ciro-noise.de/funktionen/boards - Deutsche Fassung: https://www.ciro-noise.de/funktionen/boards.md Three people mean three different tasks, and the customer has heard nothing since her request. On your project board every task gets a number like CIR-142, an owner and a due date. You plan in sprints of a few weeks and see whether your team is on track. Everything that comes from outside lands in the inbox first. ## Project management on one board Every project gets its own board with a key, say CIR for internal work and BRA for the customer Brandt & Söhne. The columns are Open, In progress, Review for the check and Done. In front of them sits the inbox for everything from outside, that is from a request, from the AI or through an external AI access. A task carries an owner, due date, priority, labels and the effort in points. On top come one level of subtasks, checklists, attachments, images and comments with @-mention. You plan in sprints of a few weeks, with progress and a chart that shows how much is still open. The board pulse shows your pace, the goal with a date and a forecast of whether the goal is on track or at risk. So you see on the board whether your team is on schedule, and you need no status meeting for it. That suits teams of twelve who plan the next two weeks precisely and the quarter roughly. Whatever is open sits on the board with its due date and on the owner's start page, overdue tasks first. The team row shows who is working on what right now and what was last completed. The log per board records who did what and when. It also shows whether a person, the AI or an external access created a task. Done work moves to the archive and stays readable there. The board is linked to the other features. A request becomes a task with one click, and because the link stays, support sees the state. A decision from a meeting becomes a task with a person and a date. You link tasks to a customer or a deal, and billable time on a task becomes an invoice line. Ask the AI about CIR-142 and it knows the state. Templates per board, keyboard shortcuts and export are included. ## How your team keeps every task in view The state is on the board, so nobody has to ask around on Monday. - **Call the task by its name**: Every board has a key, every task a sequential number like CIR-142. The global search jumps straight to the task by its number, and in chat, in the meeting and in the request it is the same one. - **Plan the next few weeks precisely**: You estimate the effort in points, and a chart shows how much of the sprint is still open. The board pulse sets a goal with a date and says whether it is on track or at risk. So “Are we on schedule?” no longer needs a meeting. - **Keep every task in view**: The inbox catches everything from outside, and the start page shows every person their open and overdue tasks. The team row shows who is working on what, and done work goes to the archive, where it stays readable. - **Bring in the right person**: An @-mention notifies exactly the colleague who should contribute. Comments, images and attachments sit on the task, subtasks and checklists structure the steps. - **Bill time on the task**: You book billable hours directly on the task, and they become an invoice line. The task hangs on the customer or the deal, so the record knows the effort. ## A week at an agency of twelve Planning on Monday, a customer request on Wednesday, and on Friday Kira wants to know what is still open. ### Monday, 9 am: the week is set in ten minutes Kira and the team pull the tasks for the next sprint from the inbox and from Open, set the owners and estimate the effort in points. The board pulse shows the goal “Brandt relaunch by October 17” as on track. Where a task is stuck, everyone sees it on the board without asking around. New tasks come from the board's template, with labels and checklist already in. - Sprint with effort in points - Chart of open points per sprint - Goal with date and forecast - Templates per board ### Wednesday: Ms. Sommer reports a bug The request comes in through the form, and Lena turns it into BRA-47 on the customer board with one click. The link to the request stays. Pascal fixes the bug and books 1.5 billable hours on the task. Lena sees the state of BRA-47 right on the request and replies to Ms. Sommer without asking Pascal. - Request becomes a task, linked - Time on the task, billable - State visible to support - Key per customer board ### Thursday: workshop with Mr. Brandt in the project room Kira sketches the new homepage with Mr. Brandt on a concept board. Tasks from the board sit on the canvas as cards, and Mr. Brandt adds his own requests. Afterwards he sees the tasks Kira shares with him in the project room, comments on BRA-52, and completes his own task. He doesn't see internal tasks, and he needs no subscription for any of it. - Concept boards with tasks as cards - Project room for the client, no subscription - The client sees only what you share - Comments right on the task ### Friday: Kira asks the AI “What is open with Pascal?” The AI answers from the board with numbers, due dates and priorities. The log shows that two tasks were created this week through an external AI access. They sat in the inbox and were planned on Monday. None of it got lost, and Kira pulled nobody out of their work for the overview. - The AI reads boards - Log per board, also via AI or access - Inbox for everything from outside - Start page with open and overdue ## Boards in detail Boards, subtasks, sprints and project rooms at a glance. - **Project boards with an inbox**: Every project has its own board with a key and the columns Open, In progress, Review and Done. In front of them sits the inbox for everything from outside. - **Tasks with due dates and priority**: Owner, due date, priority, labels and effort in points. - **Subtasks and checklists**: Subtasks on one level, checklists for the steps within a task. - **Sprints with a burndown chart**: Weeks or sprints with progress and a chart that shows how much is still open. - **Project hours and customer links**: Billable time on the task becomes invoice lines. Every task can be linked to a customer or a deal. - **Project rooms for clients**: One room per client project with tasks, wiki, concept boards, and files. Guests need no subscription, take no seat, and see only what you share. - **Attachments and comments**: Files and images on the task, comments with @-mention. - **Board pulse**: Progress, pace, goal with a date and forecast: on track or at risk. - **Log and archive**: Who did what and when, including origin: person, the AI or external access. Done work stays readable in the archive. - **Templates and keyboard shortcuts**: Templates per board for new tasks. The most common steps also work from the keyboard. - **Start page and export**: Open and overdue tasks per person and a team row that shows who is working on what. Tasks can be exported. - **Concept boards**: A free canvas for sketches, workshops, and workflows. Tasks, wiki pages, and people sit on it as cards, and you simply drag images in. ## Tell Claude. CIRO NOISE records it. ### Sort your week > What's on my plate this week, and what is the team working on right now? Your week: • CIR-142 “Credit note for IN-2026-0417” was overdue. It's now set for today with high priority, and Petra has been asked to approve. • CIR-147 “Quote for Hagedorn Logistik” and CIR-148 “Review 2027 price list” are due today. • CIR-155 “Prepare Ulm training” and CIR-158 “November newsletter” can wait until Friday. On the team, Lena is on CIR-150, Deniz on APP-145 and Mara on NRL-3. Jonas is out until Wednesday, and his tasks aren't due until next week. ### Set up a project > We're moving to the new office. Turn it into a project with the tasks from the wiki checklist and split them among the right people. Everything has to be done by Nov 30. Project MOV “Move to Hafenstraße” is set up with 18 tasks in five areas, due dates counted back from Nov 30: • IT: Can, grouped under MOV-4 with network, printers and phone system • Contracts: Petra • Mail and address: Ömer • Furniture: Mara • Moving day: you For the next sprint I suggest the 7 contract and address tasks, with furniture and IT after that. You confirm the suggestion on the board. All four are mentioned on MOV-1. ### Report status > How's project MOV going? What's stuck, and who has too much on their plate? Put the status in the wiki too. MOV is on track with 11 of 18 tasks done, only IT is behind: • MOV-6 phone system (Can, 4 days) and MOV-12 keys (Ömer, since yesterday) are overdue. • Can has 4 tasks in progress at once and is out Thursday and Friday. • So Deniz takes over MOV-7 printers and MOV-8 monitors. The status per area is now in the “Status” section of the wiki checklist. ## Frequently asked questions ### Is CIRO NOISE full project management software? For small teams, yes. Every project has its own board with a prefix, and every task has subtasks, an owner, a due date and an estimate. You plan in sprints with a forecast, and everything from outside lands in the inbox first. You also log time on the task, let customers work in the project and bill the hours, without a second tool. ### Can I bring my boards over from Trello? Yes. Under Organization › Import you upload the JSON file from Trello: cards come with description, labels, checklists, due date and comments, and recognized lists become the matching status. Your team keeps working in the new board the same day. ### How do I plan the coming weeks? In sprints. You estimate tasks in points (1, 2, 3, 5, 8 or 13) and pull them into the sprint. A chart shows you every day how much is still open and whether your team is on track. A goal with a due date adds a forecast of when it will be reached. ### Can my client work on the project with us? Yes. Every client project gets a project room. Your client sees the tasks, wiki pages, concept boards, and files you share there, comments right on them, and completes their own tasks. Guests need no subscription and take no seat. ### What are concept boards? A free canvas for sketches, workshops, and workflows. You place tasks, wiki pages, and people on it as cards, and everyone sees them with their own permissions. In the project room, your client draws along. ### How do I bill an hour? You log time right on the task, with an hourly rate and marked billable. CIRO NOISE rounds up to the started quarter hour and turns open hours into the invoice. Billed entries can no longer be changed afterwards. That way every hour lands on exactly one invoice. ### How does a customer request become a task? With one click on the request. The task gets a number like BRA-47 in the board you choose, and the link works both ways. Tasks from outside can land in the inbox above the board first, where you accept and sort them. ### Can Claude create and assign tasks? Yes. Claude connects to your organization and creates, assigns, moves and comments on tasks. If you like, Claude also suggests the plan for the next sprint. Claude works with the permissions of the person who grants access, and each board's log shows whether a person, the AI or a connected tool did something. ### What do the boards cost? They are included in the price. The first two seats are free, all features included, no credit card. Each further seat is €25 a month plus VAT and can be canceled monthly. The request, the meeting decision and the invoice line all hang on the same task. ## CIRO NOISE at a glance - CIRO NOISE is a workspace for small businesses and teams of up to about 50 people: wiki, tasks, customer requests, finance with quotes and invoices, customers (CRM), meetings, knowledge with AI, social media, password vault, and time tracking behind one login. - Price: the first 2 seats are free, with every feature. Each additional seat costs €25 per month plus VAT. No credit card to start. - Privacy: servers and AI run in EU data centers, content never trains AI models, and permissions apply per person and feature. - AI connection: Claude and other AI assistants connect through MCP, the open standard for AI tools, with exactly the permissions of the person. - Provider: CIRO GmbH, Eching, Germany. Contact: hello@ciro.gmbh, phone +49 89 24 88 31 22.