Talent / Model Booking OS
And lists the talent whose payouts crossed $600.
One pass over your bookings export flags every double booking, splits agency commission from talent payout on all of them.
And lists the talent whose payouts crossed $600.
$75/mo per agency. Every booker, every name on the roster, no per-seat charge. Cancel any day and keep your data.
Why do two bookers keep landing on the same Saturday?
Saturday is the problem. Two bookers, both looking at the same shared calendar, both certain that 10am to 2pm is open. One books an editorial. The other books a lookbook. Nobody finds out until the client calls on Friday night asking why their model is standing in someone else’s studio.
Then there’s the arithmetic. Every booking has a rate, every talent has a commission percentage, and somebody re-adds all of it by hand at month end. Miss one and you either short a model or short yourself. And in January you find out you never collected a TIN from the talent who did eleven jobs last year, which is a phone call nobody enjoys making.
How does it find the conflict?
Three steps, and the first one is the only one that takes any thought.
- Export your bookings to CSV and export your roster. The bookings file carries
booking_id,talent,client,date,start,end,rate,status. The roster carriestalent,commission_pct,tin_last4. Different headers on your export? Name yours in the.envand it reads them. - Run it. Every booking gets checked against every other booking for the same talent, and any pair whose date and time ranges overlap gets flagged.
- Open the output folder.
BOOKING_CALENDAR.mdhas the conflicts in date order,COMMISSIONS.mdhas the splits,TAX_READINESS.mdhas the 1099 list.
What one run gives you
Four files, and every one of them answers a question somebody in the office was going to ask anyway.
- Flags every overlapping booking for the same talent using half-open time ranges, so a 12pm finish and a 12pm start are not thrown at you as a conflict you then have to check by hand and dismiss.
- Splits each booking with the roster’s
commission_pct. Rate times the percentage is the agency’s, the remainder is the talent’s payout. The math stops living in one bookkeeper’s head. - Totals every talent’s payout against a
THRESHOLDof $600 and hands you the 1099 list inTAX_READINESS.mdbefore January hands it to you. - Flags anyone on that list whose roster row has no
tin_last4. That is the W-9 you chase now instead of in the last week of January. - Books a talent who isn’t on the roster at 0% commission and still counts them in the totals, so a new face never quietly vanishes from the numbers.
- Drops
bookings.jsonnext to the reports, so whoever does your books can pull the figures straight in. - Touches no payment rail at all. It computes and it reports. A typo in a CSV cannot move money out of the agency.
- Runs
--validateif you want to check your column names without reading or writing a single file. Useful the day after your booking platform changes an export header.
Is your agency the right size for this?
Built for an agency with a real roster and more than one person allowed to book it. Call it 20 to 200 names and two to six bookers. If you’re a solo model running your own calendar, you don’t have a double-booking problem, you have a phone, and this is overkill. A large agency with a booking platform and an ops team already reconciling commission won’t find anything here they don’t have. And if what you want is a tool that sends the invoice and moves the money, it won’t.
Do you have to drop the shared calendar?
No, and you shouldn’t. Google Calendar is better than this at everything live: a booker sees the week on her phone, a model gets a notification, a change shows up the second it’s made. Keep it. A spreadsheet is better at anything one-off, like a rate you negotiated once for a client who won’t come back. Neither one will read every booking against every other booking for the same talent and tell you the two that collide, then do the commission arithmetic on all of it, then tell you who crossed $600. That’s the run.
Where do the roster and the TINs live?
On your disk, and nowhere else. Both CSVs are read from the machine and never leave it. The roster carries tin_last4, which is the only fragment of a talent’s tax ID this thing ever sees, and it is never transmitted anywhere. Reports are written under OUTPUT_FOLDER, only under it, at 0600 permissions, so another account on the same machine can’t open them. No payment rail is touched. Your export path is the folder itself, because the reports are already sitting in it.
What does $75 a month get you?
The agency, not a seat. Not per booker, not per model. You get the tool, the config file, and the four reports it writes on every run. Setup is copying .env.example to .env and putting two file paths in it. Run --validate first if you want to confirm the column names before it reads anything. The first conflict report lands the same afternoon you pull your bookings export. Cancel any day. The reports were always yours.
Security and privacy
Handles agency booking data (bookings, rates, talent commission terms, partial TINs). Security is designed in.
Principles
– Local-first. BOOKINGS_CSV/TALENT_CSV are read from disk and never transmitted anywhere; nothing in this tool touches the network. Nothing is uploaded, no telemetry, no cloud dependency.
– No payments executed. This tool only computes commission splits, payout totals, and 1099 readiness for review — it never initiates a transfer, payment, or filing.
– Non-destructive. Source CSVs are only read, never modified or deleted.
– Least privilege. Reads BOOKINGS_CSV/TALENT_CSV, writes only under OUTPUT_FOLDER.
Protections implemented (v0.1.0)
– Path-traversal defense — every output filename is sanitized (safeSegment) and every write is checked with assertWithinRoot(), so reports can’t be written outside OUTPUT_FOLDER.
– Fail-fast config validation — clear errors for missing/invalid BOOKINGS_CSV/TALENT_CSV/OUTPUT_FOLDER/THRESHOLD before any file is touched; --validate checks configuration without reading or writing anything.
– Restrictive permissions — the generated reports (BOOKING_CALENDAR.md, COMMISSIONS.md, TAX_READINESS.md, bookings.json) are written 0600.
– Defensive parsing — the CSV parser never throws on malformed input (missing fields default to empty string, unparseable rates default to 0); a bad row degrades the run rather than crashing it.
– Minimal TIN handling — only the last 4 digits of a TIN (tin_last4) are ever read or written; the tool never collects or stores a full SSN/EIN.
– Secrets discipline — .env and generated Reports/ output are git-ignored; no secrets or client data in the repo.
Distribution / AV trust
Known limitations / roadmap
– Conflict detection is exact date+time overlap only in v0.1.0 — it does not account for travel/setup buffer time between bookings at different clients; reviewers should sanity-check back-to-back bookings across venues.
– THRESHOLD is a flat $ amount checked against total payout across the bookings in a single run — if an agency runs this tool per-month, YTD totals must be aggregated by the operator across runs (or by feeding a full-year BOOKINGS_CSV).
– 1099 readiness is a heuristic (payout ≥ threshold + TIN on file), not a filing — always have a bookkeeper/CPA confirm before submitting to the IRS.
– Talent not present in TALENT_CSV default to a 0% commission (100% payout) and no TIN, which will surface as a missing-TIN flag once they clear the threshold; keep the roster current.
Reporting
Report suspected vulnerabilities privately to the maintainer before public disclosure.
Frequently asked questions about Talent / Model Booking OS
What is talent software and how does the Talent / Model Booking OS work?
Talent software is the system a model or talent agency uses to run bookings, contracts, and payments from one place instead of a pile of spreadsheets and one-off documents. The Talent / Model Booking OS is built for that exact job. It keeps every booking, contract, and commission split on one shared calendar, so the agent, the talent, and the booking client all read from the same numbers. When you add talent, clients, and bookings, that calendar becomes the single record of who is booked, for what, and at what rate, and nothing important lives in a separate file that someone forgot to update.
From that booking data the tool generates signed contracts and routes them for e-signature, then produces the tax documents an agency needs when a job closes out. This matters because agency talent are almost always independent contractors rather than employees. The rules for filing and paying self-employment tax that apply to those workers are laid out by the IRS, and dependable talent software keeps the booking and payment records a preparer needs close at hand. You can review the underlying obligations at the IRS self-employed individuals tax center.
Commission math is where many agencies lose both time and trust. The booking OS calculates commission splits automatically at close-out, so the agent percentage and the talent payout come from the same booking record instead of being typed twice into a spreadsheet where the two copies drift apart. When a booking rate changes, the split, the contract, and the generated tax document all point back to the same figure. That single source of truth is the whole idea.
Here is the blunt version. If your agency already runs cleanly on spreadsheets and never argues about who owes whom, you may not need this. Most agencies are not in that position. Once you are juggling dozens of bookings a month across several talent, the manual copying is where errors and disputes creep in, and this kind of software exists to remove that copying. You can see how the pieces fit for agencies on the Talent / Model Booking OS product page.
Setup follows the same order every time. You add your talent roster, your booking clients, and each confirmed booking to the shared calendar. You generate the contract and send it for signature. At close-out the tool runs the commission split and assembles the tax document from the booking record, so the numbers on the payout match the numbers on the paperwork. Compared with generic agency tools or a stack of spreadsheets, the difference is that the booking, the signature, the split, and the tax paperwork are one connected record rather than four disconnected ones. Agencies that book models, performers, and other creators treat the calendar as the source everything else is generated from, which is what keeps agents and talent looking at matching numbers instead of reconciling two versions after the fact. Priced per agency rather than per seat, the tool is aimed at the owner who is tired of that reconciliation and wants bookings, e-signature, and commission math handled in one system built for talent agencies specifically. The calendar is not a nice-to-have. It is the record every contract, split, and tax document is built from, and that is what a loose stack of spreadsheets can never quite become.
How does talent software help talent handle FTC endorsement disclosure on brand deals?
A large share of modern bookings are brand deals where the talent posts sponsored content, and that triggers a real disclosure duty. When a creator has a material connection to a brand, meaning payment, free product, or any business relationship, the FTC says the audience has to be told clearly. The agency that arranged the deal is the party keeping the paperwork, which is why talent software should record the disclosure terms alongside the booking rather than leaving them to memory. The FTC spells out what counts and how obvious the disclosure has to be in its guide, Disclosures 101 for Social Media Influencers.
The Talent / Model Booking OS does not post to social media for anyone, and it will not police whether a given caption carried the right tag. What it does is keep the deal terms, the signed contract, and the deliverables on one booking record, so the disclosure requirement written into a brand agreement is stored where the agent and the talent can both see it. When a client later asks whether a post was properly disclosed, the contract that set the expectation is attached to the booking instead of buried in an email thread nobody can find.
That recordkeeping matters because disclosure disputes tend to surface long after the campaign ran. If the brand claims the label was missing and the talent says it was agreed differently, the booking record is the document that settles it. Good talent software turns that from a he-said argument into a quick lookup. The contract stored at signing shows exactly what the two sides agreed about disclosure, usage, and timing, and it was routed for e-signature so both parties saw the same terms.
There is an honest limit worth stating plainly. Compliance with the FTC guidance is the talent’s and the brand’s responsibility, not the software’s. The tool cannot make a disclosure clear and conspicuous on a platform it never touches. What it can do is make sure the obligation was captured in writing, signed, and preserved with the rest of the booking, so nobody later pretends the term did not exist.
For an agency running many brand bookings at once, that single connected record is the practical value. Each sponsored booking carries its own contract, its own disclosure language, and its own deliverable list, all generated from the same calendar entry rather than reassembled by hand. You can see how the booking, contract, and record-keeping pieces fit together for this market on the creators and agencies industry page. The point is not that the tool disclaims anything on your behalf. The point is that when terms are set at booking and stored with the signed contract, the whole team works from one version of what was promised, and the FTC guidance stops being a vague worry and becomes a checklist item attached to each deal your agency books. In practice that means fewer surprises. The agent knows the disclosure term was signed, the talent knows what was expected of them, and the brand has a signed agreement it can point to, all pulled from the same booking record instead of three separate inboxes.
Is my talent and client data safe, and where does it live?
Booking systems hold sensitive information. To generate contracts and tax documents, talent software has to store names, contact details, booking rates, and often taxpayer identifiers for the talent it pays. That is real personal information, and it deserves the same care a small agency would give any file cabinet full of contracts. The FTC’s plain-language guide, Protecting Personal Information: A Guide for Business, frames the job as five steps, take stock, scale down, lock it, pitch it, and plan ahead, and those steps map cleanly onto how an agency should treat booking records.
Take stock means knowing what you actually hold. The Talent / Model Booking OS keeps talent, client, booking, contract, and payout data in one place, so you can answer that question instead of guessing which spreadsheet on which laptop has a talent SSN in it. Scale down means not keeping data you do not need. Because the booking record is the single source, you are not scattering copies of a taxpayer identifier across a dozen files that each become a separate risk.
Lock it and plan ahead are about access and what happens if something goes wrong. The tool keeps the booking, the signed contract, and the tax document together with a record of what was generated and when, so there is an audit trail of the agency’s own activity. If a client or a talent ever questions what was shared or signed, you have the record rather than a reconstruction from memory. That is the honest promise here. The software is not a security product and will not claim to be one. It keeps your booking data organized and accounted for, which is the groundwork the FTC guide describes.
Where the data lives depends on how you run the agency, but the principle stays the same across the workflow. One booking record, one contract, one payout calculation, all tied together, so you are not emailing a talent’s tax details around as loose attachments. Reducing the number of loose copies is one of the most practical things any small agency can do, and good talent software is built so the sensitive fields sit inside the booking record rather than in your inbox.
None of this replaces your own judgment about who on your team should see what. It supports that judgment. When the personal information an agency handles is concentrated in one accounted-for system instead of spread across spreadsheets, screenshots, and message threads, the take-stock-and-lock-it advice the FTC lays out becomes something you can actually follow. Consolidation is not a cure-all, and no tool removes the need for sensible habits like limiting who can open the booking system. It does shrink the surface area, because there are simply fewer stray copies of sensitive fields floating around on laptops and in messages. For a small agency without a dedicated security team, fewer loose copies is the most realistic improvement available, and it is the one the FTC guide keeps returning to. You can read how the platform organizes bookings and the records tied to them on the Talent / Model Booking OS product page, and decide for yourself whether consolidating that data is safer than the scatter you have now.
How is this talent software different from running an agency on spreadsheets?
Spreadsheets and generic agency tools can hold a booking list, but they cannot connect the booking to the contract, the commission split, and the payment record in a way that stays consistent. That gap is exactly what talent software closes. In a spreadsheet, a rate change lives in one cell, and the contract, the payout, and the tax paperwork built from that rate are all somewhere else, waiting to be updated by hand. The Talent / Model Booking OS keeps them linked, so one change flows to the documents generated from it.
The payment side is where the disconnect gets expensive. Agencies and their talent often receive booking payments through cards or third-party payment networks, and those payments can show up on a Form 1099-K at year end. The IRS explains what that form reports in its overview, Understanding your Form 1099-K. When your bookings and payouts are one clean record, matching what a 1099-K reports against what you actually booked is a lookup, not a weekend of cross-referencing tabs. On a spreadsheet, that reconciliation is manual and easy to get wrong.
There is also the trust problem. When an agent keeps one spreadsheet and a talent keeps another, the two versions drift, and every close-out becomes a small negotiation about whose numbers are right. Because the booking OS calculates the commission split from the shared booking record, the agent and the talent see the same figure by construction. That does not just save time. It removes a recurring source of friction that spreadsheets quietly create.
The honest tradeoff is that a system asks you to put your bookings in properly, where a blank spreadsheet lets you scribble anything anywhere. That flexibility is exactly why spreadsheets fall apart at scale. Structure is the feature. Once a booking is entered, the contract, the e-signature routing, the split, and the tax document are generated from it, so you are not rebuilding the same facts four times. Reliable talent software trades a little up-front discipline for a lot less copying later.
This matters most for the agency running many bookings across several talent at once, which is who the tool is built for. A single busy month can mean dozens of bookings, each needing a contract, a signature, a split, and eventually a tax document. Doing that by hand is where things slip, where a contract goes unsigned, or where a payout is calculated on last month’s rate. Consolidating the workflow is the point of moving off spreadsheets in the first place. You can compare the approach against how your agency works today on the creators and agencies industry page and see whether one connected record beats four disconnected ones for the volume you actually run. There is also the year-end scramble to consider. When bookings and payouts are scattered across tabs, tax season means rebuilding the whole picture under time pressure. When they already sit in one record, the numbers a preparer needs are simply there. That shift, from reconstructing the year to reading it, is the clearest reason agencies outgrow spreadsheets and move to purpose-built talent software.
Can the booking OS store usage and copyright terms in talent contracts?
Model and talent work produces content, and content carries rights. A photo shoot, a performance, or a video session creates original work, and under United States law copyright attaches automatically the moment that work is fixed in a tangible form. The U.S. Copyright Office explains this in its overview, What is Copyright. For an agency, the practical question is not who owns the copyright in the abstract but what the booking contract actually says about how the client may use the talent’s image or performance, and for how long. That is where talent software earns its place.
The Talent / Model Booking OS generates signed contracts straight from booking data, and those contracts are where usage terms live. When a brand books a model for a campaign, the agreement can spell out where the images may run, for what period, and in what territories. The tool stores that signed contract with the booking, so the usage window a client paid for is documented rather than remembered. If a client keeps running images past the agreed term, the contract attached to the booking is the record that shows what was licensed.
It is worth being precise about what the software does and does not do. It does not register copyrights, and it does not decide who owns a given work. Ownership and registration are legal matters covered by the Copyright Office, and the automatic-protection point above is background, not a feature claim. What the tool does is keep the usage and licensing terms the parties agreed to on one booking record with the signed contract, so those terms are easy to find when a question comes up.
That documentation is quietly valuable for a talent agency. Usage disputes are common, and they almost always come down to what the contract said. Good talent software makes that answer immediate. The booking record holds the signed agreement, the deliverables, and the payout, so the usage term, the fee, and the sign-off all live together instead of being scattered across email and a shared drive nobody trusts.
For agencies that book models, performers, and creators whose likeness and content are the product, keeping these terms organized is not paperwork for its own sake. It is how you protect the value of the work you represent. When the contract that defines a usage window is generated from the booking and stored with it, you can answer a client’s or a talent’s question about rights without digging, and you can hold both sides to what was signed. You can see how contracts, e-signature, and the records tied to each booking come together on the Talent / Model Booking OS product page. It is also worth remembering that likeness and content rights are what a talent agency ultimately sells. A model’s images and a performer’s recorded work are assets, and the contract term that governs their use is what turns a booking into a protected deal rather than an open-ended handout. Keeping that term with the signed agreement and the payout, on one booking record, is how the agency keeps control of the value it represents over time.
| Attributes | Value |
|---|---|
| Deployment |
Cloud |
| Platform |
Web |
| License Type |
Subscription |
| Billing Period |
Monthly |
| Target Customer |
Creators & Agencies |
| Free Trial |
Yes |
Frequently bought together
-
Brand-Deal & Sponsorship Tracker
$19.00 -
Content Release Planner
$12.00 -
Royalty & Residual Tracker / Reconciler
$39.00 -
Split-Sheet & Royalty Splitter
$35.00 -
Tour & Event P&L Tracker
$39.00


