Safe Collaborative Call Editing
Use ownership, conflict protection, review checkpoints, and recovery evidence when several staff members build a call.
Last reviewed · Editorial policy
Prevent silent overwrite, then govern the work
Call-editor conflict protection detects when the record a staff member started editing has changed before their update is saved. The safe response is to compare versions and merge deliberately, not to force the older draft over the newer one.
Assign ownership
Give one person final responsibility for dates and publication. Assign section owners for eligibility, fields, fees, jury configuration, legal terms, email, and accessibility. Limit edit permissions to people who need them; reviewers do not automatically need publishing authority.
Work in checkpoints
Before major editing, agree on the current draft and change scope. Save meaningful increments and record why high-impact settings changed. Recheck dependencies when editing a deadline, fee, category, identity rule, jury round, or template variable.
Resolve a conflict
When conflict protection warns that the call changed:
- Preserve the unsaved text outside sensitive fields if necessary.
- Reload the current version and identify the other change.
- Merge only the intended sections.
- Retest the applicant, juror, and email consequences.
- Record the resolution owner for material policy changes.
Do not treat repeated conflicts as user error. They often reveal unclear section ownership or too many administrators editing during the same release window.
Review before publication
Use a four-role walkthrough: applicant, juror, administrator, and finance or operations owner. Verify dates and time zones, fees and waivers, required fields, redaction, conflicts, round transitions, templates, recipients, public branding, accessibility, and exports.
Keep recovery evidence
Retain the approved prospectus and a snapshot or export of the published configuration. If an urgent correction is needed after launch, record what changed, who approved it, which applicants were affected, and whether communication or remediation is required.
Conflict protection is a current capability and is not behind a rollout flag. Normal organization permissions determine who can edit and publish.
Related guides
How to Set Submission Fees for a Call
Build a transparent fee from the program budget, access goals, member policy, application structure, and artist communication.
Jury Decision Email Templates
Accessible acceptance, waitlist, decline, and late-invitation templates with a safe verification workflow.
The True Cost of Managing Art Submissions in Spreadsheets
An editable way to measure staff time, error risk, communication work, and handoffs in a spreadsheet-based submission process.