The Email That Started It All
The email from Mark, my CEO, landed in my inbox at 4:57pm on a Tuesday. Subject line: URGENT: Wedding Officiant Contract. My heart sank. I’m the HR manager for a 40-person company in Atlanta. My job is benefits, payroll, making sure we don’t get sued. Not interpreting weird contracts for people who perform marriages.
Mark’s email was short. “Priya, we have a situation. One of our contractors—a wedding officiant—is asking about a clause in her agreement. She’s concerned it’s a non-compete. I told her you’d ‘figure it out.’ Please handle. Compliance deadline is Friday.”
Friday. That was three days away. I stared at my screen. I had no idea what a non-compete even looked like in a wedding officiant contract. I thought those were for executives, not someone who works weekends performing ceremonies. Okay so, I told myself, just read the thing. How bad could it be?
My First Mistake: Thinking It Was Simple
I downloaded the PDF. It was titled “Independent Contractor Agreement for Ceremony Services.” Six pages. I skimmed. Page one: names, dates, standard stuff. Page two: scope of work. “Contractor agrees to provide officiant services for events as scheduled by Client.” Fine. Page three: payment terms. “Contractor is paid $200 per ceremony, due within 30 days.” Reasonable.
I got to page four and my eyes started to glaze. Arbitration clause. Confidentiality. Intellectual property. Blah blah. I thought, This is just boilerplate. Everyone uses the same template. I felt a wave of relief. Maybe this was easy. I could just tell the officiant, “Yeah, it’s standard, sign it.” I even started typing the email.
Then I saw it. Or rather, I almost didn’t see it. Tucked at the bottom of page five, under “Miscellaneous Provisions,” was a paragraph that started: “Non-Competition and Non-Solicitation.”
My blood ran cold. Non-competition. For a wedding officiant.
I read it three times. “Contractor shall not, for a period of two (2) years following termination of this Agreement, perform marriage ceremonies for any Client or within a fifty (50) mile radius of any venue where Contractor performed services under this Agreement.”
Fifty miles. Two years.
I pushed my chair back so hard it hit the filing cabinet. My cat, Mr. Whiskers, looked at me like I’d lost my mind. I texted my sister, who’s a paralegal. A photo of the paragraph. Her reply came back in 30 seconds: “That looks bad. That’s a non-compete. For a contractor? That’s usually not enforceable, but it’s still a huge red flag.”
Not enforceable? I had no idea what that meant. Was I about to tell someone to sign something that might be illegal? Or was it legal but just really unfair? My head spun.
The 2am Google Rabbit Hole
That was Tuesday night. By 11:30pm, I was still at it. The kitchen table was a war zone of printouts, empty coffee mugs, and my laptop humming like a angry bee. I’d typed every combination into Google I could think of: “wedding officiant non-compete,” “independent contractor agreement non-solicitation,” “are non-competes enforceable for gig workers.” The results were a mess. Law firm blogs with terrifying headlines. Forum posts from officiants who said they’d signed similar things and now couldn’t work. A few state-by-state guides that might as well have been written in code.
I was drowning. I felt stupid. I’m an HR manager. I should know this. But my expertise is in FMLA and COBRA, not this. I was this close to just telling Mark, “I can’t figure it out, we need a lawyer.” But we’re a small company. Legal fees for a simple contract review would be a hit. And the CEO expected me to handle it.
I was about to give up and just rubber-stamp the thing—after all, the officiant was an independent contractor, not an employee, so maybe it was okay?—when I remembered something. A friend from my old networking group, Sarah, had mentioned an app. She’d said, “Priya, you deal with contracts all the time. You need Legal Shell AI. It’s like having a first-year associate who works for free.”
I’d dismissed it at the time. An app? For legal stuff? Seemed gimmicky.
But at 11:47pm on a Tuesday, with my brain leaking out my ears, I was desperate. I found it in the App Store. Legal Shell AI. Blue icon. 4.8 stars. I downloaded it.
What I Actually Learned About Non-Competes for Wedding Officiants
The app was surprisingly simple. You upload a document. It asks what you want to know. I typed: “Is this non-compete clause enforceable for an independent contractor wedding officiant?”
It took maybe 30 seconds. The analysis popped up. It didn’t just say “yes” or “no.” It broke it down in plain English.
First, it explained the basics. A non-compete is a promise not to work for competitors or in a certain area for a certain time. For employees, courts look at whether it’s reasonable in scope, geography, and time. For independent contractors, it’s even harder to enforce. The app said: “Courts are skeptical of non-competes in IC agreements because they restrict a person’s ability to earn a living. For enforceability, the company must have a legitimate business interest to protect, like trade secrets or confidential client lists.”
That was my first “aha.” This officiant wasn’t getting our trade secrets. She wasn’t even our employee. She worked for dozens of companies. What was our legitimate interest? That she wouldn’t perform ceremonies at the venues we sent her to? That seemed… ridiculous.
The app then highlighted the specific clause. It flagged two things
- The two-year duration. That’s a long time for someone in a service business where relationships are everything.
- The 50-mile radius. That could cover an entire metro area. For a wedding officiant, whose “clients” are literally the couples getting married—not our company—this seemed overbroad.
It added a note about Georgia law (where we are): “Georgia courts apply a ‘reasonableness’ test. Non-competes that prevent someone from working in their chosen field are often struck down. However, courts may ‘blue pencil’ them—modify them to be reasonable—rather than throw them out entirely.”
So even if it was unenforceable as written, it could be rewritten to something smaller and still stick. That was terrifying. The officiant might sign it thinking it’s nonsense, but if she ever left and worked within 50 miles for two years, we could try to sue. The threat alone could scare her into compliance.
I felt sick. I had almost told her to sign it.
The Clause That Almost Got Me
I went back to the contract. I looked at the non-compete paragraph again. It was seven dense sentences. Buried in the middle was this gem: “Contractor acknowledges that the services provided hereunder are unique and that any breach of this covenant would cause irreparable harm to the Company, for which monetary damages would be an inadequate remedy.”
Translation: if she breaks this, we can go to court and get an order stopping her from working. Not just sue for money—stop her from working.
For a wedding officiant. Who needs to work to eat.
I imagined this woman. Let’s call her Maya. She’s probably in her 40s, does this on the side, loves love, has a little business card. She gets this contract, sees “independent contractor,” thinks it’s standard. She highlights the pay section, maybe asks about the arbitration clause (smart), but her eyes glaze over at the legalese. She signs. Six months later, she gets a better offer from a different agency that sends her to a venue she’d worked at for us. We send a cease-and-desist letter citing this clause. She panics. She turns down the job. She loses income.
Because of a clause I almost rubber-stamped.
My hands were shaking. I thought about my own career. If someone tried to stop me from working in HR in Atlanta for two years because I’d once contracted for them? I’d laugh. But Maya might not laugh. She might just be scared.
What I Did Next
First, I did not email Mark back with “It’s fine.” Instead, I called the officiant. Her name was Maya, as I’d guessed. She answered on the second ring.
“Hi Maya, this is Priya from [Our Company]. I’m reviewing your contract.”
“Oh, thank goodness,” she said. “That non-compete thing—it feels weird. I’m a minister. I perform ceremonies at gardens, barns, hotels. I can’t promise not to work within 50 miles. That’s my whole life.”
“I know,” I said. “I think we can fix it.”
I explained what I’d learned. She listened. She said, “I already have a relationship with the Peachtree Gardens venue. If I sign this, can I still do a wedding there if they call me directly?”
That was the key. The clause as written didn’t distinguish between clients we sent her to and ones she had her own relationships with. It was a blanket ban. That’s what made it so dangerous.
I told her I’d rewrite it. I drafted a new section
“Contractor agrees not to solicit or accept officiant services directly from any Client introduced by Company for a period of twelve (12) months following termination of this Agreement. This does not restrict Contractor from performing services at any venue or for any couple where no such introduction by Company occurred.”
Twelve months instead of two years. Venue-specific and client-specific, not a geographic radius. I ran the revised clause through Legal Shell AI again. It said: “This is much more tailored. Likely enforceable as a reasonable restriction to protect Company’s investment in client relationships. Still consider adding a definition of ‘Client’ to avoid ambiguity.”
I added a definition: “‘Client’ means the couple or entity that contracted with Company for officiant services and for whom Contractor provided services under this Agreement.”
I sent the revised agreement to Maya. She replied an hour later: “This works. Thank you for catching that. I was this close to signing the original and worrying for years.”
I forwarded the email chain to Mark with a note: “Here’s the revised agreement. Original non-compete was overbroad and likely unenforceable but created risk. New clause is reasonable and protects our actual interest—the clients we bring her.”
He replied: “Good work. Thanks for digging in.”
That was it. No fanfare. Just a problem solved.
Questions I Had (And What I Found Out)
What exactly is a non-compete in an independent contractor agreement, and how is it different from an employee non-compete?
Okay so, for employees, a non-compete stops them from working for a competitor or starting a competing business for a certain time and area. For independent contractors, it’s supposed to protect the company’s specific investments—like if the company trained the contractor on its secret processes or gave them access to a confidential client list. But for a wedding officiant? There are no secret processes. The “client list” is just the couples we book. The contractor isn’t stealing our customer list—they’re just performing a service. A broad non-compete for an IC often looks like the company is trying to treat them like an employee without the benefits, which courts don’t love.
How do I know if a non-compete clause is reasonable or enforceable?
The magic words are reasonable in time, geography, and scope. Two years is long. Fifty miles is huge for a local service. And “scope” matters: does it stop her from working anywhere for anyone, or just from poaching our clients? The original clause stopped her from performing ceremonies at all within 50 miles, even for couples who found her on their own. That’s way too broad. A reasonable clause would be: “Don’t solicit our clients for 12 months.” That’s it. It doesn’t stop her from working—it just protects the relationships we built. I also learned to ask: what’s the legitimate business interest? If you can’t name one (trade secrets, specialized training, customer relationships), the non-compete is probably just a power play.
What should I do if I find a non-compete in a contract I’m about to sign (either as a contractor or as a company hiring one)?
If you’re the company: Ask yourself why you need it. Are you really protecting something valuable? If yes, make it narrow. Time: 6-12 months, not 2 years. Geography: specific, not a radius that covers the whole state. Scope: specific clients or prospects, not the entire industry. And only use it with true ICs who have access to real confidential info—not every gig worker.
If you’re the contractor: Do not sign it without questioning. Ask: “What is this protecting?” If they say “our business,” that’s not enough. Ask for it to be removed or narrowed. In Maya’s case, she was right to be uncomfortable. She could have signed and later been threatened. If the company refuses to budge, that’s a huge red flag about how they treat people.
Are non-competes for wedding officiants (or other gig economy workers) even a thing? Why would a company include one?
Yes, they’re a thing. I saw them in templates. Why? I think it’s lazy drafting. Someone took an employee non-compete template and didn’t tweak it for the role. Or, worse, the company wants to lock the contractor into an exclusive relationship without formally hiring them—they get the control of an employee without the costs. For a wedding officiant, it’s especially silly because their value is in their personal relationships and reputation. A non-compete doesn’t stop a couple from booking them directly after seeing them at a wedding. It only creates fear and paperwork. It’s a power move, plain and simple.
I Still Check Every Contract Now
It’s been a month. Maya’s first ceremony under the new agreement was last Saturday. She sent me a photo—her in a blue dress, smiling under an arch of peonies. She looked happy. Free.
I still have that original contract saved in a folder called “Actually Read These.” I open it sometimes. I look at that buried paragraph. I think about how close I was. How easy it would have been to just click “approve” and move on. My CEO said “figure it out,” and I almost didn’t.
Maybe I’m paranoid now. I run vendor agreements through Legal Shell AI. I read the indemnification clauses twice. I ask “what’s the legitimate interest?” in my head. It’s extra work. It’s not in my job description.
But at least I’m paranoid and informed. And I know what a non-compete looks like in a wedding officiant contract. If you’re in a similar spot, I hope this helps. It’s not as scary as it looks. Well, some of it is. But you can figure it out. Even at 11:30pm on a Tuesday.
P.S. Legal Shell AI is on my phone now. It’s not magic, but it’s a flashlight in a dark room. I’d say just run your contract through it before you sign anything. 📱 Download Legal Shell AI