When I started Stringfest Analytics, I assumed the hard part would be the work itself: building training that lands, keeping current with Excel and Python, and figuring out how to explain tools like Power Query to people who have been burned by messy spreadsheets for years.
That work is hard, but it is also the part I know how to keep getting better at. What caught me off guard was everything that happens before the work starts: the contract, the terms, and the paragraphs that decide who carries the risk when a project goes sideways.
So, quick disclaimer before we go any further: I am not an attorney, and this is not legal advice. These are simply business terms I have learned to pay closer attention to as an independent analytics consultant and trainer. When something feels unclear, disproportionate, or unusually one-sided, that is the moment I slow down, ask questions, negotiate, or have a lawyer review it before I sign.
If you are a freelancer, a trainer, a Microsoft MVP doing side work, a data person picking up the occasional consulting gig, or someone moving from a salaried job into independent work, these are the clauses I now make a point to read carefully.
Scope of work
Start here, because almost everything else flows from it: what exactly are you being asked to deliver?
“Training” may be the obvious answer, but it is rarely the whole answer. Are you also building materials, creating sample files, holding office hours, providing recordings, offering support after the session ends, handling revisions, managing travel and setup, sitting through planning calls, or troubleshooting software access five minutes before class starts?
For data analytics work, this can get slippery fast. A one-hour Excel demo, a full-day Power BI workshop, and a custom Python in Excel training series are not the same thing, even if someone casually describes all three as “training.”
When the scope is vague, unstated work has a way of becoming your problem. You may end up delivering far more than you priced because nobody stopped to define what was included. I would rather over-specify what is included, and what is not, than discover the gap halfway through.
A few questions I want answered:
| Question | Why it matters |
|---|---|
| What exactly am I delivering? | Prevents the engagement from expanding after the agreement is signed |
| Are materials included? | Custom content can take significant unpaid time if it is not priced correctly |
| Are recordings allowed? | Recordings affect pricing, reuse, and intellectual property |
| Is post-session support included? | Q&A and office hours can become a second engagement |
| Who handles technical setup? | Platforms, laptops, permissions, and files can make or break the session |
A good contract should make the job easier to understand, not harder.
Payment terms
Next: when do you actually get paid?
Net 15, Net 30, and Net 60 are not just accounting phrases. Neither are phrases like “upon client payment” or “after final approval.” That kind of language can stretch the timeline in ways that are hard to plan around. You may have delivered the class, answered the questions, submitted the invoice, and still be waiting because someone else has not signed off, processed payment, or paid the broker.
I look for whether there is a deposit up front, whether there is a kill fee if the engagement is canceled, whether expenses are reimbursed separately, and whether payment is tied to something concrete, like delivery, or something less specific, like final approval.
A few things I want clear before I sign:
| Payment issue | What I want to know |
|---|---|
| Invoice timing | When can I invoice? Before delivery, after delivery, or at project completion? |
| Payment deadline | Is it Net 15, Net 30, Net 60, or something else? |
| Approval language | Who approves the work, and what does approval mean? |
| Brokered work | Am I paid regardless of when the end client pays the broker? |
| Expenses | Are reimbursements separate from my fee, and when are they paid? |
The class may end at 5 pm, but the business side does not. You still have to invoice, track payment, reconcile expenses, and follow up if something gets delayed. Clear payment terms save a lot of unpaid administrative work around the paid work.
Cancellation terms
If they cancel, what happens? If I cancel, what happens?
The thing I am checking for is balance. A fair contract does not have to treat both sides identically, because the client and consultant may carry different risks, but it should make clear what each side is responsible for.
I pay close attention to contracts where the client can cancel freely while I absorb the loss, or where my cancellation creates a serious financial consequence but the client’s cancellation does not.
This matters because holding a date has value. If I commit to a training day, that date is no longer available to another client. If I build custom materials, that work has happened whether the session ultimately runs or not. If I book travel, move meetings, or block off prep time, the cost is not imaginary just because the client changes direction.
Liquidated damages and penalties
I am cautious around any term that imposes a large financial consequence for a missed day, delay, or some definition of nonperformance, especially when the amount appears significantly larger than the fee for the work.
If I am receiving a day rate to teach an analytics workshop, and the contract says I could owe many times that amount if something goes wrong, I want to understand exactly what triggers that clause. Illness? Travel disruption? A flight cancellation? A software outage? A client-side technical issue? A family emergency? A weather event?
Those details matter.
Here is the kind of mental checklist I use:
| Clause type | Business question I would ask |
|---|---|
| Late delivery penalty | Is the penalty proportionate to the fee and actual risk? |
| Missed session penalty | Are illness, emergencies, or travel disruptions addressed? |
| Client cancellation | Am I compensated if they cancel after I reserve the date? |
| Consultant cancellation | Is the consequence clearly defined and realistic? |
| Undefined damages | What exactly could I be responsible for? |
And when cancellations, delays, and logistics start to go sideways, travel is often part of the story. So let’s turn to that next.
Travel and expenses
For in-person work, travel is one of those places where the math and the logistics can quietly turn against you.
To be fair, I have never had a client expect me to pay my own way entirely. But I have seen travel policies get vague or rigid in ways that make the work harder than it needs to be.
Flights are one example. I understand not flying first class to teach Excel. But requiring the lowest-cost itinerary without regard to schedule, reliability, connections, or existing airline status can be shortsighted. Airline status is not just a perk. When something goes wrong, it can mean better rebooking options, fewer fees, and a much higher chance of actually getting to the client on time.
Hotels are another. Yes, hotels are expensive. But if someone is teaching all day, managing the room, answering questions, and staying sharp from start to finish, it is reasonable to stay somewhere safe, reliable, and close enough to the client site that the day starts smoothly. That is not luxury travel; it is basic risk management.
The same goes for meals, ground transportation, baggage fees, change fees, and per diems. If travel is prepaid, reimbursed, capped, or folded into the fee, the agreement should say so clearly.
None of this is glamorous, but neither is showing up exhausted, underfed, or stranded because the contract treated travel like an afterthought.
Intellectual property
This one matters a lot for trainers, because so much of the value we bring into a project is not just what we say in the room, but what we have already built.
I am talking about the slides, Excel files, Power Query examples, Python notebooks, datasets, handouts, templates, recordings, exercises, and any derivative content that comes out of the engagement. If your business is built on reusable teaching assets, ownership is not a minor detail buried in the back of the contract. It directly affects what you are still allowed to use after the project is over.
There is a big difference between licensing a client to use your materials for a specific workshop and signing those materials over outright. There is also a big difference between custom materials created specifically for one client and pre-existing materials you brought into the engagement because they are part of your broader teaching practice.
That is why I pay close attention to language around pre-existing materials, custom work, internal distribution, recordings, reuse rights, and derivative works. Training content has a long shelf life. A dataset built for one Excel class may eventually become part of a webinar, course, article, or book. A teaching example may evolve over years. A handout may become a reusable client resource.
If I give away more rights than I realize, I may be limiting my ability to use my own work later. For a trainer, that is not a small thing.
Non-compete and non-solicit language
By definition, contractors usually work with more than one client. You are not an employee with a guaranteed salary, benefits, and a full pipeline of work handed to you. You are expected to find work, maintain relationships, and keep your calendar full enough to pay your bills.
So when a contract starts limiting who you can work with later, the details matter a lot.
Can I work with similar clients after this project? Can I teach the same topic elsewhere? Can I work in the same industry, with the same type of department, or through another training provider? Can I accept future work from someone I meet during the engagement?
I understand nonsolicitation language in many cases. If a training provider introduces me to one of their clients, it is reasonable for them to say, “Please do not go around us and solicit this relationship directly.” That is part of being a good partner.
A broad noncompete is different. If a clause seems to say I cannot work with similar companies, similar industries, similar departments, or similar training topics for a long period of time, that can quietly fence off large parts of my market. For one project, that is a significant business issue.
This is especially important in analytics training because the market is not infinite. Many potential clients fall into the same broad categories: finance, banking, healthcare, manufacturing, higher education, professional services, and technology.
I am not trying to take someone else’s client list. But I also cannot sign away my ability to keep working in my own field. That is why I read these clauses closely enough to understand exactly what doors they are closing.
Indemnification
Indemnification is one of those words that makes people’s eyes glaze over.
Mine too, frankly.
But I do not skip it anymore.
In plain terms, indemnification is usually about who covers losses, claims, damages, or legal costs if certain things go wrong. That may be reasonable in some contexts. The question is whether the obligation matches the role.
Teaching a Python class is not the same level of risk as certifying financial statements, managing production systems, or providing regulated professional advice. If I am delivering an Excel workshop, I want the contract to reflect the actual nature of that work.
I pause when the language seems to make me responsible for broad business losses, third-party claims, client data issues, platform problems, or anything else far beyond my actual role.
Again, I am not trying to decide the legal meaning on my own. I am trying to recognize when the business risk looks bigger than the business opportunity.
Insurance requirements
Some contracts require consultants to carry insurance, and that is not automatically unreasonable.
A larger organization may have standard vendor requirements around general liability, professional liability, errors and omissions, cyber insurance, workers’ compensation, or other forms of coverage. In many cases, that is simply part of doing business with bigger clients.
The important thing is to read those requirements before you sign. If a contract requires coverage you do not currently carry, that can change the economics of the engagement. It may cost money to obtain, take time to set up, or require certificates, broker conversations, and policy adjustments before the client will let the project move forward.
That is not something you want to discover the week before delivery. Agreeing to carry insurance you do not actually have is one of those problems you create for your future self, usually with a deadline attached.
Who you are signing as
Last one, and it is easy to overlook: make sure you know who is actually signing the agreement.
Are you signing as yourself, as your LLC, or somehow as both? Is the contract addressed to your personal name, your company name, or some confusing combination of the two?
I am not giving legal or accounting advice here, and the specifics are worth discussing with an attorney or accountant. But as a business owner, I want the contract to match the actual business relationship.
If the agreement is with my company, I want the contract and signature block to reflect that clearly. If a counterparty makes the contract out to me personally without asking whether I operate through an LLC, that is not necessarily a red flag by itself, but it is a signal to clarify the relationship before signing.
Before I sign, I want the agreement to make clear who is providing the service, who is getting paid, who is responsible for what, and who is legally bound by the page in front of me.
The mindset, not the verdict
The thread running through all of this is not that every uncomfortable clause is automatically illegal, unenforceable, ridiculous, or fine. That is not really my call to make, and it is usually not the most useful way to read a contract anyway.
What has helped me more is treating the contract as a business document and sorting the terms into practical categories.
| Bucket | What it means |
|---|---|
| Looks fine | The term matches the work and does not raise obvious concerns |
| Needs clarification | The term may be fine, but I need the details in writing |
| Needs negotiation | The business risk feels too high for the fee or scope |
| Needs legal review | The term is broad, unclear, or potentially serious enough to get help |
| Price it in | The risk may be acceptable, but only if the fee reflects it |
That shift has helped me a lot. Instead of staring at a wall of legal language and trying to decide whether the whole thing is good or bad, I can ask a more useful question: what do I need to clarify, negotiate, review, or price in before I agree to this?
Contracts are part of the job
It took me a few engagements to learn that reading a contract this way is part of the job, not a distraction from it. Knowing the material cold may be what gets you hired, but understanding delivery risk, client expectations, payment terms, cancellation language, intellectual property, and business boundaries is what helps keep the work sustainable once you are.
That does not mean every contract needs to become a confrontation. Many clients are reasonable, and many awkward clauses are there because someone reused a template without thinking very much about how it applies to a one-day analytics workshop. But that is exactly why reading matters. Sometimes the right move is to sign. Sometimes it is to ask for clarification. Sometimes it is to negotiate. And sometimes the best business decision is to walk away.
The goal is not to become your own lawyer. The goal is to know when to pause, ask better questions, and protect the value of your own work.
Most of my work at Stringfest Analytics is about helping teams build stronger skills in Excel, Power Query, Python, Copilot, and modern analytics workflows. But the longer I do this work, the more convinced I become that technical skill and business maturity have to grow together. The spreadsheet matters. The training design matters. The client experience matters. And yes, the terms matter too.
If your organization needs practical analytics training, or if you are an independent data professional trying to make your own training work more sustainable, I would be glad to connect.