Project-based consulting planning tool
Project-Based Consulting Agreement Checklist & Project Record
Turn a consulting brief into a review packet that identifies the business outcome, named deliverables, acceptance evidence, client dependencies, changes, fees, access, methods, and legal terms still requiring review.
Reviewed August 17, 2026Build the consulting project record
Consulting Project Record Preview
Run four project gates
- Outcome gate: name the client decision or operational result, not only the consultant activity.
- Scope gate: list deliverables, exclusions, dependencies, owners, milestones, and acceptance evidence.
- Change gate: require a written impact record for added work, timing, fees, and client inputs.
- Closeout gate: reconcile approvals, invoices, access removal, files, methods, rights proposals, and unresolved terms.
Project evidence to collect
Before work starts
Approved brief, stakeholder map, current-state data, system-access owner, deliverable inventory, assumptions, exclusions, baseline dates, and budget input.
At every milestone
Dated work product, source data, decision log, consolidated feedback, acceptance test, approver, change requests, dependency delays, and invoice support.
At closeout
Final approval, output register, method and third-party material register, access revocation, deletion confirmation, handoff inventory, open risks, and final accounting.
Separate the project records
| Record | Capture | Do not assume |
|---|---|---|
| Business outcome | Decision, operational change, baseline, observable success signal, owner | Consultant activity by itself proves value or completion |
| Deliverable | Format, contents, source, due date, approver, objective acceptance evidence | A general project label defines what is included |
| Change request | Requested difference, reason, timing, effort, fee, dependencies, written approval | Meetings, messages, or draft edits automatically expand scope |
| Rights proposal | Pre-existing methods, client inputs, project outputs, third-party materials, proposed owner/license | Payment alone transfers copyright or reusable know-how |
Worked example
Eight-week CRM sales-process redesign
Outcome locked
Decision owner approves one documented lead-to-opportunity process, field dictionary, routing rules, exception log, and 30-day adoption measurement plan.
Evidence attached
Baseline funnel export, six stakeholder interviews, current-state map, three workshop records, configuration sandbox screenshots, test cases, and dated decisions.
Acceptance defined
Operations director checks the field dictionary, ten routing test cases, ownership matrix, training handoff, and final open-risk register within five business days.
Worker status and intellectual property
Record facts before writing conclusions
For U.S. federal employment-tax purposes, the IRS says the actual relationship matters and groups relevant facts into behavioral control, financial control, and the type of relationship. A project record should capture those facts instead of deciding status from the heading or a checkbox.
The U.S. Copyright Office distinguishes ownership of a work from ownership of the copy that contains it. Identify consultant methods, client material, project outputs, third-party inputs, and any proposed transfer or license separately. A transfer of U.S. copyright ownership generally requires a signed writing by the rights owner.
Primary sources used for this checklist