Collty Help

PROCESSES, PROJECTS AND DELIVERY

Plan with Project Architect

Generate, edit, staff, analyze and activate a dependency-aware delivery plan from a real project brief.

01

From brief to working plan

Project Architect turns project context into an editable delivery structure. It can start a new draft or load an existing project, generate phases and tasks, connect the right teams, model dependencies and show the plan as a board, timeline or predictive dashboard.

The generated result is a starting structure, not an automatic commitment. Every phase, task, role, duration, dependency and expense remains reviewable before the draft is activated.

C
Project ArchitectLaunch plan · Draft revision 2
Live
Find teamsSave draftActivate draft
PROJECT SOURCENew projectPROJECT BRIEF

Launch a B2B product with a clear market narrative and validated prototype.

StrategyB2B SaaSJul 13
Correct draft
BoardTimelineDashboard−   100%   +
DiscoverMarket evidenceProject teamDecision mapProject team
DesignNarrativeProject teamPrototypeProject teamReviewProject team
DeliverHandoffProject teamLaunchProject team
EDITORPrototype reviewDependency · Narrative
The generated plan remains editable through the board and inspector.
02

Give Architect enough project context

  1. 1
    Choose the project source

    Start a new draft or continue an existing project from Project source.

  2. 2
    Select a direction

    Choose Marketing, Design, Development, Consulting, Strategy, Research, Operations, Mixed or let Architect infer the direction.

  3. 3
    Add industry and goal

    Describe the intended outcome, market context, constraints and what must be true when the project succeeds.

  4. 4
    Choose a start date

    The date anchors the generated schedule. It does not replace the project's sprint cadence or total duration.

  5. 5
    Set collaboration context

    Choose the appropriate team setup and answer clarifying questions when the brief leaves important delivery decisions open.

  6. 6
    Generate structure

    Architect creates typed phases, tasks, roles, dependencies and, where relevant, expenses for review on the board.

03

Edit the plan on the Board

  • Drag a task between phases or reorder it inside a phase; dependency lines update with the board.
  • Select a phase to edit its title, description and duration or to add a task or expense.
  • Select a task to edit its outcome, description, duration, phase, specialists, role hours and dependencies.
  • Use Board tools to add phases, tasks, expenses and dependencies or to apply Auto layout.
  • Use zoom controls for the board itself; opening or closing side panels does not change the plan data.
  • Save draft preserves the editable plan without making it an active delivery commitment.
04

Use the three views for different decisions

ViewBest forWhat to check
BoardEditing structure and ownershipPhases, task detail, roles, expenses and dependencies
TimelineReviewing sequence and scheduleStart date, phase ranges, task order and dependency pressure
DashboardReviewing plan readinessDelivery confidence, staffing fit, timeline pressure, coverage, risk and commercial logic
05

Plan with real team capacity

Find teams proposes staffing options from the brief. You can choose a ready option, attach one or several teams, inspect their members and then assign only relevant specialists or roles to each task.

When the project tracks hours or costs, the inspector shows the planned workload and modeled cost. When those capabilities are off, Architect removes those controls instead of inventing commercial data.

  1. 1
    Review Team options

    Compare the proposed staffing paths before attaching a team.

  2. 2
    Attach the required teams

    Teams on this project remain visible and can be expanded without breaking completed work.

  3. 3
    Assign tasks deliberately

    Choose a specialist or role for each task and check workload concentration in Dashboard.

  4. 4
    Confirm or request participation

    Own teams can be confirmed; external teams receive the appropriate project request before activation.

06

Complete an internal core with Hybrid team mode

Choose Hybrid team when the project already has useful internal people but still lacks role coverage, specialist evidence, market experience, language fit or available capacity. This mode uses the same professional assembly engine as Teams Canvas, with the project brief and plan as additional evidence.

Start by attaching your own team. Architect locks those profile IDs, evaluates what they already cover and returns ranked standalone team variants containing the core plus only evidence-backed additions. It does not combine several AI variants or silently replace your people.

  1. 1
    Select Hybrid team

    The team section first shows your saved teams because a real internal core is required.

  2. 2
    Attach the core

    Choose one or more owned teams. Architect records their professionals as locked members for this staffing decision.

  3. 3
    Generate or review the plan

    Add enough brief and task context for Architect to understand required outcomes and capabilities.

  4. 4
    Find missing specialists

    Compare complete hybrid options ranked against the same project. Weak or unsupported gaps remain visible instead of being filled by unrelated profiles.

  5. 5
    Apply one option

    Select the strongest single composition, edit role and workload assignments, then continue the normal request, save and activation flow.

07

Correct a plan without starting over

Correct draft opens a controlled revision workflow. Add the change you need, define the target budget when commercial data is available, and generate targeted clarification questions for ambiguous corrections.

The revision keeps the existing project context. Review the changed board, timeline and Dashboard before saving or activating it.

08

Move from draft to delivery

  1. 1
    Review Board metrics

    Check task count, phase structure, role coverage, duration and any modeled hours or costs.

  2. 2
    Resolve critical risks

    Fix missing ownership, impossible dependency sequences and overloaded roles before sending requests.

  3. 3
    Save the draft

    Give the draft a clear project title and preserve the reviewed structure.

  4. 4
    Confirm teams or send requests

    Participation state remains visible in the project editor.

  5. 5
    Activate deliberately

    Activation creates the working project boundary. Continue daily execution in Project Workspace.

09

How AI planning stays controllable

Was this guide useful?Help us keep the instructions clear and current.