diff --git a/028-notification-resources/proposal.md b/028-notification-resources/proposal.md
new file mode 100644
index 00000000..9b285041
--- /dev/null
+++ b/028-notification-resources/proposal.md
@@ -0,0 +1,37 @@
+# Notification Resources
+
+This proposal uses the [generalized resource interface](../024-generalized-resources/proposal.md) to show how the interface would be implemented and interpreted by Concourse to support "notification resources", which are composed with another resource to emit notifications for build status.
+
+## Motivation
+
+* Support notifications in a way that doesn't pollute pipeline config and UI: [concourse/concourse#1052](https://github.com/concourse/concourse/issues/1052), [concourse/rfcs#10](https://github.com/concourse/rfcs/issues/10)
+* Support notifying on state change only (i.e. don't spam on 'fail', 'fail', 'fail').
+
+## Proposal
+
+> Describe your proposal.
+>
+> Things that can help: clearly defining terms, providing example content,
+> pseudocode, etc.
+>
+> Feel free to mention key implementation concerns.
+
+## Open Questions
+
+> Raise any concerns here for things you aren't sure about yet.
+
+## Answered Questions
+
+> If there were any major concerns that have already (or eventually, through
+> the RFC process) reached consensus, it can still help to include them along
+> with their resolution, if it's otherwise unclear.
+>
+> This can be especially useful for RFCs that have taken a long time and there
+> were some subtle yet important details to get right.
+>
+> This may very well be empty if the proposal is simple enough.
+
+## New Implications
+
+> What is the impact of this change, outside of the change itself? How might it
+> change peoples' workflows today, good or bad?