Boilerplate: Difference between revisions
imported>Doug Williamson (Remove surplus text.) |
imported>Doug Williamson (Add link.) |
||
| Line 35: | Line 35: | ||
== See also == | == See also == | ||
* [[Bespoke]] | |||
* [[Contract]] | * [[Contract]] | ||
* [[Documentation]] | * [[Documentation]] | ||
Revision as of 11:44, 7 December 2021
1. Documentation - contract - law.
Standard wording that can be incorporated into a draft contract or other document, designed to reduce the expense and delay of extensive negotiations and of errors.
2. Documentation - contract - law.
Entire standard-worded draft documents produced for similar reasons.
3. Information technology.
Abbreviation for boilerplate code.
A section of code that is repeated without modification - or with only minimal modifications - in different places.
4. Financial reporting - investor relations.
In the context of reporting and communication, "boilerplate" has negative connotations.
Boilerplate comments are standard-worded ones that fail to offer useful insights about the different situations being described.
- Too much boilerplate reporting
- "Unfortunately, as last year, we continue to see the use of boilerplate or declaratory statements.
- These statements are seldom substantiated by actions or examples, and therefore do not offer insight into company governance...
- The vast majority of reporting on outcomes of community engagement remained generic and boilerplate."
- Review of Corporate Governance Reporting - Financial Reporting Council - November 2021, p3 & p30.
