UCMS Contracts
A contract is written in three steps, Contract Details, Service Details and Session Limits, with the Bank of Hours ledger opening off the third. Drawn in the UCMS live-product look.
Screens
In flow order. Screens 02, 03 and 04 are the three steps and carry the same steps strip. Screen 05 sits outside the flow. Every screen links back here.
The entry point only. Create New Contract opens the form below. Drawn as a stub, not as a designed profile screen.
Step 1. Customer Link, Contract Details, Access Number Details, Clinical Billing and the BUR list. The void reason field, the contract duration, the evergreen switch and the line type that swaps the access number controls all work. Add BUR Entry opens a drawer.
Step 2. Linked Packages, Fee Details and Additional Hours Approval, each a list with its own drawer. The package picker, the fee form, the bank-first rule band and the closed-authorization band all work.
Step 3. The session limit type, the case, member and family hours lists with their drawers, the eligibility type classification and the bank of hours summary. Tick a limit type to open its list. All eight eligibility types load classified as demo data, so the save opens released. Clear one to see the rule hold it. Transaction History opens a read-only panel.
Outside the three steps. Reached from Transaction History on step 3, and View All opens it in full. The live balance, the read-only transaction history and the below-zero alert. The four summary values are computed from the transactions below them. Filter the history by type, or enter a projected deduction over 25.5 hours to raise the alert and the CSM or AM flag.
What This Build Covers
User stories 1.1, 1.2, 1.3.2, 1.4 and 1.9 on the New Contract form, 1.3.1, 1.5 and 1.8 on Service Details, 1.6, 1.6.1, 1.6.2 and 1.6.3 on Session Limit Details, and 1.7 across the bank of hours summary and its ledger. That is the field set drawn on all four mockups, plus user story 1.9.
User story 1.9, Access Number Details, is the one story no mockup draws. It is built from its field list alone, in the visual language of the sections around it, and every rule it names is working.
Every repeating record on the three steps is a list with an Add action. The Add action and every row Edit open the same right-side panel, and Save writes the row.
Not built: a contract list, a read view, an edit mode and EAP-to-child inheritance, none of which the requirements describe.
Defaults Drawn Where the Document Is Silent
Each one is a working default for confirmation, not a decision.
| Open point | What is drawn |
|---|---|
| Products and Services on the contract | No selector. Each BUR entry states its scope as read-only text. |
| Moving between the three screens | One steps strip on all three, plus Save and Continue. Every step stays reachable in any order. |
| Contract status while the form is open | Contract in Progress until Save Contract on step 3. The requirements give the eight statuses no lifecycle. |
| Where a repeating entry is written | A right-side panel. The list on the screen is the record, and the panel writes one row at a time. |
| Access Number Details | Stays on the form. It is one set per contract, not a list, so it has no panel. |
| Transaction history on step 3 | A read-only panel carrying the same nine rows and the same filter. View All opens the full ledger. |
| Scope wording | One spelling across the set, "Product - Counselling". A new entry reads "Not set". |
| BUR entries drawn | One, the only entry the mockup fills. A list row with no values in it would state nothing. |
| Clinical billing control type | Three checkboxes, per the mockup. The requirements ask for Yes or No with nothing pre-selected. |
| Sub-annual duration | Whole completed months, end date counted inclusively. Under one month reads "Less than 1 month". |
| Eligibility types | A list box. Nine values are taken from the document and the mockups, twelve are placeholders standing in for the missing list of 21. |
| Evergreen | The switch turns on and off and changes nothing else. Its effect on the end date is unspecified. |
| Void reason | Hidden until the status is Void, then required. Save is held until a reason is chosen. |
| Fee currency | One currency for the whole contract. The only fee entry sets it, every later entry reads it back. |
| Package customer scope | Two customer IDs on one contract, per the mockup. The acceptance criteria allow only one. |
| Session limit types | Three checkboxes, per the mockup, so more than one type may be selected. One user story calls them mutually exclusive. |
| Family hours maximum | The pooled total of the employee and family buckets, per the mockup. The inherited definition reads it per participant. |
| Unselecting a limit type | The section hides and its entries are kept. The requirement reads "hidden/cleared", which are two different behaviours. |
| Eligibility types classified | All eight this contract selects, not the six the mockup draws. The two the mockup never classifies are seeded as demo data. |
| Ledger arithmetic | Nine transactions that sum to the summary. Credits and carryover in, deductions out, and the newest running balance is Hours Remaining. The mockup draws four that do not reconcile with the total it prints. |
| Below-zero deduction | A projected deduction raises the alert and the CSM or AM flag. It is never applied, because the requirement does not say whether the deduction is blocked. |
| Hours carried over | Spendable, and folded into Hours Remaining. One row is seeded at a contract-year rollover. The rule that decides how many hours carry is marked "to be confirmed" in the requirements, so none was written. |
| Access number entry | Line Type picks the control. A generic line picks from a provisioned pool, a dedicated line is typed by hand and flagged for setup. |
| Access number format | A plus sign, a country code of one to three digits, then 10 digits. The fixed 10 digits is a North American rule. |
| Access numbers per contract | One pair, English and French, and neither is required. The requirements state no count and mark neither one mandatory. |
| Linked package name | Drawn as text. The package record it should open is not part of this build. |
Two Calls to Confirm
Both are proposed, pending design-lead confirmation.
The shell is the live UCMS chrome Proposed
The mockups are annotated wireframes in a style that matches neither UCMS nor CDS. This prototype keeps the real UCMS navigation and top bar, with CDS components inside the content area.
Locked fields are shown as values, not as switched-off inputs Proposed
Customer ID, Customer Name, Contract ID and Contract Duration can never be typed into, so they are not drawn as controls at all.