Contractor payment terms and schedules: how to set clear due dates

Key takeaways

A contractor payment schedule should let both sides calculate the same due date. For each amount, the agreement needs to identify the work, the event that starts the clock, the review deadline and the payment date. Keep the scope, approval and invoice records together.

• Choose the schedule to fit the work. A retainer or recurring cycle can suit continuing services; a defined deliverable can have a delivery trigger; longer projects can divide the work into installments. For each amount, identify the related work and state the amount and due date. A deposit or installment is a contract choice, not a universal percentage to copy from another engagement.
• Make the clock calculable. “Net 30” is incomplete until the agreement says whether the count begins on invoice receipt, delivery, acceptance or another stated event. Set a review deadline, identify who may approve the work, and say how an invoice reaches that person. Completion and acceptance can be different events.
• Keep the operational record aligned. The agreement, statement of work, milestone evidence, approval decision and invoice should point to the same deliverable and amount. If scope or timing changes, record the revised terms before additional work begins. Where ownership matters, address rights in a separate written record instead of assuming that delivery or payment settles them.
• Check the governing rules before signing. Local rules can set writing requirements, due-date defaults or limits on certain contract terms. For example, NYC has rules for qualifying freelance agreements, while UK and EU commercial rules have their own scoped fallback timing. Construction and home-improvement rules are a separate category; their deposit or scheduling rules do not automatically apply to professional services.

What payment terms and schedules actually specify

Payment terms set the rules for the engagement; the schedule applies them to each amount of work. Together, they should let the contractor, project lead and finance team identify a due date without reconstructing the deal from messages.

Payment terms versus the payment schedule

Payment terms set the broader conditions: the contract currency, invoicing process, method, review path, late-payment provisions where applicable, and the law that governs the agreement. They may also say what happens when the scope changes or a deliverable is disputed. These are the rules that apply across the engagement.

The schedule turns those rules into individual obligations. For each installment, recurring period or delivery, write down:

• the work, service period or milestone it covers;
• the amount and any reimbursable expense treatment;
• the evidence that the work reached the agreed point;
• the invoice event and required information;
• the reviewer and review deadline; and
• the event that starts the due-date clock and the resulting due date.

The NYC model freelance agreement separates the services and reimbursable expenses from the payment amount, and gives separate fields for the total amount, method and timing. Its optional installment form also asks for an amount and due date for each installment. Those fields are a useful drafting pattern: they prevent a single payment label from carrying an unclear scope, trigger and date.

Ongoing advisory work may need a service period and recurring date. A defined design, build or research deliverable may need a review step; a longer project can attach each amount to a concrete milestone. Choose the arrangement both sides can apply to this assignment.

Professional services versus construction contracts

Do not borrow a schedule from a construction or home-improvement contract without checking whether its rules apply to your engagement. A freelance design, software, consulting or creative-services agreement and a regulated building project can use similar words, such as deposit, progress payment or completion, while operating under different legal requirements.

California home-improvement contracts, for example, are a separately regulated category and require a detailed written payment schedule. The regulator's down-payment limit applies to California home-improvement and swimming-pool jobs; it is not a benchmark for a professional-services deposit. Construction work may also have its own statutory notice, retainage or change-order rules that do not transfer to independent professional work.

Classify the work and the parties before choosing a schedule or deposit. Then check the governing law and applicable rules. A clause borrowed from another type of contract may set the wrong expectations.

Choose a schedule for the work

Define the work and its review points before choosing a payment structure. The right schedule makes the amount, trigger and due date clear for this engagement, whether it covers continuing service or a finite deliverable.

Prepayment and deposits

A deposit or retainer places an agreed amount before work, with the agreement stating what that amount covers and what happens next. It can be useful when both sides want to mark a commitment before a project begins. Write the amount, the related scope and the later schedule in the same document so the advance does not become a substitute for the rest of the agreement.

Avoid treating a familiar percentage as a general rule. The NYC model agreement includes an upfront retainer as an optional drafting term, alongside optional installments. California's home-improvement down-payment cap is specific to that regulated category and does not supply a figure for professional services.

Payment on delivery

For a contained deliverable, the schedule can connect an amount to delivery of the agreed work. Define what counts as delivery: a submitted design package, repository handoff, report, accepted files or another observable result. Then state whether delivery starts invoicing, review or the due-date clock.

Delivery alone may not answer every question. If the client has a review period, name its length, the reviewer and the way feedback is recorded. That keeps a completed submission from sitting in an undefined state between delivery and payment.

Milestones and progress payments

Milestones divide a larger assignment into smaller, observable stages. Each one needs its own description, amount, evidence of completion, review step and due date. A vague phase label is rarely enough: tie the stage to a document, prototype, specified feature set or another result that both sides can identify.

Milestones spread obligations across a project. They work when each stage represents real progress and its conditions are written clearly.

But it’s unreasonable to ask the freelancer to bear 100% of the risk.

— Lindsay Van Thoen, Freelancers Union finance contributor

Recurring service cycles

Use a recurring cycle for continuing services with a defined period, such as a monthly advisory, support or creative-services engagement. State the service period, the amount, invoice timing, review route and due-date trigger for each cycle. If the work varies from one period to the next, record the agreed change before the next invoice rather than relying on an earlier cycle to describe it.

The recurring date should still be traceable to the service period and invoice. A regular cadence does not remove the need to identify the work covered by each amount.

Net terms and end-of-month payment

Net terms express a number of days after a specified event. End-of-month payment uses the calendar month as part of the trigger. Both need a complete clock: say whether the period begins when the invoice is received, when work is delivered, after acceptance, or on another agreed event.

For example, 30 days after invoice receipt and 30 days after acceptance can lead to different due dates for the same assignment. Write the selected event, how it is recorded, and how weekends, public holidays or time zones are treated. Local law can also supply a scoped default if the agreement does not name a date, so check the governing rules before assuming that a label settles the deadline.

Discounts and credit arrangements

An early-payment discount or credit arrangement changes the amount or timing that would otherwise apply. State the ordinary amount and due date first, then describe the condition for the alternative amount: who may use it, the deadline, and how the reduction or credit appears on the invoice.

Keep these arrangements separate from the work description and from the approval decision. A discount should not obscure whether the underlying deliverable was completed, accepted or disputed. Where an arrangement has legal, tax or accounting consequences for the parties, check those terms under the governing law before adding it to the schedule.

Set the clock and due date

Name the event that starts the clock, define the review handoff and record when the event occurs. Without a starting point, Net 30 can produce two different due dates.

The decision path connects the work category and payment basis to a documented trigger, review, invoice and due date. Its final step keeps the payment, acceptance and rights records distinct.

The event that starts the clock

Pick one event for each amount and describe it precisely. Depending on the schedule, the clock might start when the contractor submits an invoice, delivers an agreed result, receives written acceptance, completes a recurring service period, or reaches a named milestone. Record how that event is evidenced and who receives the notice.

An invoice date and invoice receipt date can differ. Delivery and acceptance can differ too. For a due date counted from invoice receipt, specify where the invoice must be sent and how receipt is recorded. For one counted from acceptance, define the acceptance event and the deadline for review.

This just means that payment is due when you complete work, not when the client signs off on it — a subtle, but important distinction.

— Matt Fulton, Freelancers Union community contributor

Local fallback rules also depend on their scope. For NYC-covered freelance work, the contract date governs; where no date is stated, the guidance sets a 30-day fallback after completion. UK commercial guidance uses the later of invoice receipt or service delivery when no date has been agreed. Covered EU commercial transactions have their own invoice-and-delivery sequence. These are reasons to write the trigger directly and then check the rules governing the actual agreement.

Acceptance and review deadlines

Acceptance needs an operating path, not a vague promise to review. State what the contractor submits, who reviews it, how long that person has to respond, and which channel records acceptance, rejection or requested changes. If a change request affects the agreed work, document the revised scope and schedule before treating it as the next milestone.

Keep acceptance separate from events outside either party's direct control. A client may need an internal sign-off, a published piece may wait on an editorial calendar, or a project may depend on another team. If those events are intended to affect the date, name them and decide how long the contractor can reasonably be left waiting. Otherwise, link the clock to an event the agreement can identify and record.

You could take an assignment and maybe it’s six months or a year before it comes out.

— Ryan Goldberg, freelance journalist and Freelance Solidarity Project organizing committee member

Calendar days, holidays and time zones

Specify whether the schedule uses calendar days or business days. If it uses business days, identify the holiday calendar and the place that determines it. For a distributed engagement, identify the time zone that controls an end-of-day deadline and whether an invoice submitted after a stated cutoff moves to the next business day.

Write a due date when you can, even if the agreement also states the calculation. A dated schedule makes the next action visible to the contractor, reviewer and finance team. When a recurring cycle or contingent event makes a fixed date impractical, keep the calculation explicit: event date, number of days, day-count convention and the resulting deadline.

Do not assume that Net 30 settles weekends, public holidays or the location of the parties. The governing law, contract terms and the parties' actual arrangement determine how a particular deadline operates.

Write an executable payment schedule

Build the schedule one amount at a time. Each row should connect the work, evidence and invoice to a due date that the contractor, project lead and finance reviewer can all calculate.

Scope, amount and evidence for each installment

Start with the work covered by the installment. Describe a service period, deliverable or milestone in terms the parties can identify later. Add the amount and state whether it includes any reimbursable expense or whether those are handled separately. The NYC model agreement uses separate fields for services, reimbursable costs and the payment amount; that separation is useful whenever an invoice could otherwise mix several kinds of work.

Then name the evidence for the installment. It might be a completed service period, submitted report, accepted design file, documented milestone or other agreed record. The evidence does not need to be elaborate, but it should be specific enough to show which part of the agreement the invoice relates to.

Invoice requirements and the calculated due date

State when the contractor may issue an invoice, where it must be sent, and which identifiers or supporting records it needs. Identify the person or team responsible for receiving it and the route for correcting an invoice that lacks required information. An invoice sent to the wrong place or without the needed reference can leave the parties arguing about a clock that never visibly started.

For every row, write the trigger and calculation as well as the final due date. For example, the row might say that the contractor submits an invoice after a named milestone, the client receives it through the designated address, and the amount is due a stated number of calendar days later. If review or acceptance comes first, include that event and its deadline before the invoice trigger.

Keep the contract's formula clear even where local law may supply a fallback. Whether that fallback applies depends on the parties, transaction and governing law.

A schedule both sides can check

Use one row per amount, recurring period or milestone. The blank matrix below gives the fields both sides need to calculate and verify an installment; complete it with the facts of the engagement before signing.

Installment and work covered	Amount, expenses and evidence	Review owner and deadline	Invoice destination and clock trigger	Calculated due date

Keep the completed schedule with the agreement and statement of work. When scope, amount or timing changes, update the affected row through the agreed written change process and preserve the earlier record. A schedule becomes operational when the people who submit work, approve it and process invoices use the same version.

Run invoicing and approval

After work is done, the contractor needs a submission route and the client needs a named reviewer. Record the decision against the milestone or service period in the agreement.

Submit and route the invoice

Tell the contractor where to submit the invoice, which contact or system receives it, and which reference must connect it to the agreement. The reference may be a purchase order, project code, milestone identifier or service period. Include any required supporting record, such as the approved deliverable or statement of work, when that record is needed to match the invoice to the schedule.

Confirm receipt through a channel both sides can see. This matters because the invoice-receipt event may start the agreed clock. It also gives the contractor a clear point at which to correct a routing error rather than discovering it after the due date.

A 2024 UK government study of 138 businesses that reported a proportion of late supplier invoices found that 36% cited administrative error or failing, and 23% cited technical issues such as a lost or undelivered invoice. The respondents could name more than one reason, and the survey was not a measure of contractor invoices. It still shows why a named destination, receipt record and clear identifiers belong in the day-to-day process.

Review, correct and record the decision

Assign a reviewer who can confirm that the invoice matches the agreed work, amount and evidence. Give that person a review deadline and a backup for absence. If something is incomplete, send a specific correction request that identifies the missing document, incorrect amount, wrong reference or scope question.

Record one of three outcomes against the invoice: approved, returned for correction, or disputed. Keep the related deliverable, approval note and correspondence with the invoice record. That record makes it possible to see whether the delay came from missing information, a quality question, a change in scope or an internal handoff.

In the same UK study, 31% of that 138-respondent group cited disputed invoices as a reason for late supplier payment. The figure does not describe contractor invoices; it reinforces the need for a review and dispute route before the first invoice arrives.

Track upcoming and overdue amounts

Maintain a shared view of upcoming invoices, review deadlines, due dates and any disputed amounts. Each entry should link back to the schedule row, so a project lead can see the covered work and finance can see the agreed trigger without requesting a separate explanation.

Review the list before each approval or payment run. Mark completed actions with the event date: invoice received, work accepted, correction requested, approval granted, due date reached or dispute opened. If the agreement uses recurring cycles, create the next row early enough for the contractor and reviewer to confirm the period and invoice route.

When an amount passes its due date, preserve the record and use the escalation route in the agreement. Do not solve an overdue invoice by overwriting the original due date or approval history; the sequence is part of the operating record both sides may need later.

Manage changes, disputes and missed dates

When work changes, update the schedule while the agreement is still clear to both sides. A written path for changes, disputes and overdue amounts preserves what was agreed, delivered and due.

Agree changes before extra work

When the scope, delivery date, amount or acceptance criteria change, document the new agreement before the contractor starts the extra work. Identify the original schedule row, describe the change, state the revised amount or timing, and record who approved it. Keep the earlier version with the change record rather than replacing it.

That discipline is particularly important when a request sounds small but affects a milestone. A new feature, additional revision cycle, different output format or extended service period can change the evidence needed for delivery and the date on which the next invoice is appropriate.

If your deliverables are in writing, there’s less chance for a dispute when they come back wanting more.

— Gamal Hennessy, contracts lawyer and C3 business owner

California's home-improvement rules require a signed written change order before a scope or price change in that category. The broader lesson for professional services is operational rather than a claim that the same rule applies everywhere: do not rely on an informal request to redefine a recorded schedule.

Separate disputed and undisputed amounts

Define how either party raises a dispute. The notice should identify the invoice, the schedule row, the amount in question, the reason, the supporting material and the person handling the response. Set a channel and response deadline so the issue does not disappear into a general project conversation.

Where only part of an invoice is disputed, record the disputed and undisputed portions separately. The agreement should say how each portion is handled under the governing law. Do not assume that a general clause or a familiar practice decides whether the undisputed amount must be released on a particular date.

Keep the submitted work, review notes, changes, invoice, correspondence and resolution together. That sequence shows whether the disagreement concerns the work, price, a missing document or the due-date calculation.

Late-payment terms and escalation

Set the escalation path before an amount becomes overdue. It can include a reminder, a named contact, a written notice and the next contractual step. State when an amount is overdue and which record proves the due date, particularly where the clock depends on invoice receipt, delivery or acceptance.

Any interest, late fee, suspension or recovery provision needs to fit the governing law and the actual agreement. The NYC model agreement treats its late-fee clause as optional and warns that an excessive fee may be invalid. UK commercial guidance provides scoped remedies for eligible business transactions. Neither point creates a universal term for a cross-border contractor agreement.

Record each escalation with its date and the outstanding amount. A clear trail gives the parties a factual starting point for resolution and prevents a missed date from becoming a dispute about what the schedule said in the first place.

Check local rules before signing

The same wording can have different effects depending on the parties, work type and governing law. Before you sign, identify where each party is acting, whether the engagement falls within a local rule, and which law the agreement selects. Then check the due-date, writing and remedy provisions against that specific setting.

US freelance rules and construction limits

US rules in this area are not one national schedule. New York City's Freelance Isn't Free Act, for example, applies to qualifying freelance agreements. Its guidance says agreements worth at least $800 in a 120-day period must be in writing and must state the work, pay and payment date. For covered work, the hiring party must use the contract date or, if no date is stated, pay within 30 days after completion.

That NYC fallback does not make Net 30 a general US rule. Check whether the parties and work fall within the statute before relying on it, and write the due-date trigger directly even where a fallback may exist.

Construction and home-improvement work needs a separate check. California's contractor regulator requires a detailed written payment schedule for home-improvement contracts and sets a down-payment cap for home-improvement and swimming-pool jobs. Those rules are tied to that category; they do not supply a deposit rule for software, consulting, design or other professional services.

UK commercial and construction terms

For UK business-to-business transactions, an agreed payment date must usually be within 60 days, although businesses may agree a longer period where it is fair to both sides. If no payment date is agreed, the UK guidance treats payment as late 30 days after invoice receipt or service delivery, whichever is later.

These rules apply to the commercial situation described in the guidance. Confirm that the parties and transaction fit that scope, particularly when one party is outside the UK or the agreement chooses another governing law. Eligible suppliers may have a right to interest and debt-recovery costs for late payment, but the actual entitlement depends on the transaction and terms.

Construction contracts can be governed by specialist rules that do not map neatly onto professional-services work. If the project involves construction, subcontracting, retainage or statutory notices, seek jurisdiction-specific confirmation before reusing a general commercial-payment clause.

EU commercial payment rules

EU late-payment guidance addresses commercial transactions between businesses, including qualifying sole traders acting in their independent economic or professional activity, and public authorities. It excludes consumer transactions. Start by confirming that the engagement meets that commercial scope.

Where a covered contract has no payment period, the guidance says late-payment interest becomes payable 30 calendar days after the client receives the invoice or payment request. When receipt is unknown, the delivery date matters; when an invoice arrives before delivery, the countdown begins after delivery. Put the contract trigger in writing rather than relying on the parties to reconstruct this sequence later.

For cross-border EU work, the selected governing law matters. The guidance notes that non-EU law can make those EU rules inapplicable, and national implementation must be checked before making a country-specific remedy claim. Record the chosen law in the agreement and review its effect before you set the final schedule.

Plan cross-border receipt and reconciliation

In a cross-border engagement, the contractual due date and the contractor's receipt date can differ. Agree on the currency, conversion responsibility, initiation record and reconciliation path before the first invoice.

Currency and conversion responsibility

State the contract currency and the currency the contractor expects to receive. If they differ, write which party is responsible for conversion, the rate source or timing the parties will use, and how any charge allocation is handled. Do not leave these choices implied by a prior invoice or an informal message.

The agreement should also identify what the invoice displays and what record will be used to reconcile the amount. A clear currency rule lets both sides compare the scheduled amount, the approved invoice and the receipt record without debating which figure was meant to control.

These details depend on the parties' actual arrangement and chosen payment method. Check the available route, conversion terms, cutoffs and records for the specific engagement before you promise a receipt amount or date.

Initiation date, receipt expectation and failed transfers

Record the date on which the client initiates the transfer and distinguish it from the date the contractor receives it. The schedule can state the contractual due date, while the operating record captures the initiation reference and the receipt confirmation. That distinction makes a delay visible without changing the agreed due date after the fact.

Before work starts, agree who checks a missing or rejected transfer, which reference identifies it, and where supporting records are kept. A practical reconciliation record includes the invoice, approved schedule row, initiation date, reference, receipt confirmation and any correction or reissue needed to resolve a failure.

Avoid promising a universal receipt speed for cross-border work. Cutoffs, bank holidays, the payment route, currency conversion and the parties' locations can affect the actual sequence. Use the agreed records to investigate an exception and keep the contractor informed through the same channel used for the invoice and approval.

Keep a work-to-payment record

Keep one traceable record from the agreement to the completed work. It should show what was commissioned, what changed, what was delivered, who accepted it, which invoice relates to it and whether the amount became due. This is useful during an ordinary approval and essential when the parties later disagree about scope, timing or ownership.

Link the contract, work, approval and invoice

Give each engagement, deliverable or milestone an identifier that appears in the agreement, statement of work, schedule and invoice. Attach the relevant records as the work moves forward:

• the signed agreement and statement of work;
• each approved scope, price or timing change;
• the submitted deliverable or service-period evidence;
• the acceptance, rejection or correction record;
• the invoice and receipt confirmation; and
• the due-date calculation and any later escalation.

Use the same identifier in each record. That lets a reviewer move from an invoice back to the agreed scope, then forward to the delivery and approval evidence. It also avoids the common problem of a finance record that names an amount without showing which version of the work it covers.

Decide who owns the record, where it is stored and who may update it. Preserve prior versions when the schedule changes. A clean history should show what the parties agreed at the time, rather than only the latest description after a project has moved on.

Confirm rights in delivered work separately

Treat work delivery, invoice approval, payment and ownership as related but separate questions. If the engagement requires a transfer, licence or other rights outcome, put that outcome in a signed written instrument appropriate to the governing law and keep it with the relevant deliverable record.

For US copyright transfers, 17 USC §204(a) generally requires a written instrument signed by the rights owner or an authorized agent. US law also distinguishes ownership of a physical or digital copy from ownership of copyright, and work made for hire follows a separate ownership pathway. Payment or file delivery alone should not be assumed to settle the intended rights outcome.

The UK position has its own rule: the creator of commissioned copyright work is normally the first owner unless ownership is agreed in writing, while an implied licence may permit use without transferring ownership. The NYC model freelance agreement shows one optional drafting approach in which ownership transfer follows final payment. It is an example of an agreed trigger, not an automatic rule for every agreement.

For a specific contract, confirm the governing law, the rights to be transferred or licensed, and the signature requirements before relying on a payment milestone as a rights event.

Frequently asked questions

What is a typical contractor payment schedule?

There is no single typical schedule that fits every contractor engagement. Continuing services can use a recurring service period; a defined deliverable can use a delivery or acceptance trigger; a longer assignment can use installments tied to milestones. Choose the structure that matches the work, then state the amount, trigger, invoice route and due date for each row.

Do not use a local construction rule or a familiar percentage as a benchmark for professional services. The agreement should make the schedule workable for the actual scope and governing law.

Should I pay a contractor 50% upfront?

An upfront retainer or deposit is a contract choice, not a universal standard. The NYC model agreement presents a retainer and installments as optional drafting terms, without prescribing a percentage. Agree the amount only after defining the work it covers, the later schedule and the records each side will provide.

California's cap for home-improvement and swimming-pool down payments is specific to that regulated category. It does not tell you what proportion is suitable for consulting, design, software or other professional services.

When does Net 30 start for a contractor invoice?

Net 30 starts from the event named in the agreement. It may be invoice receipt, delivery, acceptance or another defined event. Write the event, how it is recorded and which time zone or day-count convention applies so both parties calculate the same date.

If no date is agreed, local fallbacks can differ. For NYC-covered freelance work, the guidance uses 30 days after completion. UK commercial guidance uses the later of invoice receipt or service delivery. Covered EU commercial transactions have a separate invoice-and-delivery sequence. Check the scope and governing law before treating any of these as the rule for your agreement.

Can payment terms change after work begins?

They can change if the parties agree to the change through the process in their agreement. Record the revised scope, amount, trigger, due date and approval before the contractor performs the additional work. Keep the original schedule row and the written change record together.

An informal request can create a gap between the work delivered and the invoice that follows. A documented change keeps both sides aligned on what the new amount covers.

What happens when part of an invoice is disputed?

Identify the disputed portion, the reason, the relevant schedule row and the supporting records. Keep it separate from the undisputed portion, and follow the agreement and governing law for how each amount is handled. The correct treatment can depend on the contract and jurisdiction, so do not assume that a general practice decides the due date for either part.

Record the notice, response deadline and resolution. The deliverable, review notes, scope changes and invoice history should remain linked to the dispute record.

Does paying for a deliverable transfer its copyright?

Not automatically in every jurisdiction. In the United States, a copyright transfer generally requires a signed written instrument, and ownership of a copy does not by itself convey copyright. Work made for hire is a separate ownership pathway. In the UK, the creator of commissioned copyright work is normally the first owner unless ownership is otherwise agreed in writing; an implied licence may allow use without transferring ownership.

If rights matter, put the intended transfer or licence in the appropriate written agreement and connect it to the delivered work. Confirm the governing law and signature requirements for the specific engagement.

Put the schedule into operation

Turn the signed schedule into a working routine before the first invoice is due. The people who commission work, approve it and handle invoices should know the same trigger, record location and escalation path.

1. Classify the engagement and confirm the governing law before choosing the schedule. Keep professional services distinct from construction or home-improvement work, which can have separate rules.
2. Create one schedule row for every installment, milestone or recurring period. Include the covered work, amount, evidence, reviewer, invoice route, clock trigger and due date.
3. Set up the record path. Give the contractor a submission destination, give the client a named reviewer and backup, and use the same identifier across the agreement, statement of work, approval and invoice.
4. Review the next due dates before each approval cycle. Record invoice receipt, completion, acceptance, correction requests and disputes as they happen instead of reconstructing the sequence later.
5. Document any change before extra work begins. Update the affected schedule row, preserve the earlier version and make the new due-date calculation visible to both sides.
6. Close each work item with its delivery, acceptance, invoice and receipt records. Where rights are part of the engagement, check that the required written rights record is complete as well.

Use the same schedule when work changes, an invoice needs correction or a date is missed. Check local requirements whenever the engagement or governing law changes.

Sources

• What Is a Contract? — California Contractors State License Board
• Model Contract for Freelance Workers — New York City Department of Consumer and Worker Protection
• Freelance Workers — New York City Department of Consumer and Worker Protection
• Late Commercial Payments: Interest, Debt Recovery and Payment Plans — UK Government
• Late Payment — Your Europe, European Union
• Copyright Law of the United States: Chapter 2 — U.S. Copyright Office
• Ownership of Copyright Works — UK Intellectual Property Office
• Late Payments Research: Understanding Variations in Payment Performance and Practices Across Business Sectors and Sizes — UK Department for Business and Trade and IFF Research
• The Definitive Guide to Freelance Payment Terms — Freelancers Union
• Don’t Get Stiffed: How to Ask for Milestone Payments — Freelancers Union
• Issues Facing Freelance Writers in 2021: Contract Standards — Freelancers Union
• If You’re Not Using a Contract Yet, This Should Convince You — Freelancers Union