Saving a submission to your account

A festival entry reaches Your projects in one of five ways, after which its two private pages open for you without a code.

• The first time, you set up a project from it on the welcome screen. See Your first project.
• After that, an entry under your account's address is saved by itself. See Automatically, by your address.
• Keep it, on a scorecard you opened with its code while signed out, emails a code to the submission's address and makes or opens the account on it. It is switched off for now. See Keep it, from your scorecard.
• Save to your account, on the code box in front of your submission page, saves it with its access code to the account you log in with, whatever address it is under. It is switched off for now. See With Save to your account.
• Add an entry, on a project's Festivals tab, takes an entry's access code. See Your festival entries.

This guide covers them, which project an entry joins, and what changes once a submission is yours.

Saving takes nothing away from the festival. The festival keeps its copy of your submission and goes on editing and judging it exactly as before. What you gain is your own record of it: the entry appears in one of your projects, and its two private pages open for you without a code.

You never have to do any of this. The button and the nine-character code in a festival's emails open your submission page and your scorecard with no account at all, and Not now hides the offer to keep a scorecard. See Your submission page and Getting into your scorecard.

Automatically, by your address

Every time you log in with an emailed code, and every time you open Your projects, FilmScorecard looks for festival submissions whose submitter address is the address your account logs in with. Each one it finds is saved to your account and put into a project.

This starts once your account has a project. Until then nothing is saved by itself: the first time, you choose what to set up on the welcome screen. See Your first project.

• The submitter address is the one the festival holds for your submission: the one its emails, codes and results go to. Capitals and spaces at either end do not matter; anything else does.
• It also takes back a submission saved under your address by somebody else, with its code. See When another account has it.
• It works for any account. A judge or a member of a festival's staff who once entered a festival with the same address finds that submission saved to their account too, once that account has a project.
• Nothing to press and nothing to approve. Nothing is emailed either.
• A submission under another address is not found, even if it is yours. Add it with its access code — see Your festival entries — or ask the festival to correct the address before anybody saves it.
• Once a submission is saved, the address on it no longer decides whose it is. If the festival changes the address afterwards, the submission stays where it is, and only the festival's emails follow the new address.
• A new submission arrives the same way. When a festival on FilmScorecard receives another entry from you later, it appears the next time you log in or open Your projects.
• If you change the address you log in with, the submissions already saved stay yours. Those under the new address are picked up next time. Those under the old address are not taken from you.

With Save to your account

Save to your account is switched off for now, on the submission page as on the scorecard: the code box shows only Continue, and nothing in this section appears until it is turned back on. Meanwhile, Add an entry takes the same access code.

Save to your account is on the code box in front of the submission page a festival sends, before edits close and after. It is offered to anybody but the account the submission is already saved to:

Signed out, the button takes you to the log-in screen first. Log in, or create an account from its First time here? note — that sign-up skips the beta list; see A submission's access code goes around it too. You come back to the page you were on — the submission page's overview, or whichever of its pages you opened — and the save finishes there: back on that page as yours, or on to the welcome screen if your account has no project yet. A refusal appears in amber beside Save to your account at the top of the page.

It is not on the "Edits are closed" card a withdrawn or disqualified submission shows, or on "Not available yet", because those pages take no code. Festival staff reading the page never see it.

From the code box

1. Type the nine characters from the festival's email.
2. Press Save to your account instead of Continue. It reads Saving… while it works.

The code is checked exactly as Continue checks it. A wrong code gets the code box's own message and counts as one of your five tries an hour, and during a lockout both buttons are greyed out. See Every message the code box can show.

When the code is right:

• Your account already has a project: the submission is saved to it, and the page you were on opens again as yours, with no code needed from then on.
• Your account has no project yet: nothing is saved yet. You go to the welcome screen, which starts with this submission. See Your first project.

A right code opens the page even when the save is refused. You are in, just as if you had pressed Continue, and the reason it was refused shows in amber beside Save to your account at the top of the page.

From the top of the page

Save to your account appears at the right of the bar across the top only when a save you started from the code box was refused, with the reason beside it in amber. Otherwise the bar does not show it. Press it to try again — it reads Saving… while it works — and the same thing happens: saved and back on this page as yours, or on to the welcome screen the first time. A refusal appears beside the button in amber.

If you were signed out in between — your session ended after the page opened — the button takes you to the log-in screen first, and the save finishes when you come back to the page.

When Save to your account is refused

Nothing is saved, and one of these appears:

Keep it, from your scorecard

Keep it is switched off for now. A scorecard opened with its code shows no bar, and nothing in this section appears until it is turned back on.

Open your scorecard with its code while you are signed out, and a bar at the bottom of the window offers to keep it:

Keep this scorecard with the rest of your work

A free account holds every entry sent from n••••@studio.co and opens this scorecard without a code.

Not now · Keep it

• The address is the one the festival holds for your submission, shown as its first letter and its domain only. The whole address is never on the page.
• It is on the scorecard only: not on the code box, the "Not available yet" page or the submission page. It is never shown while you are signed in, once the submission is yours, or to festival staff.
• Not now hides it until you close your browser. The next visit asks again. Only your browser remembers it; nothing is saved on FilmScorecard's side.
• On a phone, while a price bar holds the bottom of the screen, the same offer is a card under your score instead. The Rate this scorecard pill sits above the bar, and the bar never prints.

Keeping it

1. Press Keep it. A 6-digit code is emailed to the submission's address.
2. The Check your email screen reads "We sent a 6-digit code to n••••@studio.co.", masked the same way, with no Change email link.
3. Type the code and press Log in. The line under the boxes reads "By entering the code, you agree to the Terms of Use and Privacy Policy."

What happens next:

• No account on that address yet: entering the code creates a free one. There is no form and no role to choose, and it is not held to the private beta: the scorecard's code is what lets the account be made.
• An account already on that address: entering the code logs you in to it. The screens are the same either way.
• The account has no project yet, which is always so for a new one: you go to the welcome screen, starting with this submission. See Your first project.
• The account already has a project: the submission is saved to it by its address, and you are back on the scorecard as its owner, with no bar and no code needed from then on.

The code goes to the submission's inbox, never to whoever pressed the button. Somebody you forwarded your scorecard to can press Keep it, and gets no further than the masked address.

It needs a code that is still current and in date:

• A newer code has been sent since you opened the page: Keep it takes you back to the code box. Type the newest code, then press Keep it again.
• Your code has expired, though this browser still opens the page: nothing is sent and the page reloads as it was. Use the code from a newer email; see When you need a new code.
• "We could not send that code. Check your connection and try again.", in amber under the buttons, means the email did not go. Press Keep it again.

Which project it joins

A saved submission joins the project that is the same work: the project itself, or any festival entry already in it, has

• the same kind: a film with a film, a screenplay with a screenplay;
• the same title, ignoring capitals, accents, punctuation and extra spaces, so "Don't Look Back" matches "dont look back" and "Long-Way" matches "Long Way";
• about the same length: a runtime within one minute for a film, a page count within 5 pages for a screenplay. When either side has no runtime or page count, the kind and the title are enough.

Then:

• Two matching projects: it joins the older one.
• No matching project: FilmScorecard makes a new project from the submission.
• Several matching submissions saved at the same moment go into one new project, filled in from the newest of them.
• On the welcome screen you choose for yourself which entries join your first project. See Your first project.
• Grouped wrongly? Move the entry. See Moving an entry to another project.

A new project made from a submission starts with the festival's copy of it:

Not copied: the submission's other credits, its statement, your contact details, the festival's own fields, and anything only the festival keeps. The screener and its password do not appear anywhere in your project. If the poster cannot be copied, the project starts without one and the submission is still saved.

The new project's page is not published. Its address is made from the title at this moment, and nobody can open the page at that address until you publish it. The first time you open the project's Page, a starter page is made from these details for you to build on. See Editing your page and The public film page.

From then on the project is yours. Change its Details, or build and publish its page; none of it changes the festival's copy.

When a project goes away by itself

One kind of project can be removed without you doing anything: a project FilmScorecard made from a festival submission, that you have never saved a change to, on its Details or on its page, once no festival entries are left in it. That happens when:

• you move its last entry to another project;
• another account takes the submission;
• the festival removes the submission, for example by undoing an import or deleting the festival.

The first two remove the project at once. The third removes it the next time you log in or open Your projects. Its page goes with it, though such a project never has a published page, because publishing keeps a project.

A project you added yourself is never removed, and neither is one you have saved a change to. If you want to keep a project FilmScorecard made, do any one of these once:

• open its Details, change something and press Save changes;
• change something on its Page, which saves to your draft by itself;
• publish its page.

Just opening the project, or its Page, does not count.

When another account has it

The first save stands, with one exception. A submission saved with its code to an account on another address can be taken back by the account on the address the submission carried when it was saved. Nothing else moves it.

An unlocked scorecard belongs to the submission, not to an account. If the submission moves to another account, its scorecard stays unlocked there.

Once it is saved

• Its two private pages open without a code, whenever you are signed in to this account: the submission page — unless the submission is withdrawn or disqualified — and the scorecard once it is released. Save to your account is not shown, and everything on the pages works as it does with the code: saving your corrections, replacing the poster, writing your questions for the judges, writing to the festival, unlocking the scorecard, promo codes, Share and the PDF.
• The code still works, in any browser, as before.
• The entry is on its project's Festivals tab, and anything the festival asks for is in the bell's To do list. See Your festival entries and Missing items.
• What the festival announces about it reaches you in the bell. A selection or award it announces also appears as a laurel on the project's page, when the page has a Laurels block. See Editing your page.

If you also judge

A film saved to your account leaves your judging, at every festival:

• it is no longer offered to you, and it leaves your judging home's counts;
• if you were holding it, part-way through scoring, your hold is let go as if you had released it, and the film goes back to the other judges;
• any scorecard you had already filed on it stays filed.

See Your own submissions.

What the festival sees

• One line on its record of your submission. Its history shows that the submission was saved to an account, when, and the email address that account signs in with. Nothing else marks it — nothing on its list of submissions — and nothing is emailed to the festival.
• It can still change everything. The festival edits its record and its poster exactly as before.
• It never sees your project. Only three things of yours reach its copy: a send from the bell, Copy current details into this entry in the entry panel (see Copying your project's details into an entry), and a save on the submission page. All three count as the submitter's own edits.

Related guides

• Your projects: the workspace saved submissions land in.
• Your first project: the welcome screen, where your first entry becomes a project.
• Your festival entries: the Festivals table and entry panel, adding an entry with its access code, and moving entries between projects.
• Getting into your scorecard: the access code, its limits and every message the code box can show.
• Creating an account: the other ways an account is made.