In addition to moritz's fine points...

• Really consider your security / data sharing model. Contracting can be very competitive, IIRC, sharing information between a general and a contractor is very different from sharing information between a contractor and another contractor. Consider carefully the trust relationships that you permit by default. Security is much easier to design in up front than it is to bolt on after the fact.
• I am assuming that some contractors submitting RFIs may be competing against each other: if this is the case, then I would stress moritz's point even stronger - one contractor should not be able to see another contractor's information, unless it has been explicitly made public (or public to a specific role).
• Is there a way to limit display to only a single project, or would there be a per-project installation on this? I could ask the same question about phases of a project.
• Your header and data halves of the table do not seem to line up. This could lead to confusion for the user. Just looked at the code for the page. You have the two halves as two separate tables, and the widths don't even match up. Even if the widths do match up, depending on some of your wrap / clip settings, you may end up having them misaligned unless you make them both a single table.

These are just a couple of things off the top of my head. Experience: many years working for an electrical engineer, not doing any of the project work (other than drafting), but hearing many things, and 15ish years in the computer industry, most of them requiring thinking paranoid from a security perspective :).

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.