Project roadmap and implementation plan
We will put a legal project in the order it can actually be done: what blocks what, who owns each line, when it is due and whether that line promises a result or an effort.
When you need a roadmap and an implementation plan
Everything is urgent and nothing is first
Six workstreams started at once and each is waiting on another. The order is the whole problem, and it is not a matter of taste.
A date was promised outside the company
An investor, a customer or a board has a date. Whether it can be met is decided by the slowest official step, not by how hard anyone works.
Three advisers, three sequences
Each specialist is right about their own part and nobody owns the joins. The joins are where projects stop.
One step needed another first
You cannot apply for a thing only an existing entity may hold. Discovering that halfway is what turns a month into a quarter.
The plan exists, dates do not
A list of tasks without owners and due dates is a wish. What makes it a plan is the part everyone skips.
What you get
- The workable order of steps
- Each line with an owner
- The blocking steps named
- What each line promises
- A date you can defend
What a roadmap and implementation plan covers
A legal project is a chain of permissions, filings and documents where most steps cannot start until another one finished. A plan is useful only when it says which those are, who is responsible for each and what happens to the date if one slips.
Getting the company’s own record in order before someone reads it is pre-investment preparation; buying ongoing help and queueing it is a legal retainer.
What a usable plan contains
- The dependencies: which steps cannot begin until an earlier one produced a document, a number or a status.
- The owner of each line, named as a person and never a department, including the lines that belong to you.
- The waiting time that belongs to somebody else — a register, a bank, a regulator — separated from the time that belongs to us.
- The decisions you have to make, with the date by which each of them stops being free to postpone.
- What happens to everything downstream when a single step is late, so the conversation is about one date instead of the whole plan.
What a line actually promises
Not every line can promise the same thing, and pretending otherwise is how plans lose trust. A widely used set of principles for international contracts draws the distinction plainly: where an obligation involves a duty to achieve a specific result, the party is bound to achieve it; where it involves a duty of best efforts, the party is bound to make the efforts a reasonable person of the same kind would make in the same circumstances.
Which one a line is turns on four things named in the same text: how the obligation is expressed, the price and the other terms, the degree of risk normally involved in reaching the expected result, and how far the other side can influence the performance. Filing a document on a date is one kind of promise. A regulator’s answer is the other, and a plan that blurs them is a plan that will be argued about.
When a step is due
The same text sets out three situations, and every line in a plan sits in one of them: performance at the time fixed by the contract; performance at any time within a fixed period; and, where neither is set, within a reasonable time. Those principles take effect only where the parties adopt them, so what your plan relies on is the wording in your own documents.
Formats of work
One project, one plan
A defined outcome, broken into the order it can be reached in, with owners, dependencies and dates.
Untangling a stalled one
Work already started and stuck, read for the dependency nobody noticed and re-sequenced from there.
Keeping it alive
The plan updated as steps land and dates move, so it stays the version everyone is working from.
Sources: the difference between a duty to achieve a result and a duty of best efforts, the four factors that tell them apart and the three rules on time of performance are articles 5.1.4, 5.1.5 and 6.1.1 of a set of principles for international contracts, which take effect only where the parties adopt them.
Stages of work
The outcome, stated so it can be checked — 1 week.
Not «expand abroad» but the specific state the business has to be in, because a plan can only be built backwards from something testable.
Every step that stands between.
Filings, permissions, documents and decisions are listed without sequencing them yet, including the ones that belong to other advisers and to your own team.
What blocks what.
Each step is marked with what it needs before it can begin. This is where the order stops being a preference and becomes the only workable one.
Owners and dates.
Every line gets a person and a due date, and the waiting time that belongs to a register or a regulator is shown separately from the time anyone controls.
What each line promises.
Lines that deliver a document are marked as such; lines that depend on somebody else’s answer are marked as efforts, so nobody reads the plan as a guarantee it never gave.
Keeping it true.
A plan is only useful while it matches reality. Steps close, dates move, and the version everyone works from is updated instead of quietly abandoned.
Our standing legal work sits in Advisory & Ongoing Support.
FAQ
Discuss
the Task
Speak to our team
Speak to our team. Tell us about your task –
we’ll help you with it in any jurisdiction.