Skip to content
14Build Documentation

On-Chain SOQ Updates

On-Chain SOQ Updates

In 14Build, all updates to the Schedule of Quantities (SOQ)—including changes to quantities, tasks, or costs—are securely recorded on the blockchain. This ensures complete transparency, auditability, and immutability throughout the project lifecycle.

1. Why On-Chain Updates Matter

Recording SOQ updates on-chain provides:

  • Transparency: Stakeholders can verify all changes in real-time.
  • Traceability: Each change is logged with timestamps and user details.
  • Auditability: Immutable records ensure no data tampering or disputes.
  • Accountability: Clients, contractors, and team members are held accountable for changes.

2. What Updates Are Recorded On-Chain?

The following SOQ updates are recorded on-chain:

Update TypeDescription
Quantity ChangesAdjustments to task quantities (e.g., +10 m³ concrete)
Cost UpdatesChanges to unit rates or total task costs
Task AdditionsAdding new materials or labor tasks to the SOQ
Task RemovalsRemoving tasks no longer needed
Variation RequestsApproved changes due to scope adjustments
Proof of Work UpdatesProgress logs or attachments validating task updates

3. Workflow for On-Chain SOQ Updates

Here’s how SOQ updates are processed and recorded on-chain:

Step 1: Trigger the Update

  • Updates can be triggered by:
    1. Clients: Adding, removing, or modifying tasks.
    2. Contractors: Submitting variation requests for scope or cost adjustments.
    3. Project Managers: Approving changes based on site progress.

Step 2: Record Update Request

  • Updates are submitted via the SOQ Dashboard with the following details:
    • Task Reference (SOQ Line Item)
    • Update Type (Quantity, Cost, Addition, etc.)
    • Reason for Update
    • Supporting Documents (e.g., drawings, logs)

Step 3: Review and Approval

  1. The Client or Project Manager reviews the update request.
  2. Approved changes are recorded on-chain with:
    • Timestamp
    • Updated Value
    • User ID (who approved the change)
  3. Notifications are sent to all relevant stakeholders.

Step 4: On-Chain Update Logging

The approved changes are recorded on-chain using smart contracts. Each update log includes:

FieldDescription
SOQ Task IDReference to the updated task
Update TypeType of change (quantity, cost, etc.)
Old ValueValue before the update
New ValueUpdated value
Updated ByUser ID of the person approving the change
TimestampDate and time of the update
Proof of WorkOptional attachments validating the update

4. Use Case Example: On-Chain SOQ Update

Scenario:

During the “Foundation Work” phase, the contractor submits a variation request to increase the concrete quantity due to on-site adjustments.

Before UpdateAfter Update
Concrete Quantity: 40 m³Concrete Quantity: 50 m³
Unit Rate: $120Unit Rate: $120
Total Cost: $4,800Total Cost: $6,000
  1. The contractor submits the variation request through the SOQ Dashboard.
  2. The client reviews and approves the change.
  3. The update is recorded on-chain with:
    • Task ID: Concrete Pouring
    • Old Value: 40 m³
    • New Value: 50 m³
    • Updated By: Client ID
    • Timestamp: 2024-06-01 10:30:00
  4. The change is now visible to all stakeholders, ensuring full transparency.

5. System Flow Diagram: On-Chain SOQ Updates

flowchart TD
A[SOQ Update Request] --> B[Review and Approval]
B --> |Approved| C[Smart Contract Records Update]
C --> D[On-Chain Log Created]
D --> E[Update Visible to Stakeholders]
B --> |Rejected| F[Request Revision]