On September 10, 2026, this common mid-project request deserves a clear test: a partnership is underway, and someone asks for final work sooner. AIGA’s 2026 proposal guidance puts the work, review path, schedule, handoff, and triggers for a revised scope in the same conversation. That is a useful frame for creator work. AIGA proposal guidance
The dialogue below is illustrative. It is a way to inspect a change, not a quote, contract, or promise of availability.
Scene one — Do not answer the new date first
Brand, illustrative: “The launch moved up. Can you send the final video by Friday instead of next Wednesday?”
Creator or coordinator: “I can check the new date. Before I confirm, what changed besides the date? Is Friday the final delivery, the review cut, or the public posting date? Please confirm the time zone, the person who can approve, and when comments will arrive.”
The first job is to locate the change. A shorter calendar can be a reschedule. It can also mean an extra cut, new format, new claim, new platform, or different approval route. Ask for the exact request in writing. Do not convert urgency into acceptance.
Scene two — Run the five-line rush check
Read the existing scope beside the new request. Mark each line unchanged, changed, or open.
1. Deliverables. Is the same asset still required? Confirm length, posts, versions, captions, raw files, and destination. “Final video” may hide an extra cut or export. Write down what was removed or added.
2. Review rounds. Who sees the work, in what order, and how quickly must each person respond? A rush is not workable if reviewers keep a week-long response window. Name one decision owner. Record whether the faster date removes, adds, or leaves intact a round. AIGA recommends making revisions, approvals, handoff, and client-provided materials visible. AIGA proposal guidance
3. Usage. Is the work still for the same organic post, or will it now be reposted, edited, placed in paid media, or used elsewhere? The U.S. Copyright Office explains that owners hold exclusive rights including reproduction, derivative works, distribution, public performance, and public display, and may authorize others’ use. The practical lesson: a faster deadline does not silently grant a new use. U.S. Copyright Office, What is Copyright?
4. Dependencies. What must arrive before production can finish? List product, claims, music, footage, links, disclosure wording, access, translations, review, and other participants. Put an owner and due time beside each. A late dependency is a shared scheduling problem, not an invisible obligation for the creator to absorb.
5. Compensation. What changed in labor, capacity, opportunity cost, rights, or risk? Do not invent a universal rush percentage. Ask whether compensation stays with the same scope, changes for added work or rights, or follows a reduced package. AIGA’s 2026 guidance treats pricing as a conversation about work, uncertainty, review, schedule, handoff, expenses, and revised-scope triggers. That is a method, not a market rate.
Scene three — Choose the honest route
Route A: Same scope, earlier date. “Deliverables, review rounds, usage, dependencies, and compensation remain unchanged. I can confirm Friday after I check capacity and receive the required materials by Tuesday at noon.” This is a proposed response, not a guarantee. Write the date, time zone, approval deadline, and dependency owner.
Route B: Earlier date, smaller package. “I can meet Friday if we deliver one format, one review round, and the agreed organic placement. Extra versions and expanded use stay out of this delivery.” The reduction must be specific. “We will keep it simple” is not a scope.
Route C: Earlier date plus changed work or rights. “The new date and paid-media use change the assignment. Please confirm revised deliverables, usage, review path, dependencies, and compensation in writing. I will review that proposal before confirming.” Moving faster is not permission to widen a license, and a revised-scope conversation is not a booking.
No route should rely on a vague “yes, we’ll sort the details later.” If the authorized decision maker cannot confirm the changed fields, pause the work that depends on them.
Scene four — Send a change note before the next file
Use a short record that both sides can correct:
- Original: deliverables, review rounds, usage, dependencies, compensation, and dates.
- Requested change: new final or posting date, time zone, and requester-supplied reason.
- Unchanged: every field that remains the same.
- Changed: every added, removed, accelerated, or expanded field.
- Dependencies: material, approval, access, translation, disclosure, and decision owners with due times.
- Compensation: the amount or formula the parties actually agree, with its payment trigger and date; leave it open when it is not agreed.
- Current decision: reviewing the change, accepting the revised scope, or declining it.
Creator or coordinator: “I have captured the requested date change. I have not confirmed the revised scope yet. Please correct the open fields and identify the person authorized to approve the updated terms.”
Before sending the next file, compare the working brief, asset list, rights language, review calendar, and change note. If the rush was only a date change, say so. If the deal moved, name how. The useful outcome is not a dramatic surcharge or a forced no. It is a shared record showing what can be delivered, by when, for which use, after whose approval, and on what agreed commercial terms.
Sources and limitations
- AIGA, “Freelance Graphic Design Proposal Guide 2026” — checked September 10, 2026; supports defining work, constraints, review owners, revisions, approvals, handoff, schedule, and triggers for a revised scope or pricing conversation. Limitation: this is design-practice guidance, not a creator contract, universal rate, or legal advice.
- U.S. Copyright Office, “What is Copyright?” — checked September 10, 2026; supports the general U.S. description of copyright ownership, exclusive rights, and authorization of others’ use. Limitation: it is general U.S. information, not an agreement, rights clearance, or advice for a particular project or jurisdiction.