Weekly updates and the job agreement
A project runs calmer when you know what was agreed, what was not, and what happened that week.
A weekly update is not marketing. It is a record of decisions and open questions.
What we agree before signing
Before work starts we say what we do, what we deliver, what is out, and how larger changes are priced. Without that, every wish becomes an expectation, and every expectation becomes a dispute.
Weekly update
A short, regular note: what was done, what waits for your decision, what blocks progress. It need not be long. It must arrive on time.
Why it helps you
Fewer meetings for the sake of meetings. Faster decisions because questions arrive listed. Easier pause and resume. Easier delivery of documentation to the next party because a trail exists.
A question about what you just read? Write to us.
How we run it
The agreement goes in the proposal before work. Decisions recorded. In-agreement revisions have rules. Larger changes by annex. See Modus operandi and Why TENET.
Tell us about your project.
Questions around this topic
- In an active phase we send one weekly written update: what is done, what awaits your decision, and where we see risk. Meetings are for decisions that cannot close in writing.
- What we do, what we deliver, what is excluded, and how larger changes are priced. Scope goes in the proposal before work starts.
- We answer a short written enquiry within 48 business hours. If the project does not fit our method, we say so at the start.