Nonprofit consultant-selection guide
Guide 6: Contract for delivery, change, and accountability
Turn the selected approach into visible responsibilities, evidence, and decision points.
Connect deliverables to acceptance
For each stage, name the output, responsible parties, client inputs, review period, acceptance authority, and evidence that supports acceptance. Separate discovery findings from implementation commitments when discovery can materially change scope.
Define how defects, missed assumptions, client delays, third-party changes, and new requests are classified. A change process should show effect on time, cost, risk, and acceptance before work expands.
Make ownership and access explicit
Address business-owned accounts, administrator rights, created materials, configurations, source work, documentation, data handling, backups, subcontractors, and access removal. Use approved secret-management and identity practices instead of shared credentials in project documents.
Address confidentiality, privacy, security, accessibility, records, intellectual property, insurance, liability, termination, and dispute terms with qualified reviewers for the actual engagement and jurisdiction.
Protect the exit as carefully as the start
Specify what the nonprofit receives if work pauses or ends, how materials are transferred, how external access is removed, which fees survive, and how existing operations continue. A usable exit is part of responsible implementation design.
Keep a signed agreement, approved changes, decisions, acceptance records, and the current operating documentation in an accountable location.