Tumpline - Contract Lifecycle Management for an Ontario City
Contract Lifecycle System for a Canadian Municipality
Designed and built a clickable contract lifecycle system for an Ontario city of about 140,000 residents: one register for every contract from award to close, variations checked against the city's delegated authority thresholds, a renewals board that never lets a contract lapse without a decision, and insurance, WSIB and bond expiries on every contract.
Most of our work is under NDA. Per agreement, we can share the work but not the company details - all names and identifying information shown here have been changed.
Impact
Dashboard, contract register with quick view and a create-from-award modal, contract detail with 7 tabs, the renewals board, the variations list and variation detail.
Contract manager up to CAD 50,000, department head up to CAD 250,000, Director of Procurement up to CAD 500,000 and the CAO above, with procurement review over 10% cumulative and a council report over 20%. Illustrative by-law settings.
Decision needed, renewing, re-tendering, letting expire and lapsed, over a 90, 180 or 365 day horizon. Notice deadlines turn amber at 60 days and red at 30.
21 suppliers, 17 variations, 24 obligations, 11 departments and 14 staff users, with compliance documents, ERP invoice references, approval routes and e-signature envelopes.
The Problem
Oxbow Rapids held about 1,400 active contracts in a shared drive of signed PDFs, a spreadsheet kept by one procurement officer and the memory of each department's project lead. Renewal options lapsed, services ran on after expiry, change orders were approved by email, and insurance and WSIB certificates expired unnoticed. A council request for every contract over CAD 100,000 took three weeks to answer.
Our Solution
Tumpline picks up where the tender ends. A contract is created from the award without re-keying, then tracked through signature, delivery, variation, renewal and close. Every variation is checked against the city's by-law thresholds before it routes for approval, and every expiry, notice deadline and certificate is in view before it is missed.
The Challenge: Keeping 1,400 Contracts Inside the By-law
An Ontario city contracts under its own Procurement By-law, Canada's trade agreements, access to information law and accessibility law, across eleven departments that each think of a contract as their own.
Variations Without the Right Approval
The city's by-law sets who may vary a contract and at what value. Approved by email, several contracts had grown well past their awarded value without that approval, and nobody tracked when cumulative changes should have gone to council.
Expiries Nobody Saw Coming
No one could say which contracts expired in the next six months. Renewal options lapsed because the notice deadline passed unnoticed, and some services kept running after expiry with no contract cover.
Trade Agreement Coverage After Award
Municipalities are generally covered by the CFTA and, above higher thresholds, by CETA. A contract has to keep the coverage set at award, and a variation that looks like an unplanned extension of scope needs a procurement review.
Disclosure Without a Record
Under MFIPPA the public can request municipal contracts, subject to exemptions such as third-party commercial information. One request took two months because nobody knew which version was signed or what the supplier had marked confidential.
Our Approach: From the Procurement By-law to a Clickable System
Spec and Rules Research
Mapped 10 user roles from contract managers and Legal to the Clerk's Office, suppliers and the public, and 37 screens across staff, supplier portal and public disclosure pages. Defined the data model for contracts, awards, versions, clauses, approval routes, obligations, variations, renewals, ERP references and publications, and wrote down the rules the design follows: the Municipal Act, CFTA and CETA, the Buy Ontario Act, MFIPPA, AODA, the Electronic Commerce Act and the Construction Act.
Clickable Demo on a Production UI Kit
Built 6 key screens on a production workspace kit: the dashboard with KPIs, pipeline against target age and a 12-month expiry timeline, the contract register with saved views and a blocked-supplier check on create, contract detail with value, term and compliance cards, the drag-and-drop renewals board, and variations with the threshold check, procurement review checklist and approval route. All actions run on local state.
What a Production Build Adds
Awards from the tender system, the vendor record, Ontario Business Registry and Corporations Canada checks, DocuSign or Adobe Acrobat Sign, the city's ERP for POs and invoices, WSIB clearance lookups, records management, CKAN open data publication and Microsoft Entra ID sign-in. Plus negotiation, templates and the clause library, approvals and signing queues, redaction review, the supplier portal, public pages and a tamper-evident audit log.
Why It Works: The By-law Built Into Every Change
Threshold Check Before Approval
Each variation shows awarded value, previous approved variations, this change, the new total and cumulative %, compared with every authority level. It names the approver it needs, flags procurement review and says whether a council report is triggered, citing the approval matrix version in force.
Thresholds Are Settings, Not Code
Approval levels, review and council triggers and trade agreement thresholds are the city's own by-law values, entered by the legal team with their source and effective date. Each contract keeps the versions that applied when it was created or varied.
One Page for One Contract
Contract detail puts the lifecycle rail, award reference, trade agreement flags, Ontario business and accessibility fields, the value path from awarded to current, holdback on construction and insurance, WSIB and bond expiries in one place, with obligations, payments and approvals a tab away.
Nothing Lapses Without a Decision
The renewals board puts every contract ending in the horizon in a column, with its option, notice deadline, last supplier score and value used. A contract that expires with no decision lands in Lapsed, where everyone can see it.
Related case studies
View all: Procurement & ESG
Waag - Supplier Onboarding and Third-Party Risk Platform
Designed and built a clickable supplier onboarding and third-party risk platform for a Belgian industrial and logistics group: a 10-item onboarding checklist from request to approved vendor, registry, VAT and ownership checks, bank details confirmed by an independent call-back and a second person, and a supplier base scored by tier and risk rating.
Zabuni - Tender Management System with a Tender File Ready for Review
Designed and built a clickable tender management system for a Kenyan county that buys about KES 4.2 billion a year across ten departments: tenders raised from the procurement plan, clarifications answered to every bidder, addenda tracked per supplier, and an evaluation committee that scores alone before agreeing a consensus.
Enterprise Software Engineering - Human + AI
Contact Us
© 2026 - Copyright. All Rights reserved Oceanlab
Location
Global Headquarters
21 Merchant Road, 3rd Floor, Singapore 058267
Main corporate office and leadership operations
North America Office
548 Market Street, PMB 12345, San Francisco, CA 94104
Client operations and business development
India Office
402 Shivalik Shilp II, SG Highway, Ahmedabad 380015
Engineering and delivery center
Enterprise Software Engineering - Human + AI
Contact Us
Locations
Global Headquarters
21 Merchant Road, 3rd Floor, Singapore 058267
Main corporate office and leadership operations
North America Office
548 Market Street, PMB 12345, San Francisco, CA 94104
Client operations and business development
India Office
402 Shivalik Shilp II, SG Highway, Ahmedabad 380015
Engineering and delivery center
© 2026 - Copyright. All Rights reserved Oceanlab