Documents
Manage reusable business documents, bid attachments, project evidence, and invoice support files.
Permissioned document record
Technical Method Statement
Method statement for roof works, drainage sequencing, safety zones, and inspection handoff in the Santa Cruz Market bid.
Document dossier
Confirm the file, linked use, review state, and visibility boundary before this record is reused.
Method statement for roof works, drainage sequencing, safety zones, and inspection handoff in the Santa Cruz Market bid.
Technical method statement
Reusable Register record
Requirement depends on the linked workflow
Attached to submitted package
File packet
The document packet keeps the user-facing file state close to the workflow it supports. Replacing a file updates the record for review; it does not approve, award, publish, or release payment.
| Field | What it confirms | Visible signal |
|---|---|---|
| Document type | What kind of record is being reused or reviewed. | Technical method statement |
| Linked use | Where this file travels across bids, projects, invoices, diligence, or profile checks. | Reusable Register record |
| Requirement | Whether the file is required, recommended, reusable, or workflow-specific. | Requirement depends on the linked workflow |
| Current file | The visible uploaded/replacement state for the participant. | Submitted |
Linked use
This document remains attached to the bid, project, invoice, diligence room, profile, or opportunity that needs it. It should be reused only where the participant has a relationship to the linked record.
Reusable Register record
Requirement depends on the linked workflow
Role-safe reuse
Evidence basis preserved
Visibility boundary checked
Replacement requires review
Reuse and replacement rules
Business documents, supplier records, investor documents, bid attachments, and project evidence can be reused across Register only when the source, owner, visibility, and linked object still match the workflow.
Reuse accepted files instead of creating duplicate records.
Keep project evidence linked to the project or milestone it proves.
Keep investor and diligence files permissioned and audited.
Replacing a file starts review; it does not change governed outcomes.
Review path
The document path makes the current participant-facing state visible while keeping approvals, awards, restricted diligence access, and payment release under human-governed workflows.
Document identified
Technical method statement is linked to Reusable Register record.
Requirement checked
Requirement depends on the linked workflow
File reviewed
Attached to submitted package
Reuse controlled
Permissioned document record; reuse follows the current user's relationship to the linked record
Technical Method Statement
Permissioned preview
Reusable Register record
Preview and source handling
The preview shell is ready for the real signed file URL. Register shows only the file state, linked use, and source-safe context that this role is allowed to see.
Source-backed
3 approved source references
Permissioned document record; reuse follows the current user's relationship to the linked record
Document review supports decisions; it does not govern them.
Method coverage
The document explains how BlueCrest plans to sequence the market works while protecting access, drainage, and evidence collection.
Technical method statement
Santa Cruz Market submitted bid
Santa Cruz Market Repairs
Attached to submitted package
Roof works, drainage sequencing, safety zones, and inspection handoff
Retain for review outcome or amendment request