Working with a producer or director: send the script, get the notes back

In one line: how to put a screenplay in front of a producer or a director — what the link shows them, what they cannot do with it, where their notes have to come from, and how you pin those notes to the lines they were about.

Read this before you send anything

A Slima share link is read-only, with no way back. Your producer can open the screenplay and read it properly laid out. They cannot type a single character into Slima — there is no comment box on that page, no reactions, no reply button, and no "request access to comment". Their notes will reach you by email, on a call, or across a table.

That is not a gap you can work around with a setting. Say it to yourself now rather than discovering it a week after you sent the link.

What Slima does give you is the second half: once you have heard the notes, you can pin each one to the exact line it was about, and it will stay on that line while you rewrite around it. The comment system in this article is yours, not your reader's.

Making the link

Open the book and press the share icon in the side panel. Create Share Link has five things to set, and two of them you cannot change later.

1. Select Files. A checkbox tree of the book. Folders arrive collapsed, so open the one holding your episodes. Only files a reader can actually read are offered — screenplays, manuscripts, and the structured files (relationship map, timeline, world map, beat board). Images and PDFs are not in the list, deliberately: a reader who clicked one would land on a page with nothing but a title on it.
2. Version — Latest or Locked. See the next section; this is the one that bites.
3. Visibility — Link Only (the default: only people holding the URL, and search engines are told to stay out) or Password. There are only these two. Nothing you share is ever put on a public index.
4. Details — a Title (already filled in with the book's name), an Author (see below), and an optional Description.
5. Expires After — 7, 14, 30 or 90 days, or Never, which is the default. Set one for a submission; the point of a deadline is that it passes.

Allow Copy is on unless you turn it off. Then press Create Share Link and you get a /s/… URL with a Copy Link button.

Latest or Locked

Locked needs a book that has synced and has at least one version. If the button is greyed out it says which of the two is missing.

The byline is empty on purpose

The Author field starts blank, and that is the design, not an oversight. The grey text inside it is the name that will actually be printed if you leave it alone — your display name, which is your pen name when you have set one. Leave it empty and readers see that. Type something and they see what you typed.

It appears under the share title in the reader's sticky header. Separately, the screenplay's own title page prints the name under Written by from the top of the paper. Those are two different fields in two different places. If they should agree, set both.

What the producer actually sees

They open the URL. No account, no download, no app.

What loads, in order

The title page Scene by scene, in the file's own format Previous / Next, if the share holds more than one file

The reading page runs the same layout engine as Preview, so what you saw in Preview is what they see.

• The title page first: episode number, title, subtitle, the Written by label with the name from the paper, and the logline in italic underneath.
• The screenplay in that file's own format — Taiwan or Hollywood, whichever the file is set to. The reader has no switch. The file's own scene-number and scene-grid settings are honoured too.
• The filename is not shown. For a screenplay, the reader sees only the title you typed at the top of the paper — so if the tree says Episode 07 and the paper still says Untitled Script, the producer sees Untitled Script.
• A fixed reading width, a light/dark toggle, and a Powered by Slima line at the foot.
• On a phone: the same page. A Table of Contents drawer appears in the header only when the share holds more than one file — a single-episode share is just the screenplay, no menu.
• The page tells search engines to stay away, always, password or not.

What they cannot do

What you learn about the read

The link's card shows views and unique visitors. That is all of it.

• No names, no list of who opened it, no timestamps of individual opens.
• No notification, ever — not when someone opens the link, not when they finish it. If you need to know whether the producer read it before Thursday's meeting, Slima cannot tell you; the counter going up is the whole signal.

Their notes, on the line they were about

Now the half that is yours. You have the notes; put each one where it belongs.

Turning a phone call into something you can work from

Right-click the line Team → Add Comment Type what they said Rewrite; the comment stays on that line

A screenplay comment is anchored to the element, not to a character offset — so rewriting the line does not shake it loose.

• Right-click any line in a .script and the Team group offers Add Comment and Suggest Edit. A suggestion carries replacement text you can accept later; a comment is just a remark.
• The anchor is the line itself. Rewrite that line completely and the comment is still on it. The snippet the card shows you was captured when you made it and is not refreshed — the position is what matters, and the position holds.
• Delete the line and the comment is not deleted. It gets a Lost position badge and a note saying the original text has changed, and a suggestion in that state can no longer be applied. Nothing disappears silently.
• The panel is per book, not per file. Filter it with Current file only when you are working through one episode. For a note about a whole episode rather than one line, use Comment on this file in the panel header.
• Every line with open comments wears a small badge with the count.
• On a phone: tap a line to edit it, long-press to get the same menu with Add Comment and Suggest Edit on it.

What isn't there, plainly: no replies and no mentions. A comment is a single remark you later resolve; it is not a thread. And nothing notifies you when one appears, because in practice you are the person writing them.

Taking the link back

Revoke it from the same modal, or from Account → Share Links, which lists every link across every book with Active and Expired tabs and can revoke a selection or the whole lot at once. Revoking takes effect immediately — the reader's next click gets a not found page. The Privacy Centre lists these links too, under what you have opened to the outside.

When not to do it this way

• Don't send Latest for a submission. The reader's page changes under them while they are writing notes about it.
• Don't treat Allow Copy off as protection. It stops a casual selection and nothing more. And a share link carries no watermark — the watermark lives only in a merged multi-episode PDF export.
• Don't wait for notes to arrive in the app. They will not. Agree how the notes come back at the same time you send the link.
• Don't share the whole book when one episode was asked for. Tick one file. The reader cannot see what you did not tick, but they can see the list of what you did.

Related

• Docs: Sharing a screenplay: which files, who can open it, for how long
• Docs: Public read-only share link
• Docs: Reader View for recipients
• Docs: Inline comments
• Docs: Handing the screenplay over: one episode, one season, or the whole book
• Docs: Format switch: Taiwan and Hollywood