So I know what you're thinking; "Boy, I'd love to contribute to the SCP Foundation, but I don't have the time to write an entire page by myself!".
Well now you don't have to! Collaboration pages are the perfect way for an aspiring author to dip their toes in the water without having to make a huge commitment of crafting an SCP from scratch. It's practically a rite of passage for greenhorns to come up with a new and exciting way to try (and fail) to kill SCP-682.
But just because writing an entry for a test log takes less writing, it doesn't mean that the standards should be any lower. As such, I've come up with some guidelines.
Basics
If there are rules, follow them.
There ain't no rule that says I can't write my log entry in Esperanto!
Many collaboration pages have guidelines listed on the discussion, if not on the actual page itself. And if there aren't any rules, use your common sense; see what everyone else has been doing and follow that format as closely as possible.
Make sure it's actually a collaboration page.
You know what this article about an Apollyon class SCP that destroyed the world needs? A footnote about Dr. King and appleseeds!
Just because this is a wiki doesn't mean you can edit any page you want. Even if it's a test log, check for the "collaboration" tag at the bottom of the page before you start writing anything.
Don't do something that's already been done.
The definition of insanity is doing the same thing over and over again, expecting a different result.
In real life, scientists often repeat experiments to confirm the results. But that doesn't work for fictional science because it's boring. If you have an idea for a test on a collab page, make sure that experiment hasn't already been done.
Tone and Style
The Foundation does not employ middle-schoolers.
Input: One (1) bright pink dildo
Setting: Very Fine
Output: [DATA EXPUNGED]
Always remember that these are Scientists. It takes at least 8 years to get a PHD, and it's probably a good bet that a top-secret organization with like the foundation screens people before hiring them.
And as a side note, remember to use the metric system when recording measurements. The imperial system is extremely arbitrary, making it impractical for the sort of precise calculations that scientists and engineers perform on a daily basis.
Keep pop-culture references and memes to a minimum.
Money entered: Eighteen 500 Yen coins, followed by a single 1-yen coin.
SCP-261 Powered or Unpowered: Unpowered
Item description: A cardboard box labeled "Ka Karaot Cakes". Upon opening the box, the subject's hair began to glow and he shouted "ITS OVER NINE THOUSAAAAAAAAND!" in a manner similar to the cartoon series ██████ ████ █.
Note: This is just like one of my Japanese animes! -Dr. Selfinsert
Pop culture references and memes are not a substitute for clever writing. Reference humor can work, but if the joke boils down to "Hey, I understand that reference!", then it's not a joke; it's a TV Tropes entry.
Don't drastically change an object's function
Input: One Book Titled "How to Make Tacos"
Setting: Very Fine
Output: One Box labeled "SCP-914 Taco Maker Expansion Set!". Contains parts and instructions how how to upgrade SCP-914 to make a variety of anomalous tacos.
Note: SCP-914 now as a "taco" setting, and Dr. Selfinsert suggests that everyone try this cool new setting.
The point of a testing log is to explore the properties an object already has rather than to make up new properties. As paradoxical as it sounds, accepting limitations can often inspire creativity.
Be Careful About Cross-Testing
Input: SCP-682
Setting: Very Fine
Output: SCP-682 rapidly grows to encompass the entire universe before devouring time itself, rendering existence into a perpetual hellscape with neither beginning or end.
"I dunno why I thought this was a good idea." -Dr. Selfinsert.
While the Foundation isn't as hesitant about cross-testing as they used to be, they're not going to cross-test an extremely dangerous keter-class object without good reason.
Feedback
You are not in charge.
I AM THE LAW!
Even if you don't like an entry someone else has made, it's not your job to delete it. Feel free to bring up your concerns on the discussion page, and if you don't get any traction feel free to alert either the original author or the MAST team.
There are exceptions, of course. Nobody's going to complain if you fix an egregious typo. And if you an entry in the SCP-914 log is just the n-word repeated over and over again followed by a swastika, you can feel free to take that shitpost down (though be sure alert a moderator).
Even if you are in charge, you are not God.
I don't care if that log entry was moving, interesting, and well-written! Everyone knows Abel can't use dental floss, so I'm declaring it non-canon!
As they say, "The Author is Dead". As long as people are having fun and making interesting content don't be afraid if the testing log gradually drifts away from your personal head-canon.
Deletion happens to the best of us.
Why doesn't anyone like my really awesome ideas?
Nobody has a perfect batting average. If you find that your log is missing, check the discussion page to see if anyone discussed it, and if nobody has discussed it, bring it up yourself. Chances are your entry wasn't as good as you thought it was, but there's no shame in failure as long as you learn something from it. Listen to the feedback, and reflect on why your log entry was ultimately scrapped.
Don't be a petulant child.
Everybody betray me, I'm fed up with this world!
If your entry was deleted, you're not going to many any friends by repeatedly re-posting the same entry over and over again with no changes, throwing accusations at people not understanding your "genius". When you do that you don't look like a victim, you look like an asshole. And if by some chance there actually is cabal of people spitefully deleting your work, you'll get more mileage out of discussing this with the with the moderators rather than throwing a tantrum.
Starting your own
This probably deserves an entire guide on it's own, but for now here are a few basic guidelines.
Most SCPs don't need a collaborative testing log.
SCP-076-2 Testing Log:
Subject: A cow.
Result: SCP-076-2 kills the cow with a broadsword.
Subject: A moose
Result: SCP-076-2 kills the cow with a chainsaw.
Subject: A snake.
Result: SCP-076-2 kills the snake with a katana.
Subject: A bigger snake.
Result: SCP-076-2 kills the snake with a bigger katana.
Based on these test results I think it's safe to conclude that Abel is really good at killing things. -Dr. Selfinsert
Most SCPs tell a self-contained story, and tacking on a testing log can hurt the tone. Take SCP-184, for example; while you could do all sorts of crazy experiments with it, the attached documentation both demonstrates the objects properties and tells an interesting story in it's own right.
Seek Permission, not Forgiveness
Well in my headcanon you totally gave me permission to do that!
If you are dead-set on adding a testing log to an SCP that doesn't already have one, contact the original author; the worst they can do is ignore you, in which case you're no worse off than when you started.
Testing Logs are not the only type of collaboration
Happy times, mimes!
Cack! Am christened Herr Doktor Spankoflex, colloquially namesplapped with Essy-Pee toothreethree and Steven! You, sir, are oculating my spidersteps, which the good Mr. Lightbulb has indubitably mashed potato one blinkbox for yours truly.
If you want to write a character blog or do some kind of weird, round-robin storytelling thing, go for it. Just know that whatever form it takes you'll be responsible for running it, so try asking around on the forums or in chat to see if anyone is actually interested.