Structure handover documentation

Handover requires that as-built documentation, the O&M manual, warranties and inspection reports are collected and complete. Yesper structures the whole package and flags what is missing against a requirements list. Most relevant at project close-out.

How to do it in Yesper

  1. Add all final documentation.
  2. Ask Yesper to create a combined structure/table of contents.
  3. Let Yesper flag missing parts against a requirements list.
  4. Review in Yesper and download as a handover package if needed.

Settings & tips

  • Start from the contract's requirements for final documentation.
  • Combine with the registers for warranties and action lists.

Example prompts

Simple

Structure our handover documentation.

Advanced

Structure the handover documentation for road 52 (as-built documentation, the O&M manual, warranties, self-inspection records and inspection reports) into a table of contents and list what is missing against the contract requirements.

FAQ

Does Yesper check what is missing?

Yes, against a requirements list.

Can the warranty and action registers be linked in?

Yes, refer to them.

Do I get a complete package?

Yes, as a structured table of contents.