A deadline is the closing moment specified by the organiser or submission system. Its stated time zone may differ from the artist's. Almost every avoidable failed submission comes from one of three things: assuming the time zone, assuming the platform will stay up, or starting too late for the references and files to arrive.
Of the 220 open records in this index, 65 close within thirty days, 9 within seven, and 48 have no fixed closing date at all.
Fixed, rolling and recurring
Fixed. A stated date, often a stated time. The most common shape, and the one where time zone matters.
Rolling. Continuous acceptance, frequently until capacity is reached. Rolling calls reward early applications in a way fixed ones do not, because the places are being taken while the call is still open.
Recurring. A programme that opens on a cycle. A closed recurring call is genuinely useful: it tells you what was asked for and roughly when it will be asked again, which is why closed records stay readable here.
Time zones, precisely
A deadline such as “1 September” without a time and zone needs clarification. Record the complete instruction from the current call and ask the organiser if it is ambiguous. A platform countdown should not silently replace the official terms.
Keep both the original deadline and its conversion into your own time zone. Check daylight-saving changes on the actual date. Set an earlier personal target so a failed upload or missing confirmation leaves time for a response; a buffer reduces risk but cannot guarantee support will resolve a problem.
Planning backwards
Work back from the deadline and put dependent tasks first. Ask referees about their availability, allow time for photography and corrections, request supplier quotes and confirm account access.
Open the form early to see every required field. Then assign a completion date to each document and external dependency. The form, files and supporting submissions all need to be ready before the actual close.
Record the deadline as a complete instruction
A complete deadline record distinguishes the closing time from the work needed to reach it. A date on a listing card may be only one of several deadlines in a programme.
| Milestone | What it controls | What to record |
|---|---|---|
| Questions close | Last opportunity to clarify the brief | Official contact and response arrangements |
| Account or registration | Access to the submission system | Verification steps and any processing time |
| Reference deadline | Receipt of third-party evidence | Whether it differs from the artist's deadline |
| Final submission | The accepted application | Date, time, time zone and confirmation method |
| Decision and acceptance | When results and commitments are due | Notification channel and response window |
Time-zone conversion must use the date of the deadline. Some regions change their UTC offset seasonally, while others do not. An abbreviation can be ambiguous, so seek clarification when the location and wording do not settle it. Keep the original stated time alongside your converted calendar entry.
Plan a submission buffer around the slowest task
A submission plan works backwards from dependencies. A hypothetical three-week schedule could request references and supplier quotes first, prepare and photograph work in week two, then reserve the final week for writing, export checks and a test upload. The right duration depends on the actual requirements, not on this example.
Set your own submission target earlier than the official close. A buffer provides time to correct an invalid file, contact support or obtain a missing approval. It does not guarantee that every technical problem can be resolved, so deal with accounts and permissions early.
When you submit, save the final document set and confirmation. Check that an application has moved out of draft, pending-payment or incomplete status. Some systems require a separate final button after all uploads are finished.
If a technical failure occurs, capture the error, URL, date and time, and contact the designated support team promptly. Explain the stage reached and the evidence available. The organiser decides whether any remedy is permitted; a screenshot of an attempted upload does not by itself establish an accepted submission.
Use the application planner to estimate preparation time, then add any dependencies it does not know about, such as a partner's approval or specialist photography.
What happens if you miss it?
Nothing recoverable, in most cases. Some platforms close submission at the stated second and some organisers will accept a late file by email if asked immediately and politely — but neither is something to plan on, and neither applies to public funding bodies with procurement rules.
Does submitting early help your chances?
Submitting early does not inherently improve artistic merit. It can leave time to resolve an error. Rolling programmes may allocate places before the final advertised date, while fixed-round procedures vary; read how the particular programme assesses entries.
Why do so many deadlines cluster?
Funding bodies work to financial years and exhibition programmes to seasons, so calls bunch. This is worth knowing when planning: a month with four deadlines you care about needs its references requested in the same week.
What is a notification date?
The date the organiser expects to tell applicants the outcome. Where one is published, note it and do not chase before it. Where none is published, expect longer than you would like.
Should you set reminders?
Yes, and set two: one at the point where you would need to start, and one two days before the close. Records here carry a calendar file for exactly this reason.
When the deadline is not the constraint
For rolling programmes and for funders with several rounds a year, the binding constraint is usually readiness rather than timing — the references, the images and the budget. Where a call recurs, being a later round may allow stronger preparation, provided it still covers your project dates and the opportunity remains available.