Proposed

Summary

Submit abstracts to conferences through call-for-papers processes; treat the proposal as a binding commitment.

The Pattern in Detail

The Proposed pattern describes the voluntary path to the stage: you see a call for papers (CFP), craft an abstract, submit it, and — if selected — commit to delivering. This is the primary channel through which most conference speakers earn their slots, and the abstract itself is the first test of your ability to communicate clearly and compellingly.

Understanding the conference proposal system is essential. Most technical conferences run CFP processes where a program committee reviews hundreds of submissions to select a fraction for the schedule. Your abstract competes directly against other proposals for limited slots. This means your abstract must do two jobs simultaneously: accurately describe what you will present, and persuade the committee that your session will be valuable to attendees. These two goals sometimes conflict, and navigating that tension is a skill in itself.

Write your abstract in grammatically correct, active-voice prose. Avoid jargon that the program committee may not share — remember that committee members review proposals across multiple tracks and may not be domain experts in your specific niche. State clearly what the audience will learn, why it matters, and what makes your perspective unique. Include concrete takeaways rather than vague promises. Apply Peer Review to your proposal text before submitting; fresh eyes catch ambiguities and weaknesses that you have become blind to.

Strengthen your submission with evidence of speaking ability. Include links to videos of previous talks, speaking scores from past events, or testimonials from organizers. Program committees take a risk on every speaker they select — anything you can provide that reduces that perceived risk works in your favor. A first-time speaker with a strong abstract and a link to a well-received meetup talk has a meaningful advantage over a first-time speaker with only an abstract.

Treat submission as commitment. The moment you click "submit," you are making a promise that you will deliver this material if selected. This is not a tentative expression of interest — it is a contract. Conferences build their schedules, print programs, and sell tickets based on your commitment. Withdrawing after acceptance causes real damage to the event and to your reputation. If you are not prepared to follow through, do not submit.

When to Use / When to Avoid

Use this pattern whenever you want to speak at a conference or event with a CFP process. The discipline of writing a strong abstract also helps clarify your thinking even if you never submit it. Avoid submitting proposals you are not genuinely committed to delivering — the conference ecosystem depends on speaker reliability.

Detection Heuristics

A crisp talk does not prove that a proposal was submitted or treated as binding. Verify Proposed from the actual submitted CFP artifact and compare its promised scope with the delivered talk. Without that artifact, the pattern is unevaluable.

Scoring Criteria

• Strong signal: The submitted/accepted CFP artifact is available and the delivered talk fulfills its scope and promised takeaways
• Moderate signal: The proposal is available and the talk fulfills most promises with limited, explainable drift
• Absent: Records show no proposal was submitted for this talk or the submitted scope was not treated as a commitment
• Unevaluable: The submitted CFP artifact is unavailable

Relationship to Vault Dimensions

Relates to Dimension 9 (Speaker Credibility/Ethos).

Combinatorics

Pairs with Required (its counterpart for mandatory presentations), Peer Review (essential for polishing abstracts), and Know Your Audience (understanding conference attendees improves proposal targeting). The Proposed pattern also feeds into Abstract Attorney awareness — what you promise in your abstract, you must deliver on stage.