By Décio Dalke Jr. · Nov 2026

World 1 of Contracts, level 1: where it all begins

Contract administration means managing the contract throughout the project, and the first job is reading and mapping what it says. The claim is just the visible tip.

Part 1 of 1 of the series World 1 of Contracts.

First, read the contract — pixel-art patchwork quilt in a grid, with one patch out of line where the seam does not close

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).

World 1 of Contracts — level 1 of 5: level 1 · level 2 · level 3 · level 4 · level 5

The first level of Super Mario’s first world teaches the rules of the game without any manual. Whoever pays attention in the first few seconds finds out what they can touch, what hurts and which way the level runs. Whoever rushes off learns the same rules the expensive way, by losing lives.

Something similar happens with a contract. The rules are all written down from day one, and hardly anyone reads them before starting to play.

This world is about contract administration in any contracted project: a software system, a consultancy, an ongoing service or a construction job. The examples come from my experience on industrial projects and in systems development, and the rules apply to all of them.

What is contract administration?

Contract administration means managing the contract throughout the execution of the project, from the first day to close-out. It includes knowing what each party has to deliver and when, recording what happens, measuring what has been done, handling changes and, where appropriate, claiming what is owed.

In 2013 I wrote an article for a trade magazine entitled Contract administration isn’t (just) claims. A claim is a formal request by one party to be compensated for something the contract didn’t foresee or the other party didn’t fulfil. It is the part that shows, which is why it tends to be mistaken for the whole.

Why do so many companies only look at the contract once there is already a claim?

The contract usually goes into a drawer once it is signed, and only comes back to the table when someone needs an argument.

In Brazil, for many years, few companies had a contract administration function of their own. Claims were usually prepared by the planning team. I myself worked on claims for years without realising it was a separate discipline.

When the contract is only read at the moment of the dispute, the dispute has already started late: the evidence that should have been kept wasn’t, the deadlines for raising issues have passed, and each side remembers the story its own way.

What is the first job?

In the late 2000s I worked as contract administration coordinator on an industrial project. First job: read the contract and its annexes. Longer than the Bible, and in A4!

The basic work in a contract administration process is understanding the contract. Six things every contract should set out, and which need to be clear to whoever is going to carry it out:

  • Objectives: what the project exists for.
  • Deliverables and obligations: what each party has to do or deliver.
  • Rights: what each party can demand.
  • Rules of engagement: how the parties communicate, approve and record.
  • Penalties: what happens when someone fails to comply.
  • Deadlines and amounts: when, and for how much.

Why does a contract need a map?

With that map done, the work (without AI, obviously) was to map it by department and by subject. Every large contract tends to be one big patchwork quilt: pieces made separately, stitched together “just because”, that govern a large project.

Each piece can be right on its own, whereas the problem shows up in the seams, when the deadline in one annex doesn’t match another, or when an obligation sits in one clause and the corresponding penalty in another that says something different.

In that particular case, our map brought up inconsistencies, problems, mismatches and items needing immediate resolution. It was the first claim of my life that came before the work had even started. Technically it was a claim, though not what most people picture: an adjustment to the contract, a change to the rules of the game, with no impact on time or cost. But it saved us headaches later on.

Planning and contract: which one is in charge?

The contract says what has to be delivered, by when and on what terms. The plan says how the team is going to get there. When the two don’t talk to each other, the schedule can be perfect and still breach the contract, because nobody carried over the deadline from an annex or the condition attached to a measurement.

That is why the contract map is the first input to planning, and the two functions need to keep an eye on each other all the time. That is how I learnt the trade, inside planning, and it is why this world comes straight after World 1 of Projects.

So, what comes next?

With the contract read and mapped, execution begins, and with it the need to prove what happened. Level 2 deals with the record that stands up in arbitration: what to keep, how, and by whom.

Quick questions

What is contract administration? Managing the contract throughout the execution of the project: understanding what it says, recording what happens, measuring, handling changes and claiming what is owed.

Is contract administration just about claims? Claims are one part of it, the most visible one, although most of the work happens beforehand, so that the claim is well founded or never needed at all.

What is the first step in contract administration? Reading the contract and every annex, and mapping objectives, deliverables and obligations, rights, rules of engagement, penalties, deadlines and amounts.

Why map the contract right at the start? Because large contracts are made of pieces written separately, and the inconsistencies between them show up early if someone looks for them, or late if nobody does.