UCMS Contracts
The New Contract form, its Service Details screen and the customer profile they open from, drawn in the UCMS live-product look.
Screens
In flow order. 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.
Customer Link, Contract Details, Clinical Billing and BUR entries. The void reason field, the contract duration and the evergreen switch all work.
Linked Packages, Fee Details and Additional Hours Approval. The package picker, the fee entry form and the bank-first rule band all work.
What This Build Covers
User stories 1.1, 1.2, 1.3.2 and 1.4 on the New Contract form, and 1.3.1, 1.5 and 1.8 on Service Details. That is the field set drawn on the New Contract Form and Service Details mockups.
Not built: session limits, the bank of hours and access numbers. Also 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. |
| 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. |
| 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.