ENQUIRIES
Resolve the scope questions before making a commitment.
The right engagement depends on the information available, the outcome required and the responsibilities each party will retain. These answers explain the initial process. Your accepted proposal and engagement documents set out the terms for the actual work; a general website answer does not override them.
Scope and cost
Can we request one service rather than a recurring arrangement? Yes. A focused assignment may be appropriate. How is the fee assessed? Relevant factors include entities, periods, transaction volume, record condition, reporting needs and project complexity. Is software included? Licences, hosting, integrations and separate development are identified in the proposal rather than assumed to be included.
Information and timing
What is needed for an initial enquiry? Provide the organisation name, requirement, current system and relevant deadline. Do not send passwords or a full confidential archive. Can you guarantee a completion date immediately? No. The work and dependencies need assessment. Where a deadline matters, identify the recipient and the consequences so the proposed scope can address them realistically.
Reports and ongoing support
Does preparation include audit? No; the nature of any assurance work must be expressly agreed and appropriately authorised. Does a verification link guarantee acceptance? No; it shows the approved issue record and status, not a recipient's acceptance decision. What support follows delivery? The proposal defines any included handover, correction process and separately agreed continuing support.
Questions and answers
What happens if our requirement changes after acceptance?
We assess the effect on work, timing and fees, then record the revised scope for agreement before proceeding.