How to publish conference proceedings without creating rights problems

You've accepted the papers, announced the programme and promised delegates a copy of the proceedings. Then an author asks whether their employer has approved publication. Another wants their paper kept offline until a journal makes a decision. Your designer has already assembled the download.

The first thing you want to settle is what you're publishing and who can authorise it. Agree the publication format, audience, permitted uses and approval process before you invite final papers or sell access. Accepting someone to speak doesn't answer those questions, even when the paper and the presentation have the same title.

For a paid conference, proceedings can be a useful part of the offer. Delegates can revisit the work, follow the references and share what they've learned with colleagues within the agreed terms. But you need a deliverable you can actually produce. A smaller collection with clear permissions is easier to stand behind than a complete volume that depends on unresolved promises.

This guide walks through the decisions, an author brief and a worked publication plan. The copyright sources explain the jurisdictions or licences stated. Have a qualified adviser adapt your publication agreement to the countries and rights involved; the planning examples below aren't a ready-to-sign contract.

Start by defining what proceedings means at your event

Conference proceedings are a published collection of contributions associated with the event. That could mean full research papers, extended summaries or an abstract collection. Decide which you're producing. A programme listing and a folder of presentation slides aren't automatically the same thing as a reviewed volume of papers.

Imagine you're running a paid conference for museum managers. Contributors discuss access projects, visitor research and collections practice. Some have formal studies ready for publication. Others can discuss an early project but cannot release the underlying report. You don't need to force every contribution into the same publication commitment to run a useful conference.

You could publish approved abstracts before the event and release selected full papers afterwards. You could produce only an abstract collection. Or you could work with an established publisher on a defined volume. Each option creates different work for authors and different expectations for buyers. Choose the version your team can deliver, then name it accurately everywhere.

Write a short specification before asking for submissions. State the content type, expected length, language, format, release date and intended reader. Explain whether the collection is public, included with registration or sold separately. If there will be a later public release, say when. Specify whether readers download files or read them on a website.

Also describe the editorial process honestly. If a committee checks relevance and clarity, explain that. If subject specialists conduct a documented peer review, describe that process and its limits. Don't advertise peer-reviewed proceedings simply because someone selected the speakers. The phrase makes a claim about how the published work was assessed.

Our guide to organising a paid conference covers the wider event commitments. Treat the proceedings as one defined deliverable within that plan, with its own owner, budget and approval dates. Otherwise, it becomes the task everybody assumes the programme chair will finish after the event.

Keep presentation acceptance and publication permission separate

An acceptance email might confirm a session slot, a poster space or inclusion in the programme. It should also say whether publication is required, optional or subject to a separate decision. Authors need to know what they're agreeing to before paying registration or arranging travel.

For the museum conference, you might accept an oral presentation on a pilot project while inviting only its abstract into the proceedings. The author could later submit a full paper under a separate publication process. Keep those decisions visible. A file uploaded for reviewers to assess shouldn't quietly become the file delegates receive.

The U.S. Copyright Act's ownership provisions distinguish rights in an individual contribution from rights in a collective work. Producing the volume doesn't automatically give you ownership of every paper inside it. The same provisions cover authorship and ownership of certain work created for employers. Check who actually holds the relevant rights rather than assuming the person who emailed the file owns them.

In practice, ask the submitting author to identify the rights holder and confirm their authority to arrange the proposed publication. Where there are coauthors, employer interests or an earlier publishing agreement, resolve those before release. Your process can require documented approval from everyone relevant without pretending one country's ownership rules apply everywhere.

An established publisher may prescribe its own agreements. For example, Springer Nature's conference proceedings process requires a publishing agreement for each contribution and says the corresponding author signs after gaining coauthors' permission. That is a requirement of its process, not a universal form every conference should copy.

If you use a publisher, agree the route with it before issuing your own conflicting terms. Authors shouldn't receive one message saying they retain unrestricted control and another requiring a different arrangement after their paper has been accepted. Ask the publisher who contracts with whom, which agreement applies and when authors will see it.

Keep your speaker agreement focused on the appearance and any agreed recording or materials uses. Cross-reference the publication agreement where appropriate, but don't make the author discover an unexpected publishing obligation inside a generic speaking clause. Someone can agree to deliver a talk while withholding permission to publish the underlying paper.

Ask for the uses you need, then explain them

A licence is permission to use material under stated conditions. An assignment transfers ownership of specified rights. For a conference publishing a defined collection, start by discussing the permission you need rather than demanding ownership of everything the author has written. If your business needs an assignment or exclusive rights, get that arrangement reviewed and explain its consequences clearly.

Describe the uses in ordinary language before turning them into agreement wording. You may need to reproduce the final paper, format it for the collection, distribute copies to registered delegates and keep an archive available. You may also want to publish the title and abstract publicly so people can discover the work. Those are distinct decisions.

Work through the following questions with your editor and adviser:

• Which exact contribution and approved version does the permission cover?

• Who may publish it, and which named publisher or production suppliers may handle it?

• Can it appear online, in a downloadable collection, in print or in each of those formats?

• Who may access it, where may they be located and how long will it remain available?

• Is access included in a ticket, separately charged or freely available?

• Which edits are allowed, and which changes require the author's approval?

• Can you publish an abstract or excerpt to describe the collection?

• What happens to the archive if the conference business changes owner or hosting provider?

Don't ask for every imaginable future use because it saves drafting another agreement. Translation, an audio edition, paid advertising and reuse in a commercial course may have nothing to do with delivering this year's proceedings. If you need them later, discuss them separately. A clear initial request also makes it easier for an author to ask their employer for approval.

Your production supplier needs corresponding instructions. A typesetter may need to open, format and return the manuscript. That doesn't mean they can add it to their public portfolio or use it for another purpose. Confirm permitted handling, confidentiality and deletion or retention arrangements in the supplier agreement, including any subcontractors involved.

Be explicit about automated processing where it matters. Ask whether the supplier will upload unpublished papers into outside tools, and whether those services retain submissions or use them for their own purposes. Decide what your agreement permits. Do not promise authors a restriction your supplier cannot meet, or promise readers rights the authors haven't granted.

Set the archive term thoughtfully. A promise of permanent availability involves hosting, maintenance and future correction work. A short access period may suit a practical delegate pack, but it may be unsuitable for authors expecting a lasting scholarly record. Resolve the difference before choosing the publication route. The agreement and the buyer's description should tell the same story.

Check material inside the paper, not just its cover page

An author can write the paper and still include material they don't control. A photograph, reproduced diagram, long quotation, client screenshot or previously published table may need a separate assessment. Ask about those items when the manuscript arrives, while there is still time to replace them.

The U.S. Copyright Office's guidance on using someone else's work explains that fair use depends on the circumstances and has no automatic word-count or percentage allowance. Don't approve every short extract under an invented numerical rule. Where a use depends on an exception, have the appropriate person assess that use under the applicable law and your publisher's requirements.

For the editorial workflow, give each paper a list of material requiring attention. Record the item, its creator or rights holder, the source, the basis for use and any conditions. Some items may be original to the authors. Others may have a suitable licence, written permission or a reviewed legal basis that doesn't require permission. Uncertain items stay unresolved until someone makes and records the decision.

A credit line identifies the source. It doesn't, by itself, authorise reproduction. If an author writes "image courtesy of the museum", ask what that permission actually covers. Displaying an image during a talk may involve a different arrangement from placing it in a downloadable paper that remains online or is sold to people who never attended.

For example, a contributor might have permission to include a collection photograph in an internal project report. Your proceedings will reach paying delegates outside that organisation. Ask for the required additional permission or an alternative image. Don't let the designer recreate the same photograph or lightly redraw a protected illustration as a supposed workaround.

Track restrictions at item level. A paper might be available under one licence while a particular image is excluded and carries its own credit and terms. The final layout must make that distinction understandable. Check the figure caption, the paper's rights notice and the collection's general notice together so they don't contradict each other.

Keep confidentiality and privacy questions separate from copyright. A researcher may own the words describing a project while still being unable to publish identifiable participant information or confidential client material. Ask authors to confirm the necessary approvals for publication, and escalate concerns to the relevant institution or adviser. Removing a person's name may not be enough when the surrounding detail identifies them.

Give unresolved items a deadline and a practical alternative. The author can secure the necessary permission, replace the item, remove it with a coherent revision or withdraw the paper from publication. Your editor checks the revised argument still works. An empty space where the evidence should be isn't a useful solution for the reader.

Choose access terms that match the licence

Public access, free access and permission to reuse aren't interchangeable. A reader may be able to open a paper online without having permission to republish it. Equally, a paper with a broad public licence may allow redistribution even if your event sells a convenient printed edition. Explain which arrangement applies instead of describing everything as open access.

Under Creative Commons Attribution 4.0, compliant users may share and adapt licensed material, including commercially. Attribution and other conditions apply, and you cannot add legal or technological restrictions that remove the freedoms the licence grants. Check the actual licence before promising exclusive access or preventing permitted sharing.

That can be a good fit when authors and organisers want wide reuse. It can also conflict with a business plan built around exclusive access to the papers. Selling a publication and allowing licensed redistribution are compatible choices, but buyers should understand what they're buying. They may value the event, editorial work or a printed copy rather than exclusive possession of the text.

Other Creative Commons licences carry different conditions. The Creative Commons frequently asked questions explain that NonCommercial depends on the use, not simply whether the user is a business or nonprofit. They also explain that granted licences are generally irrevocable for compliant users. Don't select a licence on the assumption you can reverse it when a later sales opportunity appears.

If you want to use material under terms that don't permit your intended activity, ask the rights holder about separate permission or choose different material. The same applies when a figure has a more restrictive licence than the surrounding paper. Keep the evidence of that decision with the contribution rather than relying on a general label on the collection's cover.

For a restricted delegate collection, describe reader permissions precisely. Can the buyer keep a downloaded copy? Share it with colleagues? Print one for their own use? What remains accessible after the website access period ends? Have the terms reviewed against the author agreements and applicable law. Don't tell readers a download disappears when an online login expires.

Consider whether the extra restrictions are worth administering. If your audience mainly wants a useful reference after a paid conference, a clear personal-use arrangement may serve the offer better than a complicated set of access tiers. If authors need a public scholarly publication, work from that requirement instead. The conference's commercial model has to accommodate the publication you promised contributors.

Make embargoes and later publication decisions early

An embargo is a restriction on release until a stated time or condition. It needs to identify what is held back. A full paper may be restricted while its title and abstract are public, or the whole contribution may need to remain private. Ask rather than assuming the author means every file bearing their name.

Separate the sources of a restriction. A publisher may have terms about an earlier version. An employer may require approval before public release. A collaborator may be waiting for a patent review or contractual clearance. Those are different problems, and your programme chair cannot resolve all of them by moving the website date.

Ask contributors whether the work has been published, submitted elsewhere or made available as a preprint, which is a version shared before formal publication. Request enough detail for the intended publisher or editor to assess eligibility. Don't promise that appearing in your proceedings will have no effect on future journal submission. The relevant journal or publisher must confirm its own policy for the particular version and use.

Put restrictions into the production record. Name the affected paper and version, the prohibited release, the permitted public information, the release condition and the person who confirms it. Include a time zone for timed releases. "After the conference" is too vague when the website, email and print contractor each work to a different schedule.

If a paper cannot be cleared by your production deadline, decide what you can deliver instead. You may include an approved abstract and a note that the full paper isn't included. You may hold the contribution for a later release, provided that fits the agreement and buyer promise. Or you may omit it. Don't publish first because the author expects permission to arrive tomorrow.

Check previews too. The website's search listing, a sample download, a scheduled email and a shared proof link can expose material before the official launch. Give the marketing team the approved title, summary and release date rather than forwarding the whole production folder. Authors should know which information you intend to make public before the paper itself.

Our guide to a call for conference proposals helps you explain requirements before people apply. Put the publication route and the questions about existing commitments in that call. Discovering a restriction during submission is much easier to manage than discovering it after you've sold a package promising the complete papers.

Send authors a brief they can act on

Your author brief explains the practical arrangement. The publication agreement records the rights and obligations. They should agree with each other, but the brief still needs to make sense to someone trying to work out what to submit on Friday. Don't send a contract attachment as your entire set of instructions.

Here's an original example for the fictional museum conference. Adapt the decisions before using the wording. The dates and quantities are planning assumptions, not publishing standards, and the example assumes the organiser has separately obtained suitable publication agreements.

Example author brief

We are preparing a digital collection of selected papers from the Museum Access Conference on 20 May 2027. The collection will contain approved full papers and will be released to registered delegates on 3 June 2027. It is separate from the programme and the presentation recordings. Publication is optional for accepted presenters.

Please submit your final paper by 16 April 2027 using the supplied accessible document template. Include the paper title, all authors in the agreed order, affiliations, abstract, references and figure captions. Send editable files and any original figure files through the submission route in your acceptance email. Tell us if you need an alternative submission format.

The submitting author must identify the rights holder and confirm authority to arrange publication, including the required coauthor and employer approvals. Please disclose earlier publication, current submissions elsewhere and any restrictions affecting this version. Our editor will confirm whether the paper is eligible before it enters production.

List third-party items separately and provide the source, permission or other reviewed basis for use, and required credit for each. Tell us about confidentiality or participant-information concerns before submitting the final manuscript. If an item cannot be included, supply an approved replacement or a revised paper by the editorial deadline.

We will return one consolidated set of editorial queries by 23 April. Please answer by 30 April. We will send the publication proof on 7 May and need your explicit approval of that identified version by 12 May. We will not treat a missing response as approval. Material changes after approval require another review and may affect inclusion.

The agreed publication terms cover a downloadable digital collection for registered delegates, with the collection page available through 30 September 2027. Delegates may retain downloaded copies under the supplied reader terms. There is no planned public full-paper release, printed edition, translation or separate sale. Any proposed additional use will be discussed separately.

The public programme will contain the approved title, author details and abstract. It will not include your full paper. Send corrections and publication questions to the editorial contact in your acceptance email. Include your paper identifier so we can locate the correct contribution. We will acknowledge requests and explain the next action rather than silently replacing a released paper.

What that brief still needs behind it

The example shows contributors the deliverable, dates and choices in language they can use to plan their work. Your publication agreement still needs to settle responsibility if something goes wrong, which country's law applies and how disputes will be handled. Have those terms reviewed for the actual arrangement.

Check that your team can meet each promise. If you cannot return queries by the stated date, move the schedule before sending it. If an external publisher controls proof approval, use its actual process. And if author approval arrives after the deadline, record the new decision rather than pretending the original timetable still applies.

Give every paper a clear publication record

You need to be able to answer a simple question for each contribution: can this exact file be published in this exact collection? A folder containing a manuscript and several encouraging emails doesn't necessarily give your production manager that answer.

Use one record per contribution. It can be a structured tracker or a function of your publishing system. Include the paper identifier, title, authors, corresponding contact, approved manuscript version, rights holder, agreement reference, third-party items, restrictions, proof approval and release decision. Keep sensitive correspondence accessible only to people who need it.

Give statuses practical meanings. "Received" says a file arrived. "Editorially accepted" says it meets the collection's editorial requirements. "Permissions complete" says the required publication checks are resolved. "Proof approved" identifies the version the author accepted. "Released" records what actually went out and when. Don't make one green label stand for all of those decisions.

For the museum conference, paper M07 might be editorially accepted but awaiting a photograph permission. Paper M12 might have complete permissions but still need its author to approve a corrected affiliation. Both remain out of the release package until the outstanding action is resolved. Neither should hold up a ready paper unless the collection's publication plan requires a complete volume.

Assign one person to make the release decision and another named person to cover their absence. The editor can assess the content while an administrator checks agreements, but somebody must confirm the combined result. Ask the designer to use only the files marked for production. They should not have to interpret a rights dispute from a forwarded conversation.

Keep versions identifiable. For example, record "M07, approved proof dated 12 May 2027" and store the author's response against that file. If the designer replaces an image afterwards, stop and check whether the replacement needs fresh editorial or author approval. The fact that most of the paper is unchanged doesn't settle the new item's status.

Before release, compare the collection's contents list with the tracker and the actual files. Check titles, author order, captions and notices in the finished output. This catches the practical mistake where the right paper was approved but the wrong PDF was exported. Test download links using an ordinary reader's access, rather than only the administrator's account.

Make the publication useful to read and cite

Permissions work matters because you're producing something people should be able to use. Ask authors for structured source documents early. A scanned paper with no usable text creates avoidable difficulty for searching, reading and preparing accessible formats. Fixing that after release is slower than requesting a suitable file at submission.

For a web edition, follow the W3C's guidance on page structure: use meaningful structure and logically organised headings so readers can navigate the work. A visually prominent heading isn't enough if the underlying page doesn't identify it. Apply the same care to the collection directory so people can find a paper without opening every file.

Tell the production supplier what accessibility work is included and how it will be checked. For downloadable documents, agree appropriate document-specific requirements and testing. Ask for selectable text, clear reading order, useful headings, readable tables and explanations of meaningful figures. Work with authors on descriptions that preserve the evidence rather than asking a designer to guess what a technical chart means.

Use accurate publication details. Include the conference title and date, contribution title, authors, collection editor where applicable, publication date, version and relevant rights notice. Make it clear whether the contribution is an abstract, a full paper or another format. Consistency helps a delegate cite the same work a colleague actually read.

If you plan to register digital object identifiers, usually called DOIs, agree who will register and maintain them. These identifiers help people refer to and locate published work. They don't replace the publication agreement or prove the paper was reviewed. Don't advertise registration, database inclusion or indexing that hasn't been arranged and confirmed by the responsible service.

Crossref's conference proceedings guidance distinguishes conference, proceedings and paper information. Its paper guidance includes titles, publication dates, contributors, references, licence information and whether the item is full text or an abstract. Use the requirements of the service you're actually using rather than inventing a single label for every file.

If your output is a temporary delegate pack, you may not need a formal scholarly publishing route. Say that clearly. Authors who require a recognised proceedings publication need to assess the proposed arrangement before joining, while delegates mainly need an accurate description of what they'll receive. Neither group benefits from impressive publication language that your delivery cannot support.

Budget for publishing before adding it to the ticket

Proceedings create work even if every author contributes without a publication fee. You may need editing, permissions administration, layout, accessibility work, hosting and reader support. Ask suppliers what their price assumes about manuscript quality and revision rounds. A quote for formatting clean files may exclude the work your submissions actually require.

Here is a fictional digital collection budget in USD. The figures illustrate the decision; they aren't market rates. Assume twelve papers, no printing, no author fees and all supplier amounts inclusive of purchase taxes. The conference's existing event costs are already committed. This calculation covers only the additional publication project and excludes wider business overhead, borrowing and income tax.

Editing costs $900, layout costs $600 and accessibility preparation and checks cost $450. Hosting and delivery cost $150. Publication administration takes twelve paid hours at $30 per hour, adding $360. Allow another $240 for corrections or other publication work and assume that allowance is fully spent. The total additional cost is $2,700.

With 180 paid delegates receiving the collection, that cost works out at $15 per delegate. That is a way to allocate the publication cost across the package. It does not prove the proceedings created 180 ticket sales, or that charging another $15 would leave demand unchanged. You still need to test whether the overall conference offer supports its price.

If you instead propose a separately sold edition, calculate the amount you keep from each sale. Suppose the buyer pays $40 and you retain $36 after the applicable transaction charges and sales taxes. Additional fulfilment costs $3 per copy. Each retained sale then contributes $33 towards the $2,700 project cost. For this simplified example, assume no refunds or other income and sufficient permission for the separate sale.

You would need 82 sales to cover that cost because 81 sales contribute $2,673 and 82 contribute $2,706. At sixty sales, contribution is $1,980 and the project is $720 short. Those sales are an assumption, not a forecast. Before changing the publication model, ask whether you have an audience willing to buy and authors who have agreed to that distribution.

Don't count the same money twice. If a sponsor has already committed funding specifically for the publication, record the confirmed amount and associated costs. If proceedings are included in conference registration, a delegate's ticket isn't also a separate proceedings sale. Our event budget guide helps you keep the publication decision connected to the conference's full costs and income.

Check payment timing as well. A profitable plan can still require money before it arrives. In this example, suppose $1,500 of the publication bill is due before release but only $900 has been allocated in available cash. You need to arrange the $600 timing gap or revise the commitment. That gap isn't another cost to add to the $2,700 total, unless arranging finance creates an actual additional charge.

Describe the buyer's access before taking payment

A buyer should be able to tell what the collection includes, when it will arrive and how to obtain it. "Proceedings included" doesn't answer whether they're getting approved abstracts, full papers or slides. State the format and release date near the ticket description, then repeat the relevant access instructions in the post-purchase communication.

For the fictional event, you could describe a digital collection of selected approved full papers, released to registered delegates on 3 June. Explain that presentation recordings aren't part of that collection and that the online collection page remains available through 30 September. The reader terms should separately explain that delegates can keep the files they download.

Avoid promising a fixed set of named papers until you have the permissions and approvals to supply them. If an accepted session may not have a published paper, make that distinction before purchase. For material changes to an offer already sold, get the appropriate consumer and contractual advice and communicate the actual remedy. A quiet change to the website doesn't resolve an earlier promise.

Loopyah's ticket selling tools let buyers choose ticket types at their current prices and receive confirmation linked to their QR tickets. Use the ticket description to make the event package understandable. Publishing permissions, hosting the collection and delivering the files still need an agreed process; don't treat a ticket confirmation as evidence that those arrangements are complete.

Test access from the delegate's perspective. Can they find the collection without knowing an internal folder name? Does the link work with the account or email they actually used? Is the support contact monitored after the event? If one person purchased several registrations, decide how each entitled reader receives access without exposing the other buyers' details.

For a conference poster session, confirm separately whether contributors permit their poster, abstract or full paper to appear in the collection. Physical display at the event and downloadable publication serve different uses. A delegate who enjoyed the conversation at a board shouldn't be promised a full paper the presenter never agreed to supply.

Plan corrections while the editor is still available

Someone needs to look after the publication after launch. Give authors and readers a clear contact route for errors, disputed permissions or material that should not have been released. Assign responsibility through the stated access period and agree what happens afterwards. Don't leave the only working contact as an event inbox that nobody checks in June.

Distinguish a minor factual correction from a concern about the reliability or lawful publication of the work. A misspelled affiliation may need a documented correction. A missing permission, confidential disclosure or serious research concern needs assessment by the editor and the appropriate rights, institutional or legal contact. Your response should fit the issue rather than treating every complaint as a request to swap a file.

Keep an incident record with the affected paper, version, request, evidence, decision owner and action. Preserve the evidence securely while assessing it. If temporary access restriction is appropriate, record why and coordinate it with the publisher or adviser. Don't circulate the disputed material more widely by forwarding it through an unrestricted team conversation.

When you release a correction, identify the change and the corrected version so readers can understand what happened. Update the collection directory and other places you control that point to the old file. If identifiers or external publication records are involved, work with the responsible publisher to maintain those records too. A new file in your own folder doesn't automatically update every reference elsewhere.

Be honest about what you can retrieve. You can replace or remove a hosted file within your control, but you generally cannot make every earlier downloaded copy vanish. Public licensing may also allow compliant users to keep using copies. That is another reason to check the approved version carefully before release and avoid promising authors an absolute recall capability.

For the museum conference, suppose M07's author reports an incorrect figure caption after launch. The editor checks whether it is a wording error or changes the interpretation of the results, agrees the response and records the corrected version. Delegates receive a clear notice if the correction affects their use of the paper. The response explains the actual change rather than merely announcing that the download has been refreshed.

Before approving the next collection, review the work you actually had to do. Which permissions delayed production? Which instructions confused contributors? How many paid hours went into chasing proofs and supporting readers? Use that record to change the next submission brief and budget. If your team cannot maintain a full-paper publication properly, choose a smaller, clearly described collection before inviting the next round of papers.