Every requirement, date and task.
One page per Landscaping tender in Australia.

How a bid manager runs a tender in Lucius

A bid is a list of requirements, a handful of dates and a few people who each own part of the response. Lucius keeps all three on one page per tender, taken from the tender documents themselves.

1. 01

   Every requirement, with its page

   Lucius reads the tender documents and lists every requirement with the page it came from, a quote from the source and a severity. Group the list by severity to see what can sink the bid first, or by response section to plan the writing.

2. 02

   Section owners

   Name once, for your workspace, who owns each section of a bid: Legal to one person, Technical to another, Financial to a third. When a tender finishes its analysis, every requirement goes to its section's owner, and "Assign by section" does the same for tenders analysed before. A choice made by hand on one requirement wins, and each person can filter the list to their own rows.

3. 03

   Tasks with an owner and a due date

   Turn a requirement into a task, give it to a teammate and set an internal due date earlier than the tender's own. The owner gets an email, the task shows on their dashboard and on the calendar, and a reminder arrives the day before it is due and on the morning it is due. Each task can carry comments and a link to the supporting document in Google Drive.

4. 04

   Deadline reminders, and addenda that move the date

   Lucius takes the submission deadline from the tender documents and emails a reminder 7, 3 and 1 day before it and on its morning, for every tender you analyse or save. Set the date clarification questions close and it gets the same reminders. When an addendum extends the deadline, change it on the tender page: the countdowns, the calendar and the reminders move to the new date, and the old date stays in the tender's history. The pipeline board groups your tenders by how soon they close: this week, the next two weeks, later.

5. 05

   Check the finished bid, then sign off

   Tick each requirement off as your response covers it. Before you submit, upload the finished bid: Lucius reads it against the tender's requirements and lists which are answered, which are not, and the buyer's terms to note. Then ask a teammate to sign the bid off: they approve it or send it back with a note, and the tender keeps the record of who asked, who decided and why.

6. 06

   Drafts, versions and roles

   Lucius drafts a first response from the tender and your company documents. A new draft keeps the previous one, so you can compare versions and restore an earlier one. Teammates join your workspace as an admin, an editor or a viewer.