Guides
Longer reads on keeping agreements current.
Repositories, notice dates, migration and where your files already live. Each guide uses a fictional worked example and says plainly what it does not cover.
- 7 September 2026What a contract repository is, and what a folder is notMost teams already have a contract repository. It is a folder called Contracts. This guide is about the four things a folder cannot tell you, using one fictional agreement from import to renewal.Guides · 8 min read
- 7 September 2026Notice date, term end and reminder: three dates people confuseA term end is not the last day to give notice, and an internal reminder is not notice to the counterparty. This guide walks the fictional Alder Works fixture through the arithmetic and the review points.Guides · 8 min read
- 7 September 2026Managing contracts in SharePoint: what works and where it stopsSharePoint can be the right place to store contract files. It can also become a folder tree that leaves current terms, amendments and accountable owners outside the record. This guide separates what works from what still needs a checked register.Guides · 8 min read
- 7 September 2026An honest migration walkthrough: from a spreadsheet to a checked registerThe safest migration is not the one that imports everything fastest. It preserves what each column means, starts with agreements that have decisions coming, and treats imported dates as suggestions until a person confirms the source.Guides · 9 min read
- 7 September 2026Who owns this agreement? Handover, reassignment and the person who leftAn agreement without an owner becomes a file someone remembers only when the date is close. This guide explains why ownership is a field, not a comment, and how reassignment should work when a person leaves.Guides · 7 min read