Contract completeness checks
Flowtly checks every contract for the details that make it useful for planning, and labels the ones that are still missing. A contract with an outstanding check stays in the tidy-up list, so the gaps are visible from the list itself rather than only on opening each record.
A label is a prompt, not a block. The contract keeps working — it can still be edited, linked to a budget and invoiced against — while a check is outstanding.
What is checked
A contract can carry any of these labels:
- Missing contract document — no signed file is attached.
- Missing counterparty — the other party is not recorded.
- Missing project — the contract is not linked to a project.
- Missing payment schedule — the contract has no payment schedule lines.
- Missing total amount — no total value is recorded.
- Missing start/end dates — the term is not stated.
A contract with none of them shows No issues.
Declaring that a check does not apply
Some contracts can never satisfy a check, however long they sit in the list. A supplier engaged by click-through acceptance of published terms produces no signed PDF by design; an organisation-wide cost belongs to no single project; work billed on actuals has no instalments to schedule. Left alone, contracts like these stay in the tidy-up list permanently, and a list that always has items in it is a list nobody reads.
Checks that do not apply, in the contract's Details, is where you say so. Three declarations are available:
- This contract will never have a signed document — for click-through acceptance of published terms, a verbal arrangement, or an executed copy that stays in an external signing platform.
- This contract will never belong to a project — for an organisation-wide cost such as a bank data feed, an office sublease or general outsourcing.
- This contract will never have a payment schedule — for time and materials billed on actuals, or a one-off already settled in full.
Once declared, the contract stops being labelled for that check and leaves the tidy-up list on that count. The declaration can be withdrawn again at any time.
"Never" is not "not yet"
Tick a box only when the contract genuinely will never have the thing. If the document is simply not uploaded yet, or the schedule is one you have still to enter, leave the box clear and the contract in the list until it is done. The declarations say something permanent about the agreement; they are not a way to clear a label you would rather deal with later.
Each declaration appears only when the check it answers is currently failing, or when the declaration has already been made — so a contract that already has a project is not offered a box about projects, and a box you have ticked stays on screen to be untickable.
Cyclic contracts
A contract marked cyclic is not checked for a payment schedule at all, so it is never labelled for one. The payment-schedule declaration therefore changes nothing on a cyclic contract, and is not offered unless it was already set.
Example use cases
- A supplier working under published general terms accepted by click-through, where no signed file will ever exist to attach.
- An organisation-wide cost such as a bank data feed or an office sublease, which belongs to no single project.
- Time-and-materials work billed on actuals, where instalments are never scheduled in advance.
- Clearing the tidy-up list down to the contracts that genuinely still need work, so the remaining labels are worth acting on.