Digital logbooks
How to Configure Visitor Forms for Different Buildings
Build per-building visitor forms that stay practical at the desk and remain meaningful in management records.
Per-building forms preserve local operating needs. Typed fields, controlled options, and immutable historical versions make those forms useful beyond the moment of entry.
Editorial notice
General information only—not legal, security, procurement, or professional advice. Details can change; verify current requirements with primary sources, vendors, and qualified advisers.
Read our editorial policyKey takeaways
- Buildings can share a platform without sharing one identical visitor form.
- Field types and list options should remain stable after records use them.
- Test forms with real shifts before publishing them broadly.
01
Why one form rarely fits every building
A residential tower may care about destination unit and delivery type. A management office may need company and meeting purpose. A mixed-use building may require a small number of additional categorical questions.
The platform should provide a common operating model while allowing each building to collect the fields approved for its process.
02
Choose a field type that matches the answer
Use controlled options when management will need consistent filters. Avoid turning every answer into free text and expecting reliable portfolio analysis later.
- Short text for concise answers that are not intended as filters
- Long text for exceptional notes, used sparingly
- Number and date for properly typed responses
- Yes/no for a clear binary condition
- Single select for a controlled list of operational categories
03
Protect historical meaning
If an old record says the answer to a field was Contractor, management must still know what that field meant at the time. Repute publishes immutable form versions and prevents incompatible edits to used custom fields.
An unused field can be removed from a later version. A used field can be hidden or made optional, but its identifier, name, type, and list options stay stable.
See the workflow
