Headquarters / Use cases
Keep delivery visible from the first ticket to review.
Connect board work, team decisions, project time, and delivery reviews for project teams using Kooya Headquarters.
For leads, contributors, and reviewers
A project can have a clear goal while its daily work remains hard to follow. Delivery leads need to identify the next task and the review queue. Contributors need clear ownership and scope. Reviewers need acceptance criteria and enough context to decide whether the work is complete.
Headquarters gives those roles a shared board workflow, team conversations, a documentation library, and recorded project effort. Agree on the delivery stages and the names used for the project before the team starts.
A complete delivery review cycle
Organize board work
Create tickets with owners, useful details, and observable acceptance criteria. Use the board columns to show the current delivery stage.
Resolve and record decisions
Discuss open questions in chat or configured meetings. Keep the lasting decision or instruction in Documentation and point contributors to it.
Record project effort
Contributors select the relevant project in Time Tracker and describe their task. Pause or stop allocations as the work changes.
Review delivery visibility
Review the board for completed and pending work. Inspect finalized project time and live activity separately, then use that evidence to plan the next increment.
Example: publishing a new support process
A support lead breaks the launch into a draft runbook, a review task, and a team announcement. The writer owns the draft ticket; the reviewer checks the escalation steps and the linked references. They resolve a question in chat and place the agreed answer in the runbook.
Each contributor tracks effort against the support-process project. At the end of the increment, the lead checks that the runbook and announcement tickets reached the agreed completion stage, then reviews recorded time to understand the effort behind the launch. This is an illustrative workflow, not a customer result.
Give each role the access it needs
Contributors need the relevant board, ticket, collaboration, and time permissions. Project leads need access to Project Management and its analytics. Documentation authors need management or item editing rights. Configured meeting and AI capabilities can support the workflow where enabled.
Use the project workflow guide to establish the first board and the ticket-writing guide when a task needs a clearer brief.
Headquarters by Kooya
Explore your company workspace.
Discover how projects, people, and cost visibility come together in Headquarters.