MIDMAK — Contractor scope, quantities and claims

The user records the contractor, site, period and an internal retention percentage, then adds items with units, quantities and prices. While the contract is a draft, these can be reviewed, edited or removed with a reason.

Activation fixes prices, units, baseline quantities, period and retention. Later changes record a reasoned current quantity while preserving the baseline, before and after amounts, difference and operation day.

A reduction cannot go below accepted quantities or quantities submitted for review. Changing scope therefore cannot erase work already accepted or reserved in an outstanding claim.

The user creates a draft claim, records measured quantities and enters a manual deduction. Drafts do not reserve scope, and several may compete for the same remainder. Submission checks it again and permits only one claim under review per contract.

Each line value is the difference between the newly measured cumulative quantity value and its previously accepted value. Retention is also a cumulative difference. Splitting a fractional unit into small measurements therefore does not accumulate independent rounding errors.

Submission fixes its baseline, quantities, prices, gross difference, retention, deduction and net value. The deduction cannot exceed the value remaining after retention, and the saved valuation is not retrospectively recomputed when later claims are accepted.

A submitted claim has separate site and quantity reviews, each with a manual note. Acceptance requires both and a decision note. Withdrawing a review requires a reason, retains its former note and returns acceptance to a waiting state.

Rejection releases the claim's reservation without deleting its submission snapshot or decision. A corrected revision archives the previous measurements, values, reviews and decision, then starts with fresh reviews and a baseline derived from current accepted work. An accepted claim remains locked against editing or cancellation.

Contract closure requires all current quantities to be accepted and every outstanding document resolved, with a recorded reason. An operation day cannot precede the file's last event. Reading an earlier day does not rewrite history or turn overview balances into an as-of financial statement.