An EDMS licence price does not cover all the work needed for launch. To discuss a project with IQusion IT, the customer can prepare an estimate with a consistent planning horizon and currency. Show one-time and recurring payments, internal staff effort, and the basis for each estimate separately. The guide provides an educational template and a scope-change example involving an additional archive format. These are not IQusion prices or a completed project’s budget; a real budget requires discovery, supplier quotations, and agreed terms.
Fundamentals of Budgeting and Resource Planning
Start with the planning horizon, currency, and estimate date. For example, the horizon may cover launch and an agreed support period; the customer chooses it. For cash-flow planning, separate one-time and recurring payments and record when they fall due. This distinction does not determine their accounting classification: the responsible specialist assesses that separately under the company’s accounting policy and applicable rules.
It is critical to separate direct cash payments to external contractors from the cost of the company's internal efforts. Internal labor costs require separate attention, as involving one's own administrators requires significant working time. This time must be reflected in the estimate as a separate resource category. If a company does not record internal labor costs, there is a risk of hidden personnel overload. For verification, it is necessary to compare planned user involvement hours with actual timesheets during the pilot project.
Each template row should contain the cost type, estimate source, and owner. For a real budget, use a quotation, discovery findings, agreed scope, or a confirmed staff allocation plan. If evidence is missing, mark the estimate as provisional and record who will refine it and how. Synthetic data are appropriate for the teaching example but do not replace evidence for the actual project estimate.
Licenses, Subscriptions, and Basic Infrastructure
Record the licensing model, its metric, and payment terms. A perpetual licence may have separate support or upgrade charges; a subscription may be paid monthly, annually in advance, or under another contractual arrangement. Do not spread payments evenly without checking the terms. Record the actual payment calendar and service coverage period separately so that options are compared over the same horizon.
In addition to software, the budget must account for costs related to supporting information infrastructure. This includes renting cloud servers, purchasing hardware, and database management system licenses. These costs may belong to other departments' budgets, but they are an integral part of the total cost of ownership of the solution. Infrastructure requirements must be documented before implementation begins.
Special attention should be paid to costs for development and testing environments. Industrial operation requires isolated server capacities for verifying updates. Distributing these costs in a reusable estimate helps prevent situations where technical limitations become an obstacle to deploying new features.
Analysis, Configuration, and Data Migration
The preparation stage for implementation requires an analysis of the company's current state. The public description of IT consulting services covers the assessment of existing processes, systems, data, and risks, as well as process mapping. The result is a comparison of available solution options by cost, timeline, and risk. Based on this data, a phased roadmap is formed, which contains specific acceptance criteria.
After the roadmap is approved, the configuration stage begins. According to the public description of document management implementation services, this process includes researching document flow routes, setting up document models, and user roles. Data migration work and integration with existing accounting systems form a significant part of the budget.
Costs for migrating historical data require maximum detail. It is necessary to account for the effort required to extract, transform, and load data into the target system. The estimate must clearly define data volumes. The table below demonstrates an illustrative example of a reusable budget structure.
| Expense Item | Quantity/Rate Confirmation | Included/Excluded Scope | Acceptance/Payment Dependency |
|---|---|---|---|
| Software Licenses | Quantity under the actual licensing metric: users, connections, or another agreed unit | Basic access included; specific modules excluded | Transfer of license keys |
| Analysis and Process Mapping | Analyst hours at an agreed rate | Current state description included; reengineering excluded | Roadmap approval |
| Route and Role Configuration | Number of document types by specification | Model configuration included; non-standard scripts excluded | Successful completion of configuration |
| Historical Data Migration | Data volume in gigabytes or number of records | Transfer of approved formats included; data cleaning excluded | Confirmation of migrated data integrity |
| User Training | Number of training sessions and formed groups | Pilot conduct included; individual video creation excluded | Signing of the service delivery act |
| Internal Personnel Labor Costs | Customer personnel hours according to the project plan | Testing participation included; current operational work excluded | Internal time records without a separate payment to the supplier |
Change Management: Identifying Additional Archive Formats
During the execution of work, circumstances arise that require adjustments to the plan. Consider an illustrative example: during the migration stage, the team discovers an additional legacy archive document format that was not included in the base scope of work. This situation requires launching a formal change management process to update the reusable estimate.
Start the change assessment by identifying the new format and the affected data scope. The estimate owner checks sample files, the conversion approach, and what the existing quotation already includes. The teaching scenario introduces an additional format without calculating its actual effort here. For a real project, refine the estimate using discovery, a trial migration, or a supplier quotation, record uncertainty, and submit the decision to the authorized customer representative.
The steering committee makes a decision regarding the feasibility of migrating the discovered archive. If a positive decision is made, the budget is updated. It is important to add new costs as a separate row in the estimate, clearly indicating the dependency on the base scope. This approach prevents double-paying for work already covered by the supplier's initial proposal. The updated estimate becomes the new baseline for further control.
Practical Steps for Budget Approval
Completing budget formation requires several specific steps. First, it is necessary to consolidate all expense items into a single reusable template, verifying the correct distribution between one-time and recurring payments within the chosen planning horizon. Next, the internal labor cost estimate should be coordinated with the heads of relevant departments to confirm personnel availability during project implementation.
The next step is the formal approval of the baseline budget by company management. This document becomes the project's financial foundation and the starting point for measuring future deviations. Along with the budget, a change management regulation should be approved, defining the authority of responsible persons regarding the approval of additional expenses.
Reconcile the payment calendar with the contract and acceptance process. Some payments may be advances, while others depend on a checked result or service period; the estimate must reflect the agreed terms. For each stage, identify the payment evidence and who checks it. Then compare actual expenditure with the relevant budget version while preserving the history of approved changes.
Action checklist
- Define a single planning horizon and calculation currency for the entire reusable estimate.
- Separate one-time and recurring payments from internal staff effort; check accounting classification separately.
- Record specific acceptance criteria and payment dependencies for each implementation stage.
- Document the baseline version of the scope of work to prevent double-counting of services.
- Create a change management process to evaluate new requirements, such as additional archive formats.
Questions and answers
Why should internal labor costs be highlighted as a separate budget category?
Internal efforts do not require direct cash payments to the supplier, but they reflect the real load on personnel. Accounting for them helps avoid resource shortages during testing and training.
How to avoid double-counting expenses when changing the scope of work?
Each change must record a new version of the scope, the estimate owner, and the level of uncertainty. New tasks are added as separate budget rows with a dependency on the baseline plan.
How to verify data migration results before paying for this stage?
Before migration, agree its scope and acceptance criteria: the records and files to transfer, the metadata, relationships, and permissions to reconcile, and how exceptions will be checked. Record counts and file integrity form part of the checks but do not replace the other agreed criteria. Record the acceptance decision and payment basis under the contract terms.