These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Print Media / Newspaper
- Features
- Editorial Desk
Editorial Desk
Assign reporters to edition stories and follow desk progress.
OverviewMy Staff Record×
Print Media / Newspaper · Editorial Desk
New
My Staff Record
People
| Name | Role title | Active | User | |
|---|---|---|---|---|
| People 868 | People 1 | ACT-756 | ||
| People 120 | People 2 | ACT-656 | ||
| People 108 | People 3 | ACT-343 | ||
| People 351 | People 4 | ACT-520 | ||
| People 123 | People 5 | ACT-284 |
6 of 6 records
People 868People · PPL-75851
Role titlePeople 1
ActiveACT-756
What you can do
Give each story a clear desk assignment
The Editor records an assignment with an edition date, desk, story title, reporter, deadline and status. The Reporter then works from the assignment instead of relying on a separate message to know which edition needs the story. A desk can see which assignments are still assigned, drafting or editing, and which have reached approval or publication.
For a local news edition, enter the edition date and the desk that will handle the story. Pick the Reporter from the people directory and set a deadline early enough for editing. The assignment is a desk record. The related content item carries its own owner, project, due date and publication lifecycle. Agree how your team names both records so a desk assignment can be followed through to its story without treating them as the same table.
How the work is organized
- Edition date. Assignments belong to a particular print date so the Editor can review the day’s desk load.
- Reporter. The Reporter reference makes responsibility explicit and lets the desk identify that person’s work on the assignment board.
- Status. Assigned, drafting, editing, approved and published show progress on the desk record.
The capture workflow checks the edition date, desk, title, reporter, deadline and status. It resolves the reporter and linked assignment before saving a business-eligible status. Repeated submissions are handled as retries, while rejected or conflicting requests remain distinct. These checks matter when assignments arrive through a custom page as well as when a record is created in the app.
What to agree during setup
Choose consistent desk names and decide when an assignment should be moved to drafting. Agree whether the Editor or Reporter updates each desk state. Confirm that every reporter has a person record connected to the intended user. Use a deadline convention that leaves time for file review, rights checking and layout before the edition date.
The desk status is useful for planning, but final publication belongs to the content item’s approved-to-published path. The Editor should review both records during handoff. An assignment marked approved means the desk has accepted that stage; the exact file revision still needs its own approval before publication.
Check the handoff on an actual case
Assign a Reporter to a local council story for a Friday edition. Give the story a deadline before layout begins. Have the Reporter open Assignment Board, find their story, confirm the desk and deadline, and move the assignment into drafting. The Editor opens Assignment Board to see the story alongside other work. Record the corresponding content item under the right edition project and follow it into review.
Try a repeated capture with the same business request. The result should refer to the accepted assignment rather than create duplicate desk work. If the reporter or date is wrong, correct the record through the agreed desk procedure before the assignment is treated as publishable work.
What your team sees
- Assignment Board — Scan desk stories by status and reporter.
- Staff Directory — Check the reporter’s person record and linked user.
- Content Pipeline — Follow the corresponding story through editorial review.
Follow the work through
Use desk to review for the working sequence and content approval for the revision decision.
What it keeps track of
Data model- Editorial assignments
- Desk assignments linking reporters to stories for a specific edition.
- People
- Staff and contributors who own, produce, review and deliver print media work.
- Users
- Users
- Content items
- Individual stories, features, columns and advertising content produced for a project.
- Projects
- Editorial and commercial projects such as editions, supplements and special sections.
Who uses it
Permissions- Editor
- , Reporter, Admin.
Set up Print Media / Newspaper your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.