Skip to content

Only in SEQUESTO · Every action on record

See who did what. On every bid, for every person.

Every file created, moved, shared or deleted, every comment and every access change is on record, with the person who did it and when. You also see who works on which bid and how much time it takes, so you manage the team on facts.

See who did what. On every bid, for every person.
  • Barona
  • Efficy
  • ISS
  • Nextbike
  • oodrive
  • GK Software
  • Dalcour Maclaren
  • Peak3

A bid goes wrong in the gaps between people. A plain record of every action, by people and by James, closes those gaps and shows where the team's effort really goes.

THE RECORD

Why is it so hard to know who did what on a bid?

A bid has ten contributors, three deadlines and hundreds of files. When something goes wrong two days before submission, nobody knows who moved the annexes folder or changed the price sheet. When the bid is over, nobody can say how much effort it really took, or who carried it.

Why is it so hard to know who did what on a bid?
  • 01

    Most tools log for IT

    Most tools keep a technical log for IT, or nothing at all.

  • 02

    Plain sentences, one per action

    SEQUESTO keeps a record the bid director can read: plain sentences, one per action, with the person, the file and the time.

Before / With SEQUESTO

Before

  • "Who changed this?" asked in the team chat
  • No way to tell a colleague's edit from the AI's
  • Effort per bid guessed after the fact
  • A wrong edit means starting again

With SEQUESTO

  • The answer in the log, with name and time
  • Actions James took are marked with the person he acted for
  • Time spent per person and per bid
  • Restore the previous version

WHAT IS LOGGED

What is on record?

Every action that changes a bid, as it happens:

What is on record?
  • 01

    Files and folders

    Created, renamed, moved, deleted, archived, restored, and every new version.

  • 02

    Fields and people

    A status, deadline or contract value changed, a person assigned to a bid.

  • 03

    Access

    Access granted or revoked, permission and ownership changes.

  • 04

    Team

    Members added, removed or updated.

  • 05

    Bids

    Projects started, ready, deleted.

  • 06

    Collaboration

    Comments created, replied to, resolved and reopened, including comments left for a colleague.

  • 07

    Connections

    Sync connections created, changed or removed.

Each entry is a plain sentence: who did it, what, where and when. Admins filter by person, action type and date range, or search the text.

Take the record wherever you need it. When an auditor, a client or your own compliance team asks for evidence, export the log in minutes instead of piecing it together from e-mails. Or connect it to your company's security and compliance tools through SEQUESTO's API, so your IT team sees bid activity next to everything else they monitor.

ACTIVITY

Who works on what, and for how long

The log tells you what happened. Activity tells you how the team works.

Who works on what, and for how long
  • 01

    Per person and per bid

    For each person, see the bids they worked on and the time they spent on each. For each bid, see who contributed and how much.

    That answers the questions a bid director is asked every quarter.

  • 02

    How much effort a bid takes

    How much effort does a bid really take? Compare a public tender with a private RFP, or this year with last year.

  • 03

    Who is overloaded

    Who is overloaded? See where the hours go before someone burns out in the week of three deadlines.

  • 04

    Where SEQUESTO saves time

    Where does SEQUESTO save time? Compare time per bid before and after a workflow or a library set-up is introduced.

  • 05

    Who has adopted it

    Who has adopted the new way of working? See who works in SEQUESTO every week, and who still works outside it.

AI ACTIONS

What the AI did, and for whom

When James, SEQUESTO's AI bid agent, changes a document on someone's behalf, the record shows it: the person who asked and the fact that James carried it out.

What the AI did, and for whom
  • 01

    Checked before the change

    James never edits a document without the user's own instruction, which is checked before the change is made.

  • 02

    Review means review

    When you only ask him to review, he reviews.

  • 03

    James usage per person and bid

    Admins can also see how much each person and each bid used James over a period, to follow adoption across teams.

VERSIONS

Go back, not start again

Every document keeps its version history.

Go back, not start again

Undo a bad edit

Open an earlier version, compare it and restore it when an edit went wrong, whether a colleague or James made it.

TWO DAYS OUT

An example: the folder that moved two days before the deadline

Two days before a public tender deadline, the bid manager cannot find the "Annexes" folder.

Find it in the log

An admin filters the log on "Folder moved" for the last two days: a colleague moved it into an archive project by mistake. The admin moves it back.

Restore yesterday's version

A signed declaration was also overwritten in the confusion, so the bid manager restores yesterday's version from its history.

Read the time per bid

At the end of the quarter, the bid director looks at the time spent per bid and sees that security questionnaires take the team twice as long as expected.

Start from a shared workflow

The next quarter starts with a shared workflow for them.

An example: the folder that moved two days before the deadline

FOUR STEPS

How it works

Work as usual. Every action is recorded as it happens, by people and by James.

How it works
  • 01

    Search the log

    Filter by person, action type and date range, or search the text. Export it, or send it to your own tools through the API.

  • 02

    Read the activity

    Time and contributions per person and per bid.

  • 03

    Restore when needed

    Open a document's version history and restore an earlier version.

Frequently asked questions

Yes. SEQUESTO records who did what on every bid, including what James did on whose behalf. Admins filter the log by person, action type and date range, and search the text of the entries.

Files and folders created, renamed, moved, deleted, archived and restored; new versions; field changes; people assigned; access granted or revoked; permission and ownership changes; members added, removed or updated; bids started and deleted; comments; and sync connection changes.

Yes. When James changes a document on someone's behalf, the record shows the person who asked. James only edits on the user's own instruction, and every change can be undone from the version history.

Yes. For each person, see the bids they worked on and the time they spent on each. For each bid, see who contributed and for how long.

Admins. It covers the whole company, so it stays with the people responsible for access and governance. Everyone else works with the version history of the documents they can open.

Yes. Admins can export the log, for example for an audit or a client request, and your IT team can pull it into your own security and compliance tools through SEQUESTO's API.

Yes. Every document keeps its version history, and any earlier version can be restored.