The Pipeline is your project's schedule: every task and milestone for the bid, derived from the tender documents you have uploaded. It is the backbone of project scheduling in BidScript, and can be viewed either as a Gantt chart or as a Kanban board.

You do not build it from scratch. BidBot generates a structured task plan from the tender's key dates and content, and you refine it from there.

Where to find it

Open your project from the Projects area.
Select the Pipeline tab.

Before you start

Upload your tender documents and let them finish indexing first. BidBot builds the pipeline from extracted key dates and tender content, so a project with no documents has nothing to plan from.

If you want tasks assigned automatically as they are created, set up your team profiles beforehand. See Auto-assigning team members to tasks.

Generate a pipeline

In the Pipeline tab, click Generate Pipeline. A BidBot side panel opens.
Use one of BidBot's suggested quick prompts, or write your own.
Review what BidBot proposes.

BidBot asks for your permission before creating any charts or task breakdowns, so nothing is built until you approve it. Give it as much context as you can up front — if you already have a view on how the bid should be phased, say so in the prompt rather than correcting the result afterwards.

BidBot then generates a task breakdown following APMP best practice, built around the tender's key dates and whatever additional context you provided.

In this view BidBot acts as your project management co-pilot: it understands both APMP practice and the specifics of the bid in front of it, and can amend your task breakdown and task characteristics visually, pragmatically or logistically.

Refine an existing pipeline

In the Pipeline tab, click Enhance Pipeline. The BidBot side panel opens.
Type your instruction in the input bar.
Let BidBot make the changes.

Example prompts

Changing colours

For {specific phase or task set} I would like to change the current colour to {colour}.

Change colours for one phase or task set at a time rather than in a single combined prompt - iterative changes are more reliable.

Assigning by skill set

For {specific phase or task set} I would like to assign the colleagues with the best skill set for the completion of the tasks. Please provide reasoning for my confirmation.

Assignment depends on team profiles being set up. See Team Member Profiles.

Assigning subject matter experts

SMEs are not auto-assigned based on a tender's technical or organisational context, but you can prompt for them explicitly:

In this project, please read and understand all relevant context of the uploaded tender documents in the files tab. In reading the documentation, I want you to evaluate where it would be best to bring in some of our technical or expert members from the teams tab, and then I would like you to recommend who we should assign. Give me a description before assigning SMEs for my confirmation.

Moving dates

I need to change the dates of {specific phase, task set, or the whole pipeline}. {Brief context of why}. Please move {specific phase, task set, or the whole pipeline} {forwards or backwards} by {number} days.

Best practice

Give BidBot your intent in the first prompt rather than correcting the output afterwards.
Make colour and structural changes iteratively, one phase at a time.
Set up team profiles before generating, so assignment can happen as tasks are created.
Confirm BidBot's proposed breakdown before approving it — you are the human in the loop by design.

Managing pipeline tasks - the Gantt and Kanban views, and creating or editing tasks by hand.
Auto-assigning team members to tasks - how BidScript matches people to work.
Team Member Profiles - the profiles that assignment draws on.
Tasks Aggregate View - seeing pipeline tasks across every project at once.

Building your project pipeline