Getting started
What Code Contract is, how information is organised and what to do on day one.
Getting started
- What your suppliers will ask youStart hereThe five questions that arrive with your first notice, with their answers.
- The first hourStart hereWhat to do right after logging in to find out whether this helps, without setting anything up.
- Which process to start with?Start hereThe highest-yield one is not the biggest: it is the one that makes you chase someone outside.
- Starting with a deadline on topStart hereNobody starts calmly: you start because there is an audit, a client or a site in three weeks.
- What Code Contract is and what it is forThree modules on one foundation: request documents, sign them and certify them as evidence.
- How everything is organised: folders, projects, documents and dataThe four levels information is organised into, identical across all three modules.
Initial setup
- The five first-month mistakesStart hereAll avoidable, and all five happen for the same reason.
- The first thirty daysStart hereWhat to expect each week, and which week the doubt usually appears.
- Who should own this internallyStart hereThe person who makes it work is not the most technical: it is whoever suffers the problem today.
- From trial to working for realStart hereThe day it stops being an experiment and becomes where the work lives: what to tidy first.
- The first supplier you askStart hereThe first request to an outsider teaches more about your process than any internal test.
- Bringing in what you already haveGoing furtherWhat to migrate from the old archive and, above all, what not to.
Helpful resources
- Can I manage this with a spreadsheet?Start hereWhen it is enough, when it stops being enough, and exactly how you notice.
- What it costs and what it depends onStart hereWhat you pay for, what you do not, and how to estimate before talking to anyone.
- What this will not solveStart hereFive problems people expect to vanish on rollout, and that do not vanish.
- How much time this really takesStart hereThe question nobody asks in the demo and the one that decides whether this sticks. The work does not vanish: it moves.
- What to ask before signing upGoing furtherEight questions worth asking any platform, this one included.
- Getting your team to actually use itGoing furtherThe part that is not technical and decides whether any of this works.
- Do I have to create an account?Start hereTo answer a request or sign, no. An account is only needed if you are the one doing the asking.
- I don't know what I'm supposed to do nowStart hereNearly always the answer is: nothing. What is waiting on someone else needs nothing from you until they reply.
- When do you need it by?Start hereIf the request does not say, ask. A specific date is the only thing that turns «whenever» into something that gets done.
- Your first weekGoing furtherWhat to do in the first days so the platform actually earns its keep, in order.
- Which module do I needGoing furtherTrackline, Consigne or SmartCheck: which one solves what you have in front of you.