How to use Projects
Use Projects when material selections, saved tool outputs and review decisions need to remain attached to a named architectural project rather than being stored as unrelated files.
The public Croft Manor demo shows the workflow without allowing edits. Creating projects, boards and private review links requires a verified account with an active Pro subscription.
- Create a project with a clear name and identify its client and contractor, then add a board for each room, zone, package or decision that needs a focused review.
- Organize the board into zones and add library textures, uploaded images, notes, specification clauses or saved tool outputs. Give every item enough product and location information to be understood outside the editing screen.
- Review the complete board revision before copying the client, technical or contractor review link. Each link presents a focused, read-only view without requiring the reviewer to create an account.
- Record client approval and technical sign-off separately. If the board changes, the new revision requires a fresh review while the earlier sign-off remains attached to the revision that was actually reviewed.
- Use the contractor view to receive a substitution against a specific board item, compare the proposed and original information, then approve or reject the request explicitly.
- Launch BIM Material Exchange from the Project tools panel when the current board materials should seed an interoperability register for further checking and IFC export.
Client and technical review
Client approval and technical sign-off answer different questions. A client can approve the selections shown, while a technical reviewer records a professional review within their stated role. Both records belong to the exact board revision reviewed; a later edit creates a new revision that requires any necessary review to be renewed.
Contractor substitutions and revisions
A contractor link lets the recipient propose an alternative against a specific board item. Keeping the original snapshot beside the proposal makes the comparison traceable, but the project team must still assess performance, certification, specification, cost and programme consequences before approving or rejecting it.
Worked examples
These examples show how the project record supports a defined decision without replacing the wider coordination process.
Client finish approval
- Set-up
- Create a ground-floor finishes board, divide it into entrance, kitchen and living zones, and add the current flooring, wall finish and joinery selections with concise notes.
- Result
- The client receives one focused link and the resulting approval is recorded against the exact board revision they reviewed.
- Review
- Check product identity, intended location, availability and any approval conditions before treating the recorded decision as current.
Contractor substitution review
- Set-up
- Issue the contractor link for an approved board and ask the contractor to propose an alternative against the affected item, including the product reference, reason, image and supporting note.
- Result
- The original selection and proposed replacement remain connected so the architect can record an explicit approval or rejection.
- Review
- Compare appearance, dimensions, performance, certification, specification, cost and programme implications through the appropriate project process before deciding.
Suggested workflow
Use the project board as a controlled review surface linked to the wider project information process.
- Create boards around decisions that a reviewer can understand, rather than using one unstructured board for the entire project.
- Attach source-backed selections and saved tool outputs, review the assembled revision, then issue the relevant private link.
- Keep client preference, professional technical review and contractor substitution decisions as separate records with their own scope.
- When information changes, issue the updated board revision and obtain any review that the change makes necessary.
Check before saving or issuing
- Every board item identifies the product, material, location or decision clearly enough for its intended reviewer.
- Client, technical and contractor links are sent only to the people responsible for that type of review.
- The current board revision and any earlier sign-off status are understood before information is issued or relied upon.
- Accepted substitutions and linked tool outputs have been coordinated with the relevant drawings, schedules and specification.
Common problems
- A reviewer sees outdated information: confirm the board revision and issue the current review link after completing the edits.
- A saved output is missing from a board: open the project’s unplaced outputs and add the relevant record to the intended board.
- Project editing is unavailable: creating and editing project boards requires a verified account with an active Pro subscription; the public demo remains read-only.
Output
Projects produces revisioned material boards, focused review links and records of client approval, technical sign-off and contractor substitution decisions. Saved tool outputs can remain attached to the project or be placed on a board for review.
Professional boundary
Projects supports coordination and traceability, but it is not a common data environment, contract administration platform, project-management system or proof of statutory compliance. Confirm each decision through the appointments, specifications, approvals and quality processes that apply to the project.