Workflow library
Start from our set-up. Change anything, without code.
Ready-made set-ups for public tenders, private RFPs, security questionnaires, DDQs and more. Copy one into your workspace in a click, then make it yours.

The best bid teams already know how a good tender runs. The library puts that knowledge in your hands as a working set-up, and it is yours the moment you copy it.
01 · SET-UP
What is in a set-up?
A set-up is how experienced bid teams run that type of bid, ready to use. Three things make it valuable:
How the bid is organised from day one: where the tender pack goes, where answers are written, what the team tracks and when.
What good bid teams do for this type of bid, for example tracking the clarification deadline from the first day of a public tender, or linking every security answer to its evidence.
The heart of every set-up: step-by-step instructions James runs for you, such as "analyse the tender and write our bid/no-bid brief", "draft the clarification questions" or "check every requirement before submission".
Everything underneath, the folders and the information James and your team work with, is already set up, so your team doesn't have to think about it.

02 · CATALOGUE
Starter catalogue
Pick the set-up closest to your bid. Each one is a starting point, not a rule, and every set-up comes with its workflows.
One for every kind of bid.
Each is built for a specific type of bid.

| Set-up | What makes it different | Workflows included |
|---|---|---|
| Simple tender | For a short tender with one deliverable and a tight deadline. A light structure that gets the team from tender pack to answer in days, not weeks. | Tender summary · Draft the answers · Check every requirement before submission |
| Complex tender | For a large tender with lots, many annexes, a clarification round and several contributors. Built to split the work, track who does what, and keep every requirement in view. | Bid/no-bid brief · Requirements and clarification questions · Assign and follow up · Check every requirement before submission |
| Questionnaire | For any questionnaire: security, ESG, supplier or DDQ. Built around the questions, answered from your own documents, with the buyer's file filled at the end. | Answer from your documents · List open questions and owners · Fill the buyer's file |
| Forms to fill | For a set of forms the buyer sends: declarations, price sheets, company details. Built to fill each form in place and make sure none is forgotten. | Fill every form from your company data · List what is missing · Final check before submission |
| Set-up | What makes it different | Workflows included |
|---|---|---|
| Public tender (EU, Belgian, Dutch style) | Built around the procedure: clarification round, award criteria, lots and submission. Clarification deadlines are tracked from day one, and answers are written against the award criteria. | Bid/no-bid brief · Award criteria analysis · Clarification questions · Check every requirement before submission |
| Private RFP | Built around the deal: account context, Q&A rounds, and pricing kept apart from the answers. Win themes are agreed before anyone drafts. | RFP summary and win themes · Draft answers from past bids · Executive summary |
| Security questionnaire | Built around evidence: every answer linked to a policy, certificate or report, and checked by a security reviewer. | Answer from your security policies · Evidence request list · Consistency check against past questionnaires |
| Due diligence questionnaire (DDQ) | Built around the DDQ's sections and its document requests, with a legal check on sensitive answers. | Answer from company documents · Document request tracker · Legal review list |
| ESG questionnaire | Built around the framework and the reporting year, with evidence for every claim. | Answer from ESG policies and reports · Evidence gap list |
| PQQ / supplier selection | Built around pass or fail: certificates and company documents ready to attach, nothing missed. | Selection criteria check · Certificate expiry check · Fill the buyer's form |
| Framework call-off | Light and fast: a short brief, a short deadline, and answers reused from the framework bid. | Call-off summary · Reuse answers from the framework bid |
03 · COPY AND CHANGE
How it works
Browse. An admin opens the library and previews a set-up: its structure and its workflows.
Copy. One click copies the set-up into your workspace. It is now yours, not a link to ours.
Change. Adjust the structure, edit a workflow or write your own. No code, no ticket to us.
No set-up fits? Skip the library: explain your process to James and he creates the structure and workflows for you.
New projects of that bid type then start from your version, and James runs your workflows when you ask him to.

04 · TWO STARTS
Two ways to start, both fast
Most bid tools hand you one fixed process and ask your team to fit into it. With SEQUESTO you never fit into ours. You start one of two ways:
Pick the one closest to your bid, copy it, and adapt it.
Explain to James how your team works: your stages, what you track, the documents you always produce, the steps you follow for each kind of bid. James creates the structure and the workflows for you. You review them, change what you want, and start.
Starting from a blank page doesn't mean weeks of workshops. Describe your process in a conversation, and your team can be working in it the same day.

Before
- The tool's stages decide how your bid runs.
- A DDQ is forced into the same shape as a public tender.
- Changing how the bid runs means a request to the vendor.
With SEQUESTO
- Your structure, your best practices, your workflows.
- A different set-up for each bid type: public tender, DDQ, security questionnaire.
- Changes are made by your own admin, without code.
SEQUESTO adapts to each team's own bid process: custom stages, fields, document types and workflows, without code.
05 · FIRST BID
A worked example: from library to first bid
An IT services company answers Belgian public tenders, in French and in Dutch. Its bid manager copies the "Complex tender" set-up.
The bid manager renames "Clarifications" to "Questions / Vragen", because Belgian federal tenders come in both languages, and adapts the bid/no-bid workflow: "Read the tender, fill our bid/no-bid brief in French, flag every requirement about ISO 27001 and data hosting."
The next tender arrives. A new project opens with her structure.
James runs her bid/no-bid workflow, then the clarification questions workflow, and lists 140 requirements for the team. They start answering on day one.

Related features
Adapts to how your company works
SEQUESTO adapts to each team's own bid process: custom stages, fields, document types and workflows, without code. A public tender, a DDQ and a security questionnaire can each run the way your team already runs them.
Learn more →SEQUESTO aOS
SEQUESTO aOS brings eight layers together in one governed system for tenders, questionnaires, and structured document work. A stable model foundation, a purpose-built runtime, specialist agents, connected knowledge, workflows that follow your process, collaborative workspaces, and auditability all reinforce one another inside one system.
Learn more →Requirements & clarifications
James, SEQUESTO's AI bid agent, turns the buyer's requirements and questions into structured items built from your own templates. Unclear points become clarification questions you can send before the buyer's Q&A deadline.
Learn more →Analyse & qualify
James, SEQUESTO's AI bid agent, reads every file in the tender pack and tells you what is asked, by when, how it is scored and where the risks are. Then he helps you qualify it: is this one worth your team's next three weeks? The output follows your team's own format, so it fits the way you already decide.
Learn more →Never "done" until all is covered
Before a bid is marked complete, James checks every requirement against the finished document and grades it as compliant, partial, missing or needing clarification. A mention is not an answer, and James will not call a document complete while a gap is open.
Learn more →Your reports, in your format
The board pack, the monthly pipeline e-mail, the win rate per business unit: build them inside SEQUESTO. From then on there is nothing to maintain. Every number stays current, one click from the bids behind it.
Learn more →Frequently asked questions
The workflow library is a catalogue of ready-made set-ups for each bid type: public tenders, private RFPs, security questionnaires, DDQs and more. Each set-up brings a proven structure, the best practices for that type of bid, and workflows James runs for you, such as a bid/no-bid brief or a check of every requirement before submission. An admin copies one into the workspace in a click, then changes it to fit the team. No code is needed at any step.
Yes. Explain to James how your team works, in your own words, and he creates the structure and the workflows for you. You review and adjust them, and your team can start the same day. No workshops, no consultants.
Yes. A copied set-up is yours. You can adjust the structure, edit the workflows or write your own. SEQUESTO adapts to each team's own bid process: custom stages, fields, document types and workflows, without code. Changes are made by your admin, not by us.
Yes. A public tender, a DDQ and a security questionnaire can each have their own set-up and workflows. Many teams keep one set-up per bid type, so a new project always starts with the right structure and the right workflows.
Yes, and it follows your way of deciding. James reads the tender, summarises scope, key dates, award criteria and risks, and fills your bid/no-bid brief, following the workflow your team wrote. A field you define records the decision. You decide what goes into the brief.
No. Copying a set-up creates your own version, not a link. Later changes in the library do not overwrite what you have adapted. You decide when, and whether, to adopt anything new.
Workspace admins. They preview a set-up and copy it into the company workspace. After that, the set-up behaves like any other part of your workspace, with the same permissions your team already uses.