Contracts PREVIEW
Contracts keeps your agreements with customers and vendors in one place: each contract's versions, its files, who signed it, what each side promised, the rates and payment terms it sets, and the duties it puts on your company. It has its own Contracts group in the sidebar, with Contracts, Deadlines and Requests, and appears only for companies it has been turned on for. A role needs the Contracts permission to see it, Contract files to see the files, and Contract terms to see and change terms, conflicts and requirements. The Contracts screens follow the language you pick on My profile, English or Spanish.
The contracts list
Each contract gets a number such as CT-0001. The list opens with tiles for your Active contracts, the Deadlines in the next 30 days and Items to check, with Show pills by status and a search box for the number, title, or customer or vendor. A contract is a Master agreement, a Work order under a master agreement, or an Other agreement. Customer, vendor and project pages show a Related contracts card. While partners have sent requests that wait for an answer, a banner at the top links to them (see Partner requests).
Status
A contract moves through Draft, Negotiating, Negotiated, Signed, Active, Ended or Cancelled. The status only changes when someone changes it with Change status; a date passing never changes it. Signing needs a finalized revision, and Active needs dates someone confirmed. Ending a contract ends its standing duties on the end date, except the ones marked as continuing after the end; cancelling it ends all of them.
Revisions and files
The Revisions tab holds each version of the contract: the Original, then any Amendment, Restatement or Correction. A contract has at most one draft revision at a time. Finalize a draft when it is agreed; a finalized revision and its files can never be changed or deleted, and finalizing a new one sends open obligations, terms and requirements taken from the earlier wording back to Needs review.
Each revision can hold PDF or Word (.docx) files of up to 10 MB. Every file is checked for malware before it is stored, and a file that fails the check is refused. Where the site's malware scanner isn't set up yet, uploads are off and the page says so. Files are downloaded, never opened in the browser, and are not part of the company data download.
Signatures
Record each signature under Signature records on the Revisions tab: who signed, when, how, and which revision. The signed copy can be one of the revision's files, or kept elsewhere. Signature records can't be changed or deleted.
Obligations
The Obligations tab lists what each side must do, with an owner, a due date and whether it applies. An obligation is completed with the evidence that it was done, or cancelled with a reason. Due dates count days in a time zone someone confirmed.
Suggested obligations. When a company turns them on (someone who can edit Org Settings, from the Files card on the Revisions tab), Suggest obligations on a file of a finalized revision has AI read the file and list the obligations it finds, each with the contract's own words. A suggestion is kept only when its words are really in the file. Nothing becomes an obligation until someone adds it with Add suggested obligation. A scanned PDF without a text layer can't be read.
Deadlines and reminders
Contracts → Deadlines lists what is coming due across every contract: obligations and contract end dates, and, for people who can see contract terms, insurance certificate expiry dates and duties that continue after a contract ended. A surviving duty that keeps records for a number of months shows its keep-until date once the contract's end is recorded; RSA never deletes anything when that date passes.
Follow-ups. For people who can see contract terms, Deadlines also lists a Follow-up when a duty check needs attention, or when an event duty is coming due, with the reason and the day it was first flagged. A follow-up goes away on its own once a later check is fine or someone records an exception. Mark handled, with an optional note, clears only the follow-up: the duty, its status and its results don't change.
Someone who can edit Org Settings can turn on reminders there and choose how many days ahead they come (60, 30, 14, 7, 3 or 1 days; 30, 7 and 1 to start). Each morning, the owner of an open obligation gets a notice in the RSA bell when its due date reaches one of those days, and once more when it is overdue. Each reminder is sent once, and a new due date starts over. Reminders stay inside RSA: no email, text or chat, nothing to the other party, and never a legal notice. An obligation without a confirmed time zone, or marked as not applying, gets no reminder but is still listed. An owner who can't see Contracts gets no reminder until their access is back.
Rates and payment terms
The Terms tab records the contract's rate lines (an amount per hour, per day, a fixed fee or other, optionally for one of your services) and its payment terms, such as 30 days from the invoice date. Each comes from a clause of a finalized revision or is entered by hand, and stays Not checked until someone confirms it against the contract.
Conflicts. Fixed rules (no AI) compare a master agreement with its work orders, and confirmed rates with the rates on linked projects. They flag different rates for the same service, payment terms that differ between contracts, and a project that bills a different rate. Each conflict stays open until a person decides: keep one term, or accept the difference with a reason. A conflict whose values changed closes on its own as No longer applies, and Check again runs the rules on request.
Use on linked projects copies a rate line marked Confirmed and Reviewed to every project linked to the contract. It needs Projects edit too, and nothing changes a project, price or invoice until someone presses it.
Checked on sent invoices. Each morning, and with Check now, RSA compares every invoice it sent for the contract with the confirmed and reviewed terms (a work order also uses its master agreement's): the due date against the payment term, and the rate each hour was billed at against the hourly rate for that service. A match shows Supported; a difference shows Needs attention with what RSA saw, for example "due 45 days after Oct 2, 2026; the contract says 30". When it can't be sure, for example an invoice whose project is on two contracts, or a contract with open conflicts, it shows Unknown with the reason. Day, fixed and milestone terms aren't checked automatically. A person can record an exception, with a reason, for a term on one invoice. Results are kept and never rewritten. This card shows only to people who can view invoices.
Requirements and standing duties
The Requirements card on the Terms tab holds what a contract asks of your company: insurance (minimum coverage, the certificate seen and when it expires), approvals, AI use and open-source use (allowed, allowed with notice, needs approval or prohibited), hours limits, budget limits and anything else. Each comes from a clause or is entered by hand, says how often it applies (ongoing, every period, per assignment, when something happens, or once), who owns it, the dates it applies between, and whether it continues after the contract ends.
A requirement stays Not checked until someone records it: Met needs the evidence they saw (insurance also its expiry date), and an Exception needs a reason. Insurance past its expiry shows Expired, one expiring within 30 days says so, and every certificate recorded is kept under Earlier certificates. Anyone who can see contract terms can mark a requirement I've read this; the card lists who has read it, and a change to what it says asks for a fresh read.
Map obligations to duties lists the contract's open obligations that don't have a duty yet, each with a suggested kind: insurance, approvals, AI and open-source use, confidentiality, record keeping and monthly invoicing become standing duties, while notices and end-of-contract steps stay as dated deadlines. Untick or change any of them before pressing Create. Each new duty starts as Not checked and Needs review, and the obligation stays as it was, with a Standing duty tag.
Automatic checks. Once a requirement is marked Applies and Reviewed, RSA checks some kinds each morning and with Check now, using the time logged on the contract's linked projects:
- Hours and budget limits with a period (week, month or whole contract) get a result for each period: Supported when a finished period stayed within the cap, Needs attention as soon as it goes over, and Pending while the period is open, with a heads-up from 80%. View periods shows what RSA counted.
- Monthly invoicing: an Other requirement with its invoice check turned on looks, for each month of billable time, for the invoices that billed it and whether they were created, or sent, within the days the contract allows. A month with no billable time is Not needed. "Sent" means the email went out or someone pressed Mark as sent; RSA can't tell whether the customer received it. An invoice the check can't place has Count for this contract. It checks timing only, not amounts, rates or payment. A duty made with Map obligations to duties keeps this check off until someone turns it on.
- Duties that apply when something happens can name the event that starts them and a due window in hours or days, for example "report an incident within 24 hours of discovering it". Each recorded event of that kind gets its own row: Pending until it is due, Needs attention once the due time passes with nothing recorded or when it was done late, Supported when it was done in time, and Not needed if the event is voided. Record done on a row stores when and how the duty was done; the check then says whether that was in time. View events shows the rows.
- An approval for each assignment (an Approval requirement that applies per assignment) gets a row for each linked project, comparing the recorded Assignment approved event with the first day time was logged on the project: Supported when the approval came first, Needs attention when time was logged before an approval, or with none recorded, and Pending while no time is logged. The requirement keeps its own Met status and evidence as well. View projects shows the rows.
When RSA can't count reliably (no linked projects, a project on another contract, a cap in another currency) it shows Unknown with the reason instead of a number that could be wrong. Results are kept and never rewritten: a later change adds a new result, and a person can record an exception for a period. The Needs attention filter on the card shows what to look at.
Keeping records. A requirement that continues after the contract ends can say how many months records are kept, for example 84 months for seven years. Once someone records the contract's end, the requirement and Deadlines show the keep-until date. It is a reminder only: RSA never deletes anything.
Events
The Events card on the Terms tab is where a person records what actually happened on a contract: an assignment started or was approved (for a linked project), an incident was discovered, the contract's end was confirmed, a renewal or termination was decided, or something else. Each event has when it happened, in your own time zone, a short description and, optionally, what shows it, such as an email or a ticket number. Duties that apply on an event are due from these.
Events are never edited or deleted, and RSA never records one by itself. A wrong event is Voided with a reason and stays on the card, crossed out, with who voided it. Recording and voiding events need Contract terms edit.
Contract terms on invoices
An invoice from a contract shows a Contract terms card next to its lines, for people who can see both contract terms and invoices: the confirmed and reviewed rates and payment terms (a work order also shows its master agreement's), which invoice lines are at each rate, and whether the due date follows the payment terms. It is for reference only and never changes the invoice. While an invoice is a draft, someone who can edit invoices can Confirm terms for this invoice; RSA keeps a copy of those terms and lines as they were, which can't be edited or deleted. A contract with open conflicts must be sorted out first. An invoice with no contract shows no card.
Sharing a contract in the Partner Portal
Once a contract is signed and its signed copy is stored with the signature record, the Partner Portal card on its Overview can share it with the customer or vendor it is with (this needs Contracts edit and Contract files access). The partner then sees it on an Agreements page in the Partner Portal: the number, title, kind, status and dates, with Download signed copy. Nothing else about the contract is shown, and sharing sends nothing. Stop sharing hides it straight away; a cancelled contract drops out on its own.
Partner requests
Customers and vendors can ask for a new contract or work order from the Partner Portal, and customers for a new project, with a title, details, optional dates and budget, and up to three PDF or Word files. Requests are off until someone who can edit Org Settings turns them on with the switch at the top of the Partner requests page, and they work only while the Partner Portal is on. Every file is checked for malware before anything is kept; if one is refused, nothing is sent. A partner can send up to 10 requests a day and have 20 waiting.
Partner requests has its own item in the menu, right under Messages, with a count of the requests waiting for an answer (it shows to people who can see Contracts). It lists what partners sent, waiting ones first, with Waiting, Accepted, Declined, Withdrawn and All filters. Opening a request shows what they asked for, who sent it and their files to download (files need Contract files access). To answer (this needs the rights to add and edit contracts):
- Accept creates a draft contract, a draft work order (under the master agreement the partner named, when it is one with the same partner) or a project (this needs Projects add too). Nothing is signed or sent. If creating it fails, Create it now tries again.
- Decline needs a reason, which the partner sees.
Each request takes one answer, and the partner can withdraw one that is still waiting. Requests and their files are kept, never deleted. Nobody is emailed or notified in the bell; the count next to Partner requests in the menu and the banner on the contracts list are where new requests show.
Activity
The Activity tab shows every change to the contract, its revisions, signature records, obligations and linked projects (and its files, for people who can see contract files), and who made it. The same changes are in the Audit log.