Records and win/loss

crux keeps two records of its own: the bid log (what you bid and how it came out) and the quotes it reads. With the GC pack and a company database set up (any of the three choices), both are read from and written to that database, not to a separate list on this computer. Everyone connected to it sees the same records, and Estimating Intelligence shows them.

Not set up yet: crux keeps them on this computer, as it does for a trade pack (see Record wins and losses).

Win/loss and bid history#

Tell crux in the job's chat, in plain words:

• "We bid the clinic at 4.32 million, due 9/24."
• "Mark it lost, awarded to Rival A at 4.1 million." / "We got the award."

A bid is the project's row in the database: job, owner, bid date, our number, the outcome and the low or winning number; the scope, source, rank and who recorded it go in its notes. Bid openings already in the database (from the bid tabs crux recorded) show in the bid log too.

A result change is always shown first. crux answers with the one change it will make, for example "Clinic, bid event 9/24: result No award recorded → Lost (awarded to Rival A at $4,100,000)", and writes it on your yes. When several jobs match, it lists them and asks which; it never picks one itself. When your message already asked for exactly that change, it writes it at once. Afterwards it reads the result back ("Estimating Intelligence now shows Lost for ...").

The 90-day win rate and the matchup use these results.

Tip: A second copy of a project (a project row with no bid opening for the same job) is offered for removal, or its quotes are moved first. Only on your yes.

Quotes#

Every quote crux reads and records (in leveling, on bid day, or when you say "review this quote") goes into the database with its trade, job, line items and unit costs, its source file and date. The quote number, the date it is good until, its terms and notes stay in the job's binder. These quotes are your Cost Data (see Cost data).

Moving your old records in#

The first time the company database is connected while crux's own lists on this computer hold entries, crux offers once to copy them in. It shows a preview first (entries for the same job and bid date already in the database are skipped), and copies only on your yes.

When the database cannot be reached#

A result or a quote that cannot be written is not saved and not queued: crux says so plainly so you can record it again once the database is back. See Company database.