Why Contract Status exists

Built by NEC practitioners, for NEC contracts

Contract Status is not general project software with an NEC template on top. It is built around what NEC actually asks people to do: warn early, notify on the right register, reply within the period, keep the programme accepted, and move the Prices and the dates only through compensation events.

It knows that an early warning is never accepted or rejected. It knows that a notification goes separately. It knows that the eight weeks are seven on an NEC4 subcontract and that an NEC3 programme is not treated as accepted. If you run these contracts, you will know why those details matter.

It is in daily use on live NEC contracts, and it is developed in close contact with the people using it.

What we believe

• Both sides should see the same record. Most NEC arguments are not about the contract. They are about what was sent, and when.
• Software should not decide who is right. It should keep the facts straight so that people can.
• The rules should be the contract's. A Z clause or a different form changes the rules, so each contract carries its own.
• People should not need much training. If a new engineer can follow the next step without a course, the system is doing its job.
• Clause numbers should never be made up. If our library has no clause for something, we show it without a number.

Why we give NEC guidance away

Good NEC guidance is hard to find, and most people need a straight answer to a real situation. So this site has NEC guides, real questions answered, tools, quizzes, role-plays and downloads. It is all in our own plain English, with the clause numbers checked. None of it depends on you buying anything, and it is general information rather than legal advice.

If it helps you, and one day you want the same care in your contract records, you know where we are.