Drawing registers
Track drawing identity, discipline, revision, status, issue purpose, and the current accepted version.
02 / Capabilities · 06
Document & information control.
Keep current drawings, technical questions, approvals, evidence, and project records connected to the people and work they concern.
Information route
Information Route
One controlled route from receipt to retained record.
Each stage adds context without erasing what came before. The process stays useful because versions, responsibilities, decisions, and visibility remain connected.
-
01
Receive
Capture the file, question, evidence, or submission with its source and project context.
-
02
Classify
Connect the record to its type, discipline, WBS scope, responsible party, and visibility.
-
03
Review
Route current information to the people appointed to check, comment, or request revision.
-
04
Authorize
Record the decision made by the responsible party without transferring their authority to the system.
Decision by the appointed authority -
05
Issue
Make the accepted version visible to the participants and work scopes permitted to use it.
-
06
Retain
Preserve versions, decisions, evidence, and superseded records as traceable project history.
Superseded versions remain traceable
Professional service
Professional Service
Control the information that directs the work.
Technical submissions
Coordinate transmittals, review routes, responses, revisions, and supporting product or engineering information.
RFIs & decisions
Keep each question connected to its location, WBS context, responsible participant, response, and resulting action.
Inspections & approvals
Organize requests, evidence, findings, responsible reviews, follow-up, and final recorded status.
Progress evidence
Relate reported progress to dated evidence and the review that allows it to become official project information.
Handover records
Assemble approved drawings, reports, evidence, decisions, and close-out information into a usable final record.
Tomy Engineering establishes and operates the agreed information-control process within the scope of its appointment.
Design responsibility, contractual authority, statutory review, professional certification, safety duties, and final approvals remain with the responsible appointed parties.
Tenage Apps preview
Connected Project Records
The service defines the process. The platform keeps its record connected.
Tenage Apps is Tomy Engineering's construction-management PWA in development for customers, project Partners, and authorized Tomy Engineering teams. Access follows project membership, platform role, and WBS or work scope.
Customer and Partner views are experiences—not automatic authority. The backend remains responsible for enforcing every permitted action and information boundary.
PROJECT / WBS 03.02
Current informationWBS
Progress and work context
Documents
Current files and versions
Evidence
Authorized project proof
Questions
Work-specific RFIs
Inspections
Requests and findings
Approvals
Responsible decisions
Reports
Controlled project views
Activity
Traceable record history
File traceability
File Traceability
A file is more useful when its context travels with it.
File bytes belong in approved object storage while the project record retains the metadata and relationships needed to identify, verify, and authorize their use.
- 01
Context
Project · WBS branch · record type
- 02
Source
Uploader · original name · file type
- 03
Integrity
Version · size · checksum
- 04
Visibility
Role and work-scope permission
- 05
External file
Selected Drive source · modified time
- 06
Safety state
Snapshot version · checksum · status
External Google Drive support is limited to selected project files or folders. Snapshot availability depends on source access and copy permission; unavailable backups must be shown honestly rather than marked safe.
Plans & pricing
Plans & Pricing
Choose the information boundary that matches the organization.
Pricing, currencies, usage limits, and commercial terms are still being defined. The comparison below presents the approved licensing direction without implying that checkout is available.
Current direction
Project License
Pricing coming soonA license held by the organization administering one project, whether that organization is an Owner, Main Contractor, Consultant, or another approved participant.
- One project and one License Holder organization
- Authorized project participants
- Role- and work-scope visibility
- Connected project workflows
- Traceable project records
Future direction
Company Plan
Pricing coming soonA planned organization-level option that can group multiple projects without changing the roles or permissions held inside each project.
- Multiple projects grouped under one organization
- Centralized employees and reusable templates
- Organization-level permissions and reporting
- Portfolio views across permitted projects
- Coordinated storage-policy administration
Billing remains independent from construction role. Holding a license does not automatically grant unrestricted project access, approval authority, or visibility into another participant’s work.
Project information
Project Information
Define the rules before asking the record to enforce them.
Information required
- Project organization, participants, roles, responsibilities, and approved communication routes
- WBS or work-package structure and the scope visible to each participant
- Document types, numbering rules, disciplines, revision conventions, and status definitions
- Reviewers, approval authorities, response periods, hold points, and issue purposes
- Existing drawings, specifications, submissions, registers, RFIs, inspection records, and evidence
- Handover requirements, retention expectations, and approved external-file arrangements
Expected records
- Current drawing, document, and submission registers
- Version, revision, issue, review, and response history
- RFI, inspection, approval, and decision records
- Progress evidence linked to the relevant work scope
- Authorized customer and partner information views
- Close-out, as-built, reporting, and handover information
Related capabilities
Related Capabilities
Keep technical delivery connected to its current record.
01
Engineering & shop drawings
Develop and coordinate clear technical drawings for review, fabrication, and construction use.
02BOQ & quantity takeoff
Prepare measured quantities and structured bills of quantities as professional project outputs.
03BIM & digital engineering
Use coordinated models and structured information to improve technical clarity across disciplines.
04Construction management
Connect scope, participants, progress, evidence, and decisions through a disciplined delivery process.
05Project coordination
Keep responsibilities, constructability questions, and technical decisions connected to the work.
Start a conversation
Start a Conversation
Need a clearer route from project file to authorized record?