How to Use Jotform to Approve and Sign Creator Contracts

The short answer: if you sign 10 creators a month or fewer, Jotform's free Starter plan runs this whole flow, since it includes 10 signed documents a month; from the 11th contract, Bronze at $39 a month, or $34 billed yearly, allows 100 (checked on 26 October 2026 on the pricing page). Build the application form, turn your contract PDF into a Sign document, then add a workflow with a condition, an approval for the marketing lead and a Sign Document step with the creator signing first and you second, run it once in preview, and follow each creator's status in Jotform Inbox.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

The job: creators apply by email or direct message, someone forwards the promising ones, a contract goes out as an attachment, and three weeks later nobody can say which signed version is final. In Jotform the application, the yes or no and the signature become one flow with one status per creator. For what Jotform includes and what each plan allows, see the Jotform glossary entry.

Before you build:

1. Count signatures, not applications. Each approved creator uses one signed document. For example, 30 applications a month with 14 approved means 14 signed documents, over Starter's 10, so Bronze, while the 30 applications fit easily inside Starter's 100 submissions, using the pricing page.
2. Start from the contract you already use. Upload your current creator agreement as a PDF; Jotform Sign's Detect Fields finds the fillable fields, per the upload guide. Nothing needs retyping.
3. Choose the measure now. Days from application to signed contract. Your inbox gives you the before figure; Jotform Inbox gives you the after.

What you need

• A Jotform account on Starter or Bronze, as worked out above.
• The creator agreement as a PDF, approved by whoever owns contracts in your company.
• A decision on signature level. In EU law, Article 25 of the eIDAS Regulation says a court may not reject an electronic signature as evidence merely for being electronic, and reserves the effect of a handwritten signature for qualified ones, which rest on a qualified certificate. A standard creator agreement seldom needs that level; your lawyer makes the call.

Step 1: Build the application form

Describe the form to the AI Form Builder ("an application form for content creators") or start from a template, then edit the fields: name, email, handle, main platform, audience size as a number, rate per post and a portfolio link. Audience size has to be a number field, because step 4 compares it with a threshold.

Step 2: Turn the contract into a Sign document

On your Workspace page click Create, then E-Sign, then Upload Document, and choose the PDF. Click Create Signable Document, then Detect Fields, and add anything it missed from the Document Elements panel, per the upload guide. Set two signer roles, Creator and Company, so each field belongs to one of them.

Step 3: Open a workflow on the form

In the Form Builder, click Settings, then Workflows, and choose Start From Scratch, per the workflow guide. Request Approvals would build an approval flow for you; starting blank keeps every step visible while you learn the builder.

Step 4: Filter with an If/Else condition

From Add Elements, under Logic Elements on the Basic tab, add an If/Else Condition and click Add conditions. Choose the audience size field, the comparison and your threshold, per the If/Else guide. Several conditions combine with ALL or ANY. Connect True to the approval in step 5, and False to an Email element that thanks the creator and says no, set up as in the email element guide with the form's email field as recipient.

Step 5: Add the approval

Add an Approval element and open its gear icon. Under General, set Approvers to the marketing lead's address, or map it to a form field, and edit the notification email, per the approval guide. If two people must agree, add them and set the Completion Rule. Under Advanced, switch on Require Comments, so every no carries a reason, plus Send Reminder Emails and Expiration, so an application cannot wait forever. Connect Deny to a second polite email and Approve to step 6.

Step 6: Send the contract for signature

From Add Element, Basic tab, add Sign Document and click Add Document. Pick the Sign document from step 2, then under Manage Signers use the Link icon to fill the Creator role from the form's name and email fields, and enter yourself for Company, per the signature request guide. Turn on Signing Order with the creator first. The step has three outcomes, Signed, Declined and Canceled: connect Signed to the end of the flow and Declined to an email to yourself.

Step 7: Test the run

Toggle Preview in the Workflow Builder and click Start Run, then submit the form and play each role in turn: approver, creator, company, per the test run guide. The run ends with either View Run Summary or Error in Flow; the summary shows which element did what. Restart and try the False branch and the Deny outcome as well.

Step 8: Follow each creator

Approvals sit in Jotform Inbox, and each contract's status in Sign Inbox, per the signature request guide. The approver can act straight from the notification email, which opens the task in Jotform Inbox.

Where an agent fits

The Jotform MCP server gives Claude or ChatGPT a get_submissions tool that filters responses, the MCP page's own example being "show submissions for form 123 where Status is Pending". Each morning, ask for pending creator applications and a three-line summary of each: platform, audience size, rate. The agent prepares the reading; the decision stays a person's click in the Approval element, and the agent never touches the contract. Installing it takes a workspace admin, and Connected Apps under My Account is where you cut it off.

What the user guides flag

• A task passed around. An approver can reassign a task, but only up to three times, per the approver guide.
• An unfinished path. If the test run ends in Error in Flow, open the Run Summary and check that every outcome of every element leads somewhere before you share the form.
• Approvals that never close. Without reminders, escalation or expiration, an approval waits as long as the approver does.

Approvers outside your company

Require Login for Approver is on unless you switch it off, and the approval guide recommends keeping it: an approver who is not logged in is asked to sign up or log in to Jotform before the click counts. Inside your company that gives you an activity record. For a talent manager or an agency partner, it puts a Jotform sign-up between them and a yes, a default that grows Jotform's user base while adding little to your record of an outsider's decision. Turn it off for outside approvers; per the approver guide, they then decide on an Approvers Action page without an account.

FAQ

Can a creator sign on a phone?

Yes. Jotform describes Sign documents as signable on any device, per the Jotform Sign page, and the signing link arrives by email.

What happens if a creator declines the contract?

The step ends on Declined, which the signature request guide defines as at least one signer refusing, and the workflow follows the path you connected in step 6. Canceled is a separate outcome, for when you, the owner, withdraw the request.

Can two people approve before the contract goes out?

Yes. Add both as approvers and set the Completion Rule, or chain approvals for a multistep sign-off; the approval guide covers multistep and parallel approvals.