Contract Renewal

Renewing a contract in PMSuite means continuing an existing agreement into a new period by putting a fresh contract record in place for that period, while the original record stays in the Contracts module as the history of what was previously agreed.

A contract record carries Subject, Project, Description, Start Date, End Date, Contract Type, Contract Value, Currency, and Client Details. A renewal reuses those details for the same client and re-states them over the new Start Date and End Date, adjusting value, scope wording, or contract type wherever the new period differs.

Who can use it

Users whose role grants access to the Contracts module. Contracts is a toggleable module, so it must be switched on for your company under Settings → Module Settings before anyone can open it.

Prerequisites

The Contracts module is enabled in Settings → Module Settings.
The original contract exists in the Contracts list, with a client and an End Date recorded, so you know which period is ending.
The client record for the agreement already exists under Clients (/account/clients), since a renewal is raised against the same client.
Contract numbering is configured under Settings → Contract Settings if you want renewals to follow your own prefix instead of the default CONT#001 pattern.

How to Access

Contracts list: /account/contracts
Projects module dashboard: /account/project-dashboard
Contract numbering: Settings → Contract Settings (Prefix, Separator, Digits — e.g. CONT + # + 3 digits → CONT#001)
Module on/off: Settings → Module Settings

Renewing a contract

Open /account/contracts (sidebar → Projects → Contracts) and locate the contract whose period is ending, using the End Date shown on the record to confirm which period is closing.
Open the contract and review its current terms — Subject, Contract Type, Contract Value, Currency, Description, and the linked Project and Client Details. These are the fields the new period has to restate.
Go back to /account/contracts and choose the option to create a new contract, raising it against the same client and carrying over the terms you are keeping.
Set the new Start Date and End Date to cover the renewal period.
Adjust Contract Value, Currency, Contract Type, or Description wherever the new period differs from the old one — for example a revised rate or a changed scope of work.
Save. The new record is auto-numbered in its own right using your Contract Settings pattern (CONT#00…), so the original and the renewal are separate, individually traceable records.
If the renewal needs client sign-off, collect it through E-Signatures on Contracts.

The original contract remains in the Contracts list unchanged. Renewing never removes or overwrites the previous agreement.

Keeping renewals traceable

Because the original and the renewal are separate records, the link between them is one you establish in the content:

Use a consistent Subject convention, such as appending the renewal period to the original subject line, so both records sort together in the list.
Reference the original contract's number (CONT#…) in the Description of the renewal.
Keep both records attached to the same Project and Client Details so the two agreements read as one chain when you scan the Contracts list.

Effect on other features

Contracts list — the original and the renewal both appear as separate records at /account/contracts, each with its own number, dates and value.
Client — both records belong to the same client under /account/clients, so the client's history shows the full sequence of agreements.
Project — if the contract is linked to a project, link the renewal to the same project so project-side users see the current agreement.
Google Calendar — Contracts is one of the record types PMSuite pushes to Google Calendar. The sync is one-way, PMSuite → Google Calendar: a renewal you create in PMSuite can appear on the connected Google Calendar, but anything created in Google Calendar does not come back into PMSuite. It requires Google Calendar to be connected and verified for the company, with contracts enabled in Settings → Google Calendar Settings.
Slack — if your company has the Slack incoming-webhook integration enabled under Settings → Notification Settings → Slack tab, the events selected on that tab are delivered one-way into your Slack channel, which is a practical way to keep a team channel aware of contract activity.
Contract discussions and files — Discussions and Contract Files belong to the record they were added to. Material from the original stays on the original.

Limitations

The renewal is a new record, not a version of the old one. There is no automatic parent–child link in the list. Workaround: use a fixed Subject convention and quote the original CONT#… number in the renewal's Description, and keep both records on the same Project and client so the whole chain is readable from the Contracts list.
Discussions and files do not carry across. The renewal starts with an empty discussion thread and no attachments. Workaround: read the original's Discussions before drafting the renewal, and re-upload any documents that must apply to the new period under Contract Files.
Google Calendar visibility is one-way only. Renewal dates recorded in PMSuite can push out to Google Calendar, but a renewal date somebody adds in Google Calendar will never appear in PMSuite. Workaround: treat PMSuite as the system of record and enter every renewal date there first.
Contracts can be hidden entirely. If Contracts is switched off in Module Settings, nobody in the company can raise or view a renewal. Workaround: ask a company admin to re-enable Contracts under Settings → Module Settings.

Troubleshooting

No Contracts entry in the sidebar — the Contracts module is disabled, or your role has no access. Ask a company admin to check Settings → Module Settings and your role permissions.
The renewal got an unexpected contract number — numbering follows Settings → Contract Settings (Prefix, Separator, Digits). Change the pattern there; records already issued keep their existing number.
Contract value shows the wrong currency — Currency is a per-contract field. Reopen the renewal and set the currency for the new period explicitly rather than assuming it inherited the old one.
The renewal is not showing on Google Calendar — confirm Google Calendar is connected and verified for the company, that contracts are enabled in Settings → Google Calendar Settings, and that the user concerned has Google Calendar enabled on their own profile. The sync only ever runs PMSuite → Google.
The renewal is not reaching the client for signature — see E-Signatures on Contracts; the signing flow reports session-expiry and validation problems directly on screen and confirms success once signed.

Files Types Templates