Documents

Manage reusable business documents, bid attachments, project evidence, and invoice support files.

Ready
Documents
Open invoice

Permissioned document record

Pre-work Site Photos

Baseline photos for Santa Cruz Market roof and drainage areas before mobilization.


Sections

OverviewFile packetLinked useReuse rulesReview pathPreviewEvidence purposeFacts

Document dossier

Confirm the file, linked use, review state, and visibility boundary before this record is reused.

Baseline photos for Santa Cruz Market roof and drainage areas before mobilization.

Ready
Type

Project evidence

Linked use

Milestone 1

Requirement

Evidence

Review state

Ready for invoice packet

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.

FieldWhat it confirmsVisible signal
Document typeWhat kind of record is being reused or reviewed.Project evidence
Linked useWhere this file travels across bids, projects, invoices, diligence, or profile checks.Milestone 1
RequirementWhether the file is required, recommended, reusable, or workflow-specific.Evidence
Current fileThe visible uploaded/replacement state for the participant.Current file state visible in Register
No replacement selected

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.

1

Milestone 1

2

Evidence

3

Role-safe reuse

4

Evidence basis preserved

5

Visibility boundary checked

6

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.

1

Reuse accepted files instead of creating duplicate records.

2

Keep project evidence linked to the project or milestone it proves.

3

Keep investor and diligence files permissioned and audited.

4

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.

1

Document identified

Complete

Project evidence is linked to Milestone 1.

2

Requirement checked

Recommended

Evidence

3

File reviewed

Visible

Ready for invoice packet

4

Reuse controlled

Guarded

Permissioned document record; reuse follows the current user's relationship to the linked record

Ready

Pre-work Site Photos


Permissioned preview

Milestone 1

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.

Evidence basis

Source-backed

Linked evidence

3 approved source references

Visibility

Permissioned document record; reuse follows the current user's relationship to the linked record

Human boundary

Document review supports decisions; it does not govern them.

Evidence purpose

The photo set gives the invoice reviewer a baseline before mobilization and protects the project record from unsupported progress claims.

Roof baseline
Drainage baseline
Market access condition
Safety zone notes
Invoice evidence packet
Evidence type

Pre-work site photos

Project

Santa Cruz Market Repairs

Milestone

Milestone 1 mobilization and early works

Status

Ready for invoice packet

Captured areas

Roof condition, drainage points, market access, and safe work zones

Next action

Attach to milestone invoice with inspection note