Business
First Time Hiring a Consultant? Five Things the Scope Has to Settle Before Day One
A dental practice got the website it paid for and none of the accounts underneath it. What a scope of work has to decide now that it did not have to decide ten years ago.

The practice manager at a four-chair dental office outside Columbus had never hired an outside firm before, and the scope she signed ran to one page: design and build a modern website with online booking, three rounds of revisions, launch within eight weeks. Eleven weeks later the site was live and the booking widget worked. Then the renewal notices started arriving at the developer's address rather than hers. The domain was registered in his name, the scheduling tool was a monthly subscription on his card with a markup attached, and the analytics property sat inside an agency account she had no login for. Nothing in that sentence describes a scam. It describes a scope that said what would be built and never said who would own it.
1. A definition of done that someone other than the vendor can test
Launch within eight weeks is a date, not a standard. The practice manager had no written answer to the question of what the site had to do before she was obliged to pay the final invoice, which meant that when the booking form failed on older phones, the argument was about whether that counted as a defect or a new request. A usable scope names tests: the booking flow completes on the three browsers your patients actually use, the contact form delivers to a named inbox, page load stays under a stated threshold on a phone connection. Write the test and the person running it. Otherwise the vendor defines completion by delivering, and you define it by working, and those are different days.
First-time buyers tend to assume the acceptance standard is implied by professional norms, and in some fields it genuinely is, because a licensed engineer's stamped drawing has to satisfy a plan reviewer whether or not your contract mentions it. Most professional services carry no such external check. The person who decides whether the work is finished is whoever the contract says decides, and if the contract is silent, it is the party holding the unpaid balance. That is leverage, and it is worth knowing before you spend it.
2. Who the accounts belong to on the day the work ends
This is the clause that did not need to exist ten years ago and now carries more value than the deliverables list. A 2014 scope for a small-business website was close to complete once it described the pages, because the output was a set of files that arrived by FTP and sat on hosting you had bought yourself. The work product and the asset were the same object. They are no longer the same object. The current version of that job produces a domain registration, a hosting account, a content platform subscription, a payment processor connection, a scheduling tool, an email sending service and a handful of API keys, and every one of them was opened by somebody, in somebody's name, on somebody's card.
So the scope needs a short inventory: every account the engagement will create or touch, the legal entity that will own it, the billing method, and the renewal date. The practical test is simple and worth writing into the document. If this firm stopped answering the phone on Friday, what do you still control on Monday? The Federal Trade Commission oversees how businesses handle customer data and the claims they make about it, which is a useful reminder that responsibility for the patient records flowing through that booking tool stayed with the practice the whole time, regardless of whose login reached them.
3. What you owe, and what the delay costs when you are late
Scopes written by first-time buyers almost always describe only one party's obligations. The eleven weeks in Columbus were not eleven weeks of slow work; roughly three of them were the practice sitting on photographs, staff bios and a decision about whether insurance information belonged on the home page. The developer had no contractual way to stop the clock and no written basis to charge for the gap, so he absorbed it, and then pushed back hard on the browser fix because by then he was working at a loss. That is the ordinary shape of a dispute in professional services: an unpriced client delay converted into vendor reluctance three weeks later.
Name your inputs, name the person on your side responsible for each, and name the consequence. A dependency list with dates lets either party raise a problem early and in writing, which is the only moment when raising it is cheap. It also tells you something uncomfortable and useful, which is how much of the schedule you personally control.
4. The price of a change, agreed before you want one
Three rounds of revisions is a count without a unit. Moving a logo and rebuilding a navigation structure are both revisions in plain English, and no first-time buyer discovers the difference until the fourth request. What settles it is a change mechanism: a stated hourly or daily rate for work outside the scope, a written threshold under which small changes are absorbed, a requirement that anything above the threshold gets a one-paragraph estimate and your approval before work starts, and a named person on your side who can give that approval.
The last item is the one people skip and the one that causes the most trouble in an organization of any size. If the vendor can be instructed by three different people, the vendor will be instructed by three different people, and the scope will expand through accumulated small yeses that nobody remembers authorizing. Put one name in the document. Give that person the authority in fact as well as on paper, because a scope that routes approvals through someone who has to ask a partner for every three hundred dollars is slower than having no process at all.
5. What the last week looks like
Handover used to be a file transfer. It is now a transfer of control, and it takes longer, so it belongs in the scope with time allocated to it rather than appearing as a line item nobody budgeted. The components are consistent across most professional engagements: ownership of every account moved into your name with billing updated, credentials delivered through something safer than email, written documentation of how the thing works and what breaks it, a list of recurring costs with renewal dates, and a defined support window with a rate attached for what happens after it ends.
Ask one further question while you still have the vendor's attention, and have the answer written down. Who else could maintain this? A build that only its author can touch is a build with a permanent dependency attached, and that is a legitimate choice if you make it knowingly and price it. The Columbus practice eventually got everything moved, which took one paid afternoon and a lot of forwarded verification codes, and the second scope she signed, for a different firm, opened with an account inventory because she wrote it herself.
The useful habit is to read any scope asking a single question of each paragraph: if this goes wrong, who gets to decide what happens next? The answer is frequently not the person signing, and the fix is almost always a sentence long.