Tools · Call for papers

The whole call for papers from the conversation: opening the call with its guidelines, the tracks and the event days, publishing, setting up the committee, following the reviews, deciding, negotiating terms with the speaker and confirming in the program. Proposers use the assistant too: submitting and editing a proposal, answering a counter-offer, voting.

Each tool carries a badge: Read-only changes nothing, Changes creates or changes something right away, and Asks to confirm only acts after your yes to a summary. See Money and confirmation.

#Who uses what

All 40 tools show up for every role, members included: a call's owner can be a regular member, and so can whoever proposes, reviews or votes. Memberfy checks each call against the module's own rules, just like the screen does:

When the role doesn't allow it, the assistant gets Memberfy's refusal and explains it.

#In short

#The space and the calls

#Tracks and event days

#Owners, reviewers and speakers

#Review, decision and program

#Voting

#The proposer

#Ids and values

• Call (call) and space (space): the id or the link copied from the app. A proposal's link (?proposal=) also works as the call.
• Proposal (proposal): the id or the link with ?proposal=.
• Track, event day, owner and reviewer (track_id, date_id, owner_id, reviewer_id): they come from get_call_for_papers. The owner_id is the id of the link in owner_links, not the person's id.
• Person (profile_id): from list_members or from list_speakers.
• Dates and times: in the community's time zone. Date and time as 2026-11-30T23:59; date only as 2026-11-30; time only as 19:00.
• Formats: talk, lightning_talk, keynote, workshop, tutorial, masterclass, panel, roundtable, case_study, demo, poster and other.
• Call statuses: draft, open, reviewing (under review), deciding, closed and archived.
• Costs (airfare, ground transport, parking, accommodation, meals): none (nobody), organizer (the organization) or speaker (the speaker).

#list_calls_for_papers

Read-only

List calls for papers. The calls of a call-for-papers space, with status. Minimum role: any; a draft only shows up for whoever looks after it.

Ask like this: "Which calls are open?"

#get_call_space_settings

Read-only

See call-for-papers space settings. Whether the space is one call or several, who can open a call and whether opening one needs approval. Minimum role: any.

Ask like this: "Can a member open a call in the Talks space?"

#update_call_space_settings

Changes

Change call-for-papers space settings. Changes the space's mode and who can open a call. Minimum role: admin.

Ask like this: "Let moderators open calls in the Talks space."

Notes: it changes who can do what right away. See The space: one call or several.

#get_call_for_papers

Read-only

See call for papers. Everything the call's page shows: status, dates, formats, costs and fee, the tracks (with their reviewers), the event days and the owners, plus what you can do in it. Minimum role: any; a draft only for whoever looks after it.

Returns: the call and, for whoever can edit it, the owners' links (owner_links), with the ids that remove_call_owner asks for.

Ask like this: "Show me the Congress 2027 call: which tracks are there and who reviews each one?"

#create_call_for_papers

Changes

Open call for papers. Opens a call in a call-for-papers space, as a draft. Whoever creates it becomes the call's owner. Role: whoever the space's rule allows to open a call.

Returns: the created call. A bad image doesn't stop the creation; the reason comes in warnings.

Ask like this: "Open the call for Congress 2027, in person in São Paulo on March 12 and 13, with the tracks Product, Data and Career. Proposals until November 30. We pay for lodging and meals; travel is on the speaker. Leave it as a draft and show me."

Notes: the call starts as a draft; publish it with update_call_status. After it's created, the response suggests what's missing: tracks, reviewers, publishing. The fee is recorded in the agreement; payment happens outside the platform.

#update_call_for_papers

Changes

Edit call for papers. The same fields as create_call_for_papers, except tracks and days, which have their own tools. Only what is sent changes. Role: the team or the call's owner.

Ask like this: "Extend the Congress 2027 proposal deadline to December 15."

Notes: a call that already has scores or a negotiation can't go back from advanced to simple.

#update_call_status

Changes

Publish, close or reopen call. Changes a call's status. Role: the team or the call's owner.

Ask like this: "Publish the Congress 2027 call." · "Close the call: the deadline has passed."

#delete_call_for_papers

Asks to confirm

Delete call for papers. Deletes the call, with its tracks and proposals. Role: the team or the call's owner.

Returns: on the first call, the summary (title, status, how many proposals) and the confirmation code.

#add_call_track

Changes

Add track to call. Role: the team or the call's owner.

Ask like this: "Add the Data track, for real data analysis and engineering cases, no tool tutorials."

#update_call_track

Changes

Edit track. Renames a track or changes its purpose. Role: the team or the call's owner.

#delete_call_track

Asks to confirm

Delete track. Role: the team or the call's owner.

#add_call_event_date

Changes

Add event day to call. Role: the team or the call's owner.

#update_call_event_date

Changes

Change event day times. Role: the team or the call's owner.

#delete_call_event_date

Asks to confirm

Remove event day. Role: the team or the call's owner.

#add_call_owner

Changes

Invite call co-owner. Invites a member to share the call with you: an owner looks after the call, the tracks, the reviewers and the decisions. The person accepts with respond_to_call_invitation. Role: the team or the call's owner.

Notes: it gives power over the call, and the person gets the invitation by e-mail.

#remove_call_owner

Asks to confirm

Remove call owner. Role: the team or the call's owner.

#list_track_reviewers

Read-only

List track reviewers. A track's reviewers and whether each one has accepted. Role: the team or the call's owner.

#invite_track_reviewer

Changes

Add track reviewer. Makes a member a reviewer for a track: they score every proposal in that track. Role: the team or the call's owner.

Ask like this: "Make Ana and Bruno reviewers for the Data track."

Notes: the person finds out by e-mail, on the first call.

#remove_track_reviewer

Asks to confirm

Remove track reviewer. Role: the team or the call's owner.

#list_my_call_invitations

Read-only

My call invitations. Your pending invitations to be a call's owner or a track's reviewer. Minimum role: any.

Parameters: none.

Ask like this: "Do I have any invitations to review proposals?"

#respond_to_call_invitation

Changes

Answer call invitation. Minimum role: any, on your own invitations.

Notes: accepting a reviewer invitation leads to your review queue (list_my_reviews).

#list_speakers

Read-only

List speakers. Everyone who has proposed in the community, grouped by person, so you can invite them again. Role: the team or a call's owner.

#invite_speaker

Changes

Invite speaker to submit. Invites a member to send a proposal to a call, with an optional note. Role: the team or the call's owner.

Ask like this: "Invite last year's speakers to propose again for Congress 2027."

Notes: it sends an e-mail on the first call.

#list_proposals

Read-only

List a call's proposals. The proposals, with status, track and scores. Role: what shows up depends on your role in the call: owners see all of them, a reviewer those in their track, a proposer their own.

Ask like this: "Which proposals in the Product track have the best scores?"

Notes: with proposals waiting for a decision, the response suggests deciding each one.

#get_proposal

Read-only

See proposal. The text, the track, the status, the reviews you can see and the negotiation rounds. Role: the call's owners, the track's reviewers and the proposer.

#list_my_reviews

Read-only

My review queue. The proposals in the tracks you review, with your score when you've already given one. Role: reviewers.

Parameters: none.

Ask like this: "What do I still have to review?"

#review_proposal

Changes

Review proposal. Scores a proposal in a track you review. Role: a track reviewer who accepted the invitation.

Ask like this: "Give Ana's proposal a 4, recommending acceptance: the topic is great, but the outline needs a real case."

Notes: only during the review period, and never on your own proposal.

#get_review_progress

Read-only

See review progress. How many reviews each proposal and each reviewer has, against the call's minimum. Role: the team or the call's owner.

Ask like this: "Who on the committee hasn't reviewed yet?"

#get_proposal_reviews

Read-only

See proposal reviews. Each score and recommendation, and the consensus. Role: the call's owners; a reviewer, after sending theirs.

#decide_proposal

Changes

Accept or reject proposal. With an optional message to the proposer. Role: the team or the call's owner.

Ask like this: "Accept Ana's proposal and thank her for submitting."

Notes: the person receives an e-mail on the first call, which is why the assistant checks the decision and the message with you first. After accepting, the response suggests confirming in the program. See Call for papers emails.

#negotiate_proposal

Changes

Negotiate proposal. The organizers' side of a negotiation (advanced call, with counter-offers turned on). Role: the team or the call's owner.

Ask like this: "Propose to Ana that she runs the workshop in 90 minutes instead of 3 hours, with lodging on us."

Notes: each step e-mails the proposer, on the first call.

#confirm_proposal

Changes

Confirm proposal in the program. The final step of an accepted proposal, with the date and time if there is one already. Role: the team or the call's owner.

#list_votable_proposals

Read-only

See voting ballot. The proposals you can vote on in a call with a community vote, and your current vote. Role: whoever the call lets vote.

#vote_on_proposal

Changes

Vote on proposal. From 1 to 5, within the voting window, or removes the vote. Role: whoever the call lets vote.

#get_vote_results

Read-only

See voting results. As far as the call's vote visibility allows. Role: depends on the call.

#list_my_proposals

Read-only

My proposals. Your proposals in the community, or in one call, with status. Minimum role: any.

#submit_proposal

Changes

Submit proposal. Proposes a session to an open call. The proposal goes out under the name of whoever connected the assistant. Role: any member, while the call is open.

Ask like this: "Submit my talk 'Data without spreadsheets' to Congress 2027, 40 minutes, intermediate level, in the Data track."

#update_proposal

Changes

Edit my proposal. Changes the proposal while it's a draft, and submits it with send. Only what is sent changes. Role: the proposer.

#withdraw_proposal

Asks to confirm

Withdraw my proposal. With an optional note to the organizers. Role: the proposer.

Notes: it can't be undone, which is why it asks for your yes.

#respond_to_counter_offer

Changes

Answer counter-offer. The proposer's answer to the organizers' counter-offer: accept (the proposal is accepted on those terms) or answer with their own terms and a note. Role: the proposer.

Notes: it commits the proposer and notifies the organizers, on the first call.

#Related

• Call for papers
• Recipe: create a call for papers
• Tools
• Money and confirmation