1099 vs W-2: Why Your Child Needs Commissioned Projects, Not an Allowance With Extra Steps

Here's the scenario the IRS sees every filing season: a parent pays their child $12,000 for "consulting services," issues a 1099-NEC, and deducts the full amount. No project scope. No deliverables. No evidence the child did anything beyond existing in the same household.

That's not an independent contractor relationship. That's an allowance with a tax form stapled to it. And the IRS knows the difference.

The Core Problem: What Makes a 1099 Legitimate?

The IRS uses a multi-factor test to determine whether someone is an independent contractor (1099-NEC) or an employee (W-2). The three primary categories are:

1. Behavioral control: Does the business direct what work is done and how it's done? Contractors receive project specifications but control their own methods. Employees are told exactly how to perform tasks.
2. Financial control: Does the worker have unreimbursed expenses, opportunity for profit or loss, and freedom to seek other clients? Contractors invoice for completed work. Employees receive regular paychecks regardless of output.
3. Relationship type: Is there a written contract? Are there specific deliverables? Is the relationship project-based or ongoing and indefinite?

For your child to legitimately receive 1099 income, the arrangement needs to look like a real client-contractor relationship -- not a parent handing cash to their kid for vague "help."

Why "Directed Work" Is Non-Negotiable

This is where most parent-child arrangements fail the smell test. The IRS expects to see:

The keyword is commissioned. The parent (as client) commissions specific work. The child (as contractor) proposes an approach, executes the work, delivers results, and invoices for time spent. That's a contractor relationship. Everything else is a gift the IRS will reclassify -- plus penalties.

The Project Brief: Your First Line of Defense

Every legitimate contractor engagement starts with a project brief. For your child, this doesn't need to be a 40-page SOW. It needs to answer four questions:

1. What is being built or produced?
2. Why does the business need it?
3. What does "done" look like? (acceptance criteria)
4. What's the budget? (estimated hours and rate)

Example: "Build a responsive landing page for [Business Name] that includes a hero section, services overview, contact form, and mobile-optimized layout. Estimated 8-12 hours at $22/hr. Deliverable: deployed site on Vercel with source code in GitHub."

That's a real project brief. It could be sent to any freelancer on Upwork. The fact that the freelancer happens to be your child is irrelevant -- the structure is identical.

The Proposal: Proof Your Child Isn't Just Following Orders

Here's the nuance that trips up even well-intentioned parents. If you dictate every detail of how the work gets done, the IRS can argue this is an employment relationship, not a contractor one. Contractors are defined by their autonomy over methods.

The fix is simple: have your child write a brief proposal in response to the project brief. The proposal says: "Here's how I plan to approach this, here's my estimated timeline, and here's what I'll deliver." The parent reviews and approves. Now you have documentation showing:

• The parent defined what (project brief) -- this is normal client behavior
• The child defined how (proposal) -- this is contractor autonomy
• Both parties agreed on scope and rate before work began

This brief → proposal → approval flow is exactly how freelance platforms like Upwork, Toptal, and Fiverr work. It's the standard contractor engagement pattern.

During the Project: Time Logs Are Everything

Once work begins, your child needs to log time with task-level descriptions. Not "worked on project -- 3 hours." Real entries:

Each entry is specific, time-stamped, and tied to a named project. If the IRS asks "what did your child do on April 8th?" you have an answer -- plus the deployed website as proof.

Deliverables: The Work Product That Proves Everything

When the project is complete, the child submits deliverables. For development work, this is typically:

• A link to the deployed application or website
• A GitHub repository with commit history (showing actual development work)
• Screenshots or recordings of the final product
• A brief summary of what was built and any decisions made

The parent reviews the deliverables, accepts the work (or requests revisions -- just like a real client), and the child invoices for the hours worked. This close-out process creates the final piece of the documentation chain: the project started with a brief, progressed through logged hours, resulted in tangible deliverables, and ended with an invoice and payment.

What Happens Without This Structure?

If the IRS audits a 1099 arrangement between parent and child and finds no project briefs, no proposals, no time logs, and no deliverables, here's what happens:

1. Reclassification: The payments are reclassified as gifts, not earned income
2. Lost deduction: The business loses the deduction for the child's compensation
3. Roth IRA problem: If the child contributed to a Roth IRA based on "earned income" that's now reclassified, those contributions become excess contributions subject to a 6% penalty per year until corrected
4. Back taxes + penalties: Underpayment penalties of 20-75% plus interest
5. Future scrutiny: The arrangement is flagged for future years

The irony is that the underlying strategy is completely legal. The IRS wants kids to earn income. They just want the income to be real.

How KidsBuild Solves This

We built the entire KidsBuild platform around this problem. Every feature maps directly to an IRS compliance requirement:

The Project Board: Where Compliance Starts

The Project Board is the centerpiece of this system. Parents (and eventually other businesses on the platform) post project bounties. Each bounty includes:

• Title and description: What needs to be built
• Category: Development, design, research, content, or other
• Difficulty: Beginner, intermediate, or advanced
• Estimated hours and budget: Sets expectations upfront
• Tags: Technologies or skills involved

Children browse available projects, pick ones that match their skills, and submit proposals. The parent reviews proposals, approves the best one, and work begins. When complete, the child submits deliverables, the parent accepts, and an invoice is generated. Every step is timestamped and stored.

This isn't busywork paperwork -- it's the same workflow used by every freelance marketplace in the world. We just made it simple enough for a 14-year-old to use.

Beyond Your Own Family: The Community Marketplace

Here's where it gets powerful. The Project Board isn't limited to your own family. As the KidsBuild community grows, other parents and small businesses can post projects too. Your child can:

• Build a landing page for another family's side business
• Design a logo for a community member's nonprofit
• Create a portfolio site for another parent's professional practice
• Build internal tools for KidsBuild itself (we eat our own cooking)

Multiple clients strengthen the contractor classification. The IRS is more likely to challenge a 1099 arrangement where the child has exactly one "client" (their parent). When a child has completed projects for three or four different clients through the platform, the independent contractor relationship is far stronger.

What About the W-2 Route?

Some families are better served by the W-2 employee model (see our DIY Guide). The key differences:

The 1099 route has one major drawback: the 15.3% self-employment tax (Social Security + Medicare) that doesn't apply to W-2 children of sole proprietors. But it has significant advantages in simplicity, flexibility, and the ability to work with multiple clients. For many families -- especially those whose business is an S-Corp or C-Corp (where the FICA exemption doesn't apply anyway) -- the 1099 route is the better path.

The Documentation Checklist

Whether you use KidsBuild or manage this yourself, here's the minimum documentation you need for every project:

1. Written project brief (scope, deliverables, budget)
2. Child's proposal (approach, estimated hours, rate)
3. Parent approval (date-stamped)
4. Time logs with task descriptions (for every work session)
5. Deliverable submission (links, screenshots, evidence of completion)
6. Parent acceptance or revision request (date-stamped)
7. Invoice from child to parent (itemized hours and rate)
8. Payment record (bank transfer, check, or ACH receipt)

On KidsBuild, steps 1-8 happen automatically as part of the normal workflow. The platform generates every document. You just use it.