Editorial submissions
Build a packet from the debrief, send it to the publication, and track what comes back.
Updated Aug 14, 20264 min readApplies to 1.1.5
This is the flow the whole thing is named for. les Archives builds the submission, sends it to the publication, and tracks the conversation that follows.
Five minutes on the whole flow, from an editor's request to the packet going back out.
The publications
The publication list is fetched when the view loads, so what you see is the current list rather than something baked into the app. The canonical list inside the app holds fifteen titles, and a publication carries its name and nothing else:
Vogue Weddings · Over the Moon · The Wed · Style Me Pretty · Wed Vibes · Brides Magazine · Martha Stewart Weddings · Magnolia Rouge · Bridal Musings · Love My Dress · The Knot · Together Journal · Junebug Weddings · Green Wedding Shoes · Rock n Roll Bride
There is no tone field and no credit-format field. A title is a title. The words are yours.
Each publication is stored as free text on a submission, so a title that's not on the list can still be used.
Building one
Share, Submissions, New Submission. Four steps, with progress dots in the header.
1. Pick a wedding and a publication. Pick from the list or type a title of your own. Partner publications are marked.
2. Build the packet. We assemble a draft from the job's debrief, meaning the couple's story, the vendor credits and the venue notes, plus the frames you marked Featured or five-star, plus a hook and a write-up drafted for that publication. All of it's editable. Add images, cut images, reorder them, rewrite the hook, fix the credits. The star control on each thumbnail sets the cover.
3. Set up the page. This step is page settings, not a preview.
| Setting | Options |
|---|---|
| Expires in | 30, 60, 90 (the default), 180 or 365 days |
| Allow downloads | On or off |
| Watermark previews | On or off |
| Show vendor credits | On or off |
| Cover focus point | Drag to set where the cover crops from |
Under those is a summary: the wedding, the publication, the image count, whether a cover is set, whether the hook is written, the word count of the write-up, and the number of vendors.
4. Send. Preview your submission opens the finished packet so you can check it before it goes. Send to <publication> delivers it. No email to compose, no shared link to paste. You get Submission received back, with an acknowledgment from the publication.
Responses
Share, Submissions, Responses. Threads newest first, reply inline, approve or decline usage requests. One place for the whole conversation.
If an editor asks for a high-res original, that also lands in your High-Res Requests inbox. Approving uploads that one original for 72 hours. High-res requests, below, has the whole flow.
Approval rules
Share, Submissions, Approvals sets a rule per publication.
| Rule | Effect |
|---|---|
| Instant | Usage requests from that editor auto-approve |
| Review | They wait for you. This is the default |
| Blocked | Nothing from that editor is accepted |
Instant is for a publication you already have a standing arrangement with.
Taking one back
Archiving is how you withdraw a submission. There's no separate Withdraw button, and none is planned. Archive is the feature.
Archiving hides the submission from your active list and, if its page is still live, revokes the page first. The link stops working from that moment. No withdrawal notice is sent, so nobody is told. The row and its real status are preserved, so nothing is lost, and Restore puts it back on the active list.
If you need the publication to know, tell them. Use the thread in Responses.
Exclusivity isn't enforced by the app. If you're honouring a window, don't build a second packet for the same job until it ends.
Was this helpful
Still stuck
Tell us what happened and we will usually answer the same day. If it is more of a question than a bug, ask the room. Every tester reads it, and you are already signed in.