Here are some tools which can seriously help you increase your productivity (or at least help reducing the waste of time).
Yes, you need source control, even if you are working alone. A good source control software makes it possible to track all the changes you made, put labels on certain versions, or to work on separate branches of the project. With this you always have a fail safe version to rely on if something goes wrong. Here are the two I recommend:
To be perfectly honest, I don't like Subversion and I really appreciate Perforce. Now well, one is a commercial product (costly) and the second one is free. Subversion is quite reliable and usable, but the client side, the available tools, etc… are all totally outdated. It's basically a minimalistic system, devised for masochists who believe the working with branches and handling conflicts is something fun. The less worse Windows client so far is still Tortoise SVN which unfortunately inherits of all the bugs of both the Subversion client code and windows explorer fancyness…
Perforce is costly 1), but you know what you pay for. The merge tools are way better, the change list concept is brilliant, the various user interfaces are practical to use, the diff view, time lapse view, branch view, are just plain amazing and save a lot of time.
Both are available on numerous systems, so working on Mac, Linux or Windows is not a problem.
What you want to avoid, are VSS (Visual Source Safe) and CVS (Concurrent Versions System). There is no excuse for using this anymore. CVS is unusable seriously, and VSS has a tendency to corrupt it's database very easily (and is unusable over a high latency network).
Ideally, all documentation should be available to anyone without having to install any special software. What I recommend is to install a Wiki on the project intranet. Enable all the logs features, disable anonymous editing, and be sure that the content of the Wiki is backed-up with everything else. Here is what I recommend:
Media wiki is what is used on Wikipedia, so you can reasonably assume that the engine should not have scalability problems. I recommend Doku wiki because the syntax is cleaner, the handling of name-spaces is better, and the interface is not cluttered with buttons everywhere.
Both are definitively usable on large teams (60+ persons), even with large pages with lots of pictures. The choice is yours :)
There are plenty of small tools that makes life easier, here is my personal selection: