CP
Project comparison
| Project ID | Project name | Active revision | Direct cost | Tender value | Man-hours | P6 Reconciliation |
|---|
Company workspace
Projects Portfolio
Create, open, duplicate, archive and compare tender projects from one controlled workspace.
Commercial control centre
Tender estimating workspace
Import the client BOQ, build rates from resources, issue the planner package and reconcile the returned P6 programme.
Tender stage
Tendering, awarded or not awarded: changed by the head of estimating (or whom he gave the right), with a reason.
Changes
What changed in this project's pricing, who changed it and when, newest first. Official issues are listed too.
Productivity
The project's working calendar and its factor on every output of the library, and what the priced analyses hold: man-hours by trade and plant hours. For information.
Enrich the libraries
The tender is closed: what it taught can go into the company's libraries. Nothing enters them until it is applied here.
01
Estimate-to-schedule roadmap
02
Reconciliation result
03
Risk scenario
Input module
Client BOQ
Load one or more XLSX or CSV files, inspect their structures and map each client's columns to the estimating model.
↑
Drop the client BOQ here
XLSX or CSV · maximum preview size 25 MB
—
No files selectedWaiting for client BOQ files
02
NOT READYWorkbook discovery
Select a file to see every sheet it contains, what kind of sheet each one is, and which will be imported.
Import a workbook to see its sheets.
03
Sheet preview
0 rows
Choose a sheet to preview its rows.
The first 20 rows of the sheet as they were read. Every item the file yielded is listed in BOQ structure below.
Review queue
Items the owner's file left incomplete. Nothing here was guessed or filled in automatically.
| Severity | Issue and what it means | Full description (where it sits in the bill) | Answer |
|---|
04
BOQ structure
| Item | Description | Unit | Quantity | Source | Review |
|---|
Library module
Company Master
Work items, assemblies, the rate book, trades, global variables and indirect templates, kept once for the company. Pricing offers only what is approved.
Seed the standard trades, variables and indirect templates, then bring the imported Candy resources in. Every entry starts as a draft or as approved Candy data, and moves through review before pricing may use it.
Entries
Productivity Library
Each kind of work: its crew, what the crew produces in a day and the hours per unit that gives. A value typed here is a draft until another account approves it. The indicator on Price Build-up reads this library; it never changes a price.
| Kind of work | Unit | Crew | Output per crew-day | Man-hours per unit | Basis | Observations |
|---|
Price history
Every rate the company has priced or been given, kept as evidence. A new rate is judged against the same work in other projects: same price code first, similar words otherwise; cost against cost, offer against offer.
| Source | Project | Location | Date | Source | Prices |
|---|
| Description | Unit | Projects / prices | Median | Usual range | Lowest – highest | Evidence |
|---|
Library module
Resource Library
Labour, materials, plant, subcontractors and composite crews used by the price build-ups.
One list for the whole company, not for one project: every worksheet in every project takes its resources and current rates from here. A rate for one project only is typed on the worksheet line (Project rate) and never changes this list. Placeholder: a code Candy reserved with a rate of 0 or 1 - no real price; a worksheet line on it stays unpriced until a rate is entered here or on the line.
Active resources
| Code | Type | Description | Unit | Base rate | Rate status | Source |
|---|
Calculation module
Price Build-up
Decide each item's scope and pricing, build worksheets from the company library, add internal costs and the margin. Every figure comes from one run of the engine.
Candy job import
Job resources given a new code
On this job Candy used these library codes for different work.
| Library code and name | Candy's name on this job | Code used | Lines | Why |
|---|
Candy items not found in the bill
Their cost is not in the estimate. Match them by hand, or check the bill they belong to was imported.
| Candy item | Description | Quantity | Cost | Match to bill line |
|---|
Bill items
| Item | Div. | Description | Quantity | Scope | Mode | Price code / rate | Unit cost | Direct cost | Offer rate | Status |
|---|
Internal additions
Priced, never offered: their cost is recovered inside the measured rates. Evaluated after the direct cost, in dependency order.
| Description | Basis | Measure | Cost | Derivation |
|---|
Reconciliation checks
The checks a reviewer runs by hand. The run performs them and refuses to look finished if any fails.
Calculation module
Commercial
Finalise the tender, phase it over time, value progress, manage subcontracts, branch scenarios and run reports - all from the same pricing run.
Finalisation
Every layer is recovered on the measured lines only and the offer closes to the halala. The owner's bill leaves with these rates once they are saved.
Offer rate by hand
Type the offer rate of any line to fix it on the owner's bill; leave it empty for the automatic rate. The difference hand rates make to the tender is shown as its own layer. A rate under cost or far from the company's offers for the same work asks for a reason.
| Item | Description | Quantity | Cost rate | Automatic offer rate | Offer rate by hand | Margin on cost |
|---|
Forecast & cash flow
Activities phased over months from their proposed durations or from the programme; manhours per resource kind; cash flow with lag, retention and advance.
Valuations
Quantities done per bill line give earned revenue at offer rates and allowable cost at cost rates; actual cost, when entered, gives the variance and the EVM indices.
| Item | Description | Quantity | Done | Actual cost |
|---|
Subcontracts & quotes
Group bill lines into a package, adjudicate supplier quotes against our estimate (scope gaps priced at our rate and flagged), award, then record claims with retention and advance recovery.
| Package | Awarded to | Contract value | Certified | Retention held | Status |
|---|
Scenarios
Branches of the base estimate - rates, crews, mark-up, start - compared on cost, offer, duration and peak funding. Nothing here changes the estimate itself.
Reports
The standard report set - bill summary, cost breakdown, resources by trade, worksheets, indirects, mark-up, activities, histogram, cash flow, valuation - run on this project and downloaded as Excel. Definitions are data; the figures are this revision's.
| Report | Grouped by |
|---|
Actuals
What was really done against a price code, with the manhours and cost it took. The comparison proposes master updates; a reviewer approves or rejects them, nothing is applied by itself.
| Price code | Done | Manhours | Cost | Period |
|---|
Quantity impact
Change an owner quantity and see at once what it does to cost and offer, to every resource through the worksheets, to the linked activities and to the months of the cash flow.
Output module
Planner Package
Activities from the priced bill and the planner's own mapping: each bill line linked to its activity by identity, quantities split by share, resources per activity. The link is created once and kept.
P6 import files (optional):
Ready for the planner?
The package leaves only when every priced item feeds an activity, no item is over-allocated and every template suggestion is confirmed - or an exception with its reason is on record.
| Blocker | Count | Cost | Exception |
|---|
The links waiting for your confirmation
Each line is a priced bill item the planner's mapping did not cover; the company's activity templates proposed the activity. Confirm it, or move the item to the right activity. Lowest confidence first.
| Item | Full description | Quantity | Cost | Proposed activity | Confidence | Why |
|---|
Activities
| Activity ID | Discipline | Building | Activity | Quantity | Items | Direct cost | Duration |
|---|
Item - activity links
Every link between a bill item and an activity, 100 at a time. Search by item number, description or activity, show only the links waiting for confirmation, or one WBS group.
| Item | Full description | Quantity | Cost | Activity | Confidence | Why |
|---|
Link an item by hand
Search a priced bill item, see the activity it feeds now, and move it to another activity from the project dictionary or the company library. The link is kept on the project.
| Item | Description | Quantity | Cost | Feeds now |
|---|
Activities not from BOQ items
Activities the project needs that no bill item carries (mobilisation, approvals, testing, handover). Each keeps a permanent id and its P6 Activity ID; it goes to the planner package, the XER and the P6 Excel at no cost, and is never an unlinked item.
| Activity ID | Activity name | Discipline | WBS (building group) | Why the project needs it |
|---|
Priced items with no activity
Their cost is not in any activity yet. Choose an activity from the company library; the link is kept on the project.
| Item | Description | Quantity | Cost | Status | Activity |
|---|
Input / comparison module
P6 Reconciliation
Compare the planner's programme (XER) with the activities we built from the bill: at the baseline, to see what the planner changed; at the end, to see what reality did. The programme is compared, never built from.
P6
No XER imported for this projectImport the planner's programme to compare.
Our activities against the programme
| Activity ID | Our activity | Programme activity | Our days | Programme days | Variance | Status |
|---|
Baseline against the latest update
What the planner changed since the baseline: dates, durations, logic, float, progress. Tasks are matched by our EST id when the programme carries it, else by task code.
| Task | Activity | Finish slip (days) | What changed |
|---|
The planner's baseline against the issued mapping
Each difference between his baseline and the mapping we issued, beside our activity, its P6 Activity ID and the bill items and shares it carried. Nothing is learned until a named person confirms; what is rejected teaches nothing. Pricing is never changed.
What the planner changed at baseline
The activities we sent against his baseline, by identity: what he kept, renamed, split, merged or deleted, what he added and where, and the durations he gave. The company library learns it: a step he deletes in most projects is no longer proposed, an activity he adds in two projects is proposed there, his durations fill activities without one.
Our resources against the programme's assignments
Per activity: the manhours and cost our estimate carries against what the planner loaded on the matching P6 tasks. Within 5% is a match; the rest is for the planner and us to reconcile.
| Activity | Status | Our manhours | P6 manhours | Our cost | P6 cost | Cost delta % | Resources |
|---|
Programme activities no bill cost feeds
The planner schedules these and none of our activities matches. Either our mapping lacks them, or they are split finer than the bill (per floor). Schedule-only steps are excluded.
| Discipline | Activity | Buildings | Programme tasks |
|---|
Our activities the programme does not schedule
Cost we carry that the planner has no activity for - to raise with the planner, or to learn from for the next tender.
| Activity ID | Activity | Building | Direct cost |
|---|
Output module
Reports & Exports
Download controlled handover files for estimating, planning and management review.
Capability coverage
| Area | Status | Program capability | Added flexibility |
|---|
Governance
Access & Audit
Role-based permissions and an immutable activity trail across every project.
Users and permissions
Accounts live on the server; the server enforces what each role may change.
| User | Role | Permissions | State | Last sign-in | Actions |
|---|
Audit trail
| Time | User | Action | Project ID | Details |
|---|
Server and backup
The database and every stored file, as one zip. Restore replaces the server's data after backing up what is there.
