A no-force policy is used in transaction control in database theory.
The term no-force refers to the disk pages related to the actual database object being modified.
With a no-force policy, when a transaction commits, the changes made to the actual objects are not "forced", that is, required to be written to disk in-place.
[1] A record of the changes must still be preserved at commit time to ensure that the transaction is durable.
A no-force policy also reduces the seek time required for a commit by having mostly sequential write operations to the transaction log, rather than requiring the disk to seek to many distinct database objects during a commit.