Effective cost and contract management is a key element of successful project execution. A properly structured cost model ensures budget transparency, simplifies financial control, and minimizes the risk of overspending. Below are extended rules, based on the selected content, which form a unified methodology for working with costs and contractual obligations within the project.
1. Rules for Project Cost Planning
Fixed costs are not allocated to resources and contractors
Fixed costs must be specified only at the task or project stage level, without being tied to specific performers. This approach helps avoid incorrect cost distribution across resources and maintains accurate financial calculations. Fixed cost is always considered as a constant amount that does not depend on the number of executors or their workload.
Example: The project includes a fixed cost for equipment rental — 50,000 UAH. It is specified on the “Equipment Rental” task without distribution among engineers or contractors.
All costs must be covered by the total amount of payments
When planning a budget, it is important to maintain a strict balance between planned costs and the amount of payments under contracts or agreements. This ensures in advance that financial obligations are sufficient to cover all expenses. Any mismatch between costs and payments signals the need for additional analysis and budget adjustments.
Example: If the total cost of work for a lot is 200,000 UAH, the contractual payment amounts must also equal 200,000 UAH. If payments are lower, the budget must be corrected.
A payment is marked as completed, but no payment document is provided
If a payment is recorded in the project but no supporting payment documentation is attached, this creates risks for financial auditing. It is essential that every recorded payment is accompanied by a correct payment document or other proof. This ensures that financial data is verifiable and reduces risks for the project.
Example: The system shows “30,000 UAH paid,” but no document is attached. In this case, the financial manager must upload the payment document; otherwise, the payment is considered unverified.
If costs change, payment amounts remain unchanged
Even if initially planned costs change, the amounts of actual payments must remain stable until official approval of adjustments is completed. This prevents uncontrolled budget growth and ensures the financial process remains manageable.
Example: If a contractor increases the cost of work from 120,000 to 150,000 UAH, the payment amount of 120,000 UAH remains fixed until an additional agreement is signed.
2. Rules for Contract Planning in the Project
Each lot must have assigned contractors
A lot, as part of the contract structure, must be assigned to specific contractors. This allows clear understanding of who is responsible for the completion of each work package and simplifies progress monitoring.
Example: The “Electrical Installation” lot is assigned to the contractor “Electroservice LTD.” Without an assigned contractor, the lot is considered invalid.
Contractors are assigned together with cost values
Assigning contractors must be accompanied by proper cost allocation. Costs must be linked to a specific contractor to ensure transparency and clarity of financial obligations.
Example: If the contractor “StroyInvest” is assigned to a task, it must include the cost — for example, 180,000 UAH for installation work.
Costs must not remain without assigned contractors
Any amount recorded in the budget as external cost must have an assigned executor. Lack of a contractor for cost items makes the budget incomplete and complicates contract management.
Example: The budget includes 90,000 UAH for “Finishing Works,” but no contractor is assigned — this is an error that must be corrected.
Contractors must not exist in the system without being assigned to work
If a contractor is created in the system, they must be assigned to specific tasks, stages, or lots. Otherwise, contractor data becomes formal and does not reflect actual project participation.
Example: Three contractors are added to the system, but none are assigned to any tasks — this makes the data incomplete and disrupts management processes.
Each work item must have only one contractor assigned
Each task must have one contractor responsible for its execution. This minimizes the risk of diffused responsibility, simplifies quality control, and reduces the likelihood of conflicts during acceptance.
Example: The task “Cable Laying” can only have one contractor to ensure clear responsibility.
Completed work must have assigned acceptance certificates
Every completed stage or task must be documented with an acceptance certificate. These documents confirm completion, serve as the basis for payment, and represent an important element of project reporting.
Example: After completing the task “Lighting Installation,” the system must include an acceptance certificate confirming completion and enabling payment.
