"Almost a post"... what are the implications for staff?

I occasionally have an "almost a post" that gets rejected with a comment inviting correction.

I'm curious what the implications are on the back end for staff. If I ignore it and leave it in an uncorrected state, does it sit in some queue that staff end up checking?

Sometimes I look at it and I think "yeah, not worth trying to fix that one. I'll let it die". But it occurred to me that simply leaving it might make a burden on staff. Should I be deleting it? Can I even do that?

Or does it only reappear for staff to check once I have edited it?

The answer is IT DEPENDS.

We almost never use Almost-a-post.  If it doesn't meet publishing standards, it almost always gets quietly removed.  That you are getting almost-a-post at all means that there is something amazing about your posts and someone on staff thinks it worth giving you the option to repair the little bit that is wrong with it.

Most of the time, the post isn't visible to the public until the edits are approved by the staff.  

The easiest solution, don't make posts that don't meet publishing standards.  You put the effort into making the posts, might as well make it a post that is something we can publish.  

publishing standards
be nice
leaving room for other people's ideas
perennial discussions
deleting stuff
almost-a-posts
the cider press