Why will a check not close?
Because a required step is still missing its evidence — and nobody can override that.
When you try to close a check that still has a required step without evidence, it is refused, and the refusal names how many steps are outstanding.
What matters is that the refusal is not the button being greyed out. The same answer comes back through the API, through an import, and to an administrator. There is no setting that turns the rule off.
That is the whole reason the record is worth anything a year later. A closed check is a closed check because it could not have been closed any other way.
On a tablet, the refusal is a plain line under the button naming which steps are still open — not a spinner, not a vague error. A technician who thought the anchor-torque reading had been recorded finds out immediately that it never saved, rather than three weeks later when the closeout package is being assembled and nobody remembers why a chiller never made it into the ready column.
The same logic runs when a batch of checks is closed at once. A bulk action against fifty checks stops at the ones that are not actually ready and reports which, rather than closing the ninety percent that qualify and silently skipping the rest. There is no 'close anyway' button anywhere in the product, for anyone, on any device.
- A step is missing its evidence
- Capture what it asks for. The refusal tells you how many are left.
- Every step is done but it still refuses
- Some checks need independent acceptance — somebody who did not perform the work has to accept it first.
- You are an administrator and it still refuses
- That is the design, and it holds for everyone, including an administrator.
- You want the reason without reading the steps
- Open the check and ask the box "why can't I close this?" The answer comes from the record — which step, what it still needs, who has to accept it — with the check's own history under it. Nothing is guessed.