Model release forms and image licensing records, tracked automatically
We build a workflow that sends model and property releases for e-signature before each shoot, chases the unsigned ones, links signed releases to the job and its images, and records the licence for every commercial delivery: usage, territory, period and renewal date. When a client asks to reuse an image months later, the terms are one search away, and you get a reminder before a licence expires. A typical build costs $1,000 to $2,500 and takes about four weeks.
The problem
Why releases and licences get lost
Commercial and stock work depends on releases and licences, and both tend to live in folders, inboxes and paper forms. On shoot day, someone realises a model has not signed, and months later nobody can find what usage a brand actually paid for.
Reuse requests and renewals are where money is made or lost. Without a record of territory, media and period for each licence, you either undercharge or spend an evening digging through old emails.
What we build
What our model release and licensing workflow includes
Releases before the shoot
Model and property releases sent for e-signature from your own templates when the shoot is booked.
Chasing and day-before check
Reminders for unsigned releases and a list the day before showing who still needs to sign.
Linked to job and images
Signed releases attached to the job in your studio tool and referenced in image metadata or your library.
Licence record per delivery
Usage, media, territory, period and fee recorded for each commercial delivery.
Renewal reminders
A reminder before each licence ends so you can offer a renewal.
Reuse request lookup
Requests to reuse an image are matched to the original licence and release for your decision.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Shoot booked
Releases for the expected people and locations are sent for e-signature.
-
02
Automated
Releases chased
Unsigned releases get reminders and appear on the day-before list.
-
03
Automated
Licence recorded
Each commercial delivery gets a licence record with its renewal date.
-
04
Studio review
Studio checks
You check releases on the day and review reuse requests against the record.
-
05
Photographer or owner decides
Rights decisions
Licensing terms, fees and permission to reuse are decided by the photographer.
How it behaves
How releases and licence records behave
What the client and models see
- A release to sign online before the shoot
- A reminder if they have not signed
- A clear licence summary with the delivery
What the studio sees
- A day-before list of unsigned releases
- One register of releases and licences
- Renewal reminders and reuse requests with the record
What the automation does
- Sends and chases releases
- Links signed forms to jobs and images
- Tracks licence periods and renewal dates
Edge cases and fallbacks
- Model arrives without signing
- The day-before list flagged it; a tablet signature on the day completes the record.
- Client asks for wider usage than licensed
- The original terms are shown to you for a new quote.
- Release signed with a different name
- Flagged for you to confirm the person before linking.
- E-signature service unavailable
- A PDF release is sent instead and the failure is logged and retried.
Architecture
Releases and licensing records at a glance.
- Input
- Logic and services
- Output
- Data
- People
How it flows
- 1 A booked commercial or stock shoot starts the release workflow.
- 2 Releases go out for e-signature and unsigned ones are chased before the day.
- 3 Signed releases and each delivery's licence terms are stored in one rights register.
- 4 Renewal reminders go out before expiry and reuse requests come to you with the record attached.
Project planner
How the project runs, phase by phase.
Model releases & image licensing records project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Release templates, licence types, where records live and how reuse is priced.
-
02
Design
2 to 3 days
Register fields, release triggers, reminder timing and metadata approach.
-
03
Build
1 to 2 weeks
E-signature flow, register, links to jobs and images, renewal reminders.
-
04
Shadow run
About 1 week
Releases for upcoming shoots run through both processes.
-
05
Launch
1 to 2 days
Switch on and import active licences.
-
06
Support
Ongoing
Template changes and new licence types.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Templates, licence types and register fields.
$200 – $400
-
Build
Release flow, register, links and reminders.
$500 – $1,300
-
Integrations
E-signature, studio tool and image library.
$150 – $400
-
Testing and shadow run
QA and parallel run for upcoming shoots.
$100 – $250
-
Launch and training
Switch-on and licence import.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Release and licence templates are written or reviewed by your own adviser. E-signature and n8n plans are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- E-signature: Your Dropbox Sign plan, or the e-signature in your studio tool.
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter), billed annually.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
UK: metadata identifying the owner
UK guidance says deliberate removal of metadata that identifies the copyright owner is unlawful, so delivered files keep owner metadata.
Source: www.gov.ukUS: licences vs transfers
17 USC 204(a) requires a signed writing for any transfer of copyright ownership, so the register records whether each deal is a licence or an assignment.
Source: www.law.cornell.eduEU and UK: photos of people are personal data
An image of an identifiable person is personal data under GDPR Article 4, so releases and the register are stored with access limited to the studio.
Source: gdpr-info.euFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Model release and image licensing questions questions, answered.
It works like one, built on your own templates and e-signature tool, but also links each release to the job, the images and the licence, so you can find it later.
A signed permission from a person who appears in a photo, setting out how the image may be used. Whether you need one depends on the use and the country, so your template should come from your own adviser.
Yes. Each commercial delivery gets a record of usage, media, territory, period and fee, linked to the signed agreement, with a reminder before it ends.
No. Pricing is yours. It shows you the original licence when a reuse request arrives so you can quote quickly.
Releases for minors go to a parent or guardian under your template, and the workflow will not mark a minor's release complete without that signature.
Releases signed before the shoot, licences with a complete record, renewals offered before expiry and time to answer reuse requests.
Free 20-minute call
Want this for your photographers & creative?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for photographers & creatives
All servicesPhotography CRM & lead pipeline automation
Every inquiry from your website, Instagram, directories and referrals in one photography CRM pipeline, with stage automations, follow-up tasks and a monthly view of where booked clients come from.
From $1,000 · About 4 weeks Details
AI inquiry assistant for photographers
Reply to new inquiries within minutes, even mid-shoot: an assistant that answers from your own packages, checks your calendar, offers a call and hands every real conversation to you.
From $2,500 · About 5 to 7 weeks Details
Quotes, contracts, deposits & payment reminders
Quotes built from your own package rules, contracts that match the quote, retainers and balances scheduled, polite payment reminders and invoices synced to your accounting tool.
From $1,000 · About 4 weeks Details